Re: systemd timeout on startup after upgrade

2021-04-17 Thread Jean-Daniel
> Le 18 avr. 2021 à 08:22, Felix Zielcke a écrit : > > Am Sonntag, dem 18.04.2021 um 08:17 +0200 schrieb Jean-Daniel: >> systemd don’t need pid files, and the executable must be started >> without forking. >> >> >> Can you show us the content fo the system dovecot.service file. As >> long as

Re: systemd timeout on startup after upgrade

2021-04-17 Thread Felix Zielcke
Am Sonntag, dem 18.04.2021 um 08:17 +0200 schrieb Jean-Daniel: > systemd don’t need pid files, and the executable must be started > without forking. > > > Can you show us the content fo the system dovecot.service file. As > long as it contains this line, it should be fine: > > Type=simple > Exec

Re: systemd timeout on startup after upgrade

2021-04-17 Thread Jean-Daniel
systemd don’t need pid files, and the executable must be started without forking. Can you show us the content fo the system dovecot.service file. As long as it contains this line, it should be fine: Type=simple ExecStart=/usr/sbin/dovecot -F > Le 18 avr. 2021 à 07:34, Felix Zielcke a écrit

Re: systemd timeout on startup after upgrade

2021-04-17 Thread Felix Zielcke
Am Sonntag, dem 18.04.2021 um 01:04 +0200 schrieb Łukasz Szczepański: > If systemd doesn't recognize that service has started, that mean > probably pid file has other location than previously. > You can check what systemd is doing via strace: > > strace -s 1024 systemctl start dovecot > strace d

Re: systemd timeout on startup after upgrade

2021-04-17 Thread Łukasz Szczepański
If systemd doesn't recognize that service has started, that mean probably pid file has other location than previously. You can check what systemd is doing via strace: strace -s 1024 systemctl start dovecot W dniu 17 kwi 2021, 19:39, o 19:39, użytkownik Felix Zielcke napisał: >Hello *, > >I ha

Re: systemd timeout on startup after upgrade

2021-04-17 Thread Steve Litt
Felix Zielcke said on Sat, 17 Apr 2021 19:37:30 +0200 >Hello *, > >I have upgraded today a Debian buster (stable) system to bullseye >(still testing). After upgrade I did a complete reboot of the VM. > >Dovecot version changed from 1:2.3.4.1-5+deb10u6 to 1:2.3.13+dfsg1-1 > >`systemctl start dovec

Re: failed: Cached message size smaller than expected

2021-04-17 Thread Michael Grant
On Fri, Apr 02, 2021 at 04:45:36PM -0400, Michael Grant wrote: > Every few days, my mailbox seizes up. No mail come in to my imap clients. > > I'm getting these errors over and over with my mailbox: > > Error: Mailbox INBOX: Deleting corrupted cache record uid=371208: UID > 371208: Broken phy

POP3 server fails to replicate deletions

2021-04-17 Thread Stephen Gildea
When I delete messages with POP3, the change doesn't get replicated. To reproduce: run the pop3 server from the command line, type this to it: DELE 1 QUIT This correctly deletes the first message on the local server, but it does not send a replication notify message. Poking around a bit with gd

systemd timeout on startup after upgrade

2021-04-17 Thread Felix Zielcke
Hello *, I have upgraded today a Debian buster (stable) system to bullseye (still testing). After upgrade I did a complete reboot of the VM. Dovecot version changed from 1:2.3.4.1-5+deb10u6 to 1:2.3.13+dfsg1-1 `systemctl start dovecot` now complains Job for dovecot.service failed because a time