Ad Widget

Collapse

Zabbix 1.6 Agent & Sendmail Proc

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • bcarpio
    Member
    • Jun 2008
    • 96

    #1

    Zabbix 1.6 Agent & Sendmail Proc

    We just upgraded our Zabbix server to 1.6 and everything is working great. We deployed the 1.6 agent to our development environment and we seem to be unable to monitor the sendmail process.

    The ITEM in question is:
    proc.num[sendmail]

    The values reported are 1 for up and 0 for down, after we redeployed the 1.6 agent sendmail showed down on all of our servers even though it is running.

    We don't have this problem with any other processes such as sshd, syslog etc..

    I have tried to delete the item and recreate it however the problem still exists with the 1.6 agent on RHEL 5.1 64bit and RHEL 4.6 64bit (we don't have this problem on AIX).

    If I roll back the agent from 1.6 to 1.4.6 on any offending Linux server then the problem goes away.

    Now the interested thing is if I change my Item from just "sendmail" (which is all I need for the 1.4 agents) to "proc.num[sendmail: accepting connections]" there is no problem and the 1.6 agent reports that the process is running just fine here is an example:

    Code:
    [root@SERVER sbin]# ./zabbix_agentd -t "proc.num[sendmail: accepting connections]"
    proc.num[sendmail: accepting connections]     [u|1]
    
    [root@SERVER sbin]# ./zabbix_agentd -t "proc.num[sendmail]"
    proc.num[sendmail]                            [u|0]
  • bcarpio
    Member
    • Jun 2008
    • 96

    #2
    Apparently when I use the 1.6 zabbix_agentd on RHEL 5.1 64bit the item:
    proc.num[sendmail: accepting connections]
    works just fine.

    However, when I use the 1.6 zabbix_agentd on RHEL 4.6 64bit and use the Item:
    proc.num[sendmail: accepting connections]

    It doesn't work, the agent still can't detect that sendmail is running. This appears to be a problem with any daemon running with "accepting connections" after the process name.

    We don't see this problem with daemons like sshd or syslog in RHEL 5.1 or RHEL 4.6

    Comment

    Working...