GNU bug report logs -
#72166
Shepherd periodically goes unresponsive on one of my machines
Previous Next
Full log
View this message in rfc822 format
Hi Jonathan,
"Jonathan Frederickson" <jonathan <at> terracrypt.net> skribis:
> I've been running into an issue with Shepherd on one of my machines. Every so often (and I haven't figured out what conditions trigger it), my Shepherd instances (both home and PID 1) will go unresponsive. I thought I had tracked it down to a misbehaving home service that I had configured, but it's just happened again without that service running.
>
> 'herd status' hangs indefinitely:
>
> jfred <at> terracard ~$ sudo herd status
> Password:
> <never returns>
>
> ...on both instances:
>
> jfred <at> terracard ~$ herd status
> <never returns>
Ouch. What version of shepherd is running? (You can view it with
“cat /proc/1/cmdline | xargs -0”.)
> The PID 1 shepherd instance isn't reaping defunct processes:
>
> jfred <at> terracard ~$ ps aux | grep -i lock
> jfred 541 0.0 0.0 3700 2304 ? S 18:30 0:00 swayidle -w timeout 300 swaylock -f -i ~/.wallpapers/user-manual.jpg timeout 10 if pgrep swaylock; then swaymsg "output * dpms off"; fi resume swaymsg "output * dpms on" before-sleep swaylock -f -i ~/.wallpapers/user-manual.jpg
> jfred 3111 0.0 0.0 0 0 ? Z 18:53 0:00 [swaylock] <defunct>
> jfred 3112 0.0 0.0 0 0 ? Zs 18:53 0:00 [swaylock] <defunct>
>
> Some further troubleshooting... strace indicates that it's waiting on a read() on its fd 9:
Interesting. There were bugs in earlier 0.10.x version that could cause
this sort of thing; let’s see what version you have, first.
Ludo’.
This bug report was last modified 282 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.