A experienced sysadmin who's doing some guinea-pig use of DC just ran into the following situation: period when the write to the Drafts would have been hung.
- He brings up SeaMonkey
- About 30 minutes later, he's in the middle of some involved messaging, mistakenly hits the redX in the top right of the SeaMonkey window, knocking himself out of SeaMonkey.
- He immediately reinvokes SeaMonkey, all appeared to be OK Viewed some e-mail and some web page references, tries to send a message and then the Send hung for a time with a message "Sending Authenticate Info"..after some minutes, a new E-mail window appeared stating the "Server reported a timeout". As far as the message, it was apparently sent successfully, and saved in the Sent folder successfully.
- He calls me in. I look through the syslog logging. There is nothing in the syslog critical stuff...and everything in the maillog looks normal.
- He starts another message, tries to save it to Drafts and that hangs
- I look more closely at the maillog and see a lot of logins (one a minute in some cases, but all appear to have been cleanly executed) plus one bunch of disconnected messages with one disconnected in idle in the
Could it be that DC was in the middle of clean up in the initial disconnect/reconnect and SeaMonkey came back in the middle of it and one or the other's state tables got messed up (or both of them)? Shutting out of SeaMonkey, waiting a minute and reconnecting seems to have gotten things working again. Any comments? Anything I should be looking for?
OTOH, this is the first real problem I've seen in some person-months of testing.....
--
Stewart Dean, Unix System Admin, Henderson Computer Resources
Center of Bard College, Annandale-on-Hudson, New York 12504
sdean@bard.edu voice: 845-758-7475, fax: 845-758-7035