tag:support.arachni-scanner.com,2012-07-01:/discussions/problems/50-high-performance-grid-shuts-downArachni: Discussion 2013-04-26T14:05:58Ztag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-17T17:16:03Z2013-04-17T17:16:03ZHigh Performance Grid shuts down<div><p>And like i said, it happens with normal single instance scan
too, makes sense then why the grid was crawling for 6 hours and no
audit</p></div>user021tag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-17T17:20:50Z2013-04-17T17:20:50ZHigh Performance Grid shuts down<div><p>I'm not sure why you're fixated on that message, it has nothing
to do with the crawl being finished or anything like that. What you
are seeing is just a big (and somewhat slow) website being
crawled.</p>
<p>I'm having a little trouble understanding your expectations.</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-17T17:30:48Z2013-04-17T17:30:48ZHigh Performance Grid shuts down<div><p>So basically what you are telling me is that it doesn't work
like before, now it needs to crawl the whole website and when is
done, the audit process starts ?</p></div>user021tag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-17T17:36:06Z2013-04-17T17:36:06ZHigh Performance Grid shuts down<div><p>I'm saying it never worked like that and that you may have
possibly confused the <code>auto-redundant</code> option with the
<code>link-count</code> one.</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-17T21:42:39Z2013-04-17T21:42:39ZHigh Performance Grid shuts down<div><p>That two options are pretty hard to be confused, even for me,
idk why i thought that after that HTTP queue message, the audit
should start, my bad. About the exception from my first post, you
can check it on them, i don't think they mind being scanned,
limited link so it doesn't take so long:<br>
./arachni_rpc --server localhost:9184 --audit-link --audit-forms
--audit-cookies --audit-headers --modules=sqli --auto-redundant=1
--grid --spawns=3 --link-count=300 '<a href=
"http://www.hackthissite.org&#39">http://www.hackthissite.org&#39</a>;</p>
<p>ps: on first test it generated the error and i think that the
link limit worked, now running second test and it shows "Discovered
609 pages."</p></div>user021tag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-17T21:47:32Z2013-04-17T21:47:32ZHigh Performance Grid shuts down<div><p>No worries. When using multiple Instances the options specified
are for <strong>each</strong> Instance, I think I better change
that...</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-17T22:52:25Z2013-04-17T22:52:25ZHigh Performance Grid shuts down<div><p>Yay, I reproduced it! Fixing it shouldn't be that hard now that
I can trigger it.</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-17T23:13:21Z2013-04-17T23:13:21ZHigh Performance Grid shuts down<div><p>OK I just fixed it, was a type casting issue. Pushing the
nightlies again for you now, will let you know when they're
available.</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-18T01:24:26Z2013-04-18T01:24:26ZHigh Performance Grid shuts down<div><p>The nightly packages have been updated and tomorrow's will split
the <code>link-count</code> and <code>http-req-limit</code> options
by the Instance count.</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-18T10:14:22Z2013-04-18T10:14:22ZHigh Performance Grid shuts down<div><p>Thx, it is fixed. One more thing, when i start scanning a large
website with the grid and without auto-redundant option, what
exactly arachni does when status is Preparing?the logs shows that
it's crawling, if yes, using only one instance?because on
dispatchers i see no progress, and if there is a difference on
crawling performance when using grid and without.</p></div>user021tag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-18T12:48:26Z2013-04-18T12:48:26ZHigh Performance Grid shuts down<div><p>It seems that the processes are too busy crawling to reply to
progress request calls so you're left with the first one shown.
Eventually (as the crawl seeds lighten up) the processes become
less busy and start responding properly again.</p>
<p>This is more of an annoyance than a problem but I'll investigate
it further because it just bugs me.</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-18T13:35:14Z2013-04-18T13:43:21ZHigh Performance Grid shuts down<div><p>I know you probably have many things on your head as a developer
and i wouldn't be happy myself to be in your place if a guy keeps
bothering me with more and more bugs on my product but in other way
i think is a necessary evil xD<br>
Not sure, but i think i found something else, using autologin
plugin i noticed in dispatchers logs:<br>
on one<br>
"AutoLogin: Found log-in form with name: login AutoLogin: Form
submitted successfully."<br>
however, on others two :<br>
"AutoLogin: Could not find a form suiting the provided params at:
<a href=
"http://www.x.com&quot">http://www.x.com&quot</a>;</p></div>user021tag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-18T13:44:33Z2013-04-18T13:44:33ZHigh Performance Grid shuts down<div><p>I actually prefer that people keep me informed, if there are
bugs they need to be fixed, nothing wrong with that.<br>
But, I'd rather you report bugs at the <a href=
"https://github.com/Arachni/arachni/issues">issue tracker</a> as
this portal is here for support purposes and preferably keep
discussions on topic and create new ones if need be.</p>
<p>This behavior though I hadn't considered...that plugin should
only be called by the master instance and then have the cookies and
login sequence transmitted to the slaves.<br>
Unfortunately, I won't have time to fix this for the upcoming
v0.4.2 release as this is about an experimental feature. I did
however put it in my TODO list.</p>
<p>Thanks for playing with the grid man, it needed some thorough
testing, let me know if anything else comes up.</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-18T13:51:25Z2013-04-18T13:51:25ZHigh Performance Grid shuts down<div><p>I changed my mind, there's nothing wrong with each instance
having its own session, for now. Looking into this.</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-18T17:38:54Z2013-04-18T17:38:54ZHigh Performance Grid shuts down<div><p>Hm, works fine for me, would you mind sending me the details
privately via e-mail?</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-18T18:22:55Z2013-04-18T18:22:55ZHigh Performance Grid shuts down<div><p>I didin't said it doesn't work, just what i seen in logs, if you
say that the the cookies and login sequence is transmitted to the
slaves then i guess is ok, which details you mean more exactly, the
logs? deleted them but i can repro it and send them, still, there's
nothing much interesting in them, except for that message on
begining and then the crawling and audit taking place, or you want
to check if somehow one of dispatcher did not get the cookies?</p></div>user021tag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-18T18:25:56Z2013-04-18T18:25:56ZHigh Performance Grid shuts down<div><p>No I meant the autologin plugin worked for me from both
instances, it logged-in fine without complaining that it didn't
find the login form.</p>
<p>By details I meant the complete command line you used to run the
scan including the credentials -- if at all possible.</p></div>Tasos Laskostag:support.arachni-scanner.com,2012-07-01:Comment/264115122013-04-18T22:13:49Z2013-04-18T22:13:49ZHigh Performance Grid shuts down<div><p>Fixed and the nightlies have been updated. Also, it now splits
the <code>link-count</code> and <code>http-req-limit</code> values
depending on the amount of Instances.</p></div>Tasos Laskos