-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IMAGE_SIZE_URL request timed out #9231
Comments
Hey @sathvikl! Yeah that is definitely a problem we recognised already. Requests to the casper.ghost.org time out randomly. Some initial thoughts/options how to tackle this problem.
To fix this issue we can differentiate between a short and a long term solution. |
Thanks @kirrg001 curl https://casper.ghost.org/v1.0.0/images/ghost-logo.svg > /tmp/a curl https://casper.ghost.org/v1.0.0/images/blog-cover.jpg > /tmp/a The size of the files are above. Can you please give me some hints/code changes on how to disable this image size check for now or store the images locally ?
To provide you some context. I am working on making a publicly available Ghost.js node benchmark If anyone on the Ghost.js team would be interested in collaborating that would be awesome !! It's based on v0.11 of Ghost.js and I wanted to upgrade to an LTS version. |
I suggest to remove the initial fixture posts and add some custom posts with images which are stored locally (happens automatically as soon as you add an image). Then you should not hit the casper timeout problem. |
I deleted every single fixture post. In the settings/General section I deleted the publication cover(blog-cover.jpg) and Publication logo(ghost-logo.svg). I am still getting errors on this
https://casper.ghost.org/v1.0.0/images/ghost-logo.svg I am using this app in a cluster mode, with 88 node worker threads. Any guess on where this could be coming from ? |
@sathvikl Ghost doesn't support clustering, there should only be 1 Ghost process. If you want to improve perf put a cache in front and scale that out - all the Ghost generated pages are "static" so there should be very little traffic actually hitting the Ghost server |
Closing. I haven't seen any timeouts to our casper images in the last months. We can re-open this if we encounter it again. |
Hey there, getting this while running a local version of Ghost. To reproduce:
output in the console after visiting a few blog posts:
|
Hi, I'm experiencing the same issue reported by @LDubya after upgraded to 2.1.0. In my case, my images are hosted on Cloudinary and exists. |
Our fixture post images are hosted on Github pages. This is out of our control. The image size utility tries to fetch the dimensions of this image for Ghost's structured data feature. If the request takes too long, it skips. The error you are seeing should not affect the functionality of your blog.
We haven't touched this code at all. If Ghost is unable to request the image url within a specific period of time, it skips and logs an error. We'll raise a new issue soon which describes the problems of our image size utility. |
Figured it was a Github response time issue. Probably not the most urgent issue. Still, that console spasm on a default install 😭 |
I am running it behind the corporate proxy server and although I am able to view the image, I receive the below error while executing the first time.
I am not sure why it is unable to fetch this url
curl https://casper.ghost.org/v1.0.0/images/ghost-logo.svg works fine on the cmd line.
Is there a way to access this svg locally. ?
Issue Summary
INFO [2017-11-10 01:54:49] "GET /new-world-record-with-apache-spark/" 200 5106ms
[2017-11-10 01:54:55] ERROR
NAME: InternalServerError
CODE: IMAGE_SIZE_URL
MESSAGE: Request timed out.
level:critical
https://casper.ghost.org/v1.0.0/images/ghost-logo.svg
InternalServerError: Request timed out.
at new InternalServerError (/home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/ghost-ignition/lib/errors/index.js:71:23)
at /home/sathvikl/ghost1.17/Ghost-1.17.1/core/server/utils/image-size.js:129:31
at tryCatcher (/home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/bluebird/js/release/util.js:16:23)
at /home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/bluebird/js/release/catch_filter.js:34:37
at tryCatcher (/home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/bluebird/js/release/promise.js:689:18)
at Async._drainQueue (/home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/bluebird/js/release/async.js:133:16)
at Async._drainQueues (/home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/bluebird/js/release/async.js:143:10)
at Immediate.Async.drainQueues (/home/sathvikl/ghost1.17/Ghost-1.17.1/node_modules/bluebird/js/release/async.js:17:14)
at runCallback (timers.js:789:20)
at tryOnImmediate (timers.js:751:5)
at processImmediate [as _immediateCallback] (timers.js:722:5)
Technical details:
The text was updated successfully, but these errors were encountered: