Home → Problems →

0.4.2 on CentOS 6.4. Glibc problem.

• Edit

Andrea Gabellini

04 May, 2013 07:31 AM

Hello,

I'm trying to use 0.4.2 version on my CentOS 6.4 server but I got this error:

ruby: /lib/libc.so.6: version `GLIBC_2.15' not found (required by /usr/local/arachni-0.4.2-0.4/bin/../system/usr/lib/libruby.so.1.9)

CentOS 6 use glibg 2.12, and updating it is not an option.

Version 0.4.1 works fine.

Thanks,
Andrea

1. Support Staff 1 Posted by Tasos Laskos on 04 May, 2013 11:11 AM

   

   Well, if you're not adversed to installing a few build dependencies (compilers, git etc) you can easily built your own package with a single line:

   wget -O - https://raw.github.com/Arachni/build-scripts/master/bootstrap.sh | bash
   

   This will perform a sanity check at the beginning and will let you know of the build dependencies that you'll need to install.

   • Edit

2. Support Staff 2 Posted by Tasos Laskos on 04 May, 2013 11:34 AM

   

   I forgot to clarify: You don't actually need to do this on the server. You can build the package on another machine with the same GLIBC version and just move the package to the server.

   • Edit

3. 3 Posted by Andrea Gabellin... on 04 May, 2013 11:38 AM

   

   Thank you. I'll try!!!

   • Edit

4. Support Staff 4 Posted by Tasos Laskos on 04 May, 2013 01:03 PM

   

   Ah, and one more thing, the above will pull from the experimental (dev/unstable) branch, if you want to pull from the master (release/stable) branch you can use:

   ARACHNI_BUILD_BRANCH='master' wget -O - https://raw.github.com/Arachni/build-scripts/master/bootstrap.sh | bash
   

   • Edit

5. 5 Posted by Andrea Gabellin... on 06 May, 2013 09:07 AM

   

   Hello,

   with your instructions I can build the experimental tree but not the master one. It fails on buil the web-ui with this error:

   Could not find bootstrap-sass-2.3.1.1 in any of the sources

   Andrea

   • Edit

6. Support Staff 6 Posted by Tasos Laskos on 06 May, 2013 12:28 PM

   

   Ah yeah, they yanked that gem for some reason. I updated the master to use an available version, should work now.

   • Edit

7. 7 Posted by Andrea Gabellin... on 07 May, 2013 09:06 AM

   

   Yes!!! I can build the master tree!

   Now I got this warning:

   Starting arachni_web:WARNING: Nokogiri was built against LibXML version 2.8.0, but has dynamically loaded 2.7.6

   The experimental build didn't give to me this message

   • Edit

8. Support Staff 8 Posted by Tasos Laskos on 07 May, 2013 11:37 AM

   

   Great, don't worry about that warning it won't give you any problems.
   Let me know if you need more help down the line.

   Cheers

   • Edit

9. Tasos Laskos closed this discussion on 07 May, 2013 11:37 AM.

10. Andrea Gabellini re-opened this discussion on 09 May, 2013 06:50 AM

11. 9 Posted by Andrea Gabellin... on 09 May, 2013 06:50 AM

    

    Hello,

    I started to play with Arachni... I have two little questions:

    - I use the daemonized web UI. Where I can find the log that the non-daemonized put on sceen?
    - when switching from stable to experimental and viceversa, can I copy the db from one version to the other? If yes, the file is system/arachni-ui-web/db/production.sqlite3?

    Thanks,
    Andrea

    • Edit

12. Support Staff 10 Posted by Tasos Laskos on 09 May, 2013 12:19 PM

    

    These sort of logs aren't enabled by default because the size of the scan messages can get into the GB range. To get them, what you need to do is start a Dispatcher, like so:

    ./bin/arachni_rpcd --reroute-to-logfile
    

    Add that Dispatcher to the web interface (default URL is localhost:7331) and use it to perform the scans.

    Then, for the normal packages the logs can be found under:

    system/gems/gems/arachni-*/logs/
    

    For the nightlies it will most likely be under:

    system/gems/bundler/gems/arachni-*/logs/
    

    People have started to ask me this question a lot recently and this is a stupid answer to give. I'll probably update the packages to store logs under system/logs/ or something.

    About the DB thing, I wouldn't advise it; technically it could work but experimental's DB schema is considered fluid.

    I'll put it this way, you will be able to copy your previous DB to the package of the next version and if there are any changes your DB will be automatically migrated -- and this will probably be done automatically using an upgrade script.
    But, I can't make the same guarantee about the experimental branch, in fact, I have to delete and re-setup my DB during dev quite regularly.

    To put it simply, you can use master's DB in experimental provided you run rake db:migrate but you can't reliably use the same DB between experimental builds.

    Does that make sense?

    • Edit

13. Support Staff 11 Posted by Tasos Laskos on 09 May, 2013 07:44 PM

    

    Starting from today's nightlies (to be pushed in a few hours) all logs will be saved under system/logs/.

    Edit: Also added more troubleshooting instructions in the TROUBLESHOOTING file.

    • Edit

14. 12 Posted by Andrea Gabellin... on 11 May, 2013 07:20 AM

    

    Thank you very much for the support!!!

    • Edit

15. Support Staff 13 Posted by Tasos Laskos on 11 May, 2013 11:46 AM

    

    You got it. :)

    • Edit

16. Tasos Laskos closed this discussion on 11 May, 2013 11:46 AM.