Keep getting no such file directory

[fzaninotto]

Keep getting no such file directory

[talktough]

If it helps at all I have quite a slow internet connection because I'm in the UK and I'm wondering if its looking for the snapshot file before its finished rendering and writing to the file - could that be the case ?

A further piece of information - if I refresh the browser it works saying that it found it found the image in the cache.

Thanks

Chris

[fzaninotto]

No, the service waits for the screenshot to be written to disk to close the response. But it is possible that the phantomjs browser times out with your slow internet connection. If that's the case, even the cached screenshot should be incorrect.

What's your node.js and phantomjs version?

[talktough]

Hi Francois

Thanks very much for replying.

I have node version 0.6.7 and PhantomJS version 1.6.1

I just noticed you have a node minimum version of 0.6.15 - sorry about
that if I wasted your time - could it be that that is causing the
problem ?

Thanks

Chris

On 3 Sep 2012, at 16:43, Francois Zaninotto wrote:

No, the service waits for the screenshot to be written to disk to
close the response. But it is possible that the phantomjs browser
times out with your slow internet connection. If that's the case,
even the cached screenshot should be incorrect.

What's your node.js and phantomjs version?

—
Reply to this email directly or view it on GitHub.

[fzaninotto]

Yes it could. Please try upgrading and report if the problem is still there.

[talktough]

Thanks and sorry again if I have wasted your time.

On 4 Sep 2012, at 08:53, Francois Zaninotto wrote:

Yes it could. Please try upgrading and report if the problem is
still there.

—
Reply to this email directly or view it on GitHub.

[fzaninotto]

I can reproduce the problem, maybe due to a newer version of one of the dependencies. Will be investigating further.

[talktough]

Thanks

[fzaninotto]

Confirmed: upgrading to Node >= 0.6.15 (as stated in the package.json) fixes the issue. I consider this issue as duplicate of #2.

[talktough]

Thanks I will definitely give it a try in a bit - I'm just having to stick with my current version for the moment while I finish something.

[fzaninotto]

I suggest using nvm to install several Node versions simultaneously.

[tneogi]

Hi,

I tried following the steps mentioned here to troubleshoot this problem. I upgraded from an older version of node to 0.6.15 and my phantomjs version is 1.7.

However, I am still facing the same problem and getting this error message 500 Error: ENOENT, stat '/var/www/files/screenshot_cbdb7325fae079dee92f77d4fcc16f58.png'.

Any pointers or help will be greatly appreciated.

Thanks
Titash

[avikshee]

Hello I am still getting the same issue.
The following are some details regarding the versions I use on my production servers:

node -v
v0.8.12

phantomjs --version
1.7.0

It would be really helpful if you can tell me a way to fix this issue.
Looking forward to your reply.

Thanks

[chrift]

I'm also having this problem. I have the error:

404 Error: ENOENT, stat 'C:\tmp\screenshot_cbdb7325fae079dee92f77d4fcc16f58.png'

Please someone help!?

node -v
v0.8.22

phantomjs --version
1.9.0

[ne0c0de]

I'm also have same problem,

It works my first request and then it gives same 404 ENOENT error on every request

node -v : v0.10.21
phantomjs --version : 1.9.0