Your message dated Mon, 30 Oct 2006 09:16:52 +0100
with message-id <[EMAIL PROTECTED]>
and subject line I think this bug is related to network logging, not cron.
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: syslog-ng
Version: 2.0rc3-1
Severity: grave
Hi,
I've configured syslog-ng to log from the net and to a remote host, and it
worked fine.
Oct 4 06:25:05 beteigeuze syslog-ng[3953]: SIGHUP received, reloading
configuration;
Oct 4 06:25:05 beteigeuze syslog-ng[3953]: Duplicate stats counter;
Oct 4 06:25:41 beteigeuze syslog-ng[3953]: EOF occurred while idle; fd='8'
Oct 4 06:25:41 beteigeuze syslog-ng[3953]: Connection broken; time_reopen='10'
Oct 4 06:25:41 beteigeuze tripwire[11129]: Integrity Check Complete:
Oct 4 06:35:05 beteigeuze syslog-ng[3953]: Log statistics;
Oct 4 06:45:05 beteigeuze syslog-ng[3953]: Log statistics
AT the 4th Oct syslog-ng was upgraded from version 2.0rc1-2.2 to 2.0rc3-1.
2006-10-04 08:01:26 upgrade syslog-ng 2.0rc1-2 2.0rc3-1
And at the 5th Oct 6:25 it dies quit, after (or while) cron.daily runs.
Oct 5 06:21:34 beteigeuze syslog-ng[11869]: Log statistics;
Oct 5 06:25:01 beteigeuze /USR/SBIN/CRON[12306]: (root) CMD (test -x
/usr/sbin/anacron || run-parts
--report /etc/cron.daily)
Oct 5 06:25:18 beteigeuze syslog-ng[11869]: SIGHUP received, reloading
configuration;
Since there are no more entries in log-files (local or remote) because the
syslog-ng process is gone
without a word. After a few days I took notic that syslog-ng is gone so I start
it with
„/etc/init.d/syslog-ng start“ without any problems.
But next mornig after cron.daily syslog-ng dies again. I start it again and it
works the hole day till netx
morning.
Oct 13 06:25:01 beteigeuze /USR/SBIN/CRON[31470]: (root) CMD (test -x
/usr/sbin/anacron || run-parts
--report /etc/cron.daily)
Oct 13 06:25:16 beteigeuze syslog-ng[31108]: SIGHUP received, reloading
configuration;
Oct 13 06:25:58 beteigeuze tripwire[31679]: Integrity Check Complete:
Oct 13 06:28:07 beteigeuze syslog-ng[31722]: syslog-ng starting up;
version='2.0rc3'
Oct 14 06:25:01 beteigeuze /USR/SBIN/CRON[1509]: (root) CMD (test -x
/usr/sbin/anacron || run-parts --report
/etc/cron.daily)
Oct 14 06:25:16 beteigeuze syslog-ng[31722]: SIGHUP received, reloading
configuration;
Oct 14 06:26:01 beteigeuze tripwire[1639]: Integrity Check Complete:
Oct 14 07:31:07 beteigeuze syslog-ng[2079]: syslog-ng starting up;
version='2.0rc3'
I thought there is a cron-job killing syslog-ng, so I start every script in
/etc/cron.daily/ by hand but
nothing happend. I tried /etc/init.d/syslog-ng reload but it worked fine - till
next morning.
So I downgrade to syslog-ng 1.6.5-2.2 and it worked fine over the next morning
and so on.
I am using Debian GNU/Linux etch, up-to-date
kernel 2.6.17-2-686 #1 SMP Wed Sep 13 16:34:10 UTC 2006 i686 GNU/Linux
Two 2,59GHz Intel Pentium 4 Processors, 511M RAM
and libc6 2.3.6.ds1-4
Greetings,
Stefan
--- End Message ---
--- Begin Message ---
I have reread the bug report and in the beginning there is the answer
for my question.
So I think this bug is fixed in version 2.0rc3-2.
--
Szalay Attila BalaBit IT Biztonságtechnikai Kft.
tel:(36-1)-371-05-40 HU-1115 Budapest, Bártfai u. 54
fax:(36-1)-208-08-75 http://www.balabit.hu/
--- End Message ---
