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

Syslog deployment failure(No syslog entries found!)

Details

    • Bug
    • Resolution: Fixed
    • Major
    • None
    • Community Edition
    • Web Interface
    • Centos7.2
      Observium CE 0.1.16.1.7533
      rsyslog-7.4.7-12

    Description

      I deploy syslog failure according to the document.
      Document link:http://www.observium.org/docs/syslog/
      The following is my configuration:
      (1) /etc/rsyslog.conf:

      1. Provides UDP syslog reception
        $ModLoad imudp
        $UDPServerRun 514

      (2)/etc/rsyslog.d/30-observium.conf:
      #---------------------------------------------------------
      #send remote logs to observium

      $template observium,"%fromhost-ip%||%syslogfacility%||%syslogpriority%||%syslogseverity%||%syslogtag%||%$year%%$month%%$day% %timereported:8:25%||%msg%||%programname%\n"
      $ModLoad omprog
      $ActionOMProgBinary /opt/observium/syslog.php

      :inputname, isequal, "imudp" :omprog:;observium

      #& ~
      & stop
      #---------------------------------------------------------

      (3)/opt/observium/config.php:

      $config['enable_syslog'] = 1; // Enable Syslog

      [root@observium-server observium]# systemctl restart rsyslog
      [root@observium-server observium]# systemctl reload rsyslog
      Failed to reload rsyslog.service: Job type reload is not applicable for unit rsyslog.service.

      Open the web page of the syslog, an error is "No syslog entries found!"
      Please help me.
      Thanks!

      Attachments

        Activity

          [OBS-1886] Syslog deployment failure(No syslog entries found!)

          I restarted syslog but it took a few hours to start reporting, don't know why

          It works now, thank you

          kaputtzich Daniel Reinbold added a comment - I restarted syslog but it took a few hours to start reporting, don't know why It works now, thank you

          kaputtzich You restarted syslog service?

          syslog script now forcefully ends when mysql server gone error detected.
          rsyslog should rerun it again.

          In log still possible such errors one time before script exit.

          landy Mike Stupalov added a comment - kaputtzich You restarted syslog service? syslog script now forcefully ends when mysql server gone error detected. rsyslog should rerun it again. In log still possible such errors one time before script exit.

          As for the dbQuery error problem still exists in r8509

          kaputtzich Daniel Reinbold added a comment - As for the dbQuery error problem still exists in r8509

          Fixed (possible) in r8506.

          landy Mike Stupalov added a comment - Fixed (possible) in r8506.

          I don't know if it's the same problem, but for me syslog is empty because syslog.php generates the following error:

          syslog.php: Failed dbQuery (#2006 - MySQL server has gone away), ..."

          It's the only observium module which generates such an error in db.log, everything else is working as expected

          kaputtzich Daniel Reinbold added a comment - I don't know if it's the same problem, but for me syslog is empty because syslog.php generates the following error: syslog.php: Failed dbQuery (#2006 - MySQL server has gone away), ..." It's the only observium module which generates such an error in db.log, everything else is working as expected

          People

            landy Mike Stupalov
            terrell Feng Guo
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: