package atop 1.23-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127

Bug #597051 reported by scrauny@gmail.com
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
atop (Ubuntu)
Fix Released
Medium
Daniel Hahler

Bug Description

Binary package hint: atop

Tried to install via apt-get over ssh.
The install failed, crashed the machine.
After a reboot, the bug report wizard appeared.

Description: Ubuntu 9.10
Release: 9.10

ProblemType: Package
AptOrdering:
 atop: Install
 atop: Configure
Architecture: amd64
Date: Fri Jun 18 16:02:09 2010
DistroRelease: Ubuntu 9.10
ErrorMessage: subprocess installed post-installation script returned error exit status 127
Package: atop 1.23-1
ProcVersionSignature: Ubuntu 2.6.31-22.60-server
SourcePackage: atop
Title: package atop 1.23-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 127
Uname: Linux 2.6.31-22-server x86_64

Related branches

Revision history for this message
scrauny@gmail.com (scrauny) wrote :
Revision history for this message
Steve Beattie (sbeattie) wrote :

Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.

security vulnerability: yes → no
visibility: private → public
tags: added: karmic
Revision history for this message
Steve Beattie (sbeattie) wrote :

Additionally, it seems like some sort of corruption has occurred, based on the relevant failure in in the DpkgTerminalLog:

Starting atop system monitor: atop.
/var/lib/dpkg/info/atop.postinst: 20: /usr/sbin/logrotate: not found
dpkg: error processing atop (--configure):
 subprocess installed post-installation script returned error exit status 127

as it appears that the logrotate binary is missing. The attached Dependencies.txt file does show that the logrotate package is installed. You may wish to try running

  $ debsums logrotate

to see if it detects corruption, or try reinstalling the logrotate packge.

Daniel Hahler (blueyed)
Changed in atop (Ubuntu):
status: New → In Progress
assignee: nobody → Daniel Hahler (blueyed)
importance: Undecided → Medium
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package atop - 1.26-0ubuntu1

---------------
atop (1.26-0ubuntu1) natty; urgency=low

  * New upstream release (LP: #629546, Closes: #569175)
  * Use "--oknodo" in init script (LP: #188350, Closes: #477362)
  * Only call logrotate in postinst if it exists (LP: #597051)
 -- Daniel Hahler <email address hidden> Thu, 27 Jan 2011 20:28:15 +0100

Changed in atop (Ubuntu):
status: In Progress → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.