Fatal error on Virtualmin pro installation because of Dovecot

Submitted by jfquestiaux on Thu, 01/27/2011 - 14:07

Hello,

I am trying to install Virtualmin on a new server but the installation failed apparently because of something called Dovecot.

Here is the log :

Displaying the last 15 lines of /root/virtualmin-install.log to help troubleshoot this problem: dpkg: dependency problems prevent configuration of virtualmin-base: 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 mailx (1:20071201-3) ... Errors were encountered while processing: dovecot-common dovecot-imapd dovecot-pop3d virtualmin-base

I have no idea what to do. Hope you can help. Best regards

Status: 
Closed (fixed)

Comments

Submitted by andreychek on Thu, 01/27/2011 - 14:12

Howdy -- what happens if you run this command:

apt-get install dovecot-common dovecot-imapd dovecot-pop3d

Is apt able to install those three packages, or do you get an error of some kind?

Submitted by jfquestiaux on Thu, 01/27/2011 - 15:04

Hello there.

Thank you. I was able to install the three packages with your command. So I guess I will try the install again now...

Submitted by andreychek on Thu, 01/27/2011 - 15:09

Great! Let us know if that does the trick.

I'm not sure why it would have gotten hung up there. If your installation is successful this time around, we'll run a few tests with the install.sh here to see what might have caused that.

Submitted by jfquestiaux on Thu, 01/27/2011 - 15:14

Am I supposed to get a final "success" message ? In the Terminal, I am back with the prompt and the last thing done in the installation was Updating SpamAssassin rules.

Is is done ?

Submitted by andreychek on Thu, 01/27/2011 - 15:17

Actually, that sounds like it worked well.

It would typically only say something if it fails.

The SpamAssassin rule updates are the last piece of the installation, so you should be in good shape!

Try browsing to https://your_server.tld:10000, and see if you can log in as root.

Submitted by jfquestiaux on Thu, 01/27/2011 - 15:23

Yes, I am logged in (thanks for telling me to log as "root" - I did not know what to use and it is not specified in the documentation).

Have a good day. Jean-Francois

Submitted by andreychek on Fri, 01/28/2011 - 11:57

We're looking to do some testing to try and reproduce the issue you saw. We'd like to mimic your setup as closely as possible.

Which architecture was it you had installed on your system -- were you using i386 or amd64?

Also, did you recall if you used the small "netinstall" image to perform your install, or if you used a full set of CD's/DVD's?

Thanks!

Submitted by jfquestiaux on Fri, 01/28/2011 - 12:53

Hello,

I am afraid I won't be able to help you much. I have installed Virtualmin on a Virtual hosting providing by a French Hosting company (Gandi - http://www.gandi.net), so I have no precise information on the hardware. The only thing I can tell you is this : Linux serv01.virtualmin.com 2.6.32-xenU-3831-x86_64 #12 SMP Tue Oct 12 18:07:01 CEST 2010 x86_64 - the distribution is a Debian 5 64 bits.

To instal the OS, I used the image available at the hosting company, so I don't know what's in it.

Sorry to be so vague...

Submitted by JamieCameron on Fri, 01/28/2011 - 13:04

One possibility to consider is that some repositories were missing from /etc/apt/sources.list when the original install was done. This can cause some packages (like dovecot) to not be available..

Submitted by andreychek on Fri, 01/28/2011 - 13:40

That helps a lot, actually -- as it shows that you're using the amd64 architecture.

What I'll do is perform a run-through of Debian 5 on amd64... if we run into problems, we'll get them resolved. If we don't -- as Jamie mentioned, it may be related to something specific to the installation of your provider. It may be hard to track that down now -- though now that you have it working, it may not matter so much :-)

Thanks for your help, and have a good weekend!

Submitted by jfquestiaux on Fri, 01/28/2011 - 13:45

It's true that now it is working, but it is always good to know why things went wrong.

Have a good week-end too.

Submitted by andreychek on Fri, 01/28/2011 - 13:51

Actually, the one other question I have for you as I prepare for a Debian 5 installation here -- how much RAM and swap is in your system?

You can determine that by running the command "free -m".

We've occasionally seen strange issues with systems that have low amounts of memory -- though not typically on Xen-based systems like yours.

Submitted by jfquestiaux on Fri, 01/28/2011 - 14:15

Here you go :

Mem: total : 496 used 352 free : 144

Swap:
total 619
used 39
free 580

Submitted by andreychek on Fri, 01/28/2011 - 15:24

Okay, I performed an installation of Virtualmin using the install.sh script onto a server running Debian 5 on amd64, with 512MB of RAM.

It worked without a problem, and correctly installed the Dovecot packages.

So it looks like you may be seeing something specific to your setup there. Unfortunately, it's not really possible to determine what the cause was without starting over and monitoring the installation.

Down the road, if you ever end up performing a fresh Virtualmin install onto a new server by that same provider -- let us know and we can help with the installation :-)

Submitted by Issues on Fri, 02/11/2011 - 17:19

Automatically closed -- issue fixed for 2 weeks with no activity.