Hi Guix, when defining a service type that extends shepherd-root-service-type andthe 'start' function of the shepherd-service definition contains anerror, the error is silently ignored. No log output is generated at all. For example (full system definition is attached): (define (errtest-shepherd-service c) (list (shepherd-service (provision '(errtest)) (documentation "Errtest") (requirement '(file-systems)) (modules `((shepherd support) (ice-9 match) ,@%default-modules)) (start #~(lambda args (local-output "errtest start") this-is-an-unbound-variable (local-output "errtest end") #t)))))
The log message "errtest start" appears in /var/log/messages, asexpected. The next line contains an error, and aborts execution of thestart function. The error only becomes apparent when manually doing a "herd restarterrtest", which shows an error message (but without any error locationor stack trace). But the error (regarding the unbound variable) is notlogged, and there is no indication in the log that the service couldn'tbe started in any log. Furthermore the "herd status" of a service that encountered an error inthe start function is very misleading: root@errtest ~# herd status errtestStatus of errtest: It is stopped. It is enabled. Provides (errtest). Requires (file-systems). Conflicts with (). Will be respawned.
It shows "Will be respawned", which is wrong. I'd be happy to work on a patch, but it seems like there is some designdiscussion necessary, in particular how the "Will be respawned" shouldbe handled. Services have a "respawn?" flag, but of course respawningcan only work if the start function executed successfully (and only theservice process itself failed) in the first place. I generally feel like the state machine for services needs some work.In particular, it would be useful to distinguish between "failed" and"completed" services instead of conflating both states into "stopped".Or maybe have some more general mechanism for storing state about theservice, instead of just the slot that usually contains the PID? - Florian
Hi Florian, I stumbled upon this problem with https://issues.guix.gnu.org/48521,andhad a hard time to debug it (due to the completely missing informationin any output or log from shepherd). Worst, this caused the system to hang early on boot! I'm raising the priority of this issue. Thanks, Maxim