Sign up ×
Information Security Stack Exchange is a question and answer site for information security professionals. It's 100% free, no registration required.

I'm New to Cuckoo Sandbox. Why am I getting this error? I don't understand. If there is something wrong, can anyone please explain how to setup Cuckoo Sandbox? My setup works very well before I submit any kind of malicious thing. I've been working on it for the last 5 days.

Thanks !

Cuckoo Sandbox 0.5
 Copyright (c) 2010-2012
 Checking for updates...
 Good! You have the latest version available.
2013-01-12 18:42:42,738 [lib.cuckoo.core.scheduler] INFO: Using "virtualbox" machine manager
2013-01-12 18:42:42,935 [lib.cuckoo.core.scheduler] INFO: Loaded 1 machine/s
2013-01-12 18:42:42,936 [lib.cuckoo.core.scheduler] INFO: Waiting for analysis tasks...
2013-01-12 18:43:12,403 [lib.cuckoo.core.scheduler] INFO: Starting analysis of URL 
"" (task=2)
2013-01-12 18:43:12,433 [lib.cuckoo.core.scheduler] INFO: Task #2: acquired machine cuckoo1 (label=cuckoo1)
2013-01-12 18:43:12,466 [lib.cuckoo.core.sniffer] INFO: Started sniffer (interface=eth0, host=, dump path=/opt/cuckoo/storage/analyses/2/dump.pcap)
2013-01-12 18:43:20,308 [lib.cuckoo.core.guest] INFO: Starting analysis on guest (id=cuckoo1, ip=
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.6/", line 532, in __bootstrap_inner
  File "/opt/cuckoo/lib/cuckoo/core/", line 318, in run
    success = self.launch_analysis()
  File "/opt/cuckoo/lib/cuckoo/core/", line 240, in launch_analysis
  File "/opt/cuckoo/lib/cuckoo/core/", line 136, in start_analysis
  File "/opt/cuckoo/lib/cuckoo/core/", line 59, in wait
  File "/opt/cuckoo/lib/cuckoo/common/", line 107, in _set_timeout
    if t._connection[1] and t._connection[1].sock:
AttributeError: TimeoutTransport instance has no attribute '_connection'
share|improve this question
I think it is a bug in the beta release you can read relevant information from this link – Ali Ahmad Jan 12 '13 at 19:23

1 Answer 1

up vote 1 down vote accepted

Yes, that's a bug in 0.5 that has been fixed in 0.5.1-dev. In theory it should only happen with Python 2.6, as we recommend using Python 2.7. You can manually apply this patch to fix it:

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.