vm-Pop3D bug on fresh install?? Dovecot is installed

[Richard G]

I had to reinstall a server this night due to a harddisk crash. No problem there.

However, after the installation on the system information it says:

vm-Pop3d *** Stopped ***

While it should say:

dovecot 2.2.19 Running

How can I fix this? I don't run any vm-pop3d and on the service monitor, dovecot is shown as running.

Looks to me this is a bug.
This is on a Centos 6.7 server.

 

[DirectAdmin Support]

Which version of CustomBuild?

The "directadmin i" command should read the options.conf and look for:

dovecot=yes

and set that in the services.status file.
Check to ensure you have that set in your options.conf file, and see what your services.status file has in it.

John

 

[Richard G]

Sorry, I forgot to mention it. This is custombuild 2.0, which is option 1 on a new setup.

/usr/local/directadmin/custombuild]# directadmin i
-bash: directadmin: command not found

So I tried:

/usr/local/directadmin/directadmin i

The config file already exists:
/usr/local/directadmin/conf/directadmin.conf

Do you really want to install DirectAdmin again? (y/n): n

Seems the directadmin i command wants to install DA again and not display the options.conf.

So I manually looked into options.conf and it says dovecot=yes in there. I checked services.status and it says:

da-popb4smtp=ON
directadmin=ON
dovecot=ON
exim=ON
httpd=ON
mysqld=ON
named=ON
pure-ftpd=ON
sshd=ON

Looks correct to me. I also restarted DA but the vm-pop3d notice is still there.

 

[Richard G]

Oke this is odd.

The options.conf says "dovecot=yes".
But directadmin c (which is the correct command) says dovecot=0.

 

[Richard G]

I did a ./build dovecot again and now it's fixed.
So it's not a bug. I wonder though how or why this could happen in the first place. Just curiousity.

 

[DirectAdmin Support]

The directadmin.conf has a "dovecot=1" value.
CustomBuild will set this to 1 after the compile is done (it also sets the directadmn.conf template, in case of a re-run of ./directadmin i)

So my guess would be if an update.tar.gz is re-downlaoded / extracted, that reset the directadmin.conf template to not have dovecot=1.
And then, if ./directadmin i is run (or the directadmin.conf template copied over), it will put the directadmin.conf back to dovecot=0, until ./build dovecot is run again.

John

 

[Richard G]

That might indeed have been the case. The update.tar.gz was not redownloaded by me, but I did run the ./setup.sh again due to mysql problems which were caused because downgrading did not succeed. That's why I did the complete reinstall.

Glad it's solved. Thank you!