syslog-ng craches when sending from syslog-ng to another loghost (that have syslog-ng)
Hi, Im running syslog-ng-2.1beta2-1 on 2 of my servers. i have the same configuration on both the servers except that i want server A to forward messages to server B All works fine for a couple of minutes, then server A:s syslog-ng service craches without any information. running CentOS 5.0 on both servers with syslog-ng installed as rpm packages from balabit. i have also tried with udp() instead of tcp() with the same result. options { sync (0); time_reopen (10); log_fifo_size (1000); long_hostnames (off); use_dns (yes); dns_cache(yes); use_fqdn (no); create_dirs (no); keep_hostname (yes); log_msg_size(8192); }; source s_sys { file ("/proc/kmsg" log_prefix("kernel: ")); unix-stream ("/dev/log"); internal(); # udp(ip(0.0.0.0) port(514)); }; source s_udp { udp(); }; source s_tcp { tcp(max-connections(200)); }; destination d_loghost { tcp("192.168.1.150" port(514)); }; log { source(s_sys); source(s_tcp); source(s_udp); destination(d_loghost); }; Any sugestions? -- Vänliga hälsningar / Best Regards Mattias Ryrlén __________________________ op5 AB Första Långgatan 19 SE-413 27 Göteborg Mobil: +46 735-17 70 99 Support: +46 31-774 09 24 www.op5.com
On Thu, 2008-10-02 at 09:23 +0200, Mattias Ryrlén wrote:
Hi,
Im running syslog-ng-2.1beta2-1 on 2 of my servers.
i have the same configuration on both the servers except that i want server A to forward messages to server B
All works fine for a couple of minutes, then server A:s syslog-ng service craches without any information.
This is probably the "Log statistics" related bug that was fixed in 2.1.1, released a couple of weeks ago. -- Bazsi
Ok, i will try to upgrade our package then. Thanks! On Thu, 2008-10-02 at 10:06 +0200, Balazs Scheidler wrote:
On Thu, 2008-10-02 at 09:23 +0200, Mattias Ryrlén wrote:
Hi,
Im running syslog-ng-2.1beta2-1 on 2 of my servers.
i have the same configuration on both the servers except that i want server A to forward messages to server B
All works fine for a couple of minutes, then server A:s syslog-ng service craches without any information.
This is probably the "Log statistics" related bug that was fixed in 2.1.1, released a couple of weeks ago.
-- Vänliga hälsningar / Best Regards Mattias Ryrlén __________________________ op5 AB Första Långgatan 19 SE-413 27 Göteborg Mobil: +46 735-17 70 99 Support: +46 31-774 09 24 www.op5.com
participants (2)
-
Balazs Scheidler
-
Mattias Ryrlén