Hi, Just an update on the 5.3.5 release. It successfully compiled on my Redhat 4 box after the latest patch to omfile and the configure process. I ran a check of the current, very basic configuration, with:
rsyslog -c5 -f/etc/opt/rsyslog/rsyslog.conf and there were no errors reported. After I shutdown rsyslog 4.2.0 and tried to restart the server, it started fine with no errors logged, but the PostgreSQL 8.4.1 backend started spewing these error messages over and over: ... WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress WARNING: there is already a transaction in progress ... Here is my configuration: $ModLoad immark # provides --MARK-- message capability $ModLoad imtcp # provides TCP syslog reception and GSS-API (if compiled to support it) $ModLoad imuxsock $InputTCPServerRun 601 # listen on this port $WorkDirectory /var/spool/rsyslog # default location for work (spool) files $MainMsgQueueFileName mainq # set file name, also enables disk mode $ActionResumeRetryCount -1 # infinite retries on insert failure $ModLoad ompgsql # provides postgres support # Everything we receive goes in the database *.* :ompgsql:127.0.0.1,Syslog,database,xxxxxxxx Any ideas about what could be going on? I put back the version 4.2.0 for now, but I would like to be able to take advantage of the parallel input processing that is available in the 5.3.5 release. Let me know if I can do anything to help debug the problem. Regards, Ken _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
