shepherd doesn't capture service stdout/stderr

  • Done
  • quality assurance status badge
Details
4 participants
  • Gábor Boskovits
  • Brice Waegeneire
  • Ludovic Courtès
  • Robert Vollmert
Owner
unassigned
Submitted by
Robert Vollmert
Severity
important
Merged with

Debbugs page

R
R
Robert Vollmert wrote on 17 Jun 2019 09:41
(address . bug-guix@gnu.org)
60AB29DA-9E60-4C78-B1C8-7BAD9318D69F@vllmrt.net
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

G
G
Gábor Boskovits wrote on 17 Jun 2019 11:49
(name . Robert Vollmert)(address . rob@vllmrt.net)(address . 36264@debbugs.gnu.org)
CAE4v=piqPrAZHxbf90JO__SCC4+sRiV1apXd7ZQFAB_FD49gSg@mail.gmail.com
Hello guix,

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

Toggle quote (8 lines)
> 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.


Toggle quote (5 lines)
> Compare the discussion at
>
> https://lists.gnu.org/archive/html/guix-devel/2019-06/msg00186.html


Best regards,
g_bor

Toggle quote (5 lines)
>
>
>
>
>
Attachment: file
B
B
Brice Waegeneire wrote on 5 Apr 2020 07:28
merge 36264 30939
(address . control@debbugs.gnu.org)
10441295b633fc99948b7eed4aad51f3@waegenei.re
severity 36264 important
merge 36264 30939
quit
L
L
Ludovic Courtès wrote on 6 Sep 00:18 -0700
Re: bug#36264: shepherd doesn't capture service stdout/stderr
(address . 36264-done@debbugs.gnu.org)
87ed5x45da.fsf@gnu.org
Robert Vollmert <rob@vllmrt.net> skribis:

Toggle quote (11 lines)
> 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’.
Closed
?
Your comment

Commenting via the web interface is currently disabled.

To comment on this conversation send an email to 36264@patchwise.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 36264
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch