From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 23064@debbugs.gnu.org
Subject: bug#23064: herd has incomplete status reporting, not so helpful
Date: Sat, 19 Mar 2016 22:39:21 +0100 [thread overview]
Message-ID: <20160319223921.107f27bc@scratchpost.org> (raw)
In-Reply-To: <87lh5ef9uy.fsf@gnu.org>
> Sounds like postgresql died and shepherd did not notice? Or maybe it
> keeps trying to respawn it? What did /var/log/shepherd.log say?
2016-03-19 10:34:48 Service postgres has been started.
2016-03-19 10:34:49 Respawning postgres.
2016-03-19 10:34:49 Service postgres has been started.
2016-03-19 10:34:50 Respawning postgres.
2016-03-19 10:34:50 Service postgres has been started.
2016-03-19 10:34:51 Respawning postgres.
2016-03-19 10:34:51 Service postgres has been started.
2016-03-19 10:34:52 Respawning postgres.
2016-03-19 10:34:52 Service postgres has been started.
2016-03-19 10:34:53 Respawning postgres.
2016-03-19 10:34:53 Service postgres has been started.
2016-03-19 10:34:54 Respawning postgres.
2016-03-19 10:34:54 Service postgres has been started.
> Currently the Shepherd does not do log stdout/stderr of its child
> processes, which sucks somewhat.
Yeah, that's not good.
> However, daemons can usually be told to write to syslog, which is more
> appropriate than writing things to stdout/stderr anyway.
It can always be unable to open syslog for some reason.
If shepherd can't/doesn't redirect stderr on its own, it would be nice to have init write it somewhere and everyone else inherit it as default. Just throwing it away is not nice.
But I agree, the chance of being able to write it to syslog is high. Btw: How does guixsd know to start the syslog service before the postgres service?
>What’s the right command-line/configuration option to have postgresql use syslog?
The option is
log_destination = 'syslog'
in postgresql.conf
which is generated in gnu/services/databases.scm (%default-postgres-config).
Does shepherd back off from respawing it eventually (if it respawns too fast) or will it log the same messages into syslog once every 0.1 s until my disk is full? :->
next prev parent reply other threads:[~2016-03-19 21:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-19 15:13 bug#23064: herd has incomplete status reporting, not so helpful Danny Milosavljevic
2016-03-19 15:25 ` Danny Milosavljevic
2016-03-19 21:15 ` Ludovic Courtès
2016-03-19 21:39 ` Danny Milosavljevic [this message]
2016-03-21 8:35 ` Ludovic Courtès
2016-03-22 19:29 ` Danny Milosavljevic
2016-03-22 23:23 ` Ludovic Courtès
2016-03-23 21:44 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160319223921.107f27bc@scratchpost.org \
--to=dannym@scratchpost.org \
--cc=23064@debbugs.gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).