Re: gnunet-core --connection-status output nothing

We had a couple of regressions. Please try git head. The situation 
should be improved. *fingers crossed*


BR

On 7/27/26 05:11, Liberal Consulting wrote:
> I have installed gnunet 0.28 following
> https://docs.gnunet.org/latest/installing.html
>
> from git.
>
> ```
> sudo -u gnunet gnunet-arm -I
> Services (excluding stopped services):
> (started: 20 / stopped: 14)
> cadet (binary='gnunet-service-cadet', status=started)
> core (binary='gnunet-service-core', status=started)
> datastore (binary='gnunet-service-datastore', status=started)
> dht (binary='gnunet-service-dht', status=started)
> gns (binary='gnunet-service-gns', status=started)
> hostlist (binary='gnunet-daemon-hostlist', status=started)
> namecache (binary='gnunet-service-namecache', status=started)
> nat (binary='gnunet-service-nat', status=started)
> nse (binary='gnunet-service-nse', status=started)
> peerstore (binary='gnunet-service-peerstore', status=started)
> pils (binary='gnunet-service-pils', status=started)
> rest (binary='gnunet-rest-server', status=started)
> revocation (binary='gnunet-service-revocation', status=started)
> rps (binary='gnunet-service-rps', status=started)
> setu (binary='gnunet-service-setu', status=started)
> statistics (binary='gnunet-service-statistics', status=started)
> topology (binary='gnunet-daemon-topology', status=started)
> transport (binary='gnunet-service-transport', status=started)
> communicator-tcp (binary='gnunet-communicator-tcp', status=started)
> communicator-udp (binary='gnunet-communicator-udp', status=started)
> ```
>
> ```
> gnunet-arm -I
> Services (excluding stopped services):
> (started: 3 / stopped: 6)
> fs (binary='gnunet-service-fs', status=started)
> namestore (binary='gnunet-service-namestore', status=started)
> zonemaster (binary='gnunet-service-zonemaster', status=started)
> ```
>
> But 'gnunet-core --connection-status' just returns silently. I should
> have at least 1 connection, right? How to debug this problem?
>