Hi, I've released syslog-ng version 1.4.0rc2, fixing all known bugs in previous versions. I've also reorganized the downloads tree, each major version has a distinct directory, and libol was moved up in the directory hierarchy. My website in currently syncing, but as soon as this is completed you'll find 1.4.0rc2 here: http://www.balabit.hu/downloads/syslog-ng/1.4/syslog-ng-1.4.0rc2.tar.gz and libol: http://www.balabit.hu/downloads/libol/0.2/libol-0.2.16.tar.gz -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
Balazs Scheidler wrote:
Hi,
I've released syslog-ng version 1.4.0rc2, fixing all known bugs in previous versions.
bad luck, I found some probleme: this sample configuration destination all { file( "/tmp/messages"); file( "/opt/syslog/var/log/syslogs/$HOST_$FACILITY_$LEVEL_$PROGRAM_$YEAR_$MONTH_$DAY"); }; generate on hostname ts ( SunOS ts 5.6 Generic_105181-19 sun4u sparc SUNW,Ultra-60) (those file when starting syslogd ( which dump dmsg): -rw------- 1 root root 684 Feb 23 19:13 ts_kern_info_?<SUN9.0G_2000_02_23 -rw------- 1 root root 128 Feb 23 19:13 ts_kern_info_Copyright_2000_02_23 -rw------- 1 root root 104 Feb 23 19:13 ts_kern_info_Ethernet_2000_02_23 -rw------- 1 root root 636 Feb 23 19:13 ts_kern_info_PCI-device_2000_02_23 -rw------- 1 root root 184 Feb 23 19:13 ts_kern_info_SUNW,ffb0_2000_02_23 -rw------- 1 root root 446 Feb 23 19:13 ts_kern_info_SUNW,hme0_2000_02_23 -rw------- 1 root root 580 Feb 23 19:13 ts_kern_info_SUNW,hme1_2000_02_23 -rw------- 1 root root 124 Feb 23 19:13 ts_kern_info_SUNW,isptwo0_2000_02_23 -rw------- 1 root root 190 Feb 23 19:13 ts_kern_info_SunOS_2000_02_23 -rw------- 1 root root 84 Feb 23 19:13 ts_kern_info_avail_2000_02_23 -rw------- 1 root root 89 Feb 23 19:13 ts_kern_info_cpu0_2000_02_23 -rw------- 1 root root 178 Feb 23 19:13 ts_kern_info_cpu1_2000_02_23 -rw------- 1 root root 122 Feb 23 19:13 ts_kern_info_cpu_2000_02_23 -rw------- 1 root root 120 Feb 23 19:13 ts_kern_info_dump_2000_02_23 -rw------- 1 root root 214 Feb 23 19:13 ts_kern_info_glm0_2000_02_23 -rw------- 1 root root 218 Feb 23 19:13 ts_kern_info_glm1_2000_02_23 -rw------- 1 root root 154 Feb 23 19:13 ts_kern_info_isp0_2000_02_23 -rw------- 1 root root 170 Feb 23 19:13 ts_kern_info_keyboard_2000_02_23 -rw------- 1 root root 98 Feb 23 19:13 ts_kern_info_mem_2000_02_23 -rw------- 1 root root 170 Feb 23 19:13 ts_kern_info_mouse_2000_02_23 -rw------- 1 root root 96 Feb 23 19:13 ts_kern_info_pci1011,240_2000_02_23 -rw------- 1 root root 186 Feb 23 19:13 ts_kern_info_pci108e,80000_2000_02_23 -rw------- 1 root root 186 Feb 23 19:13 ts_kern_info_pci108e,80001_2000_02_23 -rw------- 1 root root 306 Feb 23 19:13 ts_kern_info_root_2000_02_23 -rw------- 1 root root 212 Feb 23 19:13 ts_kern_info_sd15_2000_02_23 -rw------- 1 root root 212 Feb 23 19:13 ts_kern_info_sd16_2000_02_23 -rw------- 1 root root 254 Feb 23 19:13 ts_kern_info_sd1_2000_02_23 -rw------- 1 root root 212 Feb 23 19:13 ts_kern_info_sd21_2000_02_23 -rw------- 1 root root 254 Feb 23 19:13 ts_kern_info_sd2_2000_02_23 -rw------- 1 root root 254 Feb 23 19:13 ts_kern_info_sd3_2000_02_23 -rw------- 1 root root 254 Feb 23 19:13 ts_kern_info_sd4_2000_02_23 -rw------- 1 root root 230 Feb 23 19:13 ts_kern_info_se0_2000_02_23 -rw------- 1 root root 170 Feb 23 19:13 ts_kern_info_stdin_2000_02_23 -rw------- 1 root root 134 Feb 23 19:13 ts_kern_info_stdout_2000_02_23 -rw------- 1 root root 230 Feb 23 19:13 ts_kern_info_su0_2000_02_23 -rw------- 1 root root 230 Feb 23 19:13 ts_kern_info_su1_2000_02_23 -rw------- 1 root root 109 Feb 23 19:13 ts_kern_info_syncing_2000_02_23
more ts_kern_info_Copyright_2000_02_23 Feb 23 19:13:27 local@ts (c) 1983-1997, Sun Microsystems, Inc. Feb 23 19:13:27 local@ts (c) 1983-1997, Sun Microsystems, Inc.
Hope this information help. ( I guess program macro is matched against a given field in the syslog line so that there is nothing to do...) S.R.
Hi,
I've released syslog-ng version 1.4.0rc2, fixing all known bugs in previous versions.
bad luck, I found some probleme:
this sample configuration
destination all { file( "/tmp/messages"); file( "/opt/syslog/var/log/syslogs/$HOST_$FACILITY_$LEVEL_$PROGRAM_$YEAR_$MONTH_$DAY"); };
generate on hostname ts ( SunOS ts 5.6 Generic_105181-19 sun4u sparc SUNW,Ultra-60) (those file when starting syslogd ( which dump dmsg):
Hope this information help.
( I guess program macro is matched against a given field in the syslog line so that there is nothing to do...)
The problem basically is that Linux sysklogd sends messages without date and host info, thus if no date is found the first word is taken as programname. I don't think clean solution exists. I added a workaround so that when a message from LOG_KERN arrives, it has "kernel" as programname. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 url: http://www.balabit.hu/pgpkey.txt
Balazs Scheidler wrote:
Hi,
I've released syslog-ng version 1.4.0rc2, fixing all known bugs in previous versions.
Got another probleme when running a "client" syslog which forward evrything to a "server" one, in the debug I see those message: ( syslog-ns -d -v) io.c: Preparing fd 22 for writing Cannot open file /opt/syslog/var/log/syslogs/limpopo_kern_info_on /pseudo/md@0_2000_02_24 for writing (No such file or directory) io.c: Preparing fd 23 for writing Cannot open file /opt/syslog/var/log/syslogs/limpopo_kern_info_is </pci@1f,4000/ebus@1/se@14,400000_2000_02_24 for writing (No such file or directory) Cannot open file /opt/syslog/var/log/syslogs/limpopo_kern_info_is </pci@1f,4000/ebus@1/se@14,400000_2000_02_24 for writing (No such file or directory) io.c: Preparing fd 24 for writing io.c: Preparing fd 25 for writing Cannot open file /opt/syslog/var/log/syslogs/limpopo_kern_info_on /pseudo/md@0_2000_02_24 for writing (No such file or directory) Cannot open file /opt/syslog/var/log/syslogs/limpopo_kern_info_is </pci@1f,4000/ebus@1/se@14,400000_2000_02_24 for writing (No such file or directory) Cannot open file /opt/syslog/var/log/syslogs/limpopo_kern_info_is </pci@1f,4000/ebus@1/se@14,400000_2000_02_24 for writing (No such file or directory) Garbage collecting while idle... both host are running solaris 2.6. S.R.
participants (2)
-
Balazs Scheidler
-
Un L'Unique