Sorry to hear you’re facing problems
In order to help you as quickly as possible, before clicking Create Topic please provide as much of the below as you can. Feel free to use a pastebin service for logs, otherwise either indent short log examples with four spaces:
Or for longer, use three backticks above and below the code snippet:
longer example here
Some or all of the below information will be requested if it isn’t supplied; for fastest response please provide as much as you can
Nextcloud version (eg, 20.0.5):
Operating system and version (eg, Ubuntu 20.04):
windows 10 pro
Apache or nginx version (eg, Apache 2.4.25):
IDK now. I will check
PHP version (eg, 7.4):
IDK now. I will check
The issue you are facing:
Constant log creation in the laptop syncing with the server. More than 10K log files of 101 KB.
They are created every 3 seconds aprox. Any idea if it can be just an error solvable stoping syncing and updating?
It is in a work computer without admin rights. I have to ask some IT to uninstall and install updates.
The logs ara mainly info and debug levels. some warning levels acomplaining about not being able to read an exclude file list:
2023-04-11 01:18:29:841 [ warning default C:\Users\sysadmin\AppData\Local\Temp\2\windows-12824\client-building\desktop\src\csync\csync_exclude.cpp:438 ]: System exclude list file could not be read: “D:/nextcloud/path/.sync-exclude.lst”
Is this the first time you’ve seen this error? (Y/N): Y
Steps to replicate it:
Just started to happen after a while and everything being fine.
The output of your Nextcloud log in Admin > Logging:
The only relevant errors shown. They are a little bit old.
2023-03-20T17:08:09+00:00 [PHP] Error: Error: exif_read_data(): Illegal IFD size at /var/www/nextcloud/lib/private/Metadata/Provider/ExifProvider.php#59 at <<closure>> 2023-03-18T11:56:01+00:00 [no app in context] Error: Sabre\DAV\Exception\BadRequest: Expected filesize of 1024000 bytes but read (from Nextcloud client) and wrote (to Nextcloud storage) 835584 bytes. Could either be a network problem on the sending side or a problem writing to the storage on the server side. at <<closure>>