[syslog-ng]1.5.19 and tcp
CHENNES@Nationwide.com
CHENNES@Nationwide.com
Thu, 8 Aug 2002 14:35:48 -0400
The truss output also shows that the process is ultimately killed. Are you
saying you suspect an "external force" is killing the process.
Balazs Scheidler
<bazsi@balabit.hu> T
To: syslog-ng@lists.balabit.hu
Sent by: cc:
syslog-ng-admin@lists.b
alabit.hu bcc:
Subject: Re: [syslog-ng]1.5.19 and tcp
08/08/02 03:28 AM
Please respond to
syslog-ng
On Wed, Aug 07, 2002 at 02:09:06PM -0400, CHENNES@Nationwide.com wrote:
>
> Here's the gdb backtrace:
>
> gdb syslog-ng -c core
> GNU gdb 4.18
> 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 "sparc-sun-solaris2.8"...
> Core was generated by `/test/syslog/bin/syslog-ng -f /etc/syslog-ng.conf
-p
> /etc/s'.
> Program terminated with signal 9, Killed.
> Reading symbols from /usr/lib/libpthread.so.1...done.
> Reading symbols from /usr/lib/libdoor.so.1...done.
> Reading symbols from /usr/lib/libl.so.1...done.
> Reading symbols from /usr/lib/libsocket.so.1...done.
> Reading symbols from /usr/lib/libnsl.so.1...done.
> Reading symbols from /usr/lib/libxnet.so.1...done.
> Reading symbols from /usr/lib/libc.so.1...done.
> Reading symbols from /usr/lib/libdl.so.1...done.
> Reading symbols from /usr/lib/libmp.so.2...done.
> Reading symbols from
> /usr/platform/SUNW,Sun-Fire-880/lib/libc_psr.so.1...done.
> Reading symbols from /usr/lib/libthread.so.1...done.
> #0 0xff141d00 in _malloc_unlocked () from /usr/lib/libc.so.1
> (gdb) bt
> #0 0xff141d00 in _malloc_unlocked () from /usr/lib/libc.so.1
> #1 0xff141ad0 in malloc () from /usr/lib/libc.so.1
> #2 0x2219c in xalloc ()
> #3 0x17978 in make_log_info (length=0,
> msg=0x3d8d8 "<13>Aug 7 13:59:21 test/test user: [ID 702911
> user.notice] test message number 3\n<13>Aug 7 13:59:21 test/
> test user: [ID 702911 user.notice] test message number 4\n<13>Aug 7
> 13:59:21 "..., prefix=0x0) at log.c:263
> #4 0x15be8 in do_handle_line (self=0xffbefa90, length=89,
> data=0x3d8d8 "<13>Aug 7 13:59:21 test/test user: [ID 702911
> user.notice] test message number 3\n<13>Aug 7 13:59:21 test
> /test user: [ID 702911 user.notice] test message number 4\n<13>Aug 7
> 13:59:21 "..., addr=0x3d8d8, addrlen=0)
> at sources.c:67
> #5 0x15de0 in do_read_line (h=0x3d8a0, read=0xffbefa90) at sources.c:134
> #6 0x202f4 in read_callback ()
> #7 0x1fed4 in io_iter ()
> #8 0x152dc in main_loop (backend=0x395d8) at main.c:191
> #9 0x159ec in main (argc=6, argv=0xffbefd54) at main.c:513
> (gdb)
hmm.. this is not a segfault. the process is killed with signal SIGKILL.
the
original truss output indicated a segfault.
--
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