Re: Fwd: Too many entries of mystore: reusing txn....

2012-12-12 Thread Adam Tauno Williams
On Sun, 2012-12-09 at 10:49 +0530, Anant Athavale wrote:

 As you say, the imap DEBUG logs are coming to maillog.  RHEL 6.3 ships
 with Rsyslogd and also it looks like cyrus-imapd is compiled to use
 MAIL_LOG facility.  (I tried local6.info /var/log/imapd.log. but it
 did log anything in imapd.log ).
 I am attaching rsyslog.conf (Not modified).  What I ultimately want is
 'maillog should not contain imap logs.  And imapd.log should contain
 all logs related to cyrus/imapd with only info level logs.  '
 As I could not achieve it in short span of time, I have released the
 system, but, would like to do that in near future.  Any pointers to
 achieve?

Yes.  Give up on syslog.  Seriously.  The model provided by syslog is
very simplistic and kludgy.  Just use syslog as a transport to get
messages into an NMS, and sort, categorize, and record them there.

We send all our syslog messages to ZenOSS.  There syslog messages can be
mapped into categories, prioritized [and discarded], recorded, viewed,
and generate notifications.  And you get a user interface to do it all
in, and a coherent way to backup/restore all your machinations.

Syslog messages from imapd have a tag of imapd, and messages from
postfix have a tag of postfix, which is almost invisible in syslog
itself.  So you have the host of origin, the tag, the facility, and the
level [and the text of the message] all to work with to categorize [and
potentially discard] any way you want.

Obviously you want to discard DEBUG messages as the syslog level - that
is just too much noise for anything.  But a decent host for you NMS can
handle a surprising load of messages.

-- 
Adam Tauno Williams awill...@whitemice.org


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus


Re: Fwd: Too many entries of mystore: reusing txn....

2012-12-12 Thread Andrew Morgan
On Wed, 12 Dec 2012, Adam Tauno Williams wrote:

 On Sun, 2012-12-09 at 10:49 +0530, Anant Athavale wrote:

 As you say, the imap DEBUG logs are coming to maillog.  RHEL 6.3 ships
 with Rsyslogd and also it looks like cyrus-imapd is compiled to use
 MAIL_LOG facility.  (I tried local6.info /var/log/imapd.log. but it
 did log anything in imapd.log ).
 I am attaching rsyslog.conf (Not modified).  What I ultimately want is
 'maillog should not contain imap logs.  And imapd.log should contain
 all logs related to cyrus/imapd with only info level logs.  '
 As I could not achieve it in short span of time, I have released the
 system, but, would like to do that in near future.  Any pointers to
 achieve?

 Yes.  Give up on syslog.  Seriously.  The model provided by syslog is
 very simplistic and kludgy.  Just use syslog as a transport to get
 messages into an NMS, and sort, categorize, and record them there.

 We send all our syslog messages to ZenOSS.  There syslog messages can be
 mapped into categories, prioritized [and discarded], recorded, viewed,
 and generate notifications.  And you get a user interface to do it all
 in, and a coherent way to backup/restore all your machinations.

 Syslog messages from imapd have a tag of imapd, and messages from
 postfix have a tag of postfix, which is almost invisible in syslog
 itself.  So you have the host of origin, the tag, the facility, and the
 level [and the text of the message] all to work with to categorize [and
 potentially discard] any way you want.

 Obviously you want to discard DEBUG messages as the syslog level - that
 is just too much noise for anything.  But a decent host for you NMS can
 handle a surprising load of messages.

Just to add another thought here...  You could use syslog-ng instead of 
rsyslog.  Syslog-ng has more advanced filtering capabilities than rsyslog, 
and you can probably just drop-in replace rsyslog with syslog-ng. 
However, I would not discourage you from looking at ZenOSS too.  Syslog-ng 
might be less work to implement if you do not need ZenOSS features.

Andy

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus


Fwd: Too many entries of mystore: reusing txn....

2012-12-08 Thread Anant Athavale
-- Forwarded message --
From: Anant Athavale athavale.an...@gmail.com
Date: Sun, Dec 9, 2012 at 10:31 AM
Subject: Re: Too many entries of mystore: reusing txn
To: Andrew Morgan mor...@orst.edu




On Sat, Dec 8, 2012 at 10:52 PM, Andrew Morgan mor...@orst.edu wrote:

 On Sat, 8 Dec 2012, Anant Athavale wrote:

  Dear Experts,

 I had been sending mails to this list in the last two days with email
 an...@isac.gov.in - with subject - Urgent Help Required.  Based on your
 advise, I have rebuilt all the mailboxes.  I am monitoring the maillog
 entries of cyrus imap after I started the cyrus-imapd.  Everything seems
 to
 be fine.

 Most of the log entries, I checked in this list and found them harmless
 and
 hence ignoring them like: setrlimit and IP_TOS etc.

 But, for this one, I did not get any proper comments in this list.

 In the maillog, I have too many lines with the same message, which is as
 below.

 cvt_cyrusdb: mystore: reusing txn .with some value of number.

 This same line repeats, at least 190+ times (including that last number).
 Is this a cause of worry? I have not yet released the system to users.  I
 will be doing it only tomorrow, based on the response for this.  Do I need
 to check something?

 I have rebuilt mailboxes and reconstructed mailboxes in RHEL 6.3 supplied
 Cyrus-IMAP 2.3.16.

 Please advise.


 Unless you really want to see all the gory details of Cyrus, turn your
 syslog level down from DEBUG to INFO.  The message you are seeing is a
 DEBUG level log message.


 Andy


As you say, the imap DEBUG logs are coming to maillog.  RHEL 6.3 ships with
Rsyslogd and also it looks like cyrus-imapd is compiled to use MAIL_LOG
facility.  (I tried local6.info /var/log/imapd.log. but it did log anything
in imapd.log ).

I am attaching rsyslog.conf (Not modified).  What I ultimately want is
'maillog should not contain imap logs.  And imapd.log should contain all
logs related to cyrus/imapd with only info level logs.  '

As I could not achieve it in short span of time, I have released the
system, but, would like to do that in near future.  Any pointers to achieve?

Thank you all for your support.

Anant.

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/
To Unsubscribe:
https://lists.andrew.cmu.edu/mailman/listinfo/info-cyrus