Sieve Sync_client 2.4.5 Lost connection to client -- exiting

[Bron Gondwana]

On Thu, Dec 09, 2010 at 09:51:53PM +1030, Stephen Carr wrote:
> Dear All
> 
> This is another problem after upgrading from 2.3.16.
> 
> The cause is I have 140+ scripts in a support account that sends a copy 
> of the email from Bacula to the user of the laptop / workstation 
> regarding the status of their backup - it is their data being backed up 
> an their responsibility to check the status (I hope).
> 
> In 2.3.16 the sync_client would die and a cron job would restart it 
> within 5 minutes
> 
> In 2.4.5 the sync_client does not die but generates errors - see below.
> 
> Temporary fix is to kill the sync_client and the cron job will restart 
> it with in5 minutes and all is OK.
> 
> Is there a fix?
> 
> Thanks again
> Stephen Carr
> 
> Dec  9 21:29:34 brooks sieve[25783]: Lost connection to client -- exiting
> Dec  9 21:29:54 brooks sieve[22338]: Lost connection to client -- exiting
> Dec  9 21:29:55 brooks sieve[23074]: Lost connection to client -- exiting
> Dec  9 21:30:18 brooks sieve[24589]: Lost connection to client -- exiting
> Dec  9 21:30:21 brooks sieve[24759]: Lost connection to client -- exiting
> Dec  9 21:30:22 brooks sync_client[25594]: Error in do_sync(): bailing 
> out! System I/O error
> Dec  9 21:30:22 brooks sync_client[25594]: Processing sync log file 
> /common/imap/sync/log-25594 failed: System I/O error
> Dec  9 21:30:23 brooks sync_client[25594]: Error in do_sync(): bailing 
> out! System I/O error
> Dec  9 21:30:23 brooks sync_client[25594]: Processing sync log file 
> /common/imap/sync/log-25594 failed: System I/O error
> Dec  9 21:30:23 brooks sync_client[25594]: Error in do_sync(): bailing 
> out! System I/O error
> Dec  9 21:30:23 brooks sync_client[25594]: Processing sync log file 
> /common/imap/sync/log-25594 failed: System I/O error
> Dec  9 21:30:24 brooks sync_client[25594]: Error in do_sync(): bailing 
> out! System I/O error

Eep - what on earth is going on with that mailbox?  Wha is the replica
saying?

It looks like we need more debugging information in sync client to say
what the IO error was caused by!

Bron.