Skip to content

Atlas stalls, and sometimes runs up to 100% CPU #77

@auspex

Description

@auspex

Over 2 hours ago, atlas started the following tasks:

root       44797  0.0  0.2  47496 32416 ?        S    12:44   0:02 nmap -O -p- 192.168.2.91 -oG /config/logs/nmap_tcp_192_168_2_91.log
root       44799  0.0  0.2  47892 33760 ?        S    12:44   0:02 nmap -O -p- 192.168.2.156 -oG /config/logs/nmap_tcp_192_168_2_156.log
root       44803  0.0  0.2  47760 32864 ?        S    12:44   0:02 nmap -O -p- 192.168.2.101 -oG /config/logs/nmap_tcp_192_168_2_101.log
root       44809  0.0  0.2  48816 33984 ?        S    12:44   0:04 nmap -O -p- 192.168.2.91 -oG /config/logs/nmap_tcp_192_168_2_91.log
root       44816  0.0  0.2  46968 32864 ?        S    12:44   0:01 nmap -O -p- 192.168.2.186 -oG /config/logs/nmap_tcp_192_168_2_186.log
root       44826  0.0  0.2  48024 33760 ?        S    12:44   0:02 nmap -O -p- 192.168.2.156 -oG /config/logs/nmap_tcp_192_168_2_156.log
root       44828  0.0  0.2  46968 33088 ?        S    12:44   0:01 nmap -O -p- 192.168.2.186 -oG /config/logs/nmap_tcp_192_168_2_186.log
root       44831  0.0  0.2  47892 33760 ?        S    12:44   0:04 nmap -O -p- 192.168.2.101 -oG /config/logs/nmap_tcp_192_168_2_101.log
root       44834  0.0  0.2  47760 32640 ?        S    12:44   0:02 nmap -O -p- 192.168.2.105 -oG /config/logs/nmap_tcp_192_168_2_105.log
root       44982  0.0  0.2  48024 33312 ?        S    12:44   0:02 nmap -O -p- 192.168.2.127 -oG /config/logs/nmap_tcp_192_168_2_127.log
root       44983  0.0  0.2  47760 33088 ?        S    12:44   0:03 nmap -O -p- 192.168.2.107 -oG /config/logs/nmap_tcp_192_168_2_107.log
root       44984  0.0  0.2  49080 34680 ?        S    12:44   0:04 nmap -O -p- 192.168.2.107 -oG /config/logs/nmap_tcp_192_168_2_107.log
root       44987  0.0  0.2  48420 34208 ?        S    12:44   0:03 nmap -O -p- 192.168.2.109 -oG /config/logs/nmap_tcp_192_168_2_109.log
root       44988  0.0  0.2  48156 33536 ?        S    12:44   0:04 nmap -O -p- 192.168.2.106 -oG /config/logs/nmap_tcp_192_168_2_106.log
root       44990  0.0  0.2  47892 33204 ?        S    12:44   0:02 nmap -O -p- 192.168.2.109 -oG /config/logs/nmap_tcp_192_168_2_109.log

16 tasks, 7 of them duplicated.

The unique ones reported "Nmap done" a minute or two later, but they haven't terminated.
The duplicated ones report:

# Nmap 7.95 scan initiated Sat Nov 29 16:44:11 2025 as: nmap -O -p- -oG /config/logs/nmap_tcp_192_168_2_109.log 192.168.2.109

and nothing else.

I never get any kind of graphical display.

Surely this isn't normal?

Note, I came to this because I was investigating a network problem. That first device, .91 is a Bosch cooktop, that is dropping every third packet when I ping it. So, I know there's something wrong with my network, but it also doesn't seem right (or useful) if Atlas gets hung up when it can't nmap a device.

I started nmap -O -p- 192.168.2.91 on my desktop a few minutes ago, and it hasn't done anything yet, either.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions