View Issue Details

IDProjectCategoryView StatusLast Update
0003256GNUnetARM servicepublic2018-06-07 23:27
ReporterBart Polot Assigned ToChristian Grothoff  
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionunable to reproduce 
Product VersionGit master 
Target Version0.11.0Fixed in Version0.11.0pre66 
Summary0003256: ARM does not start peer after crash/unplanned shutdown
DescriptionIf a peer is shut down without cleaning the sockets in GNUNET_RUNTIME (kill -9, power outage, ...) issuing a gnunet-arm -s assumes that there is already a peer running because the files exist and refuses to start anything.
Additional InformationDeleting everything in '/run/user/UID/gnunet-*' allows 'gnunet-arm -s' to work, but I takes a while (and enabling DEBUG messages) to figure out. Definitely not user-friendly!
TagsNo tags attached.

Activities

Christian Grothoff

2014-01-13 13:30

manager   ~0007985

So the question is _how_ to fix this best.

Christian Grothoff

2014-01-13 13:30

manager   ~0007986

Do we know how other applications deal with this?

Bart Polot

2014-01-13 14:04

reporter   ~0007987

In a personal project what I do is a `ps | grep [process name]` in case of non-responsiveness to make sure the socket (named fifo, in this case) is taken care of.

In debian apt-get just complains when a lock file is left around.

Kdevelop offers a force option if "singleton" files are detected when starting the program and cannot communicate with a different running instance .

Christian Grothoff

2017-02-26 02:24

manager   ~0011858

Is this still happening? I've not had this issue in a while...

Issue History

Date Modified Username Field Change
2014-01-07 16:31 Bart Polot New Issue
2014-01-13 13:30 Christian Grothoff Note Added: 0007985
2014-01-13 13:30 Christian Grothoff Status new => confirmed
2014-01-13 13:30 Christian Grothoff Note Added: 0007986
2014-01-13 14:04 Bart Polot Note Added: 0007987
2014-01-20 14:31 Bart Polot Additional Information Updated
2014-01-30 15:52 Christian Grothoff Target Version 0.10.1 =>
2014-04-11 15:23 Christian Grothoff Target Version => 0.11.0
2017-02-26 02:24 Christian Grothoff Severity major => tweak
2017-02-26 02:24 Christian Grothoff Note Added: 0011858
2018-06-07 23:27 Christian Grothoff Assigned To => Christian Grothoff
2018-06-07 23:27 Christian Grothoff Status confirmed => closed
2018-06-07 23:27 Christian Grothoff Resolution open => unable to reproduce
2018-06-07 23:27 Christian Grothoff Fixed in Version => 0.11.0pre66