Cyrus logging informational messages with too high priority?

[Rob Siemborski]

On 30 Oct 2002, Erik Enge wrote:

> The following error message seem to be at warn (syslog priority) or
> above:
>
>   Oct 30 14:24:57 myhost imapd[12489]: idle for too long, closing connection
>
> Shouldn't this be only an info, or is it really a warning that something
> is about to go wrong (which how I think of warnings)?

It could probably go to LOG_INFO.

> The other day, I got the following in the log:
>
>   Oct 30 12:49:34 myhost lmtpd[12178]: DBERROR db3: 5 lockers
>   Oct 30 12:49:34 myhost lmtpd[12178]: DBERROR db3: 5 lockers
>   Oct 30 12:49:35 myhost lmtpd[12185]: DBERROR db3: 6 lockers
>   [more like these snipped]
>
> I did some searching in the archives and the preferred solution seems to
> be to recompile cyrus with a different database (flat, for example).  Is
> this still the preferred solution?

That depends on a number of things.  mailboxes.db should be skiplist for
performance reasons anyway.

If you're using Berkeley DB 4 there's a bug in the locker counting code
that causes this number to not be decremented, so it really isn't
something to worry about unless there are other problems (like severe
performance problems all the time).

> As I said, I don't know if this is anything Cyrus is to blame for, but I
> thought I'd mention it.  Any pointers of any of these issues would be
> greatly appreciated.

If other clients were working, I'm going to blame the client that wasn't,
but that's just me.

If you could get protocol traces that'd be moure useful.

-Rob

-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Rob Siemborski * Andrew Systems Group * Cyert Hall 207 * 412-268-7456
Research Systems Programmer * /usr/contributed Gatekeeper