Re: Monitoring cyrusimapd

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Quoting Albert Shih <Albert.Shih@xxxxxxxx>:

Hi everyone,

I would like to know what kind of monitoring you perform on a cyrus-imapd.
Beside classic (check_imap, check_disk, check_cpu etc...) do you have any
special thing to monitor about cyrus-imapd.

In addition to the normal System monitoring (CPU-, Memory and Disk usage and
the Checks if tie services are running, we monitor the Cyrus logs for
Critical errors like IOERROR, or Mupdate commit errors.


For example do you launch any check on each database ? How can I check if the replication work fine ?

No database checks.

For Replication we check the size of the "sync" folder to see if the rolling
replication log is growing over 1 MB or if average size of the logs was over
500 KB for more than 15 min



--------------------------------------------------------------------------------
M.Menge                                Tel.: (49) 7071/29-70316
Universität Tübingen                   Fax.: (49) 7071/29-5912
Zentrum für Datenverarbeitung mail: michael.menge@xxxxxxxxxxxxxxxxxxxx
Wächterstraße 76
72074 Tübingen

----
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




[Index of Archives]     [Cyrus SASL]     [Squirrel Mail]     [Asterisk PBX]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [KDE]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux