Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#20522 - [syslog-ng] Remote logging stopped working

Attached to Project: Arch Linux
Opened by steve (steve___) - Thursday, 19 August 2010, 18:20 GMT
Last edited by Allan McRae (Allan) - Saturday, 11 December 2010, 10:49 GMT
Task Type Bug Report
Category Packages: Core
Status Closed
Assigned To Aaron Griffin (phrakture)
Allan McRae (Allan)
Architecture i686
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
Remote logging stopped working when syslog-ng-3.1.2-1-i686.pkg.tar.xz was installed.

Failing back to syslog-ng 3.1.0-1 works.

Relevant bits from /etc/syslog-ng.conf

destination d_net { udp("192.168.110.13"); };
filter f_all { level(warning..emerg); };
log { source(src); filter(f_all); destination(d_net); };
This task depends upon

Closed by  Allan McRae (Allan)
Saturday, 11 December 2010, 10:49 GMT
Reason for closing:  Fixed
Additional comments about closing:  syslog-ng-3.2.1-1
Comment by Allan McRae (Allan) - Tuesday, 26 October 2010, 01:51 GMT
Can anybody confirm or deny this bug? I can not find anything upstream about this and do not use remote logging myself.
Comment by steve (steve___) - Tuesday, 26 October 2010, 15:07 GMT
I can confirm syslog-ng-3.1.1-1-i686.pkg.tar.xz works. The problem for me is with syslog-ng-3.1.2-1-i686.pkg.tar.xz. I have tested on multiple computers on our LAN; both i686 and x86_64

Configuration
-------------
CLIENT MACHINE (192.168.110.100 -- HOSTNAME: steve)
$ vi /etc/syslog-ng.conf
destination d_net { udp("192.168.110.13"); };
filter f_all { level(warning..emerg); };
log { source(src); filter(f_all); destination(d_net); };

$ /etc/rc.d/syslog-ng restart

SERVER MACHINE (192.168.110.13)
$ touch /var/log/all.log
$ vi /etc/syslog-ng.conf
source s_net { udp (); };
destination d_df_all { file("/var/log/all.log"); };
filter f_central { host("192.168.110.100|steve") and level(warning..emerg); };
log { source(s_net); filter(f_central); destination (d_df_all); };

$ /etc/rc.d/syslog-ng restart

Test
----
$ logger -p user.warn ooga ## from CLIENT
$ tail /var/log/everything.log ## confirm message "ooga" got this far

$ tail /var/log/all.log ## from SERVER; confirm message "ooga" was remote logged
Comment by Allan McRae (Allan) - Friday, 03 December 2010, 13:36 GMT
try syslog-ng-3.2.1-1 in [testing] (no need to enable all [testing] - it is safe to install on its own).
Comment by steve (steve___) - Monday, 06 December 2010, 21:06 GMT
I tested syslog-ng-3.2.1-1-i686.pkg.tar.xz on one machine and it worked.

Loading...