Details

    • Help
    • Resolution: Done
    • Major
    • None
    • None
    • Default

    Description

      Hi Team, 

       

      We recently installed and added our devices to our observium environment.

      However we noticed that the poll aren't pulling automatically, we see a message poll were last pull 18 hours ago. We did a manual poll initially, approximately 18 hours ago. 

      We are also running into an issue setting up email alerts. 

      May we get some assistances for both issues? 

      Thank you. 

      Attachments

        Activity

          [OBS-5048] Setup Assistance
          sbao@sycomp.com Steven Bao added a comment -

          Thanks Mike. That was what i was missing. Thank you!!

          sbao@sycomp.com Steven Bao added a comment - Thanks Mike. That was what i was missing. Thank you!!
          landy Mike Stupalov made changes -
          Resolution New: Done [ 10000 ]
          Status Original: Pending Response [ 10000 ] New: Resolved [ 5 ]

          Probably you missed install step with configure crontab entries.

          Look into installation docs:
          https://docs.observium.org/install_debian/#perform-initial-discovery-and-poll

          # Run a complete discovery of all devices once every 6 hours
          33  */6   * * *   root    /opt/observium/observium-wrapper discovery >> /dev/null 2>&1
           
          # Run automated discovery of newly added devices every 5 minutes
          */5 *     * * *   root    /opt/observium/observium-wrapper discovery --host new >> /dev/null 2>&1
           
          # Run multithreaded poller wrapper every 5 minutes
          */5 *     * * *   root    /opt/observium/observium-wrapper poller >> /dev/null 2>&1
           
          # Run housekeeping script daily for syslog, eventlog and alert log
          13 5 * * * root /opt/observium/housekeeping.php -ysel >> /dev/null 2>&1
           
          # Run housekeeping script daily for rrds, ports, orphaned entries in the database and performance data
          47 4 * * * root /opt/observium/housekeeping.php -yrptb >> /dev/null 2>&1
          

          Anyway, general questions better to ask in our Discord channel

          If you have Enterprise subscription write to our team over there (@landy or @adama) with subscription login. We will help you with higher priority.

          landy Mike Stupalov added a comment - Probably you missed install step with configure crontab entries. Look into installation docs: https://docs.observium.org/install_debian/#perform-initial-discovery-and-poll # Run a complete discovery of all devices once every 6 hours 33 */6 * * * root /opt/observium/observium-wrapper discovery >> /dev/null 2>&1   # Run automated discovery of newly added devices every 5 minutes */5 * * * * root /opt/observium/observium-wrapper discovery --host new >> /dev/null 2>&1   # Run multithreaded poller wrapper every 5 minutes */5 * * * * root /opt/observium/observium-wrapper poller >> /dev/null 2>&1   # Run housekeeping script daily for syslog, eventlog and alert log 13 5 * * * root /opt/observium/housekeeping.php -ysel >> /dev/null 2>&1   # Run housekeeping script daily for rrds, ports, orphaned entries in the database and performance data 47 4 * * * root /opt/observium/housekeeping.php -yrptb >> /dev/null 2>&1 Anyway, general questions better to ask in our Discord channel If you have Enterprise subscription write to our team over there (@landy or @adama) with subscription login. We will help you with higher priority.
          bot Observium Bot made changes -
          Component/s New: Default [ 10900 ]
          bot Observium Bot made changes -
          Assignee Original: Adam Armstrong [ adama ] New: Mike Stupalov [ landy ]
          bot Observium Bot made changes -
          Status Original: Open [ 1 ] New: Pending Response [ 10000 ]
          sbao@sycomp.com Steven Bao created issue -

          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

            landy Mike Stupalov
            sbao@sycomp.com Steven Bao
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: