However, the VM does not start, when cuckoo procs are autostarted using supervisor
My Cuckoo version and operating system are:
Cuckoo V 2.0.7, Host: Ubuntu 18.04, Guest: Win 7 using virtualbox
This can be reproduced by:
starting cuckoo procs using supervisor
The log, error, files etc can be found at:
Time [cuckoo.processing.debug] ERROR: Error processing task #****: it appears that the Virtual Machine hasn't been able to contact back to the Cuckoo Host.
├─15118 /usr/bin/python /usr/bin/supervisord -n -c /etc/supervisor/supervisord.conf
├─15121 /home/cuckoo/.virtualenvs/cuckoo-test/bin/python2.7 /home/cuckoo/.virtualenvs/cuckoo-test/bin/cuckoo rooter
├─15122 /home/cuckoo/.virtualenvs/cuckoo-test/bin/python2.7 /home/cuckoo/.virtualenvs/cuckoo-test/bin/cuckoo web -H 192.168.57.4 -p 8080
├─15123 /home/cuckoo/.virtualenvs/cuckoo-test/bin/python2.7 /home/cuckoo/.virtualenvs/cuckoo-test/bin/cuckoo api -H 192.168.57.4 -p 8090
├─15124 /home/cuckoo/.virtualenvs/cuckoo-test/bin/python2.7 /home/cuckoo/.virtualenvs/cuckoo-test/bin/cuckoo -d -m 10000
└─15145 /home/cuckoo/.virtualenvs/cuckoo-test/bin/python2.7 /home/cuckoo/.virtualenvs/cuckoo-test/bin/cuckoo web -H 192.168.57.4 -p 8080
Mar 31 01:48:14 cuckoo-VirtualBox systemd[1]: Started Supervisor process control system for UNIX.
Mar 31 01:48:14 cuckoo-VirtualBox supervisord[15118]: 2021-03-31 01:48:14,443 CRIT Set uid to user 0
Mar 31 01:48:14 cuckoo-VirtualBox supervisord[15118]: 2021-03-31 01:48:14,443 INFO Included extra file "/etc/supervisor/conf.d/cuckoo.conf" during parsing
Mar 31 01:48:14 cuckoo-VirtualBox supervisord[15118]: 2021-03-31 01:48:14,450 INFO RPC interface 'supervisor' initialized
Mar 31 01:48:14 cuckoo-VirtualBox supervisord[15118]: 2021-03-31 01:48:14,450 CRIT Server 'unix_http_server' running without any HTTP authentication checking
Mar 31 01:48:14 cuckoo-VirtualBox supervisord[15118]: 2021-03-31 01:48:14,450 INFO supervisord started with pid 15118
Mar 31 01:48:15 cuckoo-VirtualBox supervisord[15118]: 2021-03-31 01:48:15,453 INFO spawned: 'cuckoo-rooter' with pid 15121
Mar 31 01:48:15 cuckoo-VirtualBox supervisord[15118]: 2021-03-31 01:48:15,455 INFO spawned: 'cuckoo-web' with pid 15122
Mar 31 01:48:15 cuckoo-VirtualBox supervisord[15118]: 2021-03-31 01:48:15,457 INFO spawned: 'cuckoo-api' with pid 15123
Mar 31 01:48:15 cuckoo-VirtualBox supervisord[15118]: 2021-03-31 01:48:15,459 INFO spawned: 'cuckoo-daemon' with pid 15124
Thanks for creating an issue! But first: did you read our community guidelines? https://cuckoo.sh/docs/introduction/community.html
My issue is:
My setup works when
cuckoo procs
are started manually (rooter, daemon & web). I can access VM from host using curlHowever, the VM does not start, when cuckoo procs are autostarted using
supervisor
My Cuckoo version and operating system are:
Cuckoo V 2.0.7, Host: Ubuntu 18.04, Guest: Win 7 using virtualbox
This can be reproduced by:
starting cuckoo procs using supervisor
The log, error, files etc can be found at:
Time [cuckoo.processing.debug] ERROR: Error processing task #****: it appears that the Virtual Machine hasn't been able to contact back to the Cuckoo Host.
Supervisor conf
supervisor_service_status