I’ve just installed Centos 7 with Vitualmin and immediately dovecot was not running. So I reinstalled a fresh Centos 7 and did a clean install and I had the same problem. When I checked the mail log the error is… dovecot “Warning: Killed with signal 15”.
Can someone suggest how I might be able to resolve it?
Something killed it.
Could be the OOM killer (though I thought that would be a signal 9, but maybe it tries to kill it politely first, I dunno). Do you have enough memory? If you’re handling mail, especially if you’re using ClamAV, you need a lot more memory than a web only system. ClamAV, by itself, needs ~1GB.
No using ClamAV. Have 2GB ram. I have another vps with the same company and same install and it works perfectly.
Any suggestions on how I can debug and find the cause of the failure?
You’ll need to look for other clues in the log, I guess. If you aren’t stopping it, I don’t know why else it’d be getting a signal 15.
The service isn’t starting Joe. The error message occurs when I attempt to start Dovecot.
Scroll back through journalctl -xe for further clues. If it’s not starting, it’s probably a configuration problem.
-- Unit dovecot.service has begun starting up.
Apr 10 05:20:45 server1 dovecot[22877]: Fatal: Dovecot is already running? Socket already exists: /var/run/dovecot/login/login
Apr 10 05:20:45 server1 dovecot[22877]: master: Fatal: Dovecot is already running? Socket already exists: /var/run/dovecot/login/login
Apr 10 05:20:45 server1 systemd[1]: dovecot.service: control process exited, code=exited status=89
Apr 10 05:20:45 server1 systemd[1]: Failed to start Dovecot IMAP/POP3 email server.
-- Subject: Unit dovecot.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dovecot.service has failed.
--
-- The result is failed.
Apr 10 05:20:45 server1 systemd[1]: Unit dovecot.service entered failed state.
Apr 10 05:20:45 server1 systemd[1]: dovecot.service failed.
Socket already exists. Does this mean anything?
It means Dovecot is already running. Try restart instead of start. You may have to kill it manually, if systemd is confused about the PID(s).
[root@server1 ~]# /bin/systemctl restart dovecot.service
Job for dovecot.service failed because the control process exited with error code. See “systemctl status dovecot.service” and “journalctl -xe” for details.
[root@server1 ~]# journalctl -lxe
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit dovecot.service has failed.
--
-- The result is failed.
Apr 10 05:34:54 server1 systemd[1]: Unit dovecot.service entered failed state.
Apr 10 05:34:54 server1 systemd[1]: dovecot.service failed.
Apr 10 05:35:01 server1 systemd[1]: Started Session 290798 of user root.
-- Subject: Unit session-290798.scope has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit session-290798.scope has finished starting up.
--
[root@server1 ~]# /bin/systemctl status dovecot.service
* dovecot.service - Dovecot IMAP/POP3 email server
Loaded: loaded (/usr/lib/systemd/system/dovecot.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Fri 2020-04-10 05:34:54 EDT; 4min 13s ago
Docs: man:dovecot(1)
http://wiki2.dovecot.org/
Process: 23731 ExecStart=/usr/sbin/dovecot (code=exited, status=89)
Process: 23727 ExecStartPre=/usr/libexec/dovecot/prestartscript (code=exited, status=0/SUCCESS)
Apr 10 05:34:54 server1 systemd[1]: Starting Dovecot IMAP/POP3 email server...
Apr 10 05:34:54 server1 dovecot[23731]: Fatal: Dovecot is already running? Socket already exists: /var/run/dovecot/login/login
Apr 10 05:34:54 server1 systemd[1]: dovecot.service: control process exited, code=exited status=89
Apr 10 05:34:54 server1 systemd[1]: Failed to start Dovecot IMAP/POP3 email server.
Apr 10 05:34:54 server1 systemd[1]: Unit dovecot.service entered failed state.
Apr 10 05:34:54 server1 systemd[1]: dovecot.service failed.
Try
pkill -9 dovecot
… and then
systemctl start dovecot
No luck, but thanks.
[root@server1 ~]# pkill -9 dovecot
[root@server1 ~]# systemctl start dovecot
Job for dovecot.service failed because a timeout was exceeded. See “systemctl status dovecot.service” and “journalctl -xe” for details.
– The result is failed.
Apr 10 17:28:28 server1 systemd[1]: Unit dovecot.service entered failed state.
Apr 10 17:28:28 server1 systemd[1]: dovecot.service failed.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.