FW: UNSTABLE syslog-ng 1.4.15 + redhat-7.3
After Core's dump problem I've got another with FREE-BSD 4.6, I'm still waiting for an helping hand ;). I tried to install syslog-ng 1.4.15 on a redhat-7.3 system but it's Unstable without CORE Dump File. The attachment is the debug's backtrace with installed packets and configuration files... Another question, the last, what is the most STABLE version of REDHAT or FreeBDS I'd use?? Thnks. _/CaT\_ PS: If I succeed in my syslog-server Mission when you'll come to Rome (Caput Mundi), I 'll offer you the real pizza with a real red wine to "ZOZZONE's" --- gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110) flex version 2.5.4 (rpm flex-2.5.4a-23) bison (GNU Bison) 1.35 (rpm bison-1.35-1) yacc 1.9 (rpm byacc-1.9-19) scsh-0.6.2 libol-0.2.23 syslog-ng-1.4.15 --- GNU gdb Red Hat Linux (5.2-2) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... (gdb) run -v Starting program: /usr/local/sbin/syslog-ng -v binding fd 5, inetaddr: 0.0.0.0, port: 514 Program received signal SIGTERM, Terminated. 0x420b4ae7 in pause () from /lib/i686/libc.so.6 (gdb) bt #0 0x420b4ae7 in pause () from /lib/i686/libc.so.6 #1 0x08049d0d in go_background () #2 0x08049e93 in main () #3 0x42017499 in __libc_start_main () from /lib/i686/libc.so.6 ---- ######################################################################## ## options { long_hostnames(off); keep_hostname(no); sync(0); use_dns(no); log_fifo_size(1000); gc_idle_threshold(100); gc_busy_threshold(3000); }; ######################################################################## ## source src { internal(); udp(ip(0.0.0.0) port(514)); }; ######################################################################## ### ###Destination #Sorting degl'hosts # destination hosts { file("/var/log/hosts/$HOST/$YEAR/$MONTH/$DAY/$FACILITY$YEAR$MONTH$DAY" owner(root) group(mspns) perm(0644) dir_perm(0700) create_dirs(yes)); }; # destination all { file("/var/log/all.log" owner(root) group(mspns) perm(0644)); }; # destination send_trap_prova { program("/usr/local/script/syslogtrapper_test"); }; # ######################################################################## #### ####Filtering # filter f_prova { host ("10.11.5.37") and not match ("message repeated"); }; # ######################################################################## ##### ###Logging # log { source(src); destination(hosts); }; # log { source(src); destination(all); }; # log { source(src); filter(f_prova); destination(send_trap_prova); }; # ######################################################################## ##### # /usr/local/script/syslogtrapper_test # #!/bin/bash while read line do snmptrap -c xxxxxx! 10.11.8.14 .1.3.6.1.4.1.2620.1.1.0 10.11.5.48 6 2 '' .1.3.6.1.4.1.2620.1.1.6 s "prova invio trap V1: $line" done exit
On Thu, Jul 25, 2002 at 10:14:10AM +0200, _/CaT_ wrote:
After Core's dump problem I've got another with FREE-BSD 4.6, I'm still waiting for an helping hand ;).
I tried to install syslog-ng 1.4.15 on a redhat-7.3 system but it's Unstable without CORE Dump File. The attachment is the debug's backtrace with installed packets and configuration files...
Another question, the last, what is the most STABLE version of REDHAT or FreeBDS I'd use??
Thnks.
_/CaT\_
PS: If I succeed in my syslog-server Mission when you'll come to Rome (Caput Mundi), I 'll offer you the real pizza with a real red wine to "ZOZZONE's"
---
gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110) flex version 2.5.4 (rpm flex-2.5.4a-23) bison (GNU Bison) 1.35 (rpm bison-1.35-1) yacc 1.9 (rpm byacc-1.9-19) scsh-0.6.2 libol-0.2.23 syslog-ng-1.4.15 ---
GNU gdb Red Hat Linux (5.2-2) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... (gdb) run -v Starting program: /usr/local/sbin/syslog-ng -v binding fd 5, inetaddr: 0.0.0.0, port: 514
Program received signal SIGTERM, Terminated. 0x420b4ae7 in pause () from /lib/i686/libc.so.6 (gdb) bt #0 0x420b4ae7 in pause () from /lib/i686/libc.so.6 #1 0x08049d0d in go_background () #2 0x08049e93 in main () #3 0x42017499 in __libc_start_main () from /lib/i686/libc.so.6
as syslog-ng goes to background immediately after starting up, this backtrace is unusable. please run syslog-ng with the -d option to avoid going into background. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
Hi *, When I start the application with debug mode, apparently work normally, but I remember , in other session of debug , The debug output consist in a string, the following: "Garbage Collect..." do you think that is a real problem or a normal application job ? The red-hat version I use is stable,You said that,my problem perhaps is due to a bad installation because i've got the same result in another installation, Under Free-BSD. If you have an HOW-TO Installation,detailed please, send it to me by mail, or publish it on the mailing list. Another question...The last..I tried to "CHROOT" the application whit the following options : -C <> or --chroot=<> --user=<> --group=<> in the cage space, but The program unrecognized the options. Now the application is working with debug mode and works normally..(since 15 hours).. Ciao. -----Original Message----- From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-admin@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Thursday, July 25, 2002 10:13 AM To: syslog-ng@lists.balabit.hu Subject: Re: [syslog-ng]FW: UNSTABLE syslog-ng 1.4.15 + redhat-7.3 On Thu, Jul 25, 2002 at 10:14:10AM +0200, _/CaT_ wrote:
After Core's dump problem I've got another with FREE-BSD 4.6, I'm still waiting for an helping hand ;).
I tried to install syslog-ng 1.4.15 on a redhat-7.3 system but it's Unstable without CORE Dump File. The attachment is the debug's backtrace with installed packets and configuration files...
Another question, the last, what is the most STABLE version of REDHAT or FreeBDS I'd use??
Thnks.
_/CaT\_
PS: If I succeed in my syslog-server Mission when you'll come to Rome
(Caput Mundi), I 'll offer you the real pizza with a real red wine to "ZOZZONE's"
---
gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110) flex version 2.5.4 (rpm flex-2.5.4a-23) bison (GNU Bison) 1.35 (rpm bison-1.35-1) yacc 1.9 (rpm byacc-1.9-19) scsh-0.6.2 libol-0.2.23 syslog-ng-1.4.15 ---
GNU gdb Red Hat Linux (5.2-2) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... (gdb) run -v Starting program: /usr/local/sbin/syslog-ng -v binding fd 5, inetaddr: 0.0.0.0, port: 514
Program received signal SIGTERM, Terminated. 0x420b4ae7 in pause () from /lib/i686/libc.so.6 (gdb) bt #0 0x420b4ae7 in pause () from /lib/i686/libc.so.6 #1 0x08049d0d in go_background () #2 0x08049e93 in main () #3 0x42017499 in __libc_start_main () from /lib/i686/libc.so.6
as syslog-ng goes to background immediately after starting up, this backtrace is unusable. please run syslog-ng with the -d option to avoid going into background. -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
On Fri, Jul 26, 2002 at 10:21:22AM +0200, _/CaT_ wrote:
Hi *, When I start the application with debug mode, apparently work normally, but I remember , in other session of debug , The debug output consist in a string, the following: "Garbage Collect..." do you think that is a real problem or a normal application job ?
it is normal that syslog-ng reports garbage collecting messages.
The red-hat version I use is stable,You said that,my problem perhaps is due to a bad installation because i've got the same result in another installation, Under Free-BSD. If you have an HOW-TO Installation,detailed please, send it to me by mail, or publish it on the mailing list. Another question...The last..I tried to "CHROOT" the application whit the following options :
-C <> or --chroot=<> --user=<> --group=<> in the cage space, but The program unrecognized the options.
it is implemented in 1.5.x
Now the application is working with debug mode and works normally..(since 15 hours)..
the problem should be fixed anyway. please do the following: ulimit -c unlimited (to let the program dump core) syslog-ng (dumps core) gdb syslog-ng -c core (reference to core file) gdb> bt (to get a backtrace where it aborted itself) thanks, -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
On RH I've never got a core dump....Do you know a method for generate a core dump file? Before all possible test, why you don't give me the your best installation procedure? However, in the attachment I send you a BT of FreeBSD: gdb syslog-ng -c syslog-ng.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... Core was generated by `syslog-ng'. Program terminated with signal 6, Abort trap. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x280ae7b4 in kill () from /usr/lib/libc.so.4 (gdb) bt #0 0x280ae7b4 in kill () from /usr/lib/libc.so.4 #1 0x280eeb26 in abort () from /usr/lib/libc.so.4 #2 0x280cad7b in __assert () from /usr/lib/libc.so.4 #3 0x8052116 in io_iter () #4 0x8049b4e in main_loop () #5 0x8049e57 in main () #6 0x8049779 in _start () -----Original Message----- From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-admin@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Friday, July 26, 2002 10:22 AM To: syslog-ng@lists.balabit.hu Subject: Re: [syslog-ng]FW: UNSTABLE syslog-ng 1.4.15 + redhat-7.3 On Fri, Jul 26, 2002 at 10:21:22AM +0200, _/CaT_ wrote:
Hi *, When I start the application with debug mode, apparently work normally, but I remember , in other session of debug , The debug output consist in a string, the following: "Garbage Collect..." do you think that is a real problem or a normal application job ?
it is normal that syslog-ng reports garbage collecting messages.
The red-hat version I use is stable,You said that,my problem perhaps is due to a bad installation because i've got the same result in another installation, Under Free-BSD. If you have an HOW-TO Installation,detailed please, send it to me by mail, or publish it on the mailing list. Another question...The last..I tried to "CHROOT" the application whit the following options :
-C <> or --chroot=<> --user=<> --group=<> in the cage space, but The program unrecognized the options.
it is implemented in 1.5.x
Now the application is working with debug mode and works normally..(since 15 hours)..
the problem should be fixed anyway. please do the following: ulimit -c unlimited (to let the program dump core) syslog-ng (dumps core) gdb syslog-ng -c core (reference to core file) gdb> bt (to get a backtrace where it aborted itself) thanks, -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
HI *, Thnkz gdb syslog-ng -c core.17720 GNU gdb Red Hat Linux (5.2-2) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... Core was generated by `/usr/local/sbin/syslog-ng'. Program terminated with signal 5, Trace/breakpoint trap. Reading symbols from /lib/libnsl.so.1...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/i686/libc.so.6...done. Loaded symbols for /lib/i686/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /lib/libnss_files.so.2...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /lib/libnss_nisplus.so.2...done. Loaded symbols for /lib/libnss_nisplus.so.2 Reading symbols from /lib/libnss_dns.so.2...done. Loaded symbols for /lib/libnss_dns.so.2 Reading symbols from /lib/libresolv.so.2...done. Loaded symbols for /lib/libresolv.so.2 #0 0x4000bd01 in _dl_debug_state_internal () from /lib/ld-linux.so.2 (gdb) bt #0 0x4000bd01 in _dl_debug_state_internal () from /lib/ld-linux.so.2 #1 0x421122f2 in dl_open_worker () from /lib/i686/libc.so.6 #2 0x4000b4b3 in _dl_catch_error_internal () from /lib/ld-linux.so.2 #3 0x42112761 in _dl_open () from /lib/i686/libc.so.6 #4 0x42113491 in do_dlopen () from /lib/i686/libc.so.6 #5 0x4000b4b3 in _dl_catch_error_internal () from /lib/ld-linux.so.2 #6 0x4211333c in __libc_dlopen () from /lib/i686/libc.so.6 #7 0x420f5157 in __nss_lookup_function () from /lib/i686/libc.so.6 #8 0x420f5ae1 in __nss_next () from /lib/i686/libc.so.6 #9 0x420f7b21 in gethostbyaddr_r@@GLIBC_2.1.2 () from /lib/i686/libc.so.6 #10 0x420f78cb in gethostbyaddr () from /lib/i686/libc.so.6 #11 0x0804a28f in get_source_hostname () #12 0x0804a384 in do_add_source_name () #13 0x0804f5de in do_handle_afinet_line () #14 0x0804a004 in do_handle_line () #15 0x0804a132 in do_read_line () #16 0x0805144d in read_callback () #17 0x08051198 in io_iter () #18 0x08049c15 in main_loop () #19 0x08049f51 in main () #20 0x42017499 in __libc_start_main () from /lib/i686/libc.so.6 (gdb) -----Original Message----- From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-admin@lists.balabit.hu] On Behalf Of _/CaT\_ Sent: Friday, July 26, 2002 11:27 AM To: syslog-ng@lists.balabit.hu Subject: RE: [syslog-ng]FW: UNSTABLE syslog-ng 1.4.15 + redhat-7.3 On RH I've never got a core dump....Do you know a method for generate a core dump file? Before all possible test, why you don't give me the your best installation procedure? However, in the attachment I send you a BT of FreeBSD: gdb syslog-ng -c syslog-ng.core GNU gdb 4.18 (FreeBSD) Copyright 1998 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-unknown-freebsd"...(no debugging symbols found)... Core was generated by `syslog-ng'. Program terminated with signal 6, Abort trap. Reading symbols from /usr/lib/libc.so.4...(no debugging symbols found)...done. Reading symbols from /usr/libexec/ld-elf.so.1...(no debugging symbols found)...done. #0 0x280ae7b4 in kill () from /usr/lib/libc.so.4 (gdb) bt #0 0x280ae7b4 in kill () from /usr/lib/libc.so.4 #1 0x280eeb26 in abort () from /usr/lib/libc.so.4 #2 0x280cad7b in __assert () from /usr/lib/libc.so.4 #3 0x8052116 in io_iter () #4 0x8049b4e in main_loop () #5 0x8049e57 in main () #6 0x8049779 in _start () -----Original Message----- From: syslog-ng-admin@lists.balabit.hu [mailto:syslog-ng-admin@lists.balabit.hu] On Behalf Of Balazs Scheidler Sent: Friday, July 26, 2002 10:22 AM To: syslog-ng@lists.balabit.hu Subject: Re: [syslog-ng]FW: UNSTABLE syslog-ng 1.4.15 + redhat-7.3 On Fri, Jul 26, 2002 at 10:21:22AM +0200, _/CaT_ wrote:
Hi *, When I start the application with debug mode, apparently work normally, but I remember , in other session of debug , The debug output consist in a string, the following: "Garbage Collect..." do you think that is a real problem or a normal application job ?
it is normal that syslog-ng reports garbage collecting messages.
The red-hat version I use is stable,You said that,my problem perhaps is due to a bad installation because i've got the same result in another installation, Under Free-BSD. If you have an HOW-TO Installation,detailed please, send it to me by mail, or publish it on the mailing list. Another question...The last..I tried to "CHROOT" the application whit the following options :
-C <> or --chroot=<> --user=<> --group=<> in the cage space, but The program unrecognized the options.
it is implemented in 1.5.x
Now the application is working with debug mode and works normally..(since 15 hours)..
the problem should be fixed anyway. please do the following: ulimit -c unlimited (to let the program dump core) syslog-ng (dumps core) gdb syslog-ng -c core (reference to core file) gdb> bt (to get a backtrace where it aborted itself) thanks, -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1 _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html _______________________________________________ syslog-ng maillist - syslog-ng@lists.balabit.hu https://lists.balabit.hu/mailman/listinfo/syslog-ng Frequently asked questions at http://www.campin.net/syslog-ng/faq.html
On Tue, Jul 30, 2002 at 08:33:43AM +0200, _/CaT_ wrote:
HI *, Thnkz
gdb syslog-ng -c core.17720 GNU gdb Red Hat Linux (5.2-2) Copyright 2002 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i386-redhat-linux"... Core was generated by `/usr/local/sbin/syslog-ng'. Program terminated with signal 5, Trace/breakpoint trap. Reading symbols from /lib/libnsl.so.1...done. Loaded symbols for /lib/libnsl.so.1 Reading symbols from /lib/i686/libc.so.6...done. Loaded symbols for /lib/i686/libc.so.6 Reading symbols from /lib/ld-linux.so.2...done. Loaded symbols for /lib/ld-linux.so.2 Reading symbols from /lib/libnss_files.so.2...done. Loaded symbols for /lib/libnss_files.so.2 Reading symbols from /lib/libnss_nisplus.so.2...done. Loaded symbols for /lib/libnss_nisplus.so.2 Reading symbols from /lib/libnss_dns.so.2...done. Loaded symbols for /lib/libnss_dns.so.2 Reading symbols from /lib/libresolv.so.2...done. Loaded symbols for /lib/libresolv.so.2 #0 0x4000bd01 in _dl_debug_state_internal () from /lib/ld-linux.so.2 (gdb) bt #0 0x4000bd01 in _dl_debug_state_internal () from /lib/ld-linux.so.2 #1 0x421122f2 in dl_open_worker () from /lib/i686/libc.so.6 #2 0x4000b4b3 in _dl_catch_error_internal () from /lib/ld-linux.so.2 #3 0x42112761 in _dl_open () from /lib/i686/libc.so.6 #4 0x42113491 in do_dlopen () from /lib/i686/libc.so.6 #5 0x4000b4b3 in _dl_catch_error_internal () from /lib/ld-linux.so.2 #6 0x4211333c in __libc_dlopen () from /lib/i686/libc.so.6 #7 0x420f5157 in __nss_lookup_function () from /lib/i686/libc.so.6 #8 0x420f5ae1 in __nss_next () from /lib/i686/libc.so.6 #9 0x420f7b21 in gethostbyaddr_r@@GLIBC_2.1.2 () from /lib/i686/libc.so.6 #10 0x420f78cb in gethostbyaddr () from /lib/i686/libc.so.6 #11 0x0804a28f in get_source_hostname () #12 0x0804a384 in do_add_source_name () #13 0x0804f5de in do_handle_afinet_line () #14 0x0804a004 in do_handle_line () #15 0x0804a132 in do_read_line () #16 0x0805144d in read_callback () #17 0x08051198 in io_iter () #18 0x08049c15 in main_loop () #19 0x08049f51 in main () #20 0x42017499 in __libc_start_main () from /lib/i686/libc.so.6 (gdb)
This backtrace is very strange. it shows that syslog-ng hit a breakpoint in libc while resolving names... as it seems you compiled against glibc 2.1, and running on glibc 2.2? -- Bazsi PGP info: KeyID 9AF8D0A9 Fingerprint CD27 CFB0 802C 0944 9CFD 804E C82C 8EB1
participants (2)
-
_/CaT\_
-
Balazs Scheidler