Skip navigation
6007 Views 1 Reply Latest reply: Apr 19, 2010 4:11 AM by jcurry RSS
Christian Rank: White Belt 11 posts since
Sep 6, 2007
Currently Being Moderated

Apr 16, 2010 5:10 AM

zenoss is too late with the checks

Hello all,

 

my system :

Zenoss : 2.4.2

OS : CentOS 5.3

 

my Problem :

I have a Template with one Data Source, Data Source looks like this :

Name
Source TypeCOMMAND
Enabled
Use SSH
Component
Event Class* drop down *
Event Key
Severity
Cycle Time
Parser
Command Template

 

 

Now one the remote Server everytime the Script is execute it's writes e message to syslog, here the Log entrys:

Apr 15 21:59:53  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 15 22:10:25  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 15 22:20:57  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 15 22:31:29  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 15 23:32:14  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 15 23:42:45  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 15 23:53:17  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 16 00:03:49  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 00:14:21  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 00:24:53  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 00:35:25  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 00:45:58  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 16 00:56:29  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 01:07:31  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 16 01:18:21  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 16 01:28:53  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 01:39:25  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 16 01:49:56  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 02:00:28  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 02:10:59  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=30 RC=0
Apr 16 02:21:31  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 02:32:02  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 02:42:32  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=30 RC=0
Apr 16 02:53:04  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 03:03:36  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 03:14:07  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 03:24:38  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 03:35:10  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 16 03:45:41  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 04:46:18  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 05:47:12  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 06:47:06  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 07:47:06  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0
Apr 16 08:49:30  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=32 RC=0
Apr 16 09:39:35  ZENOSS /usr/bin/sudo -u myuser /usr/local/nagios/check_basecomponents.sh runtime=31 RC=0

 

as you can see until 03:45 the Check was executet every 600 seconds (10 Minutes). After this time the check is executen only every hour. Time on the zenoss server is synchron, other checks on the same server (not in the same template) were executet ontime.Doing e restart of the hole Zenoss Server will solve this Problem.

 

Question:

Any one of you had an idea what I am doing wrong or how i can fixe this Problem ? Upgrade is in planing but the upgrad in the Test Evironment faild, so worry a bit about updating the production.

 

greez christian

  • jcurry ZenossMaster 1,021 posts since
    Apr 15, 2008
    Currently Being Moderated
    1. Apr 19, 2010 4:11 AM (in response to Christian)
    Re: zenoss is too late with the checks

    I see that you have not filled in the cycle time so I am rather surprised that Zenoss is running your template anyway, and certainly surprised that it was running every 10 minutes.

     

    On your Zenoss system, have a look at $ZENHOME/log zencommand.log to see if there is any help there.  event.log and zenhub.log are laso worth a look as they handle coordination of Zenoss daemons and often provide clues.

     

    I doubt that this is anything to do with actual time on devices.

     

    Cheers,

    Jane

More Like This

  • Retrieving data ...

Legend

  • Correct Answers - 4 points
  • Helpful Answers - 2 points