hippogrief/pobsync
1
0
Fork 0
Code Issues 21 Pull Requests Actions Packages Projects Releases 3 Wiki Activity

(bug) improve workers to check rsync state #54

New Issue
Closed
opened 2026-05-22 14:51:35 +02:00 by parkel · 1 comment
parkel commented 2026-05-22 14:51:35 +02:00
Owner
Copy Link

I have an rsync process which seems to be done; but it executed with

root@backup:~/pobsync# tail -f /mnt/backups/pobsync/nextcloud.hosting.hippogrief.nl/.incomplete/20260521-205502Z__PRY2JXSY/meta/rsync.log 
rsync error: unexplained error (code 255) at rsync.c(716) [generator=3.4.1]
rsync error: received SIGUSR1 (code 19) at main.c(1600) [receiver=3.4.1]
rsync: [generator] write error: Broken pipe (32)

It didn't 1) fail the run and 2) didn't seem to recognize the run was failing.
Also keep in mind that the error (not shown here, but failing other runs) "file vanished" or likewise, should not fail a run unless rsync really borks out.

I have an rsync process which seems to be done; but it executed with ``` root@backup:~/pobsync# tail -f /mnt/backups/pobsync/nextcloud.hosting.hippogrief.nl/.incomplete/20260521-205502Z__PRY2JXSY/meta/rsync.log rsync error: unexplained error (code 255) at rsync.c(716) [generator=3.4.1] rsync error: received SIGUSR1 (code 19) at main.c(1600) [receiver=3.4.1] rsync: [generator] write error: Broken pipe (32) ``` It didn't 1) fail the run and 2) didn't seem to recognize the run was failing. Also keep in mind that the error (not shown here, but failing other runs) "file vanished" or likewise, should not fail a run unless rsync really borks out.
parkel commented 2026-05-22 23:50:24 +02:00
Author
Owner
Copy Link

image.png

The worker picked up the failing run eventually; but considering this took almost a day we might want to revise worker pings (and probably make them configurable in global config)

![image.png](/attachments/56414af4-5763-4b1e-b667-10f094479b52) The worker picked up the failing run eventually; but considering this took almost a day we might want to revise worker pings (and probably make them configurable in global config)
image.png
18 KiB
parkel added this to the 1.2 milestone 2026-05-23 00:15:32 +02:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
area: future
Longer-term product direction.
 area: observability
Metrics, history, and capacity insights.
 area: policy
Backup policies, templates, and automation.
 area: restore
Restore and recovery workflows.
 area: security
Permissions, audit, and security hardening.
 bugfix
Bug fixes and correctness work.
 docs
Documentation and operator guidance.
 feature
New functionality.
 refactor
Internal restructuring without direct behavior changes.
 release
Release preparation and publishing.
 security
Security, permissions, and audit work.
No Label
Milestone
No items
No Milestone 1.2
Projects
Clear projects
No project
Assignees
Clear assignees
parkel
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: hippogrief/pobsync#54
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?