On 8/5/2012 8:26 μμ, Peter Haag wrote:
> So it hangs and does not die? or did I misunderstood something?
>
Sorry, my wording is wrong; it dies: Here is a new "death", I just
received:
=========================================================
Program received signal SIGPIPE, Broken pipe.
0x00000036e040df15 in __libc_send (fd=4, buf=0x12e47250, n=12, flags=0)
at ../sysdeps/unix/sysv/linux/x86_64/send.c:28
28 return INLINE_SYSCALL (sendto, 6, fd, buf, n, flags, NULL,
NULL);
(gdb) backtrace full
#0 0x00000036e040df15 in __libc_send (fd=4, buf=0x12e47250, n=12,
flags=0) at ../sysdeps/unix/sysv/linux/x86_64/send.c:28
oldtype = <value optimized out>
result = <value optimized out>
#1 0x00000036e18cf063 in Perl_pp_send (my_perl=0x122cc010) at pp_sys.c:1934
sp = <value optimized out>
mark = 0x123b2498
origmark = 0
targ = 0x12d94000
gv = 0x12e2ffa0
io = 0x12e1f980
bufsv = 0x12d93fd0
buffer = 0x12e47250 ".timeout=10\n"
length = <value optimized out>
retval = <value optimized out>
blen = 12
mg = <value optimized out>
#2 0x00000036e188a39e in Perl_runops_standard (my_perl=0x122cc010) at
run.c:37
No locals.
#3 0x00000036e18380ba in S_run_body (my_perl=0x122cc010) at perl.c:2372
No locals.
#4 perl_run (my_perl=0x122cc010) at perl.c:2289
oldscope = 1
ret = <value optimized out>
cur_env = {je_prev = 0x122cc2a8, je_buf = {{__jmpbuf =
{140737112882744, -4505203467600239115, 0, 140737112882736, 0, 0,
-4505232749203105354,
-4505203375786747859}, __mask_was_saved = 0,
__saved_mask = {__val = {11, 235712106880, 0, 0, 0, 304927072,
304922640, 304922640,
140737112882736, 304927072, 304922640, 235712042554,
0, 304923304, 0, 140737112882744}}}}, je_ret = 0, je_mustcatch = 0 '\000'}
#5 0x00000000004017bc in main (argc=3, argv=0x7fffe99ebe38, env=<value
optimized out>) at perlmain.c:99
exitstatus = -32
=========================================================
As I am running gdb in parallel, I see (the "death" has already occured):
# ps axjf | grep nfsen
13513 25096 25095 13513 pts/5 25095 S+ 0 0:00 | \_
grep nfsen
13569 21875 21875 13569 pts/7 21875 S+ 0 0:00 | \_ gdb
/data/nfsen/bin/nfsend 17558
1 2776 2775 2775 ? -1 S 504 1:17
/usr/local/bin/nfcapd -w -D -p 9995 -u nfsen -g nfsenadmin -B 200000 -S
1 -P /data/nfsen/var/run/p9995.pid -z -n pen 195.251.204.246
/data/nfsen/profiles-data/live/pen -n thi 195.251.204.209
/data/nfsen/profiles-data/live/thi
1 2783 2783 2783 ? -1 Ss 504 0:00
/data/nfsen/bin/nfsend-comm
1 13541 13541 13541 ? -1 Ss 504 0:04
/data/nfsen/bin/nfsend-comm
1 17558 17558 17558 ? -1 Ts 504 3:37 /usr/bin/perl
-w /data/nfsen/bin/nfsend
17558 17559 17559 17559 ? -1 Ss 504 0:00 \_
/data/nfsen/bin/nfsend-comm
and:
# /data/nfsen/bin/nfsen status
NfSen version: 1.3.6p1
NfSen status:
Collector for (pen thi) port 9995 is running [2776].
nfsen daemon: pid: [17558] is running.
But when I exit gdb:
(gdb) quit
A debugging session is active.
Inferior 1 [process 17558] will be detached.
Quit anyway? (y or n) y
LND: Sending signal 13 to Thread 0x2ba021cff770 (LWP 17558)
Detaching from program: /usr/bin/perl, process 17558
then:
# ps axjf | grep nfsen
...
1 2776 2775 2775 ? -1 S 504 1:17
/usr/local/bin/nfcapd -w -D -p 9995 -u nfsen -g nfsenadmin -B 200000 -S
1 -P /data/nfsen/var/run/p9995.pid -z -n pen 195.251.204.246
/data/nfsen/profiles-data/live/pen -n thi 195.251.204.209
/data/nfsen/profiles-data/live/thi
1 2783 2783 2783 ? -1 Ss 504 0:00
/data/nfsen/bin/nfsend-comm
1 13541 13541 13541 ? -1 Ss 504 0:04
/data/nfsen/bin/nfsend-comm
1 17559 17559 17559 ? -1 Ss 504 0:00
/data/nfsen/bin/nfsend-comm
Also:
# /data/nfsen/bin/nfsen status
NfSen version: 1.3.6p1
NfSen status:
Collector for (pen thi) port 9995 is running [2776].
nfsen daemon: pid: [17558] died for unknown reason.
It seems that the above nfsend-comm processes are orphaned (one from the
died nfsen process and the others from earlier nfsen restarts). These
won't go if I do "nfsen start", but only if I first do "nfsen stop" and
then "nfsen start".
> If it dies does it produce a core, you could backtrace?
>
Hmm, how do I do that? The only backtrace I know how to do is the one I
did. If there is something more I can do, please provide details and
I'll be glad to do so.
Regards,
Nick
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Nfsen-discuss mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
