This repository has been archived by the owner on Apr 26, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Multiple tasks getting assigned to the same machine #3105
Comments
This was referenced Sep 18, 2020
hi, |
I think I do, see #3106. |
Thanks for your work @Al33t , I'm also having this issue in my production system. Will implement your suggested PR and test. |
Confirmed, PR is the solution. |
@cccs-kevin how did you solve this problem. |
@nadir3392 Make the code change from the following PR: #3106 and restart the Cuckoo Daemon for the changes in |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
My issue is:
When submitting tasks in rapid succession, two tasks can get assigned to the same machine, after which that vm becomes corrupt and needs to be restarted. This is usually only observed after a while, i.e. several have to be submitted and then after any length of time this may occur.
My Cuckoo version and operating system are:
Cuckoo version 2.0.7
Debian 10
This can be reproduced by:
Submitting several tasks in rapid succession.
One wonders if there is another variable at play since the ease of reproducing this would make it obvious that most users would be affected by this but none of the other reported issues seemed comparable.
The issue has already been analyzed and a race condition was determined to be the cause. By instrumenting the code, a carefully placed delay, the issue got aggravated to such extent that it was observed sooner and more frequent.
The log, error, files etc can be found at:
The text was updated successfully, but these errors were encountered: