View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0011714 | GNUnet | ARM service | public | 2026-08-06 10:52 | 2026-08-08 10:25 |
| Reporter | Jllx | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | Git master | ||||
| Target Version | 0.29.0 | ||||
| Summary | 0011714: gnunet-arm -I never returns if no service are running | ||||
| Description | when trying to know if the services are running I do a "gnunet-arm -I" which never returns if there is no service running (have to kill the process) | ||||
| Steps To Reproduce | with no service running : gnunet-arm -I if service is running (previous step did reply): gnunet-arm -e && gnunet-arm -I | ||||
| Tags | No tags attached. | ||||
| related to | 0011712 | new | gnunet-identity never return and endless loop |
|
|
This is also true for gnunet-arm -e, btw. Not sure if that can be fixed. We could timeout I guess. |
|
|
Maybe to clarify: All CLI tools that interact with gnunet services do not "hang". They wait for the service to come online (again) to talk to them. You can ctrl-c out of this. So this issue only has 2 solutions: 1. Close as wontfix 2. Think about adding a (delayed) info message to affected CLI utilities (quite a few of those) that tell the user that gnunet may not be running. |
|
|
well, I would largely prefer to have a -m option (--monitor) or +F like less if I want to monitor (eg wait for the service to come alive) and have some monitoring most of the time I just want current status (this can also be used by a service script to have current status) if there is "Connection refused" error, then there no listening processes and anyway, this is not consistent : the service won't return any status waiting for connection, but will not monitor after and just return one state... plus, this is confusing, it hang, why? because it's bugged? because something is wrong? this can be used to implement a RC script --status default option |
|
|
or a -w option (--wait) if we want to start the service and wait... |
|
|
My assumption is that if you start gnunet with gnunet-arm -s in another terminal while gnunet-arm -I "hangs" it will then return the service info. If not, then yes this is a bug. |
|
|
yes, but I find it ackward.... no "status" tool does wait : it brings doubt! does it hanged because of a bug? is the system partially runing? shall I have to start? do I run with the wrong user? currently what a user have to do is gnunet-arm -I ^C ps -A | grep gnunet and i require user intervention : you can´t do /etc/init.d/gnunet status and have it return status |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2026-08-06 10:52 | Jllx | New Issue | |
| 2026-08-06 11:11 | schanzen | Note Added: 0029382 | |
| 2026-08-07 10:15 | schanzen | Note Added: 0029402 | |
| 2026-08-07 20:51 | Jllx | Note Added: 0029406 | |
| 2026-08-07 22:30 | Jllx | Note Added: 0029407 | |
| 2026-08-08 08:29 | schanzen | Relationship added | related to 0011712 |
| 2026-08-08 08:31 | schanzen | Note Added: 0029413 | |
| 2026-08-08 08:31 | schanzen | Target Version | => 0.29.0 |
| 2026-08-08 10:25 | Jllx | Note Added: 0029414 |
