Bug 1293995 - atop.service fails to start
atop.service fails to start
Product: Fedora
Classification: Fedora
Component: atop (Show other bugs)
Unspecified Unspecified
unspecified Severity medium
: ---
: ---
Assigned To: Gwyn Ciesla
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-12-23 18:55 EST by Dominique Brazziel
Modified: 2016-12-20 12:21 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 12:21:39 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Dominique Brazziel 2015-12-23 18:55:46 EST
Description of problem:
On reboot atop.service fails to start with the following message:
atop.service: PID NNN read from file /var/run/atop.pid does not exist or is a zombie.

Version-Release number of selected component (if applicable):

How reproducible:
Reboot system with running atop service

Steps to Reproduce:

Actual results:
atop.service won't start, subsequent efforts to manual stop/start or restart
the service fail

Expected results:
atop service starts properly

Additional info:
Comment 1 Dominique Brazziel 2015-12-23 19:00:59 EST
Running the daemon from the command line starts the daemon and creates /var/run/atop.pid
Comment 2 Dominique Brazziel 2015-12-28 08:45:35 EST
'/var/log/atop/atop.log' has reported 'incompatible header' on upgrades, and 
perhaps on some instances where the service is manually restarted by systemctl when the log file for the current day exists:

existing file /var/log/atop/atop_20151106 has incompatible header
existing file /var/log/atop/atop_20151119 has incompatible header
existing file /var/log/atop/atop_20151130 has incompatible header
existing file /var/log/atop/atop_20151221 has incompatible header
Comment 3 Gwyn Ciesla 2016-01-04 15:48:33 EST
These builds fix the issue for me if I start with clean logs:

Comment 4 Fedora End Of Life 2016-11-24 09:29:46 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 5 Fedora End Of Life 2016-12-20 12:21:39 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.