After performing and finish an update the system sent an error with serveral Open-Xchange packages. The system promotes the use of dpkg --configure -a and this was used without any succes. Any ideas on how to turn around this error?
root@mail:/# dpkg --configure -a
dpkg: error: dpkg status database is locked by another process
root@mail:/# dpkg --audit
Another process has locked the database for writing, and might currently be
modifying it, some of the following problems might just be due to that.
The following packages have been unpacked but not yet configured.
They must be configured using dpkg --configure or the configure
menu option in dselect for them to work:
open-xchange-report-client Open-Xchange reporting client
open-xchange-meta-oxucs The Open-Xchange Meta package for OX into UCS integrat
open-xchange-drive-client-windows-generic Update data for branded drive client
open-xchange-drive-client-windows New updater for windows drive clients
open-xchange-meta-backend-ox6 The Open-Xchange Meta package for OX6 backend pa
open-xchange-updater-drive The Open-Xchange Updater backend extension for the
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure <package> or the configure menu option in dselect:
open-xchange-admin The Open-Xchange backend administration extension
dpkg (the lowlevel package manager on Debian based Linux distributions like Debian, UCS or Ubuntu) complains that someone locked its status database:
dpkg: error: dpkg status database is locked by another process
The cause is most probably another dpkg process that is either still running and stuck or it was killed and the lock was not released.
Check the logs:
Please have a look at the following log files for progress (is still something going on?) and for obvious errors:
tail -f /var/log/dpkg.log
tail -f /var/log/apt/history.log
tail -f /var/log/univention/updater.log
“tail” will show the last part of the given file and “-f” outputs appended data as the file grows, so you can see if something is happening.
Try to figure out if there is still a dpkg process running. Execute the following command on the command line:
pgrep dpkg
This should return a number that is the process ID of a running dpkg process. If it doesn’t return anything, there is no dpkg process running right now. In this case you can run the following command to check if any of the higher-level package management processes are still running:
ps auxf | grep -E 'dpkg|-updater|-upgrade| apt'
This should list any process of univention-upgrade, univention-updater, apt or dpkg.
3a. If there are any processes stuck, try to terminate them:
kill <Process ID>
killall dpkg
3b. If there are no processes left, remove the lock file. But this should only be the last resort if nothing else works:
No process is running but certainly open-xchange-admin is half-configured . Correct me if I am wrong, On my understanding you only need to configure a package is "new" . Reconfigurations are part either of full new release or of a removal of the package. Here is a tail of dpkg.log
Halo,
I am going to post what actually solved the problem so others can benefit from the information.
1) My system is a 32 bits UCS install
2) The system interrupted its normal process of upgrade because of a missing package (python-ruamel.yaml) .
It is not clear to me how on the upgrade process univention-ox got removed ( Either because it is part of normal upgrade on versions change or because the process was interrupted). Regardless of the reason, we were able to SOLVE the problem with an updated version of python-ruamel.yaml for 32 bits on your repositories and through the sources list. The following commands were required
Hi,
I know this is an old post, but just wanted to add a cent worth. I did the same as rrley and added “sudo apt-get upgrade.” This worked for me. Upgrade if you need it only. After the CLI upgrade., I’ve did the we upgrade - worked fine without any issues.