-
-
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]: FilesMetadataException - json cannot exceed 100000 characters long #42308
Comments
I get the same bug using the docker image and postgres as database |
I get the same bug using ubuntu 22.04.03 LTS with mariadb and nginx |
Seing the same running Linuxservers Dockerimage with MariaDB and Redis |
Using a updated Debian 12 bookworm an updated nextcloud 28.0.1 with external mariadb. |
Could one of you try to pinpoint what's filling the metadata like that? |
Any idea on how we could figure that out? 😕 |
we will provide more logs and wait for more feedback. this exception is supposed to be here to avoid useless information (more than 100k chars) within metadata and should be high enough for 'normal' data :-) |
Can you please patch your Nextcloud using this Pull Request: #42560 ? the easiest way would be to run this command from the root of your Nextcloud:
Switch your loglevel in
Then run this occ command:
once this is done, verify your logs for any entry that starts with |
Tried the patch and the steps, but the error did not occur in this case for me. Will keep an eye on the log. |
This comment was marked as duplicate.
This comment was marked as duplicate.
Please apply the patch and post the detailed log, without that, we cannot make any progress. |
I installed NC 28.0.2 RC3, applied patch, changed config.php, and started the "'./occ files:scan --generate-metadata --all". After 3 hours it's still running but i've got many photos there (more than 850GB of data, about 150.000 photos) so it must take time (even when it's fast SSD disk (KC3000), and there is still 45GB of free RAM, CPU is also fine, it's Ryzen 5 5600G). Most of the results are thing like that:
One had this message:
But it was all on terminal. I'll check nextcloud.log when it will finish working (and maybe even more of such things will appear). Update: i've checked that nextcloud.log is already more than 14MB, it will be hard to find there anything because almost everything is logged inside :) |
We are only interested in logs containing "huge metadata content detected". |
nextcloud.log |
Thanks. Can you confirm that the file has been edited by Photoshop ? |
Can you test the following PR: nextcloud/photos#2280 ? |
I got no idea. I can't find filename in the log, so i can't verify. This is some old file so it is possible Adobe was used, but i'm not sure. Currently i use Affinity software, and haven't been using Adobe for years. |
Looks like I went too quickly over your comment. Here is the fileid of the problematic file: 1505759. You can find out more information with the following command: |
I'll check that out, but i will prepare the file so it will be tested first. I will try this PR now and let You know. Thank You for help. |
After changing PHP file i've got this error while scanning same file: |
@nicrame indeed, it was an error in the code. If you revert the patch and apply its new version, it should work. |
Bug description
Saw this exception in the log:
Steps to reproduce
No idea, happened in the background job.
Expected behavior
Should not fail.
Installation method
Community Manual installation with Archive
Nextcloud Server version
28
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
None
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: