installation failure on Debian 5.0

5 posts / 0 new
Last post
#1 Sat, 03/06/2010 - 11:35
pridebook

installation failure on Debian 5.0

Hi,

On a fresh install of Debian 5.0 - the wget of the GPL installer is the first thing I do (I have repeated this process a few times...)

This is a Debain 5.0 VPS at Rackspace.

I get this error whether or not I run an apt-get update, apt-get upgrade...

Not sure what my solution is here... Thanks Rob

Extracting templates from packages: 100%
-[ 336.728122] ip_tables: (C) 2000-2006 Netfilter Core Team
INFO - /usr/bin/apt-get --config-file apt.conf.noninteractive -y --force-yes install postfix postfix-pcre webmin usermin ruby libapache2-mod-ruby libxml-simple-perl libcrypt-ssleay-perl unzip zip: Succeeded.
INFO - Succeeded.
INFO - Installing Virtualmin and all related packages now using the command:
INFO - /usr/bin/apt-get --config-file apt.conf.noninteractive -y --force-yes install virtualmin-base
...in progress, please wait...
Extracting templates from packages: 100%
Extracting templates from packages: 100%
INIT: version 2.86 reloading
-[ 607.320669] warning: `proftpd' uses 32-bit capabilities (legacy support in use)
\E: Sub-process /usr/bin/dpkg returned an error code (1)
/usr/bin/apt-get --config-file apt.conf.noninteractive -y --force-yes install virtualmin-base failed. Error (if any): 0

Displaying the last 15 lines of /root/virtualmin-install.log to help troubleshoot this problem:
virtualmin-base depends on dovecot-common; however:
Package dovecot-common is not configured yet.
virtualmin-base depends on dovecot-imapd; however:
Package dovecot-imapd is not configured yet.
virtualmin-base depends on dovecot-pop3d; however:
Package dovecot-pop3d is not configured yet.
dpkg: error processing virtualmin-base (--configure):
dependency problems - leaving unconfigured
Setting up xml-core (0.12) ...
Setting up mailx (1:20071201-3) ...
Errors were encountered while processing:
dovecot-common
dovecot-imapd
dovecot-pop3d
virtualmin-base

FATAL - Fatal Error Occurred: Installation failed: 0
FATAL - Cannot continue installation.
FATAL - Attempting to remove virtualmin repository configuration, so the installation can be
FATAL - re-attempted after any problems have been resolved.
FATAL - Removing temporary directory and files.
FATAL - If you are unsure of what went wrong, you may wish to review the log
FATAL - in /root/virtualmin-install.log
xxx:~#

Sun, 03/07/2010 - 04:38
husskii

hi if you can Display the last 15 lines of /root/virtualmin-install.log it would probably help someone help you...

also if its a fresh install and you have nothing on it, I would suggest maybe getting a new clean install, run updates and upgrades, then try reinstall vmin..

I also ruin vmin on a vps have one in 32bit and 64bit, and have never come across this before..

Just to know you dnt have anything like LAMP etc installed, because that will cause conflicts, I had once tried to install after I installed LAMP and found it wouldnt work, but I cant remember what the error was...

Sun, 03/07/2010 - 05:27
husskii

hi if you can Display the last 15 lines of /root/virtualmin-install.log it would probably help someone help you...

also if its a fresh install and you have nothing on it, I would suggest maybe getting a new clean install, run updates and upgrades, then try reinstall vmin..

I also ruin vmin on a vps have one in 32bit and 64bit, and have never come across this before..

Just to know you dnt have anything like LAMP etc installed, because that will cause conflicts, I had once tried to install after I installed LAMP and found it wouldnt work, but I cant remember what the error was...

***EDIT********* I actually just had the same problem a few mins ago on a clean install lol... what I found is because this time I ran apt-get update first, it stuffed the install, (dnt ask me why lol) anyways i deleted my vps and recreated it, this time not running update and installing vmin first.. all worked as normal from there..

its prob not the solution but its worth at try """IT WORKED FOR ME :)"""""

Mon, 03/08/2010 - 13:55 (Reply to #3)
Joe
Joe's picture

I actually just had the same problem a few mins ago on a clean install lol... what I found is because this time I ran apt-get update first, it stuffed the install, (dnt ask me why lol) anyways i deleted my vps and recreated it, this time not running update and installing vmin first.. all worked as normal from there..

Thanks for mentioning this. I may be able to reproduce the problem with this information (which means I can fix it, or report a bug upstream so Debian can fix it, if it's a problem in their Dovecot packages).

--

Check out the forum guidelines!

Sat, 12/28/2013 - 13:32
wocul

this still seems to be the case, I have seen it happening whenever I updated the system first, on all debian-based distros I tried (including 4.0, 6.0 and 7.0).

Topic locked