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: Tue, 22 Mar 2016 20:29:16 +0100 [thread overview]
Message-ID: <20160322202916.53b89904@scratchpost.org> (raw)
In-Reply-To: <87shzkcjoi.fsf@gnu.org>
Hi Ludo,
> Could you try this and report back?
$ patch -p1 < ...
$ sudo ./pre-inst-env guix system reconfigure /etc/config.scm
$ sudo herd stop postgres
$ sudo herd start postgres
Service postgres has been started.
$ tail -f /var/log/messages
Mar 22 20:15:51 localhost nscd: 213 monitored file `/etc/services` was created, adding watch
Mar 22 20:15:51 localhost nscd: 213 monitored file `/etc/services` was written to
Mar 22 20:20:40 localhost postgres[2115]: [1-1] FATAL: database files are incompatible with server
Mar 22 20:20:40 localhost postgres[2115]: [1-2] DETAIL: The data directory was initialized by PostgreSQL version 9.3, which is not compatible with this version 9.5.1.
...
Nice :-)
Thanks!
Although it would be nice to have shepherd have a field in "herd status" which tells you when it respawned the service in < 1 s intervals (or maybe if it respawned it < 1 s after the initial start) - or maybe just how long ago it was (last) started and when the actual herd start command was :-)
next prev parent reply other threads:[~2016-03-22 19:30 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
2016-03-21 8:35 ` Ludovic Courtès
2016-03-22 19:29 ` Danny Milosavljevic [this message]
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=20160322202916.53b89904@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).