From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark H Weaver Subject: bug#36731: shepherd lost track of nginx Date: Sat, 20 Jul 2019 19:07:58 -0400 Message-ID: <871rykcniu.fsf@netris.org> References: <87ef2labds.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:56539) by lists.gnu.org with esmtp (Exim 4.86_2) (envelope-from ) id 1hoyVL-0006o3-9F for bug-guix@gnu.org; Sat, 20 Jul 2019 19:11:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1hoyVK-0006dB-BJ for bug-guix@gnu.org; Sat, 20 Jul 2019 19:11:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:49170) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1hoyVK-0006d5-8F for bug-guix@gnu.org; Sat, 20 Jul 2019 19:11:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1hoyVK-0008IS-0i for bug-guix@gnu.org; Sat, 20 Jul 2019 19:11:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87ef2labds.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 20 Jul 2019 00:49:03 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: Ludovic =?UTF-8?Q?Court=C3=A8s?= Cc: 36731@debbugs.gnu.org, Robert Vollmert Hello, Ludovic Court=C3=A8s writes: > Robert Vollmert skribis: > >> The result was this: >> >> $ sudo herd restart nginx >> Service nginx is not running. >> herd: exception caught while executing 'start' on service 'nginx': >> Throw to key `srfi-34' with args `("#> [program: >> \"/gnu/store/mlg0xfbiq03s812rm3v7mrlhyngas4xp-nginx-1.17.1/sbin/nginx\" >> arguments: (\"-c\" >> \"/gnu/store/r6gl9n7pwf4npiri05qxr40vdihdm2yy-nginx.conf\" \"-p\" >> \"/var/run/nginx\") exit-status: 1 term-signal: #f stop-signal: #f] >> 147e000>")=E2=80=99. [=E2=80=A6] >> That error message could also be clearer about what=E2=80=99s going on. = At any >> rate, after I killed the nginx process, =E2=80=9Cherd start nginx=E2=80= =9D worked fine. > > I agree that we could and should improve the error message. On the subject of this error message, why was the &invoke-error condition serialized to a string before apparently being embedded within another exception? In other words, why did it print: Throw to key `srfi-34' with args `("#")=E2=80=99. instead of something closer to: Throw to key `srfi-34' with args `(#)=E2= =80=99. We may want to go further in this specific case to make a user-friendly error message, but in the more general case of printing arbitrary exceptions, eliminating that second layer of string serialization would help make the error reports a bit nicer to read. What do you think? Mark