-
Notifications
You must be signed in to change notification settings - Fork 178
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cuckoo1: the guest initialization hit the critical timeout, analysis aborted. #503
Comments
that is bcz your network or agent is misconfigured, follow the documentation |
the network and agent are communicating curl 10.10.10.13:8000 <title>Error response</title>Error responseError code 501. Message: Unsupported method ('GET'). Error code explanation: 501 = Server does not support this operation. |
i am able to ping guest VM at 10.10.10.13 64 bytes from 10.10.10.13: icmp_seq=7716 ttl=128 time=0.273 ms |
post, logs, and versions of everything |
hi, sorry for replying late i was out of town for a few days.Following is the log of the task that i tried to run2018-04-16 21:22:10,700 [lib.cuckoo.core.scheduler] INFO: Using "virtualbox" machine manager with max_analysis_count=0, max_machines_count=0, and max_vmstartup_count=10 |
Its my understanding that for all the versions of cuckoo guest VM's should be in snapshot resume mode. As all guest VM's should be started by Cuckoo itself as mentioned by you. But in snapshot resume mode neither curl works nor guest VM IP's are pingable. Is that could be problem ? |
yes they should be in running mode.
|
let me post the VB guest configuration.Please note as it was interfering with the cuckoosandbox so i changed the IP scheme to 192.168.58.1/24 as 192.168.58.1 the host ip and 192.168.58.11 the guest VM IP and network interface to vboxnet2
|
conf looks good, any custom iptables? |
yes i had custom IP tables for the previous subnets 192.168.56.1 and 10.10.10.1. But i had no rules assigned for 192.168.58.1. following is the result.Chain INPUT (policy ACCEPT) Chain FORWARD (policy ACCEPT) Chain OUTPUT (policy ACCEPT) Chain ufw-after-forward (1 references) Chain ufw-after-input (1 references) Chain ufw-after-logging-forward (1 references) Chain ufw-after-logging-input (1 references) Chain ufw-after-logging-output (1 references) Chain ufw-after-output (1 references) Chain ufw-before-forward (1 references) Chain ufw-before-input (1 references) Chain ufw-before-logging-forward (1 references) Chain ufw-before-logging-input (1 references) Chain ufw-before-logging-output (1 references) Chain ufw-before-output (1 references) Chain ufw-reject-forward (1 references) Chain ufw-reject-input (1 references) Chain ufw-reject-output (1 references) Chain ufw-track-forward (1 references) Chain ufw-track-input (1 references) Chain ufw-track-output (1 references) |
@doomedraven hello, any update on this that could be useful? |
|
not working, still same error Can you do me a favor? If your cuckoo is working fine, can u pack ur conf folder (all files) and email me so i can cross ref it with my config files? or i can do it vice versa and you can cross ref them, which ever option suits you. |
here is the complete log ======================================= 2018-04-20 00:59:18,219 [lib.cuckoo.core.scheduler] INFO: Using "virtualbox" machine manager with max_analysis_count=0, max_machines_count=0, and max_vmstartup_count=10 (wkhtmltopdf:13735): IBUS-WARNING **: Unable to connect to ibus: Could not connect: Connection refused ============================================================= |
im not using vbox so that won't be useful for you, but it looks like network error or network configuration on your side |
i cannot think of any other way to resolve this issue. How about if you send me [api auxiliary cuckoo processing reporting memory conf files]? |
nop, they don't have anything to see here, that is network related issue |
agent.py or agent.pyw what should be used? |
that is the same, just without window -> documentation |
@doomedraven i tried almost everything. curl output to both is OK. Tried the snapshot restore, and guest power off method. All of these resulted in guest VM being up as could be seen in Gui but the debug log continuously shows 2018-04-20 02:45:54,116 [lib.cuckoo.core.resultserver] DEBUG: ResultServer running on 192.168.58.1:2043. which i understood and as mentioned by you is that agent is not communicating or there is network error. firewall is disabled on both, bit defender, uac, updates are off on guest vm. even i have disabled user login. how the hell could i get rid of this error ? its been 3 weeks now, i am unable to find its solution.. can it be the issue of virtualbox as hypervisor? |
could be, vbox doing weird iptables stuff nowdays my suggestion, start cuckoo task for example url analysis with timeout 1000 and without user interaction, and once vm is started, test curl vm:8000, ping is useless for this purpose so you will be able to investigate a bit the network and the rest |
the error not make any sense, idk what is wrong here |
i now configured KVM and result is the same. It appears that there is some kind of problem from guest side. |
idk |
can you tag anyone else who can help me out here? :/ |
all interested person receiving email about all issues so they can decide if they want to help or not |
did you resolve it? i've the same problems and i can't resolve it ! Help! |
i am continuously getting the above mentioned error. I tired to increase the time limit upto 3600 seconds with memory dump off but its still the same error. Also i tried different sampls, all result in the same manner. why is it happening?
The text was updated successfully, but these errors were encountered: