Hi,

I am trying to solve an issue with scans that stop without a clear 
indication.

Last friday (Jan 4, 2002) I installed Red Hat Linux 7.2 on a machine and 
updated the whole. Installed nmap 2.54BETA30 (latest at that moment) on 
the machine.

I installed the latest Development version from CVS. Compiling went ok and 
a quick test seemed to do just fine..

I then did the usual type of scanning against a network protected by a 
FGireWall-1 machine to verify the installation was done correctly. It 
started the scanns including the nmap scanns but stopped scanning after 
about 15 minutes.

I checked the nessusd.messages file and noticed that each individual test 
is started and ends normally. But at some point in time no further tests 
are started.

If I stop the test for a specific IP address (I'm testing 5 machines 
concurrently) then the next Ip address will be tested and things seem to 
be fine for a while untill the same issue repeats itself.

Does anyone have a clue on how to tackle this problem? I'm out of ideas 
but this has been troubling us for months now and occurs both with the 
stable and the development versions.

I have found no obvious issues and have extensive logging of the build 
process as well as the normal logging of the activities.

The machine has 256 MB and was using over half of that for 
caching/buffering and swap usage was 0

Hugo.

-- 
All email send to me is bound to the rules described on my homepage.
    [EMAIL PROTECTED]            http://hvdkooij.xs4all.nl/
            Don't meddle in the affairs of sysadmins,
            for they are subtle and quick to anger.

Reply via email to