search

owasp-amass / amass

In-depth attack surface mapping and asset discovery
https://owasp.org/www-project-amass/
Other
11.78k stars 1.86k forks source link

“the data source startup routines timed out”，Unable to Scan #928

Open komomon opened 1 year ago

komomon commented 1 year ago

the data source startup routines timed out ，Why does this bug appear after scanning several times? It can only be resolved by restarting the computer, but the latest version still has this bug image

netc4ts commented 1 year ago

Same issue here, but restarting the computer does not solve it for me. Seeing the logs I find this:

10:46:11.841582 CIRCL: check callback failed for the configuration
10:46:11.841716 Detectify: check callback failed for the configuration
10:46:11.841759 360PassiveDNS: check callback failed for the configuration
10:46:11.841781 CertCentral: check callback failed for the configuration
10:46:11.841802 ZETAlytics: check callback failed for the configuration
10:46:11.841807 ASNLookup: check callback failed for the configuration
10:46:11.841851 Chaos: check callback failed for the configuration
10:46:11.841873 Hunter: check callback failed for the configuration

I haven't configured anything by hand, I just installed amass.

TGRBirdFlying commented 1 year ago

Is there a solution to this problem？I have the same problem. Good luck to you!

guillaume-d commented 11 months ago

Same issue here, but restarting the computer does not solve it for me. Seeing the logs I find this:

10:46:11.841582 CIRCL: check callback failed for the configuration
10:46:11.841716 Detectify: check callback failed for the configuration
10:46:11.841759 360PassiveDNS: check callback failed for the configuration
10:46:11.841781 CertCentral: check callback failed for the configuration
10:46:11.841802 ZETAlytics: check callback failed for the configuration
10:46:11.841807 ASNLookup: check callback failed for the configuration
10:46:11.841851 Chaos: check callback failed for the configuration
10:46:11.841873 Hunter: check callback failed for the configuration

I haven't configured anything by hand, I just installed amass.

The "check callback failed for the configuration" messages are sometimes harmless but confusing, see https://github.com/owasp-amass/amass/issues/943.