> Means your client has dropped out 'uncleanly'. Its a harmless log message, and if you're logging at LOG_DEBUG you should expect to see a lot of harmless log messages.
Sure. However I have noted that I "only" see this when my client dies, not when it exits.. [!]
In the next version of cyrus we've turned off logging for "socket is not connected" totally.
> Shut down Cyrus and let incoming queue and users cry. > ctl_cyrusdb -r > reconstruct > Start Cyrus back up. You shouldn't ever need to reconstruct unless a mailbox is corrupted (And that can be done live). ctl_cyrusdb -r should *always* be run becfore cyrus starts (it should be in the START section of master.conf).
Ok, so what would you make of this;;
Jun 5 23:17:54 core imapd[4579]: DBERROR: error fetching user.oddjob: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 5 23:18:28 core imapd[4579]: DBERROR: error fetching user.oddjob: cyrusdb error
Jun 5 23:19:31 core imapd[4579]: DBERROR: error closing: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 5 23:19:31 core imapd[4579]: DBERROR: error closing mailboxes: cyrusdb error
Jun 5 23:19:31 core imapd[4579]: DBERROR: error exiting application: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 5 23:19:31 core imapd[4579]: DBERROR: error exiting application: cyrusdb error
Jun 5 23:19:33 core imapd[4601]: DBERROR: error closing: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 5 23:19:33 core imapd[4601]: DBERROR: error closing mailboxes: cyrusdb error
Jun 5 23:19:33 core imapd[4601]: DBERROR: error exiting application: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 5 23:19:33 core imapd[4601]: DBERROR: error exiting application: cyrusdb error
Jun 5 23:49:32 core imapd[4819]: DBERROR: error exiting application: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 5 23:49:32 core imapd[4819]: DBERROR: error exiting application: cyrusdb error
Jun 5 23:54:48 core lmtpd[4421]: DBERROR: error fetching user.oddjob: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 5 23:54:48 core lmtpd[4421]: DBERROR: error fetching user.oddjob: cyrusdb error
Jun 5 23:55:48 core lmtpd[4421]: DBERROR: error closing: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 5 23:55:48 core lmtpd[4421]: DBERROR: error closing deliverdb: cyrusdb error
Jun 5 23:55:48 core lmtpd[4421]: DBERROR: error closing: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 5 23:55:48 core lmtpd[4421]: DBERROR: error closing mailboxes: cyrusdb error
Jun 5 23:55:48 core lmtpd[4421]: DBERROR: error exiting application: DB_RUNRECOVERY: Fatal error, run database recovery
Jun 5 23:55:48 core lmtpd[4421]: DBERROR: error exiting application: cyrusdb error
Given runing recover does not fix it.. [?]
> Statements made are at all times subject to Frontier's Terms and > Conditions of Business, which are available upon request. I'm not sure what these conditions are, but disclaimers like this generally can make it hard to take posts to public mailing in any serious way (for example, if the disclaimer is that the contents of the message on a public list is "confidential" what does that mean?)
I refer to it as the "legal bullshit" that means that I don't get fired for sending an email.
What it actually says is that you can't sue my employer for anything I say, even if I'm using my employer's systems.
.. and if I didn't say it, then my emails would come to a very abrupt halt.
Happy?
Regards,
Gareth.
-Rob -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456 Research Systems Programmer * /usr/contributed Gatekeeper
|
-- Gareth Bult - Frontier Internet Services Limited Tel:02920 820 000 Fax: 02920 820 035 Email: [EMAIL PROTECTED] Web: www.bult.co.uk Statements made are at all times subject to Frontier's Terms and Conditions of Business, which are available upon request. |
<<attachment: smiley-3.png>>
