Nmap with snmp-brute script freezes at 33.33%

I’m currently undergoing a penetration testing course where I discover the basics and I have a task where I need to perform SNMP enumeration on a target.

My working environment is as follows :
Host : Windows 10 (64-bit)
Oracle VM VirutalBox machines :

  • Kali Linux 2019.4 (64-bit) : attacker machine, 4GB of RAM, 4 vCPUs, fully up-to-date, NAT network 10.10.10.0/24 with address 10.10.10.11
  • Windows Server 2012R2 (64-bit) : target machine, 5GB of RAM, 2 vCPUs, fully up-to-date, same NAT network 10.10.10.0/24 with address 10.10.10.12

On the target machine, SNMP service has been activated via the “Add roles and features” window and configured to have a basic “public” community string and to allow SNMP packets from any host.

The problem :

I need to use the following command : nmap -sU -p 161 --script=snmp-brute 10.10.10.12 on Kali Linux to brute-force the community string of the target machine.

But when I do so, UDP scan goes on without a problem, but the NSE script just freezes at 33.33%. If I use combination CTRL+X (found it accidentally, didn’t know it was a thing) I get the following information :

Stats: 12:26:31 elapsed; 0 hosts completed (1 up), 1 undergoing Script Scan NSE Timing: About 33.33% done; ETC: 04:57 (24:53:00 remaining) 

and the “time remaining” keeps on rising.

If I increase debugging level to 2 with d, I get these similar packets forever :

NSOCK INFO [47243.1930s] nsock_pcap_read_packet(): Pcap read request from IOD #2  EID 262533 NSOCK INFO [47243.4940s] nsock_trace_handler_callback(): Callback: READ-PCAP TIMEOUT for EID 262533  

Can someone please shed some light on this problem for me ? Thank you very much

gnome-shell freezes and then after a minute crashes

I have been having a lot of issues with Ubuntu such as hangs, crashes, refuses to load my account etc. I have eliminated hardware being the issue as I have checked all my hardware. Some of these issues were fixed by trying different combinations of kernel versions and bios versions. But I still have some gnome-shell crashes that I can’t fix. Checking my logs reveals a lot of error messages I don’t know how many of them or normal. I will attach 2 logs one from gnome-logs google drive to log 1 with only important events showed and another google drive to log 2from journal showing all that plus warnings

I have already said I eliminated hardware being the issue but I am including my specs here

CPU: AMD Ryzen 2700x

Motherboard: Gigabyte Arous GAMING x470

Bios V.: F42A

RAM: XPG Z1 DDR4 3000MHz (PC4 24000) 16GB (2x8GB) Gaming Memory Modules, Silver (AX4U300038G16-DSZ1)

Video Card: Gigabyte GeForce GTX 1080 Windforce OC GV-N1080WF3OC-8GD Graphics Cards)

Power Supply: Corsair TXM Gold 550 W 80+ Gold Certified Semi-modular ATX

DRIVES: M.2 drives 1 Samsung EVO 970(Linux) && 1 Samsung EVO 960 (Windows)
1 SEAGATE 2TB SSHD(games and user files) 1TB SEAGATE Drive HDD (Backups)

Ubuntu 16.04 freezes at Shutdown and restart

Im shashikanth from India. i have reinstalled Ubuntu 16.04 via USB pendrive in DELL Inspiron 15 7577 system. Ubuntu OS doesn’t shut down normally after re-installation. I have to forcefully press the shutdown button for it. I have seen this below links and tried to rectify the error and resolve it but it didn’t work out.

My Ubuntu won't shutdown

Ubuntu 16.04 hangs on shutdown/restart

i tried to install nvidia drivers manually but the screen freezes for this step also.

Can Any Help me resolve this issue asap

Thank you

Random temporary freezes on Acer Swift 3 SF314-56-35xs N17W7

I just bought an Acer Swift 3 SF314-56-35xs model N17W7 and installed Ubuntu 18.04 LTS (kernel 5.0.0-29-generic).

It works, but every 5 minutes or so, the whole system freezes temporarily. I can move the mouse pointer, but nothing is responsive. Nothing happens when I click or type on the keyboard. UI is completely frozen.

After like 2 minutes, the system unfreezes, and key presses etc “catch up”.

dmesg gives the following output:

... nvme nvme0: I/O 493 QID 1 timeout, completion polled nvme nvme0: I/O 837 QID 3 timeout, completion polled nvme nvme0: I/O 348 QID 4 timeout, completion polled ... 

and things like

... systemd-journald.service: Start operation timed out. Terminating snapd.service: Start operation timed out. Terminating snapd.service: State 'stop-sigterm' timed out. Killing. Failed to start Journal Service. Failed to start Snappy daemon. ... 

Based on this post I’ve tried adding the following GRUB_CMDLINE_LINUX parameters…

intel_idle.max_cstate=0 processor.max_cstate=1 modprobe.blacklist=dw_dmac,dw_dmac_core 

…but the problem with temporary freezes persists.

Any idea what the freezes could be due to would be greatly appreciated.

Specs:
Processor: i3-8145U
Graphics: UHD Graphics 620

Full specs


Update: The dmesg output repeats over and over, but seem to only start being generated after suspend/resume.

Random freezes on 19.04, unsure which logs to check

I have scoured both Askubuntu as well other sites for this and haven’t found anything substantial, so I hope it’s not too much of a duplicate.

In any case, I’ve been lately experiencing random freezes – the system locks up completely, my keyboard and mouse do not respond, the PC also disappears from active network clients (by scanning my network with nmap from a different PC) so I assume it dies completely instead of just losing the inputs. It started happening recently, after upgrading to 19.04.

I haven’t been able to pinpoint the problem, and the only common denominator seems to be Chrome. However, even then there’s a huge window of variation, as I can be doing anything from watching YT to just reading Latex formatting tips, so anything from high to low load. I have GPU acceleration and other experimental goodies turned off, so I don’t think it’s that – besides, I never had such problems before 19.04.

The following comes up in /var/log/syslog just before the freeze:

Sep 25 12:31:08 meeshbox systemd[1]: Started Run anacron jobs. Sep 25 12:31:08 meeshbox anacron[11822]: Anacron 2.3 started on 2019-09-25 Sep 25 12:31:08 meeshbox anacron[11822]: Normal exit (0 jobs run) Sep 25 12:31:08 meeshbox systemd[1]: anacron.service: Succeeded. Sep 25 12:31:32 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3802c74 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 214748364 7; this doesn't make much sense. Sep 25 12:31:32 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3802c74 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 214748364 7; this doesn't make much sense. Sep 25 12:36:28 meeshbox org.gnome.Shell.desktop[1329]: [1:1:0925/123628.789445:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a respo nse. Sep 25 12:36:28 meeshbox org.gnome.Shell.desktop[1329]: [1:1:0925/123628.791155:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a respo nse. Sep 25 12:36:45 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x38039d7 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 214748364 7; this doesn't make much sense. Sep 25 12:36:45 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x38039d7 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 214748364 7; this doesn't make much sense. Sep 25 12:38:08 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803b5a sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 214748364 7; this doesn't make much sense. Sep 25 12:38:08 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803b5a sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:38:26 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803bc3 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:38:26 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803bc3 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:38:40 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c21 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:38:40 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c21 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:38:41 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c35 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:38:41 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c35 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:38:42 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c49 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:38:42 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803c49 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:38:51 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803ca1 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:38:51 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803ca1 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:39:02 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803d01 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:39:02 meeshbox org.gnome.Shell.desktop[1329]: Window manager warning: Window 0x3803d01 sets an MWM hint indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x 2147483647; this doesn't make much sense. Sep 25 12:40:09 meeshbox smartd[910]: Device: /dev/sdb [SAT], SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 68 to 67 Sep 25 12:40:09 meeshbox smartd[910]: Device: /dev/sdb [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 32 to 33 Sep 25 12:41:14 meeshbox systemd-resolved[803]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP. 

Nothing of interest in kern.log. Never had this problem with 18.04. It’s not very common, but quite irritating once it happens – for example now, I lost a pretty substantial chunk of code I was writing, as I was dumb enough not to save it. It also never happened when, for example, playing games, even with other stuff in the background. I cannot really pinpoint it properly. However, scouring logs from the last week for when the freezes happened, I found that lines like this:

[1:1:0925/123628.789445:ERROR:child_process_sandbox_support_impl_linux.cc(81)] FontService unique font name matching request did not receive a response. 

are often seen shortly before a freeze – but not immediately before it, more like 3-4 minutes.

What other logs can be relevant to check?

Each alert freezes the desktop for some seconds

Say I am in an app that sends some alert. For instance, when in a terminal I write some gibberish and then press tab. Then, for some seconds, Ubuntu (I don’t know which subsystem really does it) freezes for some seconds before beeping. (I can still move around the mouse, but nothing else.) Then, if I repeat the same action again immediately, it works as expected (beeps without delay). But if I wait some seconds and try again, I get the same ill-behavior. I’m completely at loss here, and it’s really annoying. Help very much appreciated!

18.04 Boot freezes at “Started Hold until boot process finishes up” boot reboot, FYI I’m not using ubuntu as dual

I tried to install some updates and after that when I rebooted the laptop it runs some commands and at last shows “Started hold until boot process finishes up. ” Ctrl+alt+f2 opens command line but there is no display whatsoever. I tried recovery mode and deleting some files but that is of no use as I already had enough memory. Please help thanks in advance.

After an update and few freezes, ubuntu can’t restart properly

I’m facing a peculiar problem with my ubuntu 18.04, Dell computer.

I’m not a huge fan of rebooting on every updates (happened a lot recently) but since Monday few applications refused to worked (they open but nothing is actionable) like the calculator or clicking on “update” from the UI when a new update is available.

Thus today I decided to reboot my computer and then the fun happened. I got stuck on the DELL black screen with this message (the longest I waited was 20min):

Found update fwupdate-b950d63c-f9a5-4823-b48d-395e960ab468-0

File \EFI\ubuntu\fw\fwupdate-KXJikb.cap searched

I forced reboot (power off / on) it boots properly but from now on each time I want to reboot, black screen with the message and I have to manually off / on.

Anyone experienced this and would have a hint about what to look for / how to solve it?

thanks