This repository was archived by the owner on Feb 26, 2021. It is now read-only.
Conversation
Member
|
Hi @J12934, it seems this RTTVar errors are more or less a normal behavior of nmap if the network or target responses to slow. I get this error also some time at my local maschine with nmap (without SCB) ... RTT = Round-Trip-Time https://www.hackerboard.de/threads/meldungen-beim-nmap-scan.1316/ |
Member
Author
|
Ah never understood it meant round trip time 👍 I think this branch is stable enough to be merged. We've been using it for our scans since and didn't encounter any problems with it so far. |
Weltraumschaf
approved these changes
Jan 20, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Nmap scans sometimes randomly crash with its log output looking something like this:
SCANNING location: "1.2.3.4/24", parameters: "--top-ports 50" RTTVAR has grown to over 2.3 seconds, decreasing to 2.0 Failed to perform Job "32184673-aa9f-4e17-af0e-bbca77122157" Error: Failed to execute nmap portscan. at ScannerScaffolding.worker [as _worker] (/src/src/nmap.js:138:23) at process._tickCallback (internal/process/next_tick.js:68:7) Job Failure submitted succesfully.This error completely crashes the scan, even thought the log indicates that nmap is able to recover from it.
"Unfortunately" this error happens relatively rarely. So debugging / fixing this might be more of a long term effort.