So, I’ve been trying to install virtualmin all day, but I’m still a noob (that’s probably not going to change for awhile)
This is a part of my log:
The following packages have unmet dependencies:
apache2 : Depends: apache2-mpm-worker (= 2.2.16-6) but it is not going to be installed or
apache2-mpm-prefork (= 2.2.16-6) but 2.2.16-6+squeeze1 is to be installed or
apache2-mpm-event (= 2.2.16-6) but it is not going to be installed or
apache2-mpm-itk (= 2.2.16-6) but it is not going to be installed
Depends: apache2.2-common (= 2.2.16-6) but 2.2.16-6+squeeze1 is to be installed
FATAL - 2011-05-29 16:09:40 - Fatal Error Occurred: Something went wrong during installation: 0
FATAL - 2011-05-29 16:09:40 - Cannot continue installation.
FATAL - 2011-05-29 16:09:40 - Attempting to remove virtualmin repository configuration, so the installation can be
FATAL - 2011-05-29 16:09:40 - re-attempted after any problems have been resolved.
FATAL - 2011-05-29 16:09:40 - Removing temporary directory and files.
FATAL - 2011-05-29 16:09:40 - If you are unsure of what went wrong, you may wish to review the log
FATAL - 2011-05-29 16:09:40 - in /root/virtualmin-install.log
Any help would be appreciated, even suggestions
Information you might need to know?:
Running Debian 6.0 64-bit
Installed a fresh copy then tried, still same problem
512mb Ram… 501mb free
anything else?
After that, then try performing your Virtualmin installation again.
Hi
I have the same issue (Debian 6 x86) and when run:
apt-get install apache2 apache2-mpm-prefork
have the same error message:
root@server11:~# apt-get install apache2 apache2-mpm-prefork
Reading package lists… Done
Building dependency tree
Reading state information… Done
apache2-mpm-prefork is already the newest version.
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:
The following packages have unmet dependencies:
apache2 : Depends: apache2-mpm-worker (= 2.2.16-6) but it is not going to be installed or
apache2-mpm-prefork (= 2.2.16-6) but 2.2.16-6+squeeze1 is to be installed or
apache2-mpm-event (= 2.2.16-6) but it is not going to be installed or
apache2-mpm-itk (= 2.2.16-6) but it is not going to be installed
Depends: apache2.2-common (= 2.2.16-6) but 2.2.16-6+squeeze1 is to be installed
E: Broken packages
root@server11:~#
root@server11:~# dpkg -l ‘apache*’
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Description
++±=========================-=========================-==================================================================
un apache (no description available)
un apache-common (no description available)
un apache-utils (no description available)
un apache2 (no description available)
un apache2-common (no description available)
ii apache2-doc 2.2.16-6+squeeze1 Apache HTTP Server documentation
un apache2-mpm (no description available)
un apache2-mpm-event (no description available)
un apache2-mpm-itk (no description available)
ii apache2-mpm-prefork 2.2.16-6+squeeze1 Apache HTTP Server - traditional non-threaded model
un apache2-mpm-worker (no description available)
un apache2-suexec (no description available)
un apache2-suexec-custom (no description available)
ii apache2-utils 2.2.16-6+squeeze1 utility programs for webservers
ii apache2.2-bin 2.2.16-6+squeeze1 Apache HTTP Server common binary files
ii apache2.2-common 2.2.16-6+squeeze1 Apache HTTP Server common files
root@server11:~#
I’ve never seen any such problems on a fresh Ubuntu install. Are you using an “official” version of Debian, and the official/correct repositories? Did you install anything before executing the Virtualmin installer? Is your server by chance an OpenVZ container or something comparable?
There have been many reports about problems on OpenVZ in the past, so it is a safe assumption that it might be involved here somehow too. Often memory restrictions / usage of “burst memory” (where applications can get killed without warning) have been the cause.
My suggestion would be checking the corresponding OpenVZ parameters, or trying out your Debian 6 installation process on a more reliable virtualization platform, like VMWare, for comparison and fault localization (to see if it an issue related to OpenVZ, Debian 6, or the combination).
Virtualmin installs perfectly on Ubuntu 10.04, done that many times. On VMWare though, but I suppose if you increase the “guaranteed memory” a bit, it should work on OpenVZ too.
