* time out in shepherd service?
@ 2016-12-20 22:50 ng0
2016-12-21 9:13 ` Ludovic Courtès
0 siblings, 1 reply; 3+ messages in thread
From: ng0 @ 2016-12-20 22:50 UTC (permalink / raw)
To: guix-devel
Is there a time out in shepherd service start/checks, or is the
"service could not be started" simply a result of when a service
encounters a fatal error and quits?
--
♥Ⓐ ng0 | PGP keys and more: https://n0is.noblogs.org/
| http://ng0.chaosnet.org
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: time out in shepherd service?
2016-12-20 22:50 time out in shepherd service? ng0
@ 2016-12-21 9:13 ` Ludovic Courtès
2016-12-21 10:44 ` ng0
0 siblings, 1 reply; 3+ messages in thread
From: Ludovic Courtès @ 2016-12-21 9:13 UTC (permalink / raw)
To: ng0; +Cc: guix-devel
ng0 <ng0@libertad.pw> skribis:
> Is there a time out in shepherd service start/checks, or is the
> "service could not be started" simply a result of when a service
> encounters a fatal error and quits?
“Service could not be started” just means that the ‘start’ procedure of
the service returned #f or threw an exception.
To debug this, you’d have to check the service’s log files, or use
#:log-file to redirect the stdout/stderr to a log file.
HTH!
Ludo’.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: time out in shepherd service?
2016-12-21 9:13 ` Ludovic Courtès
@ 2016-12-21 10:44 ` ng0
0 siblings, 0 replies; 3+ messages in thread
From: ng0 @ 2016-12-21 10:44 UTC (permalink / raw)
To: Ludovic Courtès; +Cc: guix-devel
Ludovic Courtès <ludo@gnu.org> writes:
> ng0 <ng0@libertad.pw> skribis:
>
>> Is there a time out in shepherd service start/checks, or is the
>> "service could not be started" simply a result of when a service
>> encounters a fatal error and quits?
>
> “Service could not be started” just means that the ‘start’ procedure of
> the service returned #f or threw an exception.
>
> To debug this, you’d have to check the service’s log files, or use
> #:log-file to redirect the stdout/stderr to a log file.
>
> HTH!
>
> Ludo’.
>
Thanks.
Observed and tried yesterday: when I turn on logging and make the
output more verbose, the log file created is root:root and
therefore not accesible by the internal logging mechanisms of the
gnunet subsystems which as a consequence throw errors that they
can not log to this file.
#:user and #:group is now set, and some more changes which I
didn't publish so far.
There are some gnunet errors, so I have to go all the way back
1.5 - 2 years and see if this was fixed at some commit and have
to backport the fix 0.10.1 if these errors are caused by
gnunet. But seeing that it's functional without system service
it's unlikely that this is the case.
--
♥Ⓐ ng0 | PGP keys and more: https://n0is.noblogs.org/
| http://ng0.chaosnet.org
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-12-21 10:44 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-12-20 22:50 time out in shepherd service? ng0
2016-12-21 9:13 ` Ludovic Courtès
2016-12-21 10:44 ` ng0
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).