Re: Nmap Hangs while scanning

[Zuleyha Torku]

Ofcourse, you are right. I did not see that lines mentioning "no space
left" at first sight. Sorry, I'll look into that problem first.

Thank you so much

On 5 Aug 2017 5:22 p.m., "Ax0n"  wrote:

> From your dmesg, my first suggestion would be to look at the cause of
> what's filling up / and /home (per the snippet from your dmesg pasted below
> my response). Next, I'd upgrade to a supported release (OpenBSD 6.1) and
> fully update it with syspatch, then try nmap again. If it persists, try
> again using the latest snapshot (-CURRENT) if you can. I use nmap
> frequently from i386, sparc64 and amd64 and haven't had this problem. It
> still looks like nmap might be exhausting your hard drive space. What
> arguments are you passing to nmap? We don't need to see the IP addresses
> you're scanning, but it would help to know how many IPs are you scanning at
> a time as well.
>
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 0 on /usr: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
> uid 1000 on /home: file system full
>
> On Sat, Aug 5, 2017 at 8:29 AM, Zuleyha Torku 
> wrote:
>
>> Hi
>> I'm trying to scan a bunch of IP address with nmap on OpenBSD 5.9 amd64.
>> After a few moments nmap hangs but not crash or fall into unresponsive
>> state. When I check with tcpdump it stops packet generation. No Error
>> messages, no warning. Cpu and Mem. usages are normal as usual.
>>
>> I could not get any error that help me to define what is the problem even
>> if I set verbose option.
>> Have you ever seen this behaviour ? How can I go further ?
>>
>>
>>
>>
>> OpenBSD 5.9 (GENERIC) #1761: Fri Feb 26 01:15:04 MST 2016
>> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
>> real mem = 1056817152 (1007MB)
>> avail mem = 1020686336 (973MB)
>> mpath0 at root
>> scsibus0 at mpath0: 256 targets
>> mainbus0 at root
>> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf6a20 (9 entries)
>> bios0: vendor SeaBIOS version "
>> rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org" date 04/01/2014
>> bios0: QEMU Standard PC (i440FX + PIIX, 1996)

Re: Nmap Hangs while scanning

[Ax0n]

>From your dmesg, my first suggestion would be to look at the cause of
what's filling up / and /home (per the snippet from your dmesg pasted below
my response). Next, I'd upgrade to a supported release (OpenBSD 6.1) and
fully update it with syspatch, then try nmap again. If it persists, try
again using the latest snapshot (-CURRENT) if you can. I use nmap
frequently from i386, sparc64 and amd64 and haven't had this problem. It
still looks like nmap might be exhausting your hard drive space. What
arguments are you passing to nmap? We don't need to see the IP addresses
you're scanning, but it would help to know how many IPs are you scanning at
a time as well.

uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full

On Sat, Aug 5, 2017 at 8:29 AM, Zuleyha Torku 
wrote:

> Hi
> I'm trying to scan a bunch of IP address with nmap on OpenBSD 5.9 amd64.
> After a few moments nmap hangs but not crash or fall into unresponsive
> state. When I check with tcpdump it stops packet generation. No Error
> messages, no warning. Cpu and Mem. usages are normal as usual.
>
> I could not get any error that help me to define what is the problem even
> if I set verbose option.
> Have you ever seen this behaviour ? How can I go further ?
>
>
>
>
> OpenBSD 5.9 (GENERIC) #1761: Fri Feb 26 01:15:04 MST 2016
> dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
> real mem = 1056817152 (1007MB)
> avail mem = 1020686336 (973MB)
> mpath0 at root
> scsibus0 at mpath0: 256 targets
> mainbus0 at root
> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf6a20 (9 entries)
> bios0: vendor SeaBIOS version "
> rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org" date 04/01/2014
> bios0: QEMU Standard PC (i440FX + PIIX, 1996)
> acpi0 at bios0: rev 0
> acpi0: sleep states S3 S4 S5
> acpi0: tables DSDT FACP APIC HPET
> acpi0: wakeup devices
> acpitimer0 at acpi0: 3579545 Hz, 24 bits
> acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
> cpu0 at mainbus0: apid 0 (boot processor)
> cpu0: Westmere E56xx/L56xx/X56xx (Nehalem-C), 2200.29 MHz
> cpu0:
> FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,
> 

Nmap Hangs while scanning

[Zuleyha Torku]

Hi
I'm trying to scan a bunch of IP address with nmap on OpenBSD 5.9 amd64.
After a few moments nmap hangs but not crash or fall into unresponsive
state. When I check with tcpdump it stops packet generation. No Error
messages, no warning. Cpu and Mem. usages are normal as usual.

I could not get any error that help me to define what is the problem even
if I set verbose option.
Have you ever seen this behaviour ? How can I go further ?




OpenBSD 5.9 (GENERIC) #1761: Fri Feb 26 01:15:04 MST 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC
real mem = 1056817152 (1007MB)
avail mem = 1020686336 (973MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xf6a20 (9 entries)
bios0: vendor SeaBIOS version "
rel-1.9.1-0-gb3ef39f-prebuilt.qemu-project.org" date 04/01/2014
bios0: QEMU Standard PC (i440FX + PIIX, 1996)
acpi0 at bios0: rev 0
acpi0: sleep states S3 S4 S5
acpi0: tables DSDT FACP APIC HPET
acpi0: wakeup devices
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Westmere E56xx/L56xx/X56xx (Nehalem-C), 2200.29 MHz
cpu0:
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,MMX,FXSR,SSE,SSE2,SSE3,PCLMUL,SSSE3,CX16,SSE4.1,SSE4.2,x2APIC,POPCNT,AES,HV,NXE,LONG,LAHF,ARAT
cpu0: 64KB 64b/line 2-way I-cache, 64KB 64b/line 2-way D-cache, 512KB
64b/line 16-way L2 cache
cpu0: ITLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: DTLB 255 4KB entries direct-mapped, 255 4MB entries direct-mapped
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges
cpu0: apic clock running at 999MHz
ioapic0 at mainbus0: apid 0 pa 0xfec0, version 11, 24 pins
acpihpet0 at acpi0: 1 Hz
acpiprt0 at acpi0: bus 0 (PCI0)
acpicpu0 at acpi0: C1(@1 halt!)
pvbus0 at mainbus0: KVM
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel 82441FX" rev 0x02
pcib0 at pci0 dev 1 function 0 "Intel 82371SB ISA" rev 0x00
pciide0 at pci0 dev 1 function 1 "Intel 82371SB IDE" rev 0x00: DMA, channel
0 wired to compatibility, channel 1 wired to compatibility
pciide0: channel 0 disabled (no drives)
pciide0: channel 1 disabled (no drives)
uhci0 at pci0 dev 1 function 2 "Intel 82371SB USB" rev 0x01: apic 0 int 11
piixpm0 at pci0 dev 1 function 3 "Intel 82371AB Power" rev 0x03: apic 0 int
9
iic0 at piixpm0
vga1 at pci0 dev 2 function 0 "Bochs VGA" rev 0x02
wsdisplay0 at vga1 mux 1: console (80x25, vt100 emulation)
wsdisplay0: screen 1-5 added (80x25, vt100 emulation)
virtio0 at pci0 dev 3 function 0 "Qumranet Virtio Network" rev 0x00
vio0 at virtio0: address 52:54:00:a5:1f:57
virtio0: apic 0 int 11
eap0 at pci0 dev 4 function 0 "Ensoniq AudioPCI" rev 0x00: apic 0 int 11
audio0 at eap0
midi0 at eap0: 
virtio1 at pci0 dev 5 function 0 "Qumranet Virtio Storage" rev 0x00
vioblk0 at virtio1
scsibus1 at vioblk0: 2 targets
sd0 at scsibus1 targ 0 lun 0:  SCSI3 0/direct fixed
sd0: 51200MB, 512 bytes/sector, 104857600 sectors
virtio1: apic 0 int 10
virtio2 at pci0 dev 6 function 0 "Qumranet Virtio Memory" rev 0x00
viomb0 at virtio2
virtio2: apic 0 int 10
isa0 at pcib0
isadma0 at isa0
fdc0 at isa0 port 0x3f0/6 irq 6 drq 2
fd0 at fdc0 drive 1: density unknown
pckbc0 at isa0 port 0x60/5 irq 1 irq 12
pckbd0 at pckbc0 (kbd slot)
wskbd0 at pckbd0: console keyboard, using wsdisplay0
pms0 at pckbc0 (aux slot)
wsmouse0 at pms0 mux 0
pcppi0 at isa0 port 0x61
spkr0 at pcppi0
usb0 at uhci0: USB revision 1.0
uhub0 at usb0 "Intel UHCI root hub" rev 1.00/1.00 addr 1
nvram: invalid checksum
uhidev0 at uhub0 port 1 configuration 1 interface 0 "QEMU QEMU USB Tablet"
rev 2.00/0.00 addr 2
uhidev0: iclass 3/0
ums0 at uhidev0: 3 buttons, Z dir
wsmouse1 at ums0 mux 0
vscsi0 at root
scsibus2 at vscsi0: 256 targets
softraid0 at root
scsibus3 at softraid0: 256 targets
root on sd0a (0077973165a15151.a) swap on sd0b dump on sd0b
WARNING: / was not properly unmounted
clock: unknown CMOS layout
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 0 on /usr: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid 1000 on /home: file system full
uid