[systemd-bugs] [Bug 62876] New: Timer-activated services don't recover after failure and reset-failed

[bugzilla-daemon at freedesktop.org]

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

          Priority: medium
            Bug ID: 62876
          Assignee: systemd-bugs at lists.freedesktop.org
           Summary: Timer-activated services don't recover after failure
                    and reset-failed
        QA Contact: systemd-bugs at lists.freedesktop.org
          Severity: major
    Classification: Unclassified
                OS: Linux (All)
          Reporter: david at davidstrauss.net
          Hardware: x86-64 (AMD64)
            Status: NEW
           Version: unspecified
         Component: general
           Product: systemd

Units with timer activation currently get rescheduled for their next run
following successful completion of their last run. However, if the service
fails on a run, it goes into a failed state that has no future run scheduled.

Currently:
After exist with failure, only starting the timer-activated service manually
and having it exit successfully recovers the state of scheduled runs.

Expected behavior:
At a minimum, running "systemctl reset-failed" (or similar) should cause it to
go back into having scheduled runs, but it doesn't.

It's possible that future runs should get scheduled even if service units exits
with failure, to be more like cron/anacron. Maybe such "honeybadger" scheduling
could be an option for a given timer.

Workarounds:
It's possible to set expected exit codes to mask failure from systemd so future
runs always get scheduled.

-- 
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/20130328/4ea6d376/attachment.html>