Skip to content

Cuckoo Error Handling

Jump to bottom
Clevero edited this page May 3, 2019 · 1 revision

Cuckoo Error Handling

All jobs are hanging in "Pending", what could be wrong?

Please look through the logs of cuckoosandbox if you find some like

Please update your configuration. Unable to shut 'win7_2_java8x86_1' down or find the machine in its proper state: Unable to get status for win7_2_java8x86_1

or 2.

CuckooDependencyError: Couldn't import pyVmomi, please install it (using `pip install -U pyvmomi`)

  1. If you use VirtualBox as your hypervisor, su to user peekaboo and run vboxmanage list vms

    1. This ensures that your vboxmanage.conf file is correctly filled. Possible problems could be the wrong IP of the cuckoo host or wrong ssh credentials (also if you do not accepted the key of the ssh-server of the cuckoo host)
    2. If you get asked for the password -> you do not have correctly installed the ssh-key of the peekaboo user of the peekaboo-vm to the user of the user of the hypervisor that is managing your VM's

  2. If you use vSphere, the PeekabooAV-Installer does not install the python package that cuckoo needs when talking to the vSphere host (since Peekaboo uses virtualbox per default)

    1. Install the python "pyVomi" package inside the env of cuckoo

    2. activate env/go

All jobs are hanging in "Pending" and vboxmanage can correctly display me the configured vm's or at least you know that cuckoo can successfully load the configured analysis vm (displayed at startup of cuckoo)

Do always remember that cuckoo is splitted into multiple processes.

If the Webinterface shows that attachments are "Pending", please ensure that cuckooapi, cuckoosandbox and cuckoohttpd are correctly running

Quote:

If analyses are all remaining on pending, I suspect Cuckoo itself is not running.
Cuckoo, Cuckoo web, Cuckoo API are all seperate processes.

Have you started Cuckoo? You can start it using cuckoo or cuckoo --debug. 😄

https://github.com/cuckoosandbox/cuckoo/issues/2346#issuecomment-400460945


I do always get the error message It appears that this Virtual Machine hasn't been configured properly as the Cuckoo Host wasn't able to the connect [...]

Please go through this checklist for ensuring that both VM's can correctly communicate:

I assume for example the following config:

  • Peekaboo: 192.168.56.5
  • cuckoo101: 192.168.56.101
  • Hypervisor/Gateway: 192.168.56.1
  • Do both VM's have their correct static IP address and the address of the gateway assigned?
  • Start cuckoo101 from the snapshot:
    • Can you ping from both VM's the gateway at 192.168.56.1?
    • Can you ping the peekaboo vm from cuckoo101? (and vice versa)
  • Inside virtualbox.conf
    • do you have set the correct interface that has access to the subnet of both vm's?
    • is the IP for the result_server correct? Should be 192.168.56.5 in this example
Clone this wiki locally