I'm having the same problem running rsyslog in CentOS. I don't have a really important setup and am occupied with other things, so I did a cron job to restart rsyslog every 6 hours and am leaving the issue for another day. I can try to provide info if it will help.

On Wed, May 11, 2016 at 2:03 AM, John Klasa <John.Klasa@itiviti.com> wrote:

Hi, we have syslog-ng configured and went through the documentation about how to get syslog into Observium.
It works for a while(from 10mins to several hours) and then it stops to display or handle syslog. Restarting the syslog daemon generates a strange message in the logs.

-0001-11-30 00:00:00 Alert (1) 1 : 1

It's very low volume. Maybe 100-1000 messages per day.

We have tried rsyslog (default in RedHat)

Version Information

Observium 0.16.5.7833 (6th May 2016)
OS Linux 2.6.32-431.29.2.el6.x86_64 [amd64] (RedHat 6.7)
Apache 2.2.15 (Red Hat)
PHP 5.6.21
Python 2.6.6
MySQL 5.1.73 (extension: mysqli 5.1.73)
SNMP NET-SNMP 5.5
RRDtool 1.4.8

__________________________________________________

Regards

John Klasa
Managed Services, Itiviti

John.Klasa@itiviti.com

Kungsgatan 36 , P.O. Box 7742
10395 Stockholm , Sweden

Homepage: itiviti.com »
_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium