package psad failed to remove : find: `/var/run/psad/': No such file or directory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
psad (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Hardy |
Fix Released
|
Medium
|
Michael Vogt |
Bug Description
Binary package hint: update-manager
update-manager failed to upgrade when upgrading from Hardy to Intrepid
TEST CASE:
1. use hardy (e.g. hardy server, chroot)
2. install psad
3. reboot
4. run dpkg -r psad and verify that it fails
5. install psad from hardy-proposed
6. reboot
7. run dpkg -r psad and verify that it works
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)
Package: update-manager 1:0.93.32
PackageArchitec
SourcePackage: update-manager
Title: package update-manager 1:0.93.32 failed to install/upgrade: ErrorMessage: SystemError in cache.commit(): E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1)
Uname: Linux 2.6.24-21-generic i686
Related branches
Changed in psad: | |
importance: | Undecided → Medium |
status: | New → In Progress |
assignee: | nobody → mvo |
description: | updated |
Thanks for your report.
The following issues have caused the upgrade failure:
=====
Removing psad ...
find: `/var/run/psad/': No such file or directory
dpkg: error processing psad (--remove):
subprocess pre-removal script returned error exit status 1
=====
This is probably due to /var/run being a tmpfs filesystem
The other with otrs
=====
Removing otrs2 ...
debconf: unable to initialize frontend: Gnome
debconf: (Unable to load Gnome -- is libgnome2-perl installed?)
debconf: falling back to frontend: Dialog
debconf: unable to initialize frontend: Dialog
debconf: (Dialog frontend will not work on a dumb terminal, an emacs shell buffer, or without a controlling terminal.)
debconf: falling back to frontend: Readline
Configuring otrs2
-----------------
Since you are removing otrs2, it's possible that you no longer want the
underlying database.
If you like, database removal can be handled with dbconfig-common.
If you know that you do want to keep this database, or if you want to handle the
removal of this database manually, you should refuse this option.
Otherwise, you should choose this option.
Deconfigure database for otrs2 with dbconfig-common? y
If you no longer need the database for otrs2, this is your chance to remove
them.
If you no longer have need of the data being stored by otrs2, you should choose
this option. If you want to hold this data for another time, or if you would
rather handle this process manually, you should refuse this option.
Do you want to purge the database for otrs2? y
What is the password for the administrative account with which this package
should create its MySQL database and user?
Password of your database's administrative user:
dbconfig-common: dumping mysql database otrs2 to /var/tmp/ otrs2.otrs2. 2008-11- 04-09.15. mysql.b13487.
sanity check failed for mysql.
error encountered dumping database:
No mysql client to execute. (have you installed the mysql-client package?
An error seems to have occurred while removing the database.
For some reason it was not possible to perform some of the actions necessary to
remove the database for otrs2. At this point you have two options: you can find
out what has caused this error and fix it, or you can refuse the offer for help
removing the database (the latter implies you will have to remove the database
manually). If it's of any help, this was the error encountered:
No mysql client to execute. (have you installed the mysql-client package?
At this point, you have the option to retry or abort the operation. If you
choose "retry", you will be prompted with all the configuration questions once
more and another attempt will be made at performing the operation. "retry (skip
questions)" will immediately attempt the operation again, skipping all
questions. If you choose "abort", the operation will fail and you will need to
downgrade, reinstall, reconfigure this package, or otherwise manually intervene
to continue using it.
1. abort 2. retry
Error removing database for otrs2. Retry? y
Error removing database for otrs2. Retry? y
Error removing database for otrs2. ...