Can't run Arachni container (current version v1.4-0.5.10)
Hello,
i'm having issues with the container provided on Arachni's website (current version v1.4-0.5.10).
Here are the errors I get (see attached files for details)
$ ./arachni_web
/home/jack/arachni-1.4-0.5.10/system/gems/gems/bundler-1.11.2/lib/bundler/runtime.rb:80:in `rescue in block (2 levels) in require': There was an error while trying to load the gem 'arachni'. (Bundler::GemRequireError)
$ ./arachni -version
/home/jack/arachni-1.4-0.5.10/system/usr/lib/ruby/2.2.0/webrick/httpservlet/cgihandler.rb:29:in `<class:CGIHandler>': incompatible character encodings: ASCII-8BIT and UTF-8 (Encoding::CompatibilityError)
Are you aware of theses issues ? Is there a workaround ?
Thank you in advance,
Jack
- arachni_web.txt 3.04 KB
- arachni_version.txt 2.7 KB
Comments are currently closed for this discussion. You can start a new one.
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
Support Staff 1 Posted by Tasos Laskos on 02 Apr, 2016 11:20 AM
Hello,
You're in
/home/jack/arachni-1.4-0.5.10/bin/when running these executables right?Did you alter the packages in any way after extracting them?
Cheers
2 Posted by Jack on 02 Apr, 2016 12:04 PM
Yes, i'm running the files from the in the aforementioned path.
No, i didn't alter the packages after extraction and the SHA1sums are correct before extraction.
Errors occur on both containers (32 and 64bits).
Support Staff 3 Posted by Tasos Laskos on 02 Apr, 2016 12:09 PM
That's very strange, can you please tell me your OS and CPU arch?
4 Posted by Jack on 02 Apr, 2016 12:52 PM
Sure, I'm using a standard Xubuntu 15.10 distribution running in 64bits
5 Posted by Jack on 02 Apr, 2016 01:07 PM
It's OK, I figured out the problem :
the real path I was launching the executable from contained accentuated chars...
Encountered errors disappeared when moving the container in a full ascii path.
(sorry, I should not have anonymized the traces I provided in my previous post)
Problem solved :)
Regards
Tasos Laskos closed this discussion on 02 Apr, 2016 05:51 PM.