Open Meow-ops opened 8 years ago
I wonder why 2016-11-21 17:41:12,177 [lib.cuckoo.core.guest] DEBUG: cuckoo1: error retrieving status: timed out
happens. It seems it cannot contact the agent anymore so maybe the agent did freeze.
I have the same issue with the same guest (Win7x86), did you by chance use VMCloak to create the VM?
Did the VM reboot? 9 times out of 10 in my environment I get that error because some program caused the VM to reboot. Once that happens we cant contact the agent anymore and the agent also can't tell us the analysis is over so it continues until the critical timeout is reached.
The vm didn't reboot, but the cuckoo agent froze.
If it's just happening with some particular sample, it could also be that it's disabling networking somehow, which would prevent the agent from communicating. I would like to start using libguestfs actually instead of networking for transferring files and logs between the guest and host.
-Brad
Using cuckoo in a Windows 7 32bits environment with the following sample:
34510ceb373808c65949cbbe111bf2e3
The error2016-11-21 17:41:13,178 [lib.cuckoo.core.scheduler] ERROR: The analysis hit the critical timeout, terminating.
appears in red.The results are not complete, some process are empty, dropped files too, and process memory cannot be accessed.
With debug log:
In the vm, the agent seems to freeze. I cannot move the window anymore.