Results 1 to 10 of 25

Thread: Zimbra .pids / service monitoring

Hybrid View

  1. #1
    Join Date
    Jan 2006
    Posts
    20
    Rep Power
    9

    Question Zimbra .pids / service monitoring

    Hi - I was wondering where the pids for Zimbra are located as I would really like to set up monitoring of the vital services in Zimbra using somehting like monit (http://www.tildeslash.com/monit/index.php) and the easiest way to do this is via process IDs

    Ade

  2. #2
    Join Date
    Jan 2006
    Posts
    83
    Rep Power
    9

    Default

    Quote Originally Posted by bin2hex
    Hi - I was wondering where the pids for Zimbra are located as I would really like to set up monitoring of the vital services in Zimbra using somehting like monit (http://www.tildeslash.com/monit/index.php) and the easiest way to do this is via process IDs

    Ade
    what's wrong with SNMP?

  3. #3
    Join Date
    Feb 2007
    Posts
    52
    Rep Power
    8

    Default Monit doesnt do snmp.

    Quote Originally Posted by robbyt View Post
    what's wrong with SNMP?
    And snmp is just for monitoring. Monit is used to actively monitor and restart services.

    I just had the same though, clamav died and user's email got queued up. Monit would have caught it.

  4. #4
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    There's a few pids in different directories, you'll find them if you do a search of the /opt/zimbra directories.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  5. #5
    Join Date
    Feb 2007
    Posts
    52
    Rep Power
    8

    Default Unfortunately..

    Quote Originally Posted by phoenix View Post
    There's a few pids in different directories, you'll find them if you do a search of the /opt/zimbra directories.
    There are more pid's then zmcontrol status report.

    If someone has a monit recipe for zimbra that they can post here, that would be awsome.

    Otherwise I'm going to have to go through the pid's and see which services those actually are. Kind of a bummer to do on a production system.

  6. #6
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,587
    Rep Power
    58

    Default

    There's only thirteen of them.

    You could always contribute your findings to the wiki once you're done.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  7. #7
    Join Date
    Feb 2008
    Posts
    11
    Rep Power
    7

    Default

    I've updated the monit file for Zimbra 5.x with jetty. See below.

    Code:
    #zimbra processes                           
    
    check process antivirus with pidfile /opt/zimbra/log/clamd.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/zmantivirusctl start"
            stop program = "/bin/su - zimbra /opt/zimbra/bin/zmantivirusctl stop"  
            if children > 250 then alert                                           
            depends on ldap                                                        
            group zimbra                                                           
    
    
    check process ldap with pidfile /opt/zimbra/openldap/var/run/slapd.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/ldap start" with timeout 120 seconds
            stop program = "/bin/su - zimbra /opt/zimbra/bin/ldap stop" with timeout 120 seconds  
            if children > 250 then alert                                                          
            group zimbra                                                                          
    
    check process logwatch with pidfile /opt/zimbra/log/logswatch.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/zmlogswatchctl start"
            stop program = "/bin/su - zimbra /opt/zimbra/bin/zmlogswatchctl stop"  
            if children > 250 then alert                                           
            group zimbra                                                           
    
    check process mysql with pidfile /opt/zimbra/db/mysql.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/mysql.server start" with timeout 120 seconds
            stop program = "/bin/su - zimbra /opt/zimbra/bin/mysql.server stop" with timeout 120 seconds  
            if children > 250 then alert                                                                  
            group zimbra                                                                                  
    
    check process apache with pidfile /opt/zimbra/log/httpd.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/zmapachectl start"
            stop program = "/bin/su - zimbra /opt/zimbra/bin/zmapachectl stop"  
            if children > 250 then alert                                        
            depends on jetty                                                    
            group zimbra                                                        
    
    check process amavis with pidfile /opt/zimbra/log/amavisd.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/zmamavisdctl start"
            stop program = "/bin/su - zimbra /opt/zimbra/bin/zmamavisdctl stop"  
            if children > 250 then alert                                         
            group zimbra                                                         
    
    check process jetty with pidfile /opt/zimbra/log/zmmailboxd_java.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/zmmailboxdctl start" with timeout 240 seconds
            stop program = "/bin/su - zimbra /opt/zimbra/bin/zmmailboxdctl stop" with timeout 240 seconds  
            if children > 250 then alert                                                                   
            depends on ldap                                                                                
            group zimbra
    
    check process cyrus-sasl with pidfile /opt/zimbra/cyrus-sasl/state/saslauthd.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/zmsaslauthdctl start"
            stop program = "/bin/su - zimbra /opt/zimbra/bin/zmsaslauthdctl stop"
            if children > 250 then alert
            depends on ldap
            group zimbra
    
    check process snmp-swatch with pidfile /opt/zimbra/log/swatch.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/zmswatchctl start"
            stop program = "/bin/su - zimbra /opt/zimbra/bin/zmswatchctl stop"
            if children > 250 then alert
            group zimbra
    
    check process postfix with pidfile /opt/zimbra/data/postfix/spool/pid/master.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/postfix start" with timeout 120 seconds
            stop program = "/bin/su - zimbra /opt/zimbra/bin/postfix stop" with timeout 120 seconds
            if children > 250 then alert
            depends on ldap
            group zimbra
    
    check process zmmtaconfigctl with pidfile /opt/zimbra/log/zmmtaconfig.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/zmmtaconfigctl start"
            stop program = "/bin/su - zimbra /opt/zimbra/bin/zmmtaconfigctl stop"
            if children > 250 then alert
            depends on postfix
            group zimbra
    
    check process freshclam with pidfile /opt/zimbra/log/freshclam.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/zmclamdctl start"
            stop program = "/bin/su - zimbra /opt/zimbra/bin/zmclamdctl stop"
            if children > 250 then alert
            depends on antivirus
            group zimbra
    
    #Only for commercial version of zimbra
    #check process zmconvertdmon with pidfile /opt/zimbra/log/zmconvertdmon.pid
    #        start program = "/bin/su - zimbra /opt/zimbra/bin/zmconvertctl start"
    #        stop program = "/bin/su - zimbra /opt/zimbra/bin/zmconvertctl stop"
    #        if children > 250 then alert
    #        depends on postfix
    #        group zimbra
    
    check process mysqllogger with pidfile /opt/zimbra/logger/db/mysql.pid
            start program = "/bin/su - zimbra /opt/zimbra/bin/logmysql.server start" with timeout 120 seconds
            stop program = "/bin/su - zimbra /opt/zimbra/bin/logmysql.server stop" with timeout 120 seconds
            if children > 250 then alert
            depends on mysql
            group zimbra
    Last edited by sblandford; 06-24-2009 at 06:30 AM.

Similar Threads

  1. Can't start Zimbra!
    By zibra in forum Administrators
    Replies: 5
    Last Post: 03-22-2007, 12:34 PM
  2. Post instsallation problems
    By Assaf in forum Installation
    Replies: 14
    Last Post: 01-29-2007, 11:38 AM
  3. huge log size
    By rmvg in forum Administrators
    Replies: 5
    Last Post: 01-02-2007, 10:39 AM
  4. zimbra-core missing
    By kinaole in forum Developers
    Replies: 1
    Last Post: 10-02-2006, 12:59 PM
  5. Unable to start tomcat
    By chanck in forum Administrators
    Replies: 11
    Last Post: 06-11-2006, 01:58 AM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •