On Jan 22, 2004, at 3:12 PM, Marc Powell wrote:
> If you're really desparate, you might try to find an OSX equivalent of
> strace/truss to actually attach to the process and see what it's doing.
>
> --
> Marc
Here is a ktrace (translated into text by kdump) of the nsca daemon
while receiving a few submissions. decryption_method=1. it seems to in
fact read in the submission, and seems to do a write as well which
contradicts the problem I am having. I am not knowledgeable enough to
read this ktrace much more than this basic stuff. one thing I dont
understand is the port numbers it's listing... thats not the problem
here I'm sure:
22499 nsca RET select 1
22499 nsca CALL accept(0x3,0,0)
22499 nsca RET accept 6
22499 nsca CALL getpeername(0x6,0xbffff3e0,0xbffff400)
22499 nsca RET getpeername 0
22499 nsca CALL sendto(0x5,0xbfffe6e0,0x48,0,0,0)
22499 nsca GIO fd 5 wrote 72 bytes
"Jan 22 16:21:37 nsca[22499]: Connection from 127.0.0.0 port
50497" ***NOTE: I changed this to not publish the IP
22499 nsca RET sendto 72/0x48
22499 nsca CALL sendto(0x5,0xbfffe6e0,0x3b,0,0,0)
22499 nsca GIO fd 5 wrote 59 bytes
"Jan 22 16:21:37 nsca[22499]: Host address checks out ok"
22499 nsca RET sendto 59/0x3b
22499 nsca CALL select(0x7,0xbffff280,0xbffff300,0xbffff380,0)
22499 nsca RET select 1
22499 nsca CALL sendto(0x5,0xbfffe680,0x3b,0,0,0)
22499 nsca GIO fd 5 wrote 59 bytes
"Jan 22 16:21:37 nsca[22499]: Handling the connection..."
22499 nsca RET sendto 59/0x3b
22499 nsca CALL fcntl(0x6,0x3,0xbffff410)
22499 nsca RET fcntl 2
22499 nsca CALL fcntl(0x6,0x4,0x5)
22499 nsca RET fcntl 0
22499 nsca CALL open(0x6d28,0,0x1b6)
22499 nsca NAMI "/dev/urandom"
22499 nsca RET open 7
22499 nsca CALL fstat(0x7,0xbffff0a0)
22499 nsca RET fstat 0
22499 nsca CALL ioctl(0x7,FIODTYPE,0xbffff0f0)
22499 nsca RET ioctl 0
22499 nsca CALL read(0x7,0x14000,0x20000)
22499 nsca GIO fd 7 read 131072 bytes
"\^E\M-%\M-Z|\M^S\M-O\M-a\M-D\M-j\M-h\M-h;A\M-9\M-e\M^Zc\^D\M-2\M^E\M-
m})\^F\M-4\0\^C\M-%\^_1\M-f\M^\\M-j\M-_\M-\4e\M-o\M^Bl\M-Mb\M-_'{M\
22499 nsca RET read 131072/0x20000
22499 nsca CALL close(0x7)
22499 nsca RET close 0
22499 nsca CALL sendto(0x6,0xbffff380,0x84,0,0,0)
22499 nsca GIO fd 6 wrote 132 bytes
"\0\M-(\M-GK\M-)\^X
\M-[\^C*\M-,~\M-F\M-=\M-Et\^_5\M-L\^P\M^R\M-&t_\^C\^R"\M^L\M
-03@\^Pi\^Q"
22499 nsca RET sendto 132/0x84
22499 nsca CALL select(0x7,0xbffff280,0xbffff300,0xbffff380,0)
22499 nsca RET select 1
22499 nsca CALL recvfrom(0x6,0xbfffee70,0x2d0,0,0,0)
22499 nsca GIO fd 6 wrote 0 bytes
""
22499 nsca RET recvfrom 0
22499 nsca CALL sendto(0x5,0xbfffe170,0x35,0,0,0)
22499 nsca GIO fd 5 wrote 53 bytes
"Jan 22 16:21:37 nsca[22499]: End of connection..."
22499 nsca RET sendto 53/0x35
22499 nsca CALL close(0x6)
22499 nsca RET close 0
22499 nsca CALL select(0x4,0xbffff280,0xbffff300,0xbffff380,0)
22499 nsca RET select 1
22499 nsca CALL accept(0x3,0,0)
22499 nsca RET accept 6
22499 nsca CALL getpeername(0x6,0xbffff3e0,0xbffff400)
22499 nsca RET getpeername 0
22499 nsca CALL sendto(0x5,0xbfffe6e0,0x48,0,0,0)
22499 nsca GIO fd 5 wrote 72 bytes
"Jan 22 16:21:38 nsca[22499]: Connection from 127.0.0.1 port
50498" ***NOTE: I changed this to not publish the IP
22499 nsca RET sendto 72/0x48
22499 nsca CALL sendto(0x5,0xbfffe6e0,0x3b,0,0,0)
22499 nsca GIO fd 5 wrote 59 bytes
"Jan 22 16:21:38 nsca[22499]: Host address checks out ok"
22499 nsca RET sendto 59/0x3b
22499 nsca CALL select(0x7,0xbffff280,0xbffff300,0xbffff380,0)
22499 nsca RET select 1
22499 nsca CALL sendto(0x5,0xbfffe680,0x3b
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]