I'm replying to my own message :) I think I found the cause of the problem. Syslog-ng isn't crashing anymore, I removed the line: timereap (10); from the configuration. And I forgot to mention, that the there wasn't a computer that receives the log messages on the other end, so I got the following messages in logs. [Fri 00:00:04] syslog-ng[354]: Error connecting to remote host AF_INET(159.148.62.9:65535), reatte mpting in 10 seconds [err - syslog] Hope this helps someone else... Regards, Rudolfs On Thursday 14 August 2003 09:55, Rudolfs Osins wrote:
Hello everyone,
I have the folloving problem:
After some hours as daemon (~1 - 2h) syslog-ng crashes, leaving no info on what happened in the logs or elsewhere. I run the daemon with syslog-ng -u syslog-ng -g syslog-ng and the user and group exists in the system. The config file I use is attached. Compile options are following:
libol-0.3.10 ./configure --prefix=/usr/local/opt/libol make
syslog-ng-1.6.0rc3 ./configure --prefix=/usr/local/opt/syslog-ng --with-libol=/usr/src/libol-0.3.10 make make install
The system is a celeron 1700Mhz with 128Mb ram and there are just 2 other proccesses beside syslog-ng - fcron and ntpd.
Another question is: when I delete a logfile when syslog-ng is still running for the first time, syslog-ng recreates the file, when it recives a message thats destination is the deleted file, but when I delete the same file a second time, it's not being recreated. Is there a way to make syslog-ng recreate the file everytime ?
And the last question is, when could the message encryption feature be implemented ?
Btw. great work ! Syslog-ng is a really good product !
best regards, Rudolfs