#36264 shepherd doesn't capture service stdout/stderr

Message #5 received at submit@debbugs.gnu.org (full text, mbox, reply):

From: Robert Vollmert <rob@vllmrt.net>

To: bug-guix@gnu.org

Subject: shepherd doesn't capture service stdout/stderr

Date: Mon, 17 Jun 2019 18:41:37 +0200

On a pretty fresh Guix System install, I see some regular
sshd error messages on tty1 (which I guess means they’re
written to /dev/console). Also, setting up a regular
shepherd service via make-forkexec-constructor for a
program that logs to stderr (postgrest which I’m in the
process of packaging), all output goes to tty1.

Compare the discussion at

https://lists.gnu.org/archive/html/guix-devel/2019-06/msg00186.html

Message #8 received at 36264@debbugs.gnu.org (full text, mbox, reply):

From: Gábor Boskovits <boskovits@gmail.com>

To: Robert Vollmert <rob@vllmrt.net>

Cc: 36264@debbugs.gnu.org

Subject: Re: bug#36264: shepherd doesn't capture service stdout/stderr

Date: Mon, 17 Jun 2019 20:49:41 +0200

[Message part 1 (text/plain, inline)]

Hello guix,

Robert Vollmert <rob@vllmrt.net> ezt írta (időpont: 2019. jún. 17., Hét
18:55):

> On a pretty fresh Guix System install, I see some regular
> sshd error messages on tty1 (which I guess means they’re
> written to /dev/console). Also, setting up a regular
> shepherd service via make-forkexec-constructor for a
> program that logs to stderr (postgrest which I’m in the
> process of packaging), all output goes to tty1.
>

This is also on my todo list for a while, so I can provide some additional
information. I noticed this on two services I was using:
ntp-service-type with default config and
prometheus-node-exporter-service-type with default config. I hope that
helps somewheat.


> Compare the discussion at
>
> https://lists.gnu.org/archive/html/guix-devel/2019-06/msg00186.html


Best regards,
g_bor

>
>
>
>
>

[Message part 2 (text/html, inline)]

Message #17 received at 36264-done@debbugs.gnu.org (full text, mbox, reply):

From: Ludovic Courtès <ludo@gnu.org>

To: 36264-done@debbugs.gnu.org

Subject: Re: bug#36264: shepherd doesn't capture service stdout/stderr

Date: Fri, 06 Sep 2024 09:18:41 +0200

Robert Vollmert <rob@vllmrt.net> skribis:

> On a pretty fresh Guix System install, I see some regular
> sshd error messages on tty1 (which I guess means they’re
> written to /dev/console). Also, setting up a regular
> shepherd service via make-forkexec-constructor for a
> program that logs to stderr (postgrest which I’m in the
> process of packaging), all output goes to tty1.
>
> Compare the discussion at
>
> https://lists.gnu.org/archive/html/guix-devel/2019-06/msg00186.html

Fortunately that was fixed in Shepherd 0.9.0 (April 2022).

Ludo’.

Send a report that this bug log contains spam.