Klipper backup stopped working after some days.

[Zephyrus67]

I installed Klipper backup about 10 days ago and it worked fine. Then suddenly I see now that it has not made any backups since Oct. 7th. at all...in other words..the last 5 days it has not made backup..

I checked the services and they seem to run. Well the on boot is dead but loaded and I think that is normal on "on boot" services right?

Filewatch service is running and active.

I tried reloading daemon, enabling and starting the services again but no luck. What can this be about?

Just for the record then i DID make several changes to the files it is supposde to back up until today.

[github-actions]

Please use markdown syntax (``) for code snippets in your issue. You have confirmed the checkbox that you are using markdown, but none was recognized here. The markdown syntax makes your issue more readable and makes it easier to find a solution to your problem more quickly.

Examples:
The symbol turnscodeintocode`.

For more code use ` three times at the beginning and at the end like this:

some
code

turns into:

some
code

Please edit your outgoing post immediately. If you think that this hint is not necessary and you have correctly used markdown, then you can simply ignore this message.

[Staubgeborener]

Please deactivate the filewatch service, edit a file of your choice (for example printer.cfg) and run script.sh --debug manually and post the output.

[Staubgeborener]

Update: i just tested the latest inotify version and its working properly.

voron@voron:~/printer_data/config $ systemctl status klipper-backup-filewatch.service
● klipper-backup-filewatch.service - Klipper Backup Filewatch Service
     Loaded: loaded (/etc/systemd/system/klipper-backup-filewatch.service; enabled; preset: enabled)
     Active: active (running) since Sun 2025-10-12 17:16:18 CEST; 1min 4s ago
   Main PID: 6436 (bash)
      Tasks: 3 (limit: 9571)
        CPU: 737ms
     CGroup: /system.slice/klipper-backup-filewatch.service
             ├─6436 bash /home/voron/klipper-backup/utils/filewatch.sh
             ├─6445 inotifywait -mrP -e close_write -e move -e delete --exclude ".swp|.tmp|printer-[0-9]*_[0-9]*.cfg|.bak|.bkp" /home/voron/printe>
             └─6446 bash /home/voron/klipper-backup/utils/filewatch.sh

Oct 12 17:16:18 voron systemd[1]: Started klipper-backup-filewatch.service - Klipper Backup Filewatch Service.
Oct 12 17:16:18 voron env[6445]: Setting up watches.  Beware: since -r was given, this may take a while!
Oct 12 17:16:18 voron env[6445]: Watches established.
Oct 12 17:16:47 voron env[6446]: Event Type: CLOSE_WRITE,CLOSE, Watched Path: /home/voron/printer_data/config/, File Name: printer.cfg

I then put a random #comment in my printer.cfg and Klipper-Backup updated the repository automatically as intended. So it's not the latest inotify release.

Only thing left we can check is the --debug output mentioned in my other post.

[Zephyrus67]

what du you mean bu debug manually? Den søn. 12. okt. 2025 kl. 17.22 skrev Staubgeborener < ***@***.***>:

…

*Staubgeborener* left a comment (Staubgeborener/Klipper-Backup#162) <#162 (comment)> Update: i just tested the latest inotify version <https://github.com/inotify-tools/inotify-tools/releases/tag/4.25.9.0> and its working properly. ***@***.***:~/printer_data/config $ systemctl status klipper-backup-filewatch.service ● klipper-backup-filewatch.service - Klipper Backup Filewatch Service Loaded: loaded (/etc/systemd/system/klipper-backup-filewatch.service; enabled; preset: enabled) Active: active (running) since Sun 2025-10-12 17:16:18 CEST; 1min 4s ago Main PID: 6436 (bash) Tasks: 3 (limit: 9571) CPU: 737ms CGroup: /system.slice/klipper-backup-filewatch.service ├─6436 bash /home/voron/klipper-backup/utils/filewatch.sh ├─6445 inotifywait -mrP -e close_write -e move -e delete --exclude ".swp|.tmp|printer-[0-9]*_[0-9]*.cfg|.bak|.bkp" /home/voron/printe> └─6446 bash /home/voron/klipper-backup/utils/filewatch.sh Oct 12 17:16:18 voron systemd[1]: Started klipper-backup-filewatch.service - Klipper Backup Filewatch Service. Oct 12 17:16:18 voron env[6445]: Setting up watches. Beware: since -r was given, this may take a while! Oct 12 17:16:18 voron env[6445]: Watches established. Oct 12 17:16:47 voron env[6446]: Event Type: CLOSE_WRITE,CLOSE, Watched Path: /home/voron/printer_data/config/, File Name: printer.cfg I then put a random #comment in my printer.cfg and Klipper-Backup updated the repository automatically as intended. So it's not the latest inotify release. Only thing left we can check is the --debug output mentioned in my other post. — Reply to this email directly, view it on GitHub <#162 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A475OZQ3VYCXIIE2SJBY6CL3XJW25AVCNFSM6AAAAACI63BIRWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTGOJUGY3TCNBZGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Zephyrus67]

ok Sorry but I am not goin to let that post stay....it seems to me that some of the output got information I am not too happy about being published...anyway....you should have received it by email

[Staubgeborener]

Is your GitHub repo private?

Please try script.sh --fix, put in some stuff in your printer.cfg and run script.sh --debug afterwards.

[Zephyrus67]

yes it is private and has been from start and it still worked to begin with. So if that is the cause not sure why it would change....I set it to public before and it is also now but it still does not work..I will try the fix parameter

[Zephyrus67]

ok after using --fix and running the --debug parameter after it seems like all files are now updated....

Is this because of the visibility setting in the repo?

[Staubgeborener]

No, you can change it back to private. I guess there was some issue in your local git files and folders which is --fixd now.

In case you deactivated your filewatch service: activate it again and check if this is working now.

[Zephyrus67]

OK thank you. And yes after enabling the service again it works both for the filewatch and the on boot (not sure if it actually works for the on boot but with the filewatch it should not be a big del I guess.

I installed Happy-hare around the time it stopped working so that could maybe have done something or?

Anyway it is good to know there is a way to get it back up running in these cases.

[Staubgeborener]

Yeah if you have any issues, always try --fix first. Sometimes git does his git things, see this.

And no, Happy-Hare shouldn't be the issue. But talking about that: if you want to backup Happy-Hare related config files I would suggest this article about symbolic links.

[Zephyrus67]

Thank you very much. I already have all the modifiable files from HH backed up and I am not sure it matters so much backing up the read only files-