Home → Problems →

An error

• Edit

user021

25 Jul, 2013 04:42 PM

Hello Tasos i am afraid i have to bother you again, i encountered this error a few moments ago

• error.log 26.1 KB

1. Support Staff 1 Posted by Tasos Laskos on 25 Jul, 2013 04:45 PM

   

   No worries, I'll take care of it.

   PS. This portal is for providing support to users, use the issue tracker on GitHub to report bugs.

   • Edit

2. 2 Posted by user021 on 25 Jul, 2013 04:49 PM

   

   Yeah i know but sucks that can't upload log files to github

   • Edit

3. Support Staff 3 Posted by Tasos Laskos on 25 Jul, 2013 06:49 PM

   

   You can just paste small logfiles like these and use markdown to preserve the formatting.
   Anyways, have you got any hints for how to reproduce this? The issue seems to be that something slipped in the cookies array but there's nothing weird in it.
   Is there any way you can narrow it down for me please?

   • Edit

4. 4 Posted by user021 on 25 Jul, 2013 06:57 PM

   

   It happened during the audit when was almost over around 98%. so basically what would help is if i provide a debug log file and end the scan exactly after the error produced so you can have a closer look at the info ?

   • Edit

5. Support Staff 5 Posted by Tasos Laskos on 25 Jul, 2013 07:01 PM

   

   Did you have the stats showing all the time or hit Ctrl+C just then?

   • Edit

6. 6 Posted by user021 on 25 Jul, 2013 07:05 PM

   

   All time. and i did even let scan finish

   • Edit

7. Support Staff 7 Posted by Tasos Laskos on 25 Jul, 2013 07:08 PM

   

   That's good, if you just audit that last URL before it failed, does the issue appear? That would allow me to track down the issue.

   • Edit

8. 8 Posted by user021 on 25 Jul, 2013 08:39 PM

   

   I used the rescan plugin and edited links on healthmap deleted most of them except a few from end that thought might be a issue and ran same scan, nothing, ran another scan using full unedited afr report just with --audit-cookies, nothing. ill run another full scan tomorrow hopefully will trigger

   • Edit

9. 9 Posted by user021 on 26 Jul, 2013 01:34 PM

   

   Ok i ran full scan with same options except to avoid crawling used the afr report and it did not trigger the error, i guess it have to do with sessions. Can you make it to log the URL with the problem too in the error info? is not a problem, ill run the scan again including crawl but will be easier that way

   • Edit

10. Support Staff 10 Posted by Tasos Laskos on 26 Jul, 2013 07:32 PM

    

    No unfortunately not, if you enable --reroute-to-logfile though that should let us know when the error occurred.

    • Edit

11. 11 Posted by user021 on 27 Jul, 2013 02:05 PM

    

    Bad news, i did try to repro it using exact command as first time twice but no success. weird...i did not had more time-outs than first time so nothing much changed.

    • Edit

12. user021 closed this discussion on 27 Jul, 2013 02:06 PM.