Hello,
Is anyone running Dovecot on either a Fedora 20 or 21 system? I'm having an issue, on a system reboot, which I admit does not happen often, Dovecot fails to start in the systemctl list, output is status failed. The issue seems to be Dovecot can not bind to the ipv6 address. Now later if I manually log in to the box and start dovecot it works just fine no problems. I've googled and seen similar issues to this. Does anyone have a solution?
Thanks. Dave.
Hello Dave,
Are you using NetworkManager or /etc/init.d/network to set up your network interfaces ?
Le 10/01/2015 19:34, David Mehler a écrit :
Hello,
Is anyone running Dovecot on either a Fedora 20 or 21 system? I'm having an issue, on a system reboot, which I admit does not happen often, Dovecot fails to start in the systemctl list, output is status failed. The issue seems to be Dovecot can not bind to the ipv6 address. Now later if I manually log in to the box and start dovecot it works just fine no problems. I've googled and seen similar issues to this. Does anyone have a solution?
Thanks. Dave.
On 10.01.2015 19:34, David Mehler wrote:
Hello,
Is anyone running Dovecot on either a Fedora 20 or 21 system? I'm having an issue, on a system reboot, which I admit does not happen often, Dovecot fails to start in the systemctl list, output is status failed. The issue seems to be Dovecot can not bind to the ipv6 address. Now later if I manually log in to the box and start dovecot it works just fine no problems. I've googled and seen similar issues to this. Does anyone have a solution?
Sounds like Dovecot just starts too early. Before the v6 interface is ready. You should be able to either define dependencies or delays in systemctl, right?
Michael
Am 10.01.2015 um 19:34 schrieb David Mehler:
Is anyone running Dovecot on either a Fedora 20 or 21 system?
surely
having an issue, on a system reboot, which I admit does not happen often, Dovecot fails to start in the systemctl list, output is status failed. The issue seems to be Dovecot can not bind to the ipv6 address. Now later if I manually log in to the box and start dovecot it works just fine no problems. I've googled and seen similar issues to this. Does anyone have a solution?
you could avoid that by have it loisten on the global IP (0.0.0.0 for ipv4 and ::: for ipv6) instead configure a specific IP for the service, otherwise you need to make sure ordering with After= or Before= in the systemd-units
[root@srv-rhsoft:~]$ cat /usr/lib/systemd/system/dovecot.service [Unit] Description=Dovecot IMAP/POP3 Proxy After=network.service systemd-networkd.service network-online.target dbmail-imapd.service dbmail-pop3d.service mysqld.service mysqld-dbmail.service Before=postfix.service
[Service] Type=simple ExecStart=/usr/sbin/dovecot -F Environment="LANG=en_GB.UTF-8" NonBlocking=yes Restart=always RestartSec=1 PrivateTmp=true CapabilityBoundingSet=CAP_CHOWN CAP_DAC_OVERRIDE CAP_IPC_LOCK CAP_KILL CAP_NET_BIND_SERVICE CAP_SETGID CAP_SETUID CAP_SYS_CHROOT ReadOnlyDirectories=/etc ReadOnlyDirectories=/usr ReadOnlyDirectories=/proc ReadOnlyDirectories=/sys ReadOnlyDirectories=/var/lib ReadWriteDirectories=/var/lib/dovecot InaccessibleDirectories=/boot InaccessibleDirectories=/home InaccessibleDirectories=/media InaccessibleDirectories=/root InaccessibleDirectories=/run/console InaccessibleDirectories=/run/dbus InaccessibleDirectories=/run/lock InaccessibleDirectories=/run/mount InaccessibleDirectories=/run/systemd/generator InaccessibleDirectories=/run/systemd/system InaccessibleDirectories=/run/systemd/users InaccessibleDirectories=/run/udev InaccessibleDirectories=/run/user InaccessibleDirectories=/usr/local/scripts InaccessibleDirectories=/var/lib/rpm InaccessibleDirectories=/var/lib/yum InaccessibleDirectories=/var/lib/dbus InaccessibleDirectories=/var/lib/systemd
[Install] WantedBy=multi-user.target
participants (4)
-
David Mehler
-
Hoggins!
-
Michael
-
Reindl Harald