From mboxrd@z Thu Jan  1 00:00:00 1970
From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=)
Subject: bug#23064: herd has incomplete status reporting, not so helpful
Date: Sat, 19 Mar 2016 22:15:01 +0100
Message-ID: <87lh5ef9uy.fsf@gnu.org>
References: <20160319161337.609ada55@scratchpost.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:58318)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ahOE8-0006wK-5b
	for bug-guix@gnu.org; Sat, 19 Mar 2016 17:16:05 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ahOE6-0006ob-QB
	for bug-guix@gnu.org; Sat, 19 Mar 2016 17:16:04 -0400
Received: from debbugs.gnu.org ([208.118.235.43]:56842)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ahOE6-0006oX-Mw
	for bug-guix@gnu.org; Sat, 19 Mar 2016 17:16:02 -0400
Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1ahOE6-0001gP-IG
	for bug-guix@gnu.org; Sat, 19 Mar 2016 17:16:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.23064.B23064.14584221163973@debbugs.gnu.org>
In-Reply-To: <20160319161337.609ada55@scratchpost.org> (Danny Milosavljevic's
	message of "Sat, 19 Mar 2016 16:13:37 +0100")
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
To: Danny Milosavljevic <dannym@scratchpost.org>
Cc: 23064@debbugs.gnu.org

Danny Milosavljevic <dannym@scratchpost.org> skribis:

> $ sudo herd status postgres
> Status of postgres:
>   It is started.
>   Running value is 18438.
>   It is enabled.
>   Provides (postgres).
>   Requires (user-processes loopback).
>   Conflicts with ().
>   Will be respawned.
>
> So it claimed that everything was just peachy.
>
> $ sudo herd stop postgres
> $ sudo herd start postgres
>
> ... which reported nothing out of the ordinary either.
>
> $ ps -ef |grep postgres
> [xxxx] <defunct>

Sounds like postgresql died and shepherd did not notice?  Or maybe it
keeps trying to respawn it?  What did /var/log/shepherd.log say?

> $ sudo -u postgres postgres --config-file=3D/etc/postgresql.conf -D /var/=
lib/postgresql/data
> FATAL:  database files are incompatible with server
> DETAIL:  The data directory was initialized by PostgreSQL version 9.3, wh=
ich is not compatible with this version 9.5.1.
> $=20
>
> Aha! It says so right there in the standard output (or error?). Where did=
 that message go in the shepherd case?
>
> $ cd /var/log
> $ grep -r incompatible .
> $=20

Currently the Shepherd does not do log stdout/stderr of its child
processes, which sucks somewhat.

However, daemons can usually be told to write to syslog, which is more
appropriate than writing things to stdout/stderr anyway.  What=E2=80=99s the
right command-line/configuration option to have postgresql use syslog?

Thanks,
Ludo=E2=80=99.