Bug 1293995 - atop.service fails to start
Summary: atop.service fails to start
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: atop
Version: 23
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-12-23 23:55 UTC by Dominique Brazziel
Modified: 2016-12-20 17:21 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-12-20 17:21:39 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dominique Brazziel 2015-12-23 23:55:46 UTC
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:
1.
2.
3.

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-24 00:00:59 UTC
Running the daemon from the command line starts the daemon and creates /var/run/atop.pid

Comment 2 Dominique Brazziel 2015-12-28 13:45:35 UTC
'/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 20:48:33 UTC
These builds fix the issue for me if I start with clean logs:


https://fedorapeople.org/~limb/atop/

Comment 4 Fedora End Of Life 2016-11-24 14:29:46 UTC
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 17:21:39 UTC
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
bug.

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.