/etc/init.d/resolver generates wrong resolver.pid file (Kresd)

Omnia here. I hit it basically by the accident (as I dont check cronlog regularly)

/etc/init.d/resolver generates wrong resolver.pid file, which brokes watchdog functionality, ending with restarting resolver every 10min or so. Mine .pid always contains more numbers, because running process:

/etc/init.d/resolver restart

meanwhile running resolver restart…

root@Doma:~# pidof kresd
11245 11238
root@Doma:~# ps | grep 11238
11238 root 1228 S {kresd} /bin/sh /etc/rc.common /etc/init.d/kresd start
11255 root 1088 R grep 11238

… resolver script ends

root@Doma:~# pidof kresd

11245 - correct PID, which should be on resolver.pid
11238 - bogus PID form script, which I assume broke watchdog functionality

after nasty workaround (recreate resolver.pid from watchdog script before other actions), resolver are no longer restarted. Not sure about solution from actual/etc/init.d/resolver right now.

Thanks for description. I just created issue for this bug https://gitlab.labs.nic.cz/turris/turris-os-packages/issues/104

1 Like