Hi, thanks for reporting this bug, iirc it's more an issue in dovecot.
Assigned to the package maintainer. (or a padawan, I don't know)

(Please set the status to 'assigned' if you are working on it)

Keywords: (none) => Triaged
Assignee: bugsquad => stormi
Source RPM: systemd-37-17.mga2.src.rpm => dovecot

(In reply to comment #1)
> Hi, thanks for reporting this bug, iirc it's more an issue in dovecot.

You might be right, but source packages appear to be the same as Mandriva's
Source rpm: dovecot-1.2.17-1.mga2.src.rpm
Source rpm: dovecot-1.2.17-1.src.rpm

both installs have a /var/run/dovecot/master.pid after startup.

Just fixed on svn. Please test next dovecot rpm.

Status: NEW => RESOLVED
CC: (none) => dmorganec
Resolution: (none) => FIXED

Dec 21 01:57:57 localhost perl: [RPM] dovecot-1.2.17-2.mga2.x86_64 installed
Dec 21 01:58:00 localhost perl: [RPM] dovecot-1.2.17-1.mga2.x86_64 removed

# shutdown -r now

Dec 21 02:03:33 localhost systemd[1]: Failed to read PID file /var/run/dovecot after start.


Test procedure is really hard:

urpmi dovecot
service dovecot restart
grep dovecot /var/log/messages

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

(In reply to comment #3)
> Just fixed on svn. Please test next dovecot rpm.

Still broke.
      Install rpm: dovecot-1.2.17-2.mga2
      Source rpm: dovecot-1.2.17-2.mga2.src.rpm


dovecot needs a /lib/systemd/system/dovecot.service file.
If it does not exist, will delay system boot completion for 5 minutes or more.

Suggested /lib/systemd/system/dovecot.service follows:
[Unit]
Description=Dovecot IMAP/POP3 email server
After=local-fs.target network.target

[Service]
Type=simple
ExecStart=/usr/sbin/dovecot -F
NonBlocking=yes

[Install]
WantedBy=multi-user.target

clean beta1 install does not have the problem.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED

No idea what happened. I even removed/installed it again and still broke.


Feb 24 02:56:13 wb2 dovecot[2898]: 
Starting IMAP daemon (dovecot): If you have trouble with authentication failures,
: enable auth_debug setting. See http://wiki.dovecot.org/WhyDoesItNotWork
: This message goes away after the first successful login.
Feb 24 02:56:13 wb2 dovecot[2898]dovecot[2898]: [  OK  ]
Feb 24 02:56:13 wb2 systemd[1]: PID file /var/run/dovecot not readable (yet?) after start.
Feb 24 03:01:13 wb2 systemd[1]: dovecot.service operation timed out. Terminating.
systemd[1]: Unit dovecot.service entered failed state.

# ll /var/run/dovecot
total 8
srw------- 1 root root       0 Feb 24 02:56 auth-worker.2952
srwxrwxrwx 1 root root       0 Feb 24 02:56 dict-server
lrwxrwxrwx 1 root root      17 Feb 24 02:56 dovecot.conf -> /etc/dovecot.conf
drwxr-x--- 2 root dovecot 4096 Feb 24 02:56 login
-rw------- 1 root root       5 Feb 24 02:56 master.pid

Severity: normal => major
Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

This problem is simply that the pidfile: header of the LSB initscript contains bogus details.

It states:
# pidfile: /var/run/dovecot

But when dovecot is started it writes it's pid to:
/var/run/dovecot/master.pid

Changing the LSB script is trivial and should avoid this problem.

I've pushed an updated package and it seems to start/stop fine here without any delay.

CC: (none) => mageia
Status: REOPENED => RESOLVED
Resolution: (none) => FIXED