Ad Widget

Collapse

Trouble with monitoring services

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rkruck
    Junior Member
    • Mar 2014
    • 9

    #1

    Trouble with monitoring services

    I have set up an alert to monitor services in linux (in this case we will use crond).

    [Item]
    Name: crond status
    Type: Zabbix agent
    Key: proc.num[crond]
    (rest is defalt)

    [Trigger]
    Name: Cron not running on {HOSTNAME}
    Expression: {Custom Linux Templateroc.num[crond].last(0)}<1

    Most of my linux servers this works fine on but I have 9 servers which coincidentally are all RHEL 6.5 servers show up as being down, or under the latest data a value of 0. I went to one of the hosts and ran "zabbix_agentd -t proc.num[crond]" and received:
    proc.num[crond] [u|1]

    I'm lost why it's working on some and not others. I even copied the zabbix_agent.conf file (changing the Hostname= section) from a working server and restarted the agent.

    Any help is appreciated.

    Robert
  • aib
    Senior Member
    • Jan 2014
    • 1615

    #2
    Do you mind to check if that system has any different daemon like anacron?
    https://access.redhat.com/site/docum...tem_Tasks.html

    May be because of that the daemon crond didn't start and cannot be checked.
    Sincerely yours,
    Aleksey

    Comment

    • rkruck
      Junior Member
      • Mar 2014
      • 9

      #3
      service status crond shows that it is running. ps -ef|grep cron shows crond running.

      Comment

      • rkruck
        Junior Member
        • Mar 2014
        • 9

        #4
        Not sure if this helps any but I set up another alert to monitor auditd and the same 9 servers show it as failed, yet it's running.

        "zabbix_agentd -t proc.num[auditd]" and received:
        proc.num[auditd] [u|1]

        Comment

        • rkruck
          Junior Member
          • Mar 2014
          • 9

          #5
          I found the issue. SELinux is stopping it. I turned it off on my dev/test servers but I need to figure out how to fix it through selinux for our production servers. Unfortunately I know very little about selinux. Has anyone come across this before and may be able to offer assistance.

          Comment

          Working...