package openssh-server (not installed) failed to install/upgrade: subprocess new pre-installation script killed by signal (Aborted)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openssh (Ubuntu) |
Invalid
|
High
|
Unassigned |
Bug Description
package openssh-server (not installed) failed to install/upgrade: subprocess new pre-installation script killed by signal (Aborted)
ProblemType: Package
DistroRelease: Ubuntu 10.04
Package: openssh-server (not installed)
ProcVersionSign
Uname: Linux 2.6.32-24-generic i686
NonfreeKernelMo
Architecture: i386
Date: Mon Aug 16 10:08:33 2010
ErrorMessage: subprocess new pre-installation script killed by signal (Aborted)
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
SourcePackage: openssh
Title: package openssh-server (not installed) failed to install/upgrade: subprocess new pre-installation script killed by signal (Aborted)
Hi Randall, thank you for reporting this bug and working with us to make Ubuntu better!
I notice these lines in the Dmesg.txt:
[ 1.890131] EXT3-fs: INFO: recovery required on readonly filesystem. cleanup: deleting unreferenced inode 431687 cleanup: deleting unreferenced inode 782324 cleanup: deleting unreferenced inode 782320 cleanup: deleting unreferenced inode 782315 cleanup: deleting unreferenced inode 782311 cleanup: deleting unreferenced inode 782307 cleanup: deleting unreferenced inode 782305 cleanup: deleting unreferenced inode 782294 cleanup: deleting unreferenced inode 757417
[ 1.890137] EXT3-fs: write access will be enabled during recovery.
[ 3.777970] kjournald starting. Commit interval 5 seconds
[ 3.777997] EXT3-fs: sda5: orphan cleanup on readonly fs
[ 3.778009] ext3_orphan_
[ 3.787929] ext3_orphan_
[ 3.787953] ext3_orphan_
[ 3.792731] ext3_orphan_
[ 3.792747] ext3_orphan_
[ 3.792762] ext3_orphan_
[ 3.792776] ext3_orphan_
[ 3.798283] ext3_orphan_
[ 3.804154] ext3_orphan_
[ 3.807915] EXT3-fs: sda5: 9 orphan inodes deleted
[ 3.807919] EXT3-fs: recovery complete.
[ 3.820009] EXT3-fs: mounted filesystem with ordered data mode.
Is it possible that you had a hard system crash that may have corrupted sda5? According to the attached Df.txt, that is your root drive and has all of the binaries on the system. Given that you had a very abnormal error from perl, I'd suspect that there may be an issue with your disk being corrupted.
Make sure you backup your data immediately! And then try
' sudo apt-get -f install' to re-attempt the configuration of the system that caused the error. If it succeeds, then this may be a false alarm, though I would still be suspicious of system integrity. If you see the error again, then I would recommend reinstalling the system without deleting or formatting the filesystems (after backing everything up!).
Marking Incomplete pending information from Randall. Marking High as this would be a very serious problem if it turns out to be an issue with perl.