in reply to Re^2: WWW::Mechanize::PhantomJS - can't exec "phantomjs"
in thread WWW::Mechanize::PhantomJS - can't exec "phantomjs"

Any ideas on this one? The main.js file referenced in the message does exist.

Well, it needs to exist :)

See https://metacpan.org/source/CORION/WWW-Mechanize-PhantomJS-0.08/MANIFEST it lists https://metacpan.org/source/CORION/WWW-Mechanize-PhantomJS-0.08/lib/WWW/Mechanize/PhantomJS/ghostdriver/main.js

So wherever you installed it (let perl know about it PERL5LIB...), whatever your cpan configuration, whatever your logs say ... you probably need to reinstall it :)

  • Comment on Re^3: WWW::Mechanize::PhantomJS - can't exec "phantomjs"

Replies are listed 'Best First'.
Re^4: WWW::Mechanize::PhantomJS - can't exec "phantomjs"
by Special_K (Pilgrim) on Sep 13, 2014 at 17:10 UTC
    No, what I am saying is that the file referenced in the error message:
    '/usr/lib/perl5/site_perl/5.14/WWW/Mechanize/PhantomJS/ghos +tdriver/main.js'

    already does exist - it was put there when I installed WWW::Mechanize::PhantomJS. The question is: why is PhantomJS unable to open it?

      The error message did not say the file was missing.

      Rather it said : Selenium server did not return proper status at (eval 82) line 61.
      (Emphasis is mine)

      Selenium is known to have issues with popup messages (or so I've heard - no personal experience with it).
      You probably need to dig into Selenium logs to see what it did not like.

              "You're only given one little spark of madness. You mustn't lose it."         - Robin Williams

        Where does Selenium put its log files?