<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW --- - Timer-activated services don't recover after failure and reset-failed"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=62876">62876</a>
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>Timer-activated services don't recover after failure and reset-failed
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>major
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Unclassified
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (All)
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>david@davidstrauss.net
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>x86-64 (AMD64)
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>general
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>systemd
          </td>
        </tr></table>
      <p>
        <div>
        <pre>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.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>