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 -- Stephen Carr Computing Officer School of Civil and Environmental Engineering The University of Adelaide Tel +618-8303-4313 Fax +618-8303-4359 Email sgcarr@xxxxxxxxxxxxxxxxxxxxxx CRICOS Provider Number 00123M ----------------------------------------------------------- This email message is intended only for the addressee(s) and contains information that may be confidential and/or copyright. If you are not the intended recipient please notify the sender by reply email and immediately delete this email. Use, disclosure or reproduction of this email by anyone other than the intended recipient(s) is strictly prohibited. No representation is made that this email or any attachments are free of viruses. Virus scanning is recommended and is the responsibility of the recipient. ---- Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
