Hello,
I've got IMAP Server problem, I think to update dovecot and get this error.
Thank you.
cd /usr/local/directadmin/custombuild
./build update
./build dovecot
build dovecot back to 1.2.14 same error
Update, I deleted the master.pid file and tried to restart the Dovecot service. It worked, and the service came back up.
Problem solved.
I've got IMAP Server problem, I think to update dovecot and get this error.
Thank you.
cd /usr/local/directadmin/custombuild
./build update
./build dovecot
Code:
test -z "/usr/include/dovecot" || /bin/mkdir -p "/usr/include/dovecot"
make[2]: Leaving directory `/usr/local/directadmin/custombuild/dovecot-1.2.15'
make[1]: Leaving directory `/usr/local/directadmin/custombuild/dovecot-1.2.15'
Restarting dovecot.
Shutting down dovecot: [FAILED]
Starting dovecot: Fatal: Dovecot is already running with PID (read from /var/run/dovecot/master.pid)
[FAILED]
[root@server custombuild]#
build dovecot back to 1.2.14 same error
Code:
make[3]: Leaving directory `/usr/local/directadmin/custombuild/dovecot-1.2.14/doc'
make[2]: Leaving directory `/usr/local/directadmin/custombuild/dovecot-1.2.14/doc'
make[1]: Leaving directory `/usr/local/directadmin/custombuild/dovecot-1.2.14/doc'
make[1]: Entering directory `/usr/local/directadmin/custombuild/dovecot-1.2.14'
make[2]: Entering directory `/usr/local/directadmin/custombuild/dovecot-1.2.14'
test -z "/usr/lib/dovecot" || /bin/mkdir -p "/usr/lib/dovecot"
test -z "/etc" || /bin/mkdir -p "/etc"
/usr/bin/install -c -m 644 dovecot-example.conf '/etc'
test -z "/usr/include/dovecot" || /bin/mkdir -p "/usr/include/dovecot"
make[2]: Leaving directory `/usr/local/directadmin/custombuild/dovecot-1.2.14'
make[1]: Leaving directory `/usr/local/directadmin/custombuild/dovecot-1.2.14'
Restarting dovecot.
Shutting down dovecot: [FAILED]
Starting dovecot: Fatal: Dovecot is already running with PID (read from /var/run/dovecot/master.pid)
[FAILED]
[root@server custombuild]#
Update, I deleted the master.pid file and tried to restart the Dovecot service. It worked, and the service came back up.
Problem solved.
Last edited: