Syncthing spamming log


(Cooad) #1

Hello.

Yesterday my Raspberry pi unexpectedly told me that there’s no space left on my SD card. As it turned out, the reason for this was a very large /var/log/daemon.log and /var/log/syslog files (4 GB each). Upon inspection, most of the file consists of theses messeges:

Sep  5 18:55:46 rpi3 syncthing[17773]: [5PPX5] INFO: Puller (folder "", file "ASK/CPU simulator/CPU simulator/Form1.resx"): shortcut: chmod: chmod /mnt/usbhdd/private/Studia/ASK/CPU simulator/CPU simulator/Form1.resx: operation not permitted
Sep  5 18:55:46 rpi3 syncthing[17773]: [5PPX5] INFO: Puller: shortcut: chmod /mnt/usbhdd/private/Studia/ASK/CPU simulator/CPU simulator/Form1.resx: operation not permitted
Sep  5 18:55:46 rpi3 syncthing[17773]: [5PPX5] INFO: Puller (folder "", file "ASK/PanelOperatorski/PanelOperatorski/Properties/AssemblyInfo.cs"): shortcut: chmod: chmod /mnt/usbhdd/private/Studia/ASK/PanelOperatorski/PanelOperatorski/Properties/AssemblyInfo.cs: operation not permitted
Sep  5 18:55:46 rpi3 syncthing[17773]: [5PPX5] INFO: Puller: shortcut: chmod /mnt/usbhdd/private/Studia/ASK/PanelOperatorski/PanelOperatorski/Properties/AssemblyInfo.cs: operation not permitted
Sep  5 18:55:46 rpi3 syncthing[17773]: [5PPX5] INFO: Puller (folder "", file "ASE/lab1/.idea/encodings.xml"): shortcut: chmod: chmod /mnt/usbhdd/private/Studia/ASE/lab1/.idea/encodings.xml: operation not permitted
Sep  5 18:55:46 rpi3 syncthing[17773]: [5PPX5] INFO: Puller: shortcut: chmod /mnt/usbhdd/private/Studia/ASE/lab1/.idea/encod

Syncthing has been running flawlessly on this machine for months - user and file permissions have not changed. What could have caused this behaviour? How do I fix it?


(Jakob Borg) #2

Assuming that the USB HD is FAT formatted, possibly a lacking “ignore permissions” checkbox?

Otherwise maybe Syncthing doesn’t have permissions to write to the files in question any more.


(Cooad) #3

The HD has a EXT4 filesystem. The other client is a Windows 10 machine, where these files live on a NTFS filesystem. The problem appeared yesterday - is it possible that it’s somehow connected to 0.14.37 update?


(Jakob Borg) #4

Maybe, but chmod failure on ext4 sounds like a permission issue. I suggest you look into that first.


(system) #5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.