"Problem We are unable to process that as an image."
Talk Talk about LibraryThing
Join LibraryThing to post.
This topic is currently marked as "dormant"—the last message is more than 90 days old. You can revive it by posting a reply.
12012
Getting the same problem described on 2016-12-06 in https://www.librarything.com/topic/242683
While trying to upload a cover image, I got the message:
"Problem: We are unable to process that as an image."
Has the server run out of inodes again?
The image file was no larger than those I've successfully uploaded earlier today.
In fact, trying an image that worked earlier in the day now fails, so something changed.
While trying to upload a cover image, I got the message:
"Problem: We are unable to process that as an image."
Has the server run out of inodes again?
The image file was no larger than those I've successfully uploaded earlier today.
In fact, trying an image that worked earlier in the day now fails, so something changed.
2MarthaJeanne
You also get that message if you are trying to upload a picture that is in the wrong format or with the file name mangeled. Check if it has .jpeg at the end. (There may also be others that work.)
3MarthaJeanne
There really does seem to be a problem. I've reopened the bug. Maybe someone is still up and will notice.
4anglemark
It's a bug alright. I just tried to upload an ordinary screenshot to my junk drawer and got that error.
5PhaedraB
>3 MarthaJeanne: I've uploaded hundreds, perhaps a thousand or more files with with a file extension .jpeg.
6timspalding
I'm not getting an error. Is anyone else?
7MarthaJeanne
Yes, jpeg works, but the files I've tried that weren't labelled jpeg haven't.
8MarthaJeanne
>6 timspalding: Seems to be working now. Wasn't 12 hours ago.
92012
It now works with an image that produced the error last night.
So something changed, perhaps inode exhaustion occured and then the inodes were replenished ;)
At least we know it wasn't a policy change such as a lower limit on image size.
So something changed, perhaps inode exhaustion occured and then the inodes were replenished ;)
At least we know it wasn't a policy change such as a lower limit on image size.
10timspalding
Pedro is saying that there was higher load last night. That's as far as he got diagnosing it. So, let's see if it reoccurs.
12CtrSacredSciences
Yes, Pacific daylight time 6:26 pm 5/12/17
small jpeg cover won't load
small jpeg cover won't load
13timspalding
Yeah. The server is clearly full. I don't think Pedro has an alert on this.
Going to look myself.
Going to look myself.
14timspalding
Okay, I cleared out a very large file. Should be good now.
16CtrSacredSciences
Happening again here, PST 5:33 for a small 97k jpeg cover. New message though: "500 Internal Server Error
nginx"
nginx"
17pedro.pessoa
fixed both issues contributing to this. One was a re-occurrence. Added non-critical alerting to it.
(149)
(149)
18Pepys
Hello,
I got the same problem as above, resulting in
**Problem
We are unable to process that as an image.
Back to page**
while trying to upload a 128k cover with the .jpg suffix (which I've done many times in the past years). Perhaps is it due to the fact that I previously attempted to upload it in a much bigger (3M) version before I realized that it wouldn't do... (In case it helps: the file name was img092.jpg when it was big, and Lliboutry.jpg when it was small.)
Will try to rename Lliboutry.jpg to Lliboutry.jpeg, to see what happens.
Edited: No, changing to .jpeg doesn't solve the problem...
I got the same problem as above, resulting in
**Problem
We are unable to process that as an image.
Back to page**
while trying to upload a 128k cover with the .jpg suffix (which I've done many times in the past years). Perhaps is it due to the fact that I previously attempted to upload it in a much bigger (3M) version before I realized that it wouldn't do... (In case it helps: the file name was img092.jpg when it was big, and Lliboutry.jpg when it was small.)
Will try to rename Lliboutry.jpg to Lliboutry.jpeg, to see what happens.
Edited: No, changing to .jpeg doesn't solve the problem...
19anglemark
There are two open bug threads in Bug Collectors:
https://www.librarything.com/topic/242683
https://www.librarything.com/topic/285799
https://www.librarything.com/topic/242683
https://www.librarything.com/topic/285799

