[Bug 6] New: syslog-ng dies after cron.daily
https://bugzilla.balabit.com/show_bug.cgi?id=6 Summary: syslog-ng dies after cron.daily Product: syslog-ng Version: 2.0.x Platform: PC URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=427791 OS/Version: Linux Status: NEW Severity: critical Priority: unspecified Component: syslog-ng AssignedTo: bazsi@balabit.hu ReportedBy: sasa@debian.org Type of the Report: bug Estimated Hours: 0.0
From bugs.debian.org:
Syslog-ng is dying repeatedly after logrotate runs. I believe that in most cases it continues to log to the original file, despite it having been rotated, though I am not 100% sure of this. Where it does continue running, it dies when the 2nd rotate occurs, where the logfile is gzipped. When trying to reproduce it manually, sending kill -HUP causes syslog-ng to die shortly after it gets a new PID. I am able to consistently reproduce this. No data is written to the new logfile until I manually restart syslog-ng For now, as a workaround, I have altered the post-rotate command to restart syslog-ng rather than reload. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=6 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |NEEDINFO --- Comment #1 from Balazs Scheidler <bazsi@balabit.hu> 2007-12-25 21:35:26 --- Well, this report is for 2.0.0 which is over a year old. I don't know about any recent HUP related issues and the strace dump is not very helpful either. At least a core file and an accompanying debug-enabled binary is what could move me forward. (or alternatively a way to reproduce the problem). -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=6 Jacek Kalinski <jacek_kal@o2.pl> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEEDINFO |REOPENED CC| |jacek_kal@o2.pl --- Comment #2 from Jacek Kalinski <jacek_kal@o2.pl> 2008-01-29 11:21:05 --- I can confirm, that after running logrotate, kill -HUP stops to log messages to logfile. But only to the file which was rotated - all other (not rotated) files are correct and new messages appear in that files. So the syslog-ng is still working in the background. It started after I upgraded (on 11th January) syslog-ng from 2.0.5 to 2.0.7 and eventlog from 0.2.5 to 0.2.7. Before upgrade (on 2.0.5 everything was working fine). There wasn't any other changes in packages version or is system configuration. I know, that at least 3 times 'maillog' file wasn't correctly created after logrotate (nothing was logged in this file). Only full restart of syslog-ng (stop, start) can fix the problem. logrotate entry: /log/system/log/maillog /log/system/log/maillog-amavis /log/system/log/maillog-imapd /log/system/log/maillog-pop3d { size=80M rotate 8 compress sharedscripts postrotate /bin/kill -HUP `cat /var/run/syslog-ng.pid 2>/dev/null` 2>/dev/null || true endscript olddir /log/system/log/old } major syslog-ng.conf entries: options { dir_perm(0700); perm(0600); chain_hostnames(no); keep_hostname(yes); dir_owner(root); dir_group(root); owner(root); group(root); }; source local { unix-stream("/dev/log" max_connections(300)); file("/proc/kmsg"); internal(); }; filter f_notimapd { not program("imapd"); }; filter f_notpop3d { not program("pop3d"); }; filter f_notamavis { not program("amavis"); }; filter f_11 { facility(mail) and level(debug..emerg); }; destination d_7 { file("/log/system/log/maillog" create_dirs(yes)); }; log { source(local); filter(f_11); filter(f_notimapd); filter(f_notpop3d); filter(f_notamavis); destination(d_7); }; It is a production environment, so I can't do a lot of tests, but I can try. If a corefile would be helpful, how can I dump it from a running process? -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
https://bugzilla.balabit.com/show_bug.cgi?id=6 Balazs Scheidler <bazsi@balabit.hu> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution| |WORKSFORME Status|REOPENED |RESOLVED --- Comment #3 from Balazs Scheidler <bazsi@balabit.hu> 2008-01-31 10:04:48 --- This is a completely different issue. 2.0.7 had a change which caused a similar regression. Latest snapshots should be fine. See the mailing list archives for more details. I'm closing this with WORKSFORME now, the original crash problem has not appeared since, if you still have problems with the latest snapshot, please file a new bug. Thanks. -- Configure bugmail: https://bugzilla.balabit.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.
participants (1)
-
bugzilla＠bugzilla.balabit.com