[Freifunk Franken Firmware 0000115]: Locks not deleted for mesh routers after Uplink goes off

[Mantis Bug Tracker]

Der folgende Eintrag wurde erfasst. 
====================================================================== 
https://mantis.freifunk-franken.de/view.php?id=115 
====================================================================== 
Berichtet von:              Adrian Schmutzler
Zugewiesen an:              
====================================================================== 
Projekt:                    Freifunk Franken Firmware
Eintrag-ID:                 115
Kategorie:                  Freifunk Franken Firmware
Reproduzierbarkeit:         nicht getestet
Auswirkung:                 Blocker
Priorität:                  dringend
Status:                     neu
Zielversion:                next-stable
====================================================================== 
Erstellt am:                2018-12-06 15:33 CET
Zuletzt geändert:           2018-12-06 15:33 CET
====================================================================== 
Zusammenfassung:            Locks not deleted for mesh routers after Uplink goes
off
Beschreibung: 
We have a set of Mesh-Routers that all did not come back after the Uplink went
down and up some time later:
https://monitoring.freifunk-franken.de/routers/4017

>From a mesh router connected via Ethernet, I was able to find out that
configurehood was not running, but the locks for configurehood and nodewatcher
were still present.

Thus, there must have been a situation where configurehood (and nodewatcher)
were cancelled without raising INT, TERM or EXIT, so execution is blocked by the
left-over lock file:
root at km005:~# ls -al /var/lock
drwxr-xr-x    2 root     root           320 Dec  4 16:45 .
drwxrwxrwt   12 root     root           380 Dec  6 10:38 ..
-rwx------    1 root     root             6 Dec  6 10:38 configurehood.lock
-rwx------    1 root     root             6 Dec  6 10:35 nodewatcher.lock
-rw-r--r--    1 root     root             0 Dec  4 16:43 procd_dropbear.lock
[...]

It is particularly interesting that this happened for BOTH configurehood AND
nodewatcher (note the time difference above).
====================================================================== 

Eintrags-Historie 
Änderungsdatum   Benutzername   Feld                     Änderung             
====================================================================== 
2018-12-06 15:33 Adrian SchmutzlerNeuer Eintrag                                
======================================================================