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