[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Dovecot Update Fails on Jessie [resolved]



Hi Roberto,

 

thanks for the careful testing.

 

I found a solution for the problem and I think it is a problem in the package (likely not introduced by your patch though). I think your testing went well, because you did not upgrade while dovecot was under heavy load, but in your test installation dovecot was probably idle.

 

I noticed that Dovecot started always immediately after stopping it again:

 

Aug 31 19:24:22 netcup systemd[1]: Activated swap /dev/vda1.
Aug 31 19:24:23 netcup systemd[1]:
Stopping Dovecot IMAP/POP3 email server...
Aug 31 19:24:23 netcup dovecot[12183]:
log: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Aug 31 19:24:23 netcup dovecot[12180]:
master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)
Aug 31 19:24:23 netcup systemd[1]: Starting Dovecot IMAP/POP3 email server...
Aug 31 19:24:23 netcup systemd[1]: Starting Dovecot IMAP/POP3 email server...

When looking careful at the output of

root@netcup:~# invoke-rc.d dovecot stop

Warning: Stopping dovecot.service, but it can still be activated by:

dovecot.socket

root@netcup:~#

 

it says dovecot can be activated again by dovecot.socket, when stopping dovecot the way the pre-rm script does it.

 

I then stopped dovecot.socket first and dovecot.service second:

 

root@netcup:~# systemctl stop dovecot.socket

root@netcup:~# systemctl stop dovecot.service

 

This really stops dovecot

 

root@netcup:~# systemctl status dovecot

● dovecot.service - Dovecot IMAP/POP3 email server

Loaded: loaded (/lib/systemd/system/dovecot.service; enabled)

Active: inactive (dead) since Sat 2019-08-31 19:27:16 CEST; 15s ago

Process: 20921 ExecStart=/usr/sbin/dovecot -F (code=exited, status=0/SUCCESS)

Main PID: 20921 (code=exited, status=0/SUCCESS)

 

Aug 31 19:26:53 netcup dovecot[20924]: imap-login: Login: user=<rd>, method=PLAIN, rip=78.43.40.8, lip=37.120.169.230, mpid=20944, TLS, session=<Aid0C22RGwBOKygI>

Aug 31 19:26:53 netcup dovecot[20924]: imap-login: Login: user=<rd>, method=PLAIN, rip=78.43.40.8, lip=37.120.169.230, mpid=20945, TLS, session=<wod0C22RHABOKygI>

Aug 31 19:26:53 netcup dovecot[20924]: imap-login: Login: user=<rd>, method=PLAIN, rip=78.43.40.8, lip=37.120.169.230, mpid=20948, TLS, session=<cqx1C22ReQBOKygI>

Aug 31 19:26:53 netcup dovecot[20924]: imap-login: Login: user=<rd>, method=PLAIN, rip=78.43.40.8, lip=37.120.169.230, mpid=20949, TLS, session=<BaF2C22R1gBOKygI>

Aug 31 19:26:53 netcup dovecot[20924]: imap-login: Login: user=<rd>, method=PLAIN, rip=78.43.40.8, lip=37.120.169.230, mpid=20950, TLS, session=<ChZ3C22RqQBOKygI>

Aug 31 19:26:53 netcup dovecot[20924]: imap-login: Login: user=<rd>, method=PLAIN, rip=78.43.40.8, lip=37.120.169.230, mpid=20951, TLS, session=<+yZ3C22R2ABOKygI>

Aug 31 19:26:53 netcup dovecot[20924]: imap-login: Login: user=<rd>, method=PLAIN, rip=78.43.40.8, lip=37.120.169.230, mpid=20952, TLS, session=<nq13C22RIQBOKygI>

Aug 31 19:27:16 netcup systemd[1]: Stopping Dovecot IMAP/POP3 email server...

Aug 31 19:27:16 netcup dovecot[20921]: master: Warning: Killed with signal 15 (by pid=1 uid=0 code=kill)

Aug 31 19:27:16 netcup systemd[1]: Stopped Dovecot IMAP/POP3 email server.

root@netcup:~#

 

Now the upgrade went through flawless:

 

root@netcup:~# apt-get -f install

Reading package lists... Done

Building dependency tree

Reading state information... Done

Correcting dependencies... Done

The following extra packages will be installed:

dovecot-imapd dovecot-managesieved

The following packages will be upgraded:

dovecot-imapd dovecot-managesieved

2 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

5 not fully installed or removed.

Need to get 0 B/1,218 kB of archives.

After this operation, 0 B of additional disk space will be used.

Do you want to continue? [Y/n]

Retrieving bug reports... Done

Parsing Found/Fixed information... Done

Reading changelogs... Done

(Reading database ... 93995 files and directories currently installed.)

Preparing to unpack .../dovecot-imapd_1%3a2.2.13-12~deb8u7_amd64.deb ...

Unpacking dovecot-imapd (1:2.2.13-12~deb8u7) over (1:2.2.13-12~deb8u6) ...

Preparing to unpack .../dovecot-managesieved_1%3a2.2.13-12~deb8u7_amd64.deb ...

Unpacking dovecot-managesieved (1:2.2.13-12~deb8u7) over (1:2.2.13-12~deb8u6) ...

Setting up libsvn1:amd64 (1.8.10-6+deb8u7) ...

Setting up dovecot-core (1:2.2.13-12~deb8u7) ...

Setting up dovecot-imapd (1:2.2.13-12~deb8u7) ...

Setting up dovecot-sieve (1:2.2.13-12~deb8u7) ...

Setting up dovecot-lucene (1:2.2.13-12~deb8u7) ...

Setting up subversion (1.8.10-6+deb8u7) ...

Processing triggers for dovecot-core (1:2.2.13-12~deb8u7) ...

Setting up dovecot-managesieved (1:2.2.13-12~deb8u7) ...

Processing triggers for libc-bin (2.19-18+deb8u10) ...

Processing triggers for dovecot-core (1:2.2.13-12~deb8u7) ...

root@netcup:~#

 

Many thanks again Roberto and Mike for looking into that and helping to get the issue resolved.

 

Rainer

 

 

 

Am Samstag, 31. August 2019, 14:36:35 CEST schrieb Roberto C. Sánchez:

> On Sat, Aug 31, 2019 at 09:52:47AM +0200, Rainer Dorsch wrote:

> > Hi Roberto,

> >

> >  

> >

> > thanks, for the quick reply.

> >

> >  

>

> I carefully reviewed the additional output you provided. I also created

> a new jessie VM installed deb8u6 versions of dovecot-core,

> dovecot-imapd, dovecot-lucene, dovecot-managesieved, and dovecot-sieve

> then upgraded to the deb8u7 version. The stop/start worked correctly

> and no errors were printed to the console nor did any appear in the

> logs.

>

> It seems most likely that in this case there is a system-specific issue

> with either your configuration, runtime environment, etc. that is

> causing the unexpcted failure.

>

> I'm sorry I can't be more helpful.

>

> Regards,

>

> -Roberto

 

 

--

Rainer Dorsch

http://bokomoko.de/


Reply to: