tag:support.arachni-scanner.com,2012-07-01:/discussions/problems/4922-workload-exhaustedArachni: Discussion 2018-03-26T08:03:21Ztag:support.arachni-scanner.com,2012-07-01:Comment/443025322017-12-19T16:17:42Z2017-12-19T16:17:42ZWorkload exhausted<div><p>Do the "Pending jobs" keep going down or is it just stuck there?</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/443025322017-12-20T09:00:02Z2017-12-20T09:00:03ZWorkload exhausted<div><p>Arachni seems stuck when the "Pending jobs" state is reached. When I request the Arachni REST server with summary order, the job is : scanning and busy true. But on the log file (arachni_path/system/logs/framework no activity after the Workload exhausted entry.</p>
<p>Regards,</p></div>Malween Le Goffictag:support.arachni-scanner.com,2012-07-01:Comment/443025322017-12-21T08:40:15Z2017-12-21T08:40:16ZWorkload exhausted<div><p>Hi,</p>
<p>I did more tests on the targeted application to try to understand where the problem is coming from. The last test carried out had a very light profile with only a few checks. The analysis still stopped (stucked) after a few hours of operation. On the profile I did however exclude the javascript file indicated above, it does not seem to be the root cause of the problem. Here are the last lines of the analysis log:</p>
<pre>
<code>[Wed Dec 20 15:53:06 2017] [info] Pending jobs: 44483
[Wed Dec 20 15:53:19 2017] [info] Pending jobs: 44482
[Wed Dec 20 15:53:31 2017] [info] Pending jobs: 44481
[Wed Dec 20 15:53:44 2017] [info] Pending jobs: 44480
[Wed Dec 20 15:53:56 2017] [info] Pending jobs: 44479
[Wed Dec 20 15:54:09 2017] [info] Pending jobs: 44478
[Wed Dec 20 15:54:22 2017] [info] Pending jobs: 44477
[Wed Dec 20 15:54:35 2017] [info] Pending jobs: 44476
[Wed Dec 20 15:54:47 2017] [info] Pending jobs: 44475
[Wed Dec 20 15:55:59 2017] [info] Pending jobs: 44474</code>
</pre>
<p>However, the summary analysis is still active (active and busy).</p>
<p>I also made a call to the REST API to delete the scan, and the log on the REST API side indicated the following information:<br></p>
<pre>
<code>[Thu Dec 21 09:18:23 2017] [status] Shutting down...
[Thu Dec 21 09:18:23 2017] [error] [Arachni::BrowserCluster::Error::AlreadyShutdown] Cluster has been shut down.
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/browser_cluster.rb:473:in <code>fail_if_shutdown&#39;
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/browser_cluster.rb:276:in</code>done?'
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/framework/parts/browser.rb:54:in <code>wait_for_browser_cluster?&#39;
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/framework/parts/audit.rb:179:in</code>block in audit'
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/framework/parts/audit.rb:177:in <code>loop&#39;
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/framework/parts/audit.rb:177:in</code>audit'
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/framework.rb:117:in <code>block in run&#39;
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/utilities.rb:425:in</code>call'
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/utilities.rb:425:in <code>exception_jail&#39;
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/framework.rb:117:in</code>run'
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/rpc/server/framework.rb:156:in <code>block in run&#39;
[Thu Dec 21 09:18:23 2017] [error]
[Thu Dec 21 09:18:23 2017] [error] Parent:
[Thu Dec 21 09:18:23 2017] [error] Arachni::RPC::Server::Framework
[Thu Dec 21 09:18:23 2017] [error]
[Thu Dec 21 09:18:23 2017] [error] Block:
[Thu Dec 21 09:18:23 2017] [error] #&lt;Proc:0x000000055d14e8@/arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/framework.rb:117&gt;
[Thu Dec 21 09:18:23 2017] [error]
[Thu Dec 21 09:18:23 2017] [error] Caller:
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/utilities.rb:425:in</code>exception_jail'
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/framework.rb:117:in <code>run&#39;
[Thu Dec 21 09:18:23 2017] [error] /arachni-1.5.1-0.5.12/system/gems/gems/arachni-1.5.1/lib/arachni/rpc/server/framework.rb:156:in</code>block in run'
[Thu Dec 21 09:18:23 2017] [error] --------------------------------------------------------------------------------</code>
</pre>
Is it normal that the error indicating that the cluster is already shut down while the scan is supposed to be still active ?
<p>I hope this can help move forward on the issue.</p>
<p>Best regards,</p></div>Malween Le Goffictag:support.arachni-scanner.com,2012-07-01:Comment/443025322018-03-01T10:04:48Z2018-03-01T10:04:49ZWorkload exhausted<div><p>Hi,</p>
<p>Some news about the scan of the target which end with a "workload exhausted" message (and an infinite loop). After a certain amount of tests I found out that the option called "Audit UI forms" in "Audit" section causes this error/infinite loop (Worlkload exhaustive message). Without this option, the analysis of the target ends correctly after few hours.</p>
<p>Can you explain what exactly do this option and if you have an idea of why this option causes an this infinite loop ?</p>
<p>Best regards,</p></div>Malween Le Goffictag:support.arachni-scanner.com,2012-07-01:Comment/443025322018-03-26T08:03:19Z2018-03-26T08:03:19ZWorkload exhausted<div><p>That option basically turns all orphan page inputs (like textareas and selects that don't belong to a specific form) and submit buttons into virtual-forms, sort of.</p>
<p>So if there are a lot of those, the scan can take a long time, although I don't know about inf loops, there are limits to basically every procedure that could cause one, but bugs are unavoidable as well.</p>
<p>About the error, this:</p>
<pre>
<code>[Thu Dec 21 09:18:23 2017] [status] Shutting down...</code>
</pre>
<p>Means that the scan wasn't actually active, you deleted it, i.e. shut it down, so pending jobs were rejected by the cluster.<br>
The error looks scary but nothing went wrong, although catching this post-shutdown case prior to it getting to the point where the system thinks it's in error is something I need to do.</p>
<p>Cheers</p></div>Tasos Laskos