[syslog-ng] [Bug 6] syslog-ng dies after cron.daily

[bugzilla at bugzilla.balabit.com]

https://bugzilla.balabit.com/show_bug.cgi?id=6


Jacek Kalinski <jacek_kal at o2.pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEEDINFO                    |REOPENED
                 CC|                            |jacek_kal at o2.pl




--- Comment #2 from Jacek Kalinski <jacek_kal at 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.