Hi,
I have uninstalled and reinstalled gnunet using the installation guide
mentioned above https://gnunet.org/en/install.html
I followed all the steps to completion.but I am still not able to run the
services and logfile shows the same error messages.
<snip>
$ gnunet-arm -I
Services (excluding stopped services):
(started: 5 / failed: 6 / stopped: 31)
gns (binary='gnunet-service-gns', status=failed, exit_status=255,
restart_delay='183 ms')
zonemaster (binary='gnunet-service-zonemaster', status=started)
zonemaster-monitor (binary='gnunet-service-zonemaster-monitor',
status=started)
nse (binary='gnunet-service-nse', status=failed, exit_status=255,
restart_delay='218 ms')
fs (binary='gnunet-service-fs', status=failed, exit_status=255,
restart_delay='223 ms')
cadet (binary='gnunet-service-cadet', status=failed, exit_status=255,
restart_delay='225 ms')
revocation (binary='gnunet-service-revocation', status=failed,
exit_status=255, restart_delay='206 ms')
topology (binary='gnunet-daemon-topology', status=started)
dht (binary='gnunet-service-dht', status=failed, exit_status=255,
restart_delay='184 ms')
hostlist (binary='gnunet-daemon-hostlist', status=started)
namestore (binary='gnunet-service-namestore', status=started)
<snip>
<snip>
1 Feb 03 19:47:57-490752 arm-8968 ERROR `mkdir' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-dns.sock' at
gnunet-service-arm.c:467 with error: Permission denied
2 Feb 03 19:47:57-491004 arm-8968 WARNING Unable to bind listening socket
for service `dns' to address
`/tmp/gnunet-system-runtime//gnunet-service-dns.sock': Address already in
use
3 Feb 03 19:47:57-491240 arm-8968 ERROR `mkdir' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-peerstore.sock' at
gnunet-service-arm.c:467 with error: Permission denied
4 Feb 03 19:47:57-491289 arm-8968 WARNING Unable to bind listening socket
for service `peerstore' to address
`/tmp/gnunet-system-runtime//gnunet-service-peerstore.sock': Permission
denied
5 Feb 03 19:47:57-491340 arm-8968 ERROR `mkdir' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-set.sock' at
gnunet-service-arm.c:467 with error: Permission denied
6 Feb 03 19:47:57-491382 arm-8968 WARNING Unable to bind listening socket
for service `set' to address
`/tmp/gnunet-system-runtime//gnunet-service-set.sock': Address already in
use
7 Feb 03 19:47:57-491472 arm-8968 WARNING `unlink' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-transport.sock' at
network.c:238 with error: Permission denied
8 Feb 03 19:47:57-491502 arm-8968 WARNING `unlink' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-transport.sock' at
network.c:238 with error: Permission denied
9 Feb 03 19:47:57-491522 arm-8968 WARNING Unable to bind listening socket
for service `transport' to address
`/tmp/gnunet-system-runtime//gnunet-service-transport.sock': Address alr
eady in use
10 Feb 03 19:47:57-491600 arm-8968 WARNING `unlink' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-regex.sock' at network.c:238
with error: Permission denied
11 Feb 03 19:47:57-491620 arm-8968 WARNING `unlink' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-regex.sock' at network.c:238
with error: Permission denied
12 Feb 03 19:47:57-491632 arm-8968 WARNING Unable to bind listening socket
for service `regex' to address
`/tmp/gnunet-system-runtime//gnunet-service-regex.sock': Address already in
use
13 Feb 03 19:47:57-491665 arm-8968 ERROR `mkdir' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-nat.sock' at
gnunet-service-arm.c:467 with error: Permission denied
14 Feb 03 19:47:57-491703 arm-8968 WARNING Unable to bind listening socket
for service `nat' to address
`/tmp/gnunet-system-runtime//gnunet-service-nat.sock': Permission denied
15 Feb 03 19:47:57-491762 arm-8968 ERROR `mkdir' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-dht.sock' at
gnunet-service-arm.c:467 with error: Permission denied
16 Feb 03 19:47:57-491799 arm-8968 WARNING Unable to bind listening socket
for service `dht' to address
`/tmp/gnunet-system-runtime//gnunet-service-dht.sock': Address already in
use
17 Feb 03 19:47:57-491858 arm-8968 WARNING `unlink' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-conversation.sock' at
network.c:238 with error: Permission denied
18 Feb 03 19:47:57-491877 arm-8968 WARNING `unlink' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-conversation.sock' at
network.c:238 with error: Permission denied
19 Feb 03 19:47:57-491889 arm-8968 WARNING Unable to bind listening socket
for service `conversation' to address
`/tmp/gnunet-system-runtime//gnunet-service-conversation.sock': Addre ss
already in use
20 Feb 03 19:47:57-491948 arm-8968 WARNING `unlink' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-namecache.sock' at
network.c:238 with error: Permission denied
21 Feb 03 19:47:57-491967 arm-8968 WARNING `unlink' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-namecache.sock' at
network.c:238 with error: Permission denied
22 Feb 03 19:47:57-491978 arm-8968 WARNING Unable to bind listening socket
for service `namecache' to address
`/tmp/gnunet-system-runtime//gnunet-service-namecache.sock': Address alr
eady in use
23 Feb 03 19:47:57-492046 arm-8968 WARNING `unlink' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' at
network.c:238 with error: Permission denied
24 Feb 03 19:47:57-492064 arm-8968 WARNING `unlink' failed on file
`/tmp/gnunet-system-runtime//gnunet-service-statistics.sock' at
network.c:238 with error: Permission denied
25 Feb 03 19:47:57-492085 arm-8968 WARNING Unable to bind listening socket
for service `statistics' to address
`/tmp/gnunet-system-runtime//gnunet-service-statistics.sock': Address a
lready in use
<snip>
Thanks,
Vikas
On Mon, Feb 3, 2020 at 5:20 PM Schanzenbach, Martin <[email protected]>
wrote:
> Hi,
>
> 0. make sure you kill all processes of gnunet.
> 1. Then run ./configure again (so that you get the text at the end). Do
> what is written there.
> 2. Run make and make install again.
> 3. Try running it again.
>
>
> Alternatively, maybe check of of the installation guides here:
> https://gnunet.org/en/install.html
> They include the steps you have to take.
>
> BR
> Martin
>
> > On 3. Feb 2020, at 16:57, Vikas Maurya <[email protected]> wrote:
> >
> > Hi,
> > I used the following installation guide (compiled and installed using
> source code)
> >
> https://docs.gnunet.org/tutorial/gnunet-tutorial.html/Installation.html#Installation
> >
> > but I am not sure if I followed the ./configure steps
> >
> > what can I do now to correct it?
> >
> > I tried running after killing all gnunet process, But wasn't able to run
> all services and got same error messages in log file.
> >
> > Thanks,
> > Vikas
> >
> > On Mon, Feb 3, 2020 at 4:34 PM Schanzenbach, Martin <
> [email protected]> wrote:
> > Hi,
> >
> > did you follow one of the installation guides?
> > As what user are you trying to start GNUnet?
> > Did you follow the instructions printed after you did './configure'?
> >
> > My guess the issue is with one of the above.
> > Also check if any gnunet processes are currently running and kill them
> before you try again.
> >
> > BR
> > Martin
> >
> > > On 3. Feb 2020, at 16:11, Vikas Maurya <[email protected]>
> wrote:
> > >
> > >
> > >
> > > ---------- Forwarded message ---------
> > > From: Vikas Maurya <[email protected]>
> > > Date: Mon, Feb 3, 2020 at 4:09 PM
> > > Subject: Re: no peer visible
> > > To: Schanzenbach, Martin <[email protected]>
> > >
> > >
> > > Hi,
> > > This is common sequence of errors in the log file. I have also
> attached log file for your reference. one more thing to mention when I run
> sudo ss -ntlp, I see that gnunet-service is already listening on port 2086,
> even before running gnunet-arm -s . Is this a common behaviour? because one
> of the error in log file says port already in used
> > > $ sudo ss -ntlp
> > > State Recv-Q Send-Q Local
> Address:Port Peer Address:Port
>
> > > LISTEN 0 5
> 0.0.0.0:2086 0.0.0.0:*
> users:(("gnunet-service-",pid=2144,fd=12))
> > > LISTEN 0 80
> 127.0.0.1:3306 0.0.0.0:*
> users:(("mysqld",pid=1783,fd=21))
> > > LISTEN 0 128
> 127.0.0.53%lo:53 0.0.0.0:*
> users:(("systemd-resolve",pid=891,fd=13))
> > > LISTEN 0 5
> 127.0.0.1:631 0.0.0.0:*
> users:(("cupsd",pid=12959,fd=7))
> > > LISTEN 0 5
> [::]:2086 [::]:*
> users:(("gnunet-service-",pid=2144,fd=11))
> > > LISTEN 0 5
> [::1]:631 [::]:*
> users:(("cupsd",pid=12959,fd=6))
> > > logfile output.
> > >
> > > <snip>
> > > 60 Feb 03 16:00:25-207988 revocation-22631 ERROR `mkdir' failed on
> file `/tmp/gnunet-system-runtime//gnunet-service-revocation.sock' at
> service.c:1140 with error: Permission denied
> > > 61 Feb 03 16:00:25-208096 nse-22642 ERROR Could not bind to any of
> the ports I was supposed to, refusing to run!
> > > 62 Feb 03 16:00:25-208239 util-service-22631 ERROR `bind' failed at
> service.c:1405 with error: Permission denied
> > > 63 Feb 03 16:00:25-208281 revocation-22631 ERROR `bind' failed at
> service.c:1558 with error: Success
> > > 64 Feb 03 16:00:25-208304 revocation-22631 ERROR Could not bind to
> any of the ports I was supposed to, refusing to run!
> > > 65 Feb 03 16:00:25-208924 arm-22628 WARNING Service `nse' terminated
> with status exit/255, will restart in 4 ms
> > > 66 Feb 03 16:00:25-209153 arm-22628 WARNING Service `revocation'
> terminated with status exit/255, will restart in 1 ms
> > > 67 Feb 03 16:00:25-215409 gns-22632 ERROR `mkdir' failed on file
> `/tmp/gnunet-system-runtime//gnunet-service-gns.sock' at service.c:1140
> with error: Permission denied
> > > 68 Feb 03 16:00:25-215592 util-service-22632 ERROR `bind' failed at
> service.c:1405 with error: Permission denied
> > > 69 Feb 03 16:00:25-215627 gns-22632 ERROR `bind' failed at
> service.c:1558 with error: Success
> > > 70 Feb 03 16:00:25-215648 gns-22632 ERROR Could not bind to any of
> the ports I was supposed to, refusing to run!
> > > 71 Feb 03 16:00:25-216175 revocation-22643 ERROR `mkdir' failed on
> file `/tmp/gnunet-system-runtime//gnunet-service-revocation.sock' at
> service.c:1140 with error: Permission denied
> > > 72 Feb 03 16:00:25-216303 util-service-22643 ERROR `bind' failed at
> service.c:1405 with error: Permission denied
> > > 73 Feb 03 16:00:25-216337 revocation-22643 ERROR `bind' failed at
> service.c:1558 with error: Success
> > > 74 Feb 03 16:00:25-216358 revocation-22643 ERROR Could not bind to
> any of the ports I was supposed to, refusing to run!
> > > 75 Feb 03 16:00:25-216345 arm-22628 WARNING Service `gns' terminated
> with status exit/255, will restart in 1 ms
> > > 76 Feb 03 16:00:25-216747 arm-22628 WARNING Service `revocation'
> terminated with status exit/255, will restart in 2 ms
> > > 77 Feb 03 16:00:25-219790 nse-22644 ERROR `mkdir' failed on file
> `/tmp/gnunet-system-runtime//gnunet-service-nse.sock' at service.c:1140
> with error: Permission denied
> > > 78 Feb 03 16:00:25-219925 util-service-22644 ERROR `bind' failed at
> service.c:1405 with error: Permission denied
> > > 79 Feb 03 16:00:25-219951 nse-22644 ERROR `bind' failed at
> service.c:1558 with error: Success
> > > 80 Feb 03 16:00:25-219977 nse-22644 ERROR Could not bind to any of
> the ports I was supposed to, refusing to run!
> > > 81 Feb 03 16:00:25-220458 arm-22628 WARNING Service `nse' terminated
> with status exit/255, will restart in 8 ms
> > > 82 Feb 03 16:00:25-222676 gns-22645 ERROR `mkdir' failed on file
> `/tmp/gnunet-system-runtime//gnunet-service-gns.sock' at service.c:1140
> with error: Permission denied
> > > 83 Feb 03 16:00:25-222770 util-service-22645 ERROR `bind' failed at
> service.c:1405 with error: Permission denied
> > > 84 Feb 03 16:00:25-222786 gns-22645 ERROR `bind' failed at
> service.c:1558 with error: Success
> > > 85 Feb 03 16:00:25-222795 gns-22645 ERROR Could not bind to any of
> the ports I was supposed to, refusing to run!
> > > 86 Feb 03 16:00:25-222919 revocation-22646 ERROR `mkdir' failed on
> file `/tmp/gnunet-system-runtime//gnunet-service-revocation.sock' at
> service.c:1140 with error: Permission denied
> > > 87 Feb 03 16:00:25-223009 util-service-22646 ERROR `bind' failed at
> service.c:1405 with error: Permission denied
> > > 88 Feb 03 16:00:25-223025 revocation-22646 ERROR `bind' failed at
> service.c:1558 with error: Success
> > >
> > > <snip>
> > >
> > > On Sun, Feb 2, 2020 at 10:55 PM Schanzenbach, Martin <
> [email protected]> wrote:
> > > Hi,
> > >
> > > it seems like your services fail to start. Can you post the output of
> your logfile(s)?
> > > (~/.cache/gnunet/)
> > >
> > > You may also open a bugreport on mantis if you want to attach files.
> > > Or you just copy relevant parts here.
> > >
> > > BR
> > > Martin
> > >
> > > > On 1. Feb 2020, at 21:37, Vikas Maurya <[email protected]>
> wrote:
> > > >
> > > > Hi,
> > > > I have recently installed gnunet(trying for the first time) and was
> trying single-user setup.
> > > > but after installation when I run gnunet-arm -s and gnunet-arm -I ,
> I see that most of the services are being stopped and when I run
> gnunet-peerinfo -s, I do not see any output. also gnunet-peerinfo-gtk does
> not display any information.
> > > >
> > > >
> > > > <snip>
> > > > $gnunet-arm -s
> > > > $gnunet-arm -I
> > > > Services (excluding stopped services):
> > > > (started: 4 / failed: 6 / stopped: 30)
> > > > fs (binary='gnunet-service-fs', status=failed, exit_status=255,
> restart_delay='6 m')
> > > > revocation (binary='gnunet-service-revocation', status=failed,
> exit_status=255, restart_delay='6 m')
> > > > namestore (binary='gnunet-service-namestore', status=started)
> > > > gns (binary='gnunet-service-gns', status=failed, exit_status=255,
> restart_delay='6 m')
> > > > dht (binary='gnunet-service-dht', status=failed, exit_status=255,
> restart_delay='6 m')
> > > > cadet (binary='gnunet-service-cadet', status=failed,
> exit_status=255, restart_delay='6 m')
> > > > zonemaster (binary='gnunet-service-zonemaster', status=started)
> > > > zonemaster-monitor (binary='gnunet-service-zonemaster-monitor',
> status=started)
> > > > nse (binary='gnunet-service-nse', status=failed, exit_status=255,
> restart_delay='6 m')
> > > > topology (binary='gnunet-daemon-topology', status=started)
> > > >
> > > > <snip>
> > > >
> > > > can you please help me in identifying what I could have done wrong
> here.
> > > >
> > > > Thanks,
> > > > Vikas
> > >
> >
>
>
