bug#63736: [Shepherd] Loss of SIGCHLD notifications

2023-11-23 Thread Ludovic Courtès
Ludovic Courtès skribis: > Another possibility is lockup: one of the relevant fibers is either gone > or stuck in ‘put-message’ or ‘get-message’. > > I did two things: > > b9a37f3 shepherd: Make signal handling fiber an essential task. > 8ae2780 service: Do not attempt to restart transient se

bug#63736: [Shepherd] Loss of SIGCHLD notifications

2023-05-27 Thread Ludovic Courtès
Ludovic Courtès skribis: > Long story short: there seems to be a problem with signal delivery. > Most likely, the initial grace period expiration above when stopping > nscd is a symptom of shepherd no longer receiving/processing SIGCHLD > rather than the cause. Another possibility is lockup: one

bug#63736: [Shepherd] Loss of SIGCHLD notifications

2023-05-26 Thread Ludovic Courtès
I experienced, with the Shepherd 0.10.0, a situation where ‘herd restart’ would get stuck after the end-of-grace-period expiration (restarting nscd in this case): --8<---cut here---start->8--- May 26 08:44:33 localhost shepherd[1]: [NetworkManager] Status of nsc