[systemd-bugs] [Bug 81019] New: if unit's process exits non-zero no more logging for that unit until reboot

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=81019

          Priority: low
            Bug ID: 81019
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: if unit's process exits non-zero no more logging for
                    that unit until reboot
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: p.staszewski at gmail.com
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

If you have a unit that Execs a process that doesn't handle SIGTERM, that is
exists non-zero on it, logging will stop working after first `systemctl stop`
or `systemctl restart`.

There will be logging since the initial start (either by `systemctl start` or
if start on boot if `enable`d) till the non-zero exit. After that `start`ing or
`restart`ing will succeed but no logging will be performed. This will be
regardless of Standard*= options, as I have tested them.

I haven't tested if logging will work if the Execed process craps out and dies
non-zero (that is 'dies on its own', as oppossed to any of the `systemctl`
commands), but above behaviour is still a bug. Logging should *always* work,
regardless of the exit status and exit conditions. I do logging not because I
fancy having TB of data, but because I want *error* situations to be written
down. And a process exiting non-zero should not mean 'no more logging for this
unit during this boot!'.

Versions and stuff:

Linux rpi 3.12.23-1-ARCH #1 PREEMPT Fri Jun 27 01:32:04 MDT 2014 armv6l
GNU/Linux
local/libsystemd 214-2.1

Service file:
[Unit]
Description=DNS blackhole
After=network.target

[Service]
ExecStart=/home/user/adhole -t 250ms 192.168.0.3 192.168.0.21 blacklist.txt
WorkingDirectory=/home/user
Restart=always

[Install]
WantedBy=multi-user.target

AdHole that doesn't do SIGTERM:
https://github.com/drbig/adhole/tree/6b464386a99c50474eba5c735bb833c998cffddd

AdHole that does SIGTERM:
https://github.com/drbig/adhole/blob/a18f491c82bd0d485c69c290583329781cf94d24

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20140707/404138ad/attachment.html>