Atop binary file corruption after the node recieved a hot shutdown

Bug #1401562 reported by Bogdan Dobrelya on 2014-12-11
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Medium
Fuel Documentation Team
6.1.x
Medium
Fuel Documentation Team

Bug Description

Then the node got unexpected shutdown, atop binary file could became corrupted. Then corrupted, it cannot be either greped with atop -P nor listed with atop -r *starting from some point of the time*. Beyond of this time point, atop will through an error:
"atop/atopsar - uncompress: failed due to corrupted/incomplete data" and exits abnormally.

Looks like the only solution is to remove this file or back it up and restat atop service to start a new one.
This is not a Fuel bug, but atop one, though it impacts any troubleshooting/debugging based on the atop files.

Changed in fuel:
status: New → Confirmed
importance: Undecided → Medium
milestone: none → 6.1
assignee: nobody → Fuel for Openstack (fuel)
Roman Vyalov (r0mikiam) on 2014-12-11
Changed in fuel:
assignee: Fuel for Openstack (fuel) → MOS Linux (mos-linux)
Bogdan Dobrelya (bogdando) wrote :

Please add this to 6.0 release notes as well

One can get all kind of corruptions in case of non-proper shutdown, including filesystem level errors.

tags: added: release-notes
Bogdan Dobrelya (bogdando) wrote :

This issue cannot be fixed due to everything could be broken in case of sudden node power off. But it should be documented, and workaround (backup the broken atop binary file, restart atop service, recreate a link to atop_current) should be specified in docs

Changed in fuel:
assignee: MOS Linux (mos-linux) → Fuel Documentation Team (fuel-docs)
status: Confirmed → Triaged
no longer affects: fuel/6.1.x
no longer affects: fuel/6.0.x
Changed in fuel:
status: Triaged → New
Igor Shishkin (teran) on 2015-10-08
Changed in fuel:
milestone: 7.0 → 8.0
Dmitry Pyzhov (dpyzhov) on 2015-10-22
tags: added: area-docs
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers