On Tue, 4 Oct 2005, Dan Muldoon wrote:
You could always strace it .. Or is it truss on Solaris ..
Something like:
strace nessusd
and watch the tons of output you'll get .. You want debugging? Try that ..
Yep, truss under Solaris.
The client's looping with:
ioctl(4, FIONREAD, 0xFFBFF304) = 0
pollsys(0x003EF528, 1, 0xFFBFF3C8, 0x00000000) = 0
pollsys(0xFFBFF138, 1, 0xFFBFF1D0, 0x00000000) = 0
ioctl(4, FIONREAD, 0xFFBFF304) = 0
pollsys(0x003EF528, 1, 0xFFBFF3C8, 0x00000000) = 0
nessusd is looping with:
pollsys(0xFFBFD390, 1, 0xFFBFD438, 0x00000000) = 0
pollsys(0xFFBFD3A0, 1, 0xFFBFD438, 0x00000000) = 0
waitid(P_ALL, 0, 0xFFBFD360, WEXITED|WTRAPPED|WNOHANG) = 0
kill(8156, SIG#0) = 0
pollsys(0xFFBFD390, 1, 0xFFBFD438, 0x00000000) = 0
pollsys(0xFFBFD3A0, 1, 0xFFBFD438, 0x00000000) = 0
waitid(P_ALL, 0, 0xFFBFD360, WEXITED|WTRAPPED|WNOHANG) = 0
kill(8156, SIG#0) = 0
and the parent nessusd is having a nap, as you'd expect, with:
accept(4, 0xFFBFF500, 0xFFBFF0F4, SOV_DEFAULT) (sleeping...)
Reading the output of truss before either the client or server process
starts looping doesn't give me any hints as to what's going wrong.
You said you got the binaries from sunfreeware? If so, try compiling
your own .. Even without GTK, heck .. Honestly the windows GUI client is
the best GUI client anyway, even the authors will admit that. I usually
stick to the CLI though ... Less headaches..
Yep, been there - tried that. :) Tried both CSW/Blastwave's pre-compiled
binaries and compiled my own from source. Both result in a nessusd that
does exactly the same. GTK, cmd-line, batch-mode - doesn't matter what the
client's doing or where it is.
gcc version 3.43, Solaris 10 Generic sun4u, nessus 2.2.5, openssl 0.9.8
(and tried downgrading to last version of 0.9.7).
PD
--
Paul Day
Network Security Administrator
Toll Corporate IT
_______________________________________________
Nessus mailing list
[email protected]
http://mail.nessus.org/mailman/listinfo/nessus
