You are not logged in.
Pages: 1
running it manually, I get
# syslog-ng -d
Trying to open module; module='syslogformat', filename='/usr/lib/syslog-ng/libsyslogformat.so'
Trying to open module; module='basicfuncs', filename='/usr/lib/syslog-ng/libbasicfuncs.so'
Trying to open module; module='afsocket', filename='/usr/lib/syslog-ng/libafsocket.so'
Trying to open module; module='affile', filename='/usr/lib/syslog-ng/libaffile.so'
Trying to open module; module='afprog', filename='/usr/lib/syslog-ng/libafprog.so'
Trying to open module; module='afuser', filename='/usr/lib/syslog-ng/libafuser.so'
Trying to open module; module='dbparser', filename='/usr/lib/syslog-ng/libdbparser.so'
Trying to open module; module='csvparser', filename='/usr/lib/syslog-ng/libcsvparser.so'
Persistent configuration file is in invalid format, ignoring;
It fails to start as a daemon as well.
Last edited by brazzmonkey (2011-02-16 09:05:18)
what goes up must come down
Offline
Offline
Strange, there aren't any errors there... the linked forum post is supposed to be solved by 45ea08652a which was committed prior to the release of 3.2.2
persist-state: ignore unsupported on-disk formats and overwrite the file
In case syslog-ng crashes, the persist-state file can become empty, and in
case we're downgrading the file will be in an unknown format. Accept
this situation instead of failing at startup
Offline
Thanks Allan. All fixed now.
what goes up must come down
Offline
Pages: 1