[Akonadi] [Bug 322199] New: akonadi_imap spams perdition log when two clients are active and gets restarted all the time

[Martin Steigerwald]

https://bugs.kde.org/show_bug.cgi?id=322199

            Bug ID: 322199
           Summary: akonadi_imap spams perdition log when two clients are
                    active and gets restarted all the time
    Classification: Unclassified
           Product: Akonadi
           Version: 4.10
          Platform: Debian unstable
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: IMAP resource
          Assignee: ervin at kde.org
          Reporter: ms at teamix.de
                CC: kdepim-bugs at kde.org, vkrause at kde.org

Hi! I migrated KDEPIM from 4.4.11 to 4.10.4 yesterday in my workstation. Today
a co-worker reported that my IMAP clients spam our perdition IMAP proxy logs
with

Jul 10 16:29:25 rproxy perdition.imaps[15127]: Fatal Error reading
authentication information from client clientip:51242->serverip:993: Exiting
child

Reproducible: Always

Steps to Reproduce:
It does only seem to happen when two instances of my Akonadi are running - one
on laptop and one on workstation (both with local MySQL databases)

1. Have two Akonadiserver with IMAP resource pointed to the same perdition
server
2. Monitor perdition log (/var/log/syslog in Debian)

Actual Results:  
I get this:

Jul 10 16:29:25 rproxy perdition.imaps[15127]: Fatal Error reading
authentication information from client clientip:51242->serverip:993: Exiting
child
Jul 10 16:29:25 rproxy perdition.imaps[15129]: Connect: 
clientip:51244->serverip:993
Jul 10 16:29:25 rproxy perdition.imaps[15128]: Fatal Error reading
authentication information from client clientip:51243->serverip:993: Exiting
child
Jul 10 16:29:25 rproxy perdition.imaps[15130]: Connect: 
clientip:51245->serverip:993
Jul 10 16:29:25 rproxy perdition.imaps[15129]: Fatal Error reading
authentication information from client clientip:51244->serverip:993: Exiting
child
Jul 10 16:29:25 rproxy perdition.imaps[15131]: Connect: 
clientip:51246->serverip:993
Jul 10 16:29:25 rproxy perdition.imaps[15130]: Fatal Error reading
authentication information from client clientip:51245->serverip:993: Exiting
child
Jul 10 16:29:25 rproxy perdition.imaps[15132]: Connect: 
clientip:51247->serverip:993
Jul 10 16:29:25 rproxy perdition.imaps[15131]: Fatal Error reading
authentication information from client clientip:51246->serverip:993: Exiting
child
Jul 10 16:29:25 rproxy perdition.imaps[15133]: Connect: 
clientip:51248->serverip:993
Jul 10 16:29:25 rproxy perdition.imaps[15132]: Fatal Error reading
authentication information from client clientip:51247->serverip:993: Exiting
child
Jul 10 16:29:25 rproxy perdition.imaps[15134]: Connect: 
clientip:51249->serverip:993
Jul 10 16:29:25 rproxy perdition.imaps[15133]: Fatal Error reading
authentication information from client clientip:51248->serverip:993: Exiting
child
Jul 10 16:29:25 rproxy perdition.imaps[15135]: Connect: 
clientip:51250->serverip:993
Jul 10 16:29:25 rproxy perdition.imaps[15134]: Fatal Error reading
authentication information from client clientip:51249->serverip:993: Exiting
child


On client netstat -anpe shows that port numbers of akonadi_imap resource are
changing rapidly. It seems to get restarted all the time.

Another indication that this is happening is:

ms at mango:~/.local/share/akonadi> cat akonadi_control.error.old
ProcessControl: Application /usr/bin/akonadi_imap_resource stopped unexpectedly
( "Process crashed" )

(I also got a akonadi_control.error that had the same, but this got deleted
again)



Expected Results:  
Some rare occurences of:

Jul 10 16:59:33 rproxy perdition.imaps[15174]: Auth:
clientip:53966->servierip:993 client-secure=ssl authorisation_id=NONE
authentication_id="my at mail.adress" server="zimbraserverip:7143" protocol=IMAP4
server-secure=plaintext status="ok"

Akonadi resource uses same client port and is running for as long as session is
running.

We use perdition 1.19~rc4-2 on Debian Squeeze 6.0.7 with Zimbra Collaboration
Server (ZCS) 8.0.4.

Akonadi version on Debian Sid/Experimental client is: 1.9.2-2


I have seen website regarding Akonadi IMAP logging. But no time right now. Next
week I hold a training, so can take a while till I can get back to this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.