From: Rich Wales (no email)
Date: Sun Nov 04 2007 - 22:13:25 EST
Wesley Craig wrote:
> The log files are pretty obvious in what they say, e.g., they just
> list mailboxes or users to check. So I suspect they would reveal
> to you which mailboxes are problematic. I sort of assume that
> you're running sync_client with -l, otherwise it doesn't log much.
> If it's run with -l, it should mention the action that preceded
> the problem.
Here's one of the leftover log files, time-stamped right at the time
of one of these bailout crashed.
APPEND user.marie
SEEN marie user.marie
MAILBOX user.marie
MAILBOX user.marie.Junk
SEEN marie user.marie.Junk
SEEN marie user.marie
MAILBOX user.marie
Other messages have been delivered since that time to both user.marie
and user.marie.Junk without crashing sync_client. So if this log is
telling me there's a problem with either of these mailboxes, I don't
understand what the log is telling me.
Yes, I am using the "-l" flag (sync_client -r -l -v), but I'll have
to say once again that neither /var/log/messages nor any other log
file on my master server shows any other sync-related error message
of any sort whatsoever, except for the "Error in do_sync(): bailing
out!" message I mentioned previously. In /var/log/debug.log, I see
things such as these:
Nov 3 18:55:44 whodunit sync_client[6875]: seen_db: user richw opened
/var/imap/user/r/richw.seen
Nov 3 19:03:29 whodunit sync_client[7008]: DIGEST-MD5 client step 1
Nov 3 19:03:29 whodunit sync_client[7008]: DIGEST-MD5 client step 2
Nov 3 19:03:29 whodunit sync_client[7008]: DIGEST-MD5 client step 3
Nov 3 19:13:44 whodunit sync_client[7127]: DIGEST-MD5 client step 1
Nov 3 19:13:44 whodunit sync_client[7127]: DIGEST-MD5 client step 2
Nov 3 19:13:44 whodunit sync_client[7127]: DIGEST-MD5 client step 3
(the bailout message itself occurred at 19:14:37)
and on the replica server, I see the following:
Nov 3 19:03:29 flipflop syncserver[15942]: accepted connection
Nov 3 19:03:29 flipflop syncserver[15942]: cmdloop(): startup
Nov 3 19:13:45 flipflop master[16110]: about to exec /usr/cyrus/bin/sync_server
Nov 3 19:13:45 flipflop syncserver[15942]: accepted connection
Nov 3 19:13:45 flipflop syncserver[15942]: cmdloop(): startup
Nov 3 19:13:45 flipflop syncserver[16110]: executed
but that's all. Should I be seeing additional debugging output? If
so, where should I be looking for it?
I'm very sorry, but at the moment, all I can see is that the sync
software mysteriously dies every so often, with no intelligible clue
as to why. I understand you're saying that there should be additional
info, but either it's NOT there or I don't know where to look for it.
If anyone can help me figure out what I'm doing wrong here, I'll be
grateful.
-- Rich Wales === Palo Alto, CA, USA === http://www.richw.org === http://en.wikipedia.org/wiki/User:Richwales "The difference between theory and practice is that, in theory, theory and practice are identical -- whereas in practice, they aren't." ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
|
|
|