-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
builtins.OSError: cannot identify image file '/var/lib/synapse/media_store/local_content/[…]' #4379
Comments
Over 5 days, I have 25 MB of logs filled with those errors and some other ones related to the psql db used by synapse. |
Still happens in 0.99.2
|
Not sure it is related but I have a similar here : #4594 |
I can reproduce this with a Synapse is running in the official Docker image ( Here's the image file causing the problem: Traceback is like this:
|
I don't know is our problem related, but we get very similar result when a user through self-hosted appservice-slack tries to upload image to an bridged room.. TravisR from Our synapse side log from the event:
and same event stuff from appservice-slack log:
|
See also element-hq/element-web#10010, which may or may not be related. |
I don't just want to delete my post, so I'll do status update for our thing which might not be related after all: I think our situation is somehow appservice-slack bot user having no correct rights to show nor get files, this it pushes "log in to slack" webpage into the image file to be.. and everything failing because of that.... |
Same error still.
I should mention that this is only happening on some devices, my phone works (been logged in since forever), my dual-boot PC works on one OS but not the other. It seams tied to when you logged in with the account. Older logins work. |
@Torxed, that's a pretty old Synapse version. Upgrading to Synapse v1.0+ is of grave importance, especially if you expect your server to federate with others. Perhaps the above error has been fixed there, due to some dependency getting upgraded, etc. |
Done, same issue. now running Sadly I can't copy paste text for some reason at the moment. Looking at the file that was "uploaded", the contents of it is:
So I'm guessing it's the front-end that's messing things up. Because that's some JavaScript jibberish. |
Yepp, updating the UI (front-end) solved the problem. |
The issue is not fixed for me, on Synapse 1.2.1 too. |
Just ran into this as well, image is a PNG exported by gimp 2.10.12 |
I see the same issue when uploading a file via Chrome. Uploading the same image file in Firefox works just fine, so I guess it's not a problem of the image data. Client is riot 1.2.1, server synapse 1.3.1. (updated: tested with riot 1.3.3, same result) Here is the trace of the error:
Same file uploaded from Firefox:
This seems to be reproducibly bound to the browser / client doing the upload. |
At some point the OS cannot identify the files anymore. https://stackoverflow.com/questions/56968200/python-oserror-cannot-identify-image-file. Matrix writes the file, but it is corrupt (empty I think), so the PLI cannot identify an image or pdf (no matter the extension). Microsoft Edge works fine uploading the file, but not for Chrome and Firefox. We have two servers that were working fine for several months and suddenly this error came out. We didn't change the configuration or permissions. The only thing that changed were the Browsers versions. We are going to keep investigating |
anything new about this? |
Description
Synapse log are spitting errors related to two images in
local_content
. They are both SVG.Full excerpt:
Version information
The text was updated successfully, but these errors were encountered: