Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4512

Strange Housekeeping Cron Log Entries

Details

    • Bug
    • Resolution: Not A Bug
    • Trivial
    • None
    • Professional Edition
    • Scripts
    • CentOS 7

    Description

      Updated from 23.5.12764 to 23.5.12788 last Thursday.  Since then we have seen strange entries in the daily cron log:

       --------------------- Cron Begin ------------------------ 

       Commands Run:
          User root:
                /opt/observium/discovery.php -h all >> /dev/null 2>&1: 4 Time(s)
                /opt/observium/discovery.php -h new >> /dev/null 2>&1: 96 Time(s)
                /opt/observium/poller-wrapper.py >> /dev/null 2>&1: 288 Time(s)
                /opt/observium/housekeeping.php -yrptb: 1 Time(s)
                /opt/observium/housekeeping.php -ysel: 1 Time(s)
                run-parts /etc/cron.hourly: 24 Time(s)
       
       *Unmatched Entries*
       CMDOUT (#033[0;32mObservium 23.5.12788)
       CMDOUT (#033[1;37mHouseKeeping#033[0m)
       CMDOUT (#033[0m)
       CMDOUT (#033[0m)
       CMDOUT (#033[0;32mObservium 23.5.12788)
       CMDOUT (#033[1;37mHouseKeeping#033[0m)
       CMDOUT (#033[0m)
       CMDOUT (#033[0m)
       ---------------------- Cron End -------------------------

       

      Attachments

        Activity

          [OBS-4512] Strange Housekeeping Cron Log Entries
          NegwerIT Scott Driemeier-Showers added a comment - - edited

          Sorry for the tardy reply, I didn't receive notice that a response had been posted.

          I'm not trying to argue, simply to provide background.  Our install has been running since February, 2020 without producing the cron log entries, so something definitely changed; but it may have been something in an OS update.

          Were running on RHEL, not Debian, and installed using the RHEL instructions that do not include the /dev/null pipes at the end of the housekeeping lines.  I will add them to our cron job...

          NegwerIT Scott Driemeier-Showers added a comment - - edited Sorry for the tardy reply, I didn't receive notice that a response had been posted. I'm not trying to argue, simply to provide background.  Our install has been running since February, 2020 without producing the cron log entries, so something definitely changed; but it may have been something in an OS update. Were running on RHEL, not Debian, and installed using the RHEL instructions that do not include the /dev/null pipes at the end of the housekeeping lines.  I will add them to our cron job...

          Not sure if there really something changed.. that output was always.
          But seems as you should use housekeeping with pipe to /dev/null:

          /opt/observium/housekeeping.php -ysel >> /dev/null 2>&1
          /opt/observium/housekeeping.php -yrptb >> /dev/null 2>&1
          

          as written in docs: https://docs.observium.org/install_debian/?h=housekeeping#perform-initial-discovery-and-poll

          landy Mike Stupalov added a comment - Not sure if there really something changed.. that output was always. But seems as you should use housekeeping with pipe to /dev/null: /opt/observium/housekeeping.php -ysel >> /dev/null 2>&1 /opt/observium/housekeeping.php -yrptb >> /dev/null 2>&1 as written in docs: https://docs.observium.org/install_debian/?h=housekeeping#perform-initial-discovery-and-poll

          FYI, updated to 23.5.12826 yesterday.  Overnight the cron daemon generated an E-mail to root on the output of each job:

          • /opt/observium/housekeeping.php -yrptb
            • [0;32mObservium 23.5.12826
              [1;37mHouseKeeping [0m
              [0m
              [0m
          • /opt/observium/housekeeping.php -ysel
            • [0;32mObservium 23.5.12826
              [1;37mHouseKeeping [0m
              [0m
              [0m

          This is the first time it has done that.  The lines still appear in the cron log (as would be expected)...

          NegwerIT Scott Driemeier-Showers added a comment - FYI, updated to 23.5.12826 yesterday.  Overnight the cron daemon generated an E-mail to root on the output of each job: /opt/observium/housekeeping.php -yrptb [0;32mObservium 23.5.12826 [1;37mHouseKeeping [0m [0m [0m /opt/observium/housekeeping.php -ysel [0;32mObservium 23.5.12826 [1;37mHouseKeeping [0m [0m [0m This is the first time it has done that.  The lines still appear in the cron log (as would be expected)...

          FYI, I do not see similar messages in the debug output if I run the script from the shell prompt (attached).

          housekeeping.txt

           

           

          NegwerIT Scott Driemeier-Showers added a comment - FYI, I do not see similar messages in the debug output if I run the script from the shell prompt (attached). housekeeping.txt    

          General questions and device support can be discussed in our Discord channel, click here to join.


          Please make and attach additional information about the device:

          • full snmp dump from device:

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs:

            ./discovery.php -d -h <device>
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -Ih -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            adama Adam Armstrong
            NegwerIT Scott Driemeier-Showers
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: