-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
[Bug]: Error: exif_read_data(): File not supported at /var/www/nextcloud/lib/private/Metadata/Provider/ExifProvider.php#59 #34958
Comments
I get similar errors and after that the client locks showing the blue circle and I dont think it syncs the files after that. As far as I can say it happens when I move images from directory to directory. |
I have same error: |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I installed production docker image, version 25 is very buggy |
strange, because these errors should be only logged but should not disrupt the file access @artonge can you have a look ? |
As @PVince81 said, this is probably unrelated to the desktop client issue. |
The "locking on blue circle" started happening after the server upgrade. So I dont think it's the client and i dont see anything interesting in the client log. Just the normal updated/created/deleted. But the client locks multiple times a day and the only way to fix it is a client restart. |
Can you share the full error of "Error no app in context Computed md5 hash is incorrect." ? |
This is the last one I found.
|
Same here since Upgrade from NC 24.0.7 to 25.0.1 My action before was to rename an image file *.png in a folder in an external fileshare. my whole log says:
The action itself (renaming, moving file) is not interrupted by the error. |
|
Append info I can reproduce the "ExifProvider.php line 59 - Errors" by uploading any kind of images *ico; *png; *jpg ... |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
@artonge do you have any recommendations on what needs to be changed i can test and create a pull request of you show me the light ;) |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
I've noticed that if I re-save one file (Python script in the last case) too quick (I had to make small changes) and the client locks at the blue circle quite often. |
Me too, fresh 25.0.2.3 install from today, using the docker image, with mariadb. Fed it 50 gigs of data and walked away, came back to only 20 gigs uploaded and a lot of this in the error logs. The client had stopped syncing, but restarting it shook it loose. |
I was running into an issue with a new nextcloud instance (server release version 25.0.1). In my past nextcloud instance I didn't face that issue. I suspect that somewhere in One hint if one wants to reproduce the issue: Do bulk upload with tons of new files (they may be small, to me the issue was on various file types) and keep an eye on the memory consumption of the client (mine is on Windows, consumed all mem that it got). Btw: In the meanwhile I temporarily bypassed the issue by disabling bulk upload in the server config file ('bulkupload.enabled' => false) with drawbacks of not bulk-uploading any more. |
So there are two things mixed here apparently:
For the latter: is there a reason not to use Imagick for this job? It seems to be much better in extracting this kind of information and also supports more MIME types - I for example get this error on every WebP file I have:
See https://stackoverflow.com/a/50890651 for an example and implementation with Imagick. |
Still an issue NC 25.0.2
|
I resolve this issue by re-pull and re-deploy the container image. |
I'm having the exact same issue while deploying it on Fly using official Docker image and BackBlaze B2 storage. Let's see if I can get some help on Reddit. |
Hi. Same issue after updating to NC 25.0.2, php 8.0, Mageia Linux, Plasma, Nextcloud-client 3.6.4
|
Same issues here on 25.0.2 apache docker with smb external
|
Still having this error after Update 25.0.2 -> 25.0.3
|
Tossing a bump in. Fresh server install, Ubuntu Server 22.04 LTS, Apache, MariaDB, APCu, Redis, all using the recommended configurations.
|
It's not the bad news that I'm not the only one. Same problem ubuntu 22.04 |
I also tried this option but the desktop client is still bulk uploading. |
I have the exact same problem. For some reason, downgrading my Desktop Client to version 3.3.6 solved it for me. Files sync again and no errors occur. |
|
This comment was marked as off-topic.
This comment was marked as off-topic.
The same problem. I can trace the problem on the production server, but need a little help to dive in faster into sources. PM
|
Hi, can you please apply this patch and check if that resolves the issue for you? https://patch-diff.githubusercontent.com/raw/nextcloud/server/pull/36420.patch Thanks a lot! |
Tested myself. Doesnt seem to work yet... |
Okay, suppressing the php error with @ was indeed the only way I could suppress the log. Strange. |
This will be fixed in 25.0.4 |
Bug description
Upgraded from NC 24.0.7 to NC 25.0.1
Steps to reproduce
N/A
Expected behavior
N/A
Installation method
Community Manual installation with Archive
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.1
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated to a major version (ex. 22.2.3 to 23.0.1)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
Configuration report
No response
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: