ghost
commented
6 years ago I'm also having this issue when trying to use an AVD. Did you managed to solve this issue or does it still persist?
Closed ramirez3805 closed 6 years ago
ghost
commented
6 years ago I'm also having this issue when trying to use an AVD. Did you managed to solve this issue or does it still persist?
ramirez3805
commented
6 years ago Issue still persists for me.
ghost
commented
6 years ago I actually managed to solve this specific issue by doing some trial and error on de configuration. For me my settings are as follows:
avd.conf
ip = 10.0.2.15 (Got this with adb shell into the emulator and then ifconfig to get the local ip)
emulator_port = 5554
resultserver_ip =
cuckoo.conf
[resultserver]
ip = 127.0.0.1
port = 2042
From this, I was able to throw the emulator automatically after submitting the APK to be analyzed. Now I'm getting [cuckoo.core.guest] DEBUG: cuckoo3: not ready yet . I then realized that my emulator is not actually rooted with Xposed package properly installed. From my perspective, this problem might come from the emulator problem or the IP's themselves as the cuckoo itself is not able to connect to the emulator. I've turned avd mode to gui in order to get a visual status of whats' happening and from what I've seen it doesn't even install the app. Also, I'm able to throw x86 emulators but when I switch to an ARM architecture the emulator simply doesn't start (I think I have some sort of problem with my images and AVD path) This being said, don't take my settings as correct, I'm not getting the old error but it still doesn't work.
Just wanted to share my progress as it may help you overcome the ConnectionError.
ramirez3805
commented
6 years ago Thanks for sharing your progress but I'm still having this issue and I am not doing any Android analysis if anyone from the Cuckoo team is around to help, been patiently waiting. Thanks.
daanfs
commented
6 years ago @ramirez3805: 2.0.4 is the first linux version that uses the new agent.py file (the same one as for windows analysis). Are you using the new version (0.7) inside your VM?
Can you query it from outside like so?
$ curl 192.168.56.101:8000
{"message": "Cuckoo Agent!", "version": "0.7", "features": ["execpy", "pinning", "logs", "largefile", "unicodepath"]}Hi, thanks for responding. This is my output.
{"message": "Cuckoo Agent!", "version": "0.7", "features": ["execpy", "pinning", "logs", "largefile", "unicodepath"]}
nancychuang
commented
6 years ago Hi @ramirez3805 , I have exactly the same error as you, and i finally solve it running agent in linux guest VM by root, and it works. It seems the agent is trying to create a folder for analyzer but lack of permission. Hope it also works for you. :-)
daanfs
commented
6 years ago @ramirez3805: this can happen if the agent fails to create the analyzer directory. Is agent.py running as root inside your guest?
By default it will create a directory in / for the analyzer, maybe we should change this to /tmp/.
daanfs
commented
6 years ago Seems nancychuang beat me to this answer :)
ramirez3805
commented
6 years ago You guys are absolutely correct! That was the issue! Thank you guys so much!
Hi guys, running into an issue with my new setup. Running 2.0.4 doing an analysis against a Ubuntu 16 guest and host. This is what I am getting.