On Mon, 23 Jan 2006 19:46:27 +0000 Dominic Cleal <[EMAIL PROTECTED]> wrote:
> After just updating to version 1.9.8, syslog-ng is repeatedly logging > this, causing 100% CPU usage and was creating some very large log > files. Ok, I didn't realise that this host had a custom config file on and not a stock one. Replacing it with the backed up stock one caused syslog-ng to act normally. Looking at my custom config further, it uses the $HOST_FROM macro in the log file paths for my destination definitions. It appears that src/macros.c defines HOST_FROM (line 96) but the switch statement starting on line 149 doesn't handle it, so it falls through to the default case and causes that log error. For whatever reason, this is looping as fast as the PC can handle, which is resulting in 100% CPU usage with syslog-ng running. It has however hit a 2GB cap on the log file size which has stemmed the tide as syslog-ng isn't starting up with the 2GB log file in place. I don't see anything in either changelog regarding HOST_FROM changing or being removed. Has it been superseded? -- Dominic Cleal [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
