Wait for network-online.target before mirror sync#3
Open
amikhailov7 wants to merge 1 commit into
Open
Conversation
systemd's network.target is passive — only signals that the network stack is loaded, not that the network is actually usable (interfaces configured, default route present, DNS responsive). Timers firing right after boot (especially with Persistent=true catching up missed runs) can race ahead of network readiness, causing rsync to exit 10 (socket I/O error) and the service to enter failed state until the next scheduled run. Replace After=network.target with After=network-online.target and add Wants=network-online.target so the service waits until the network is fully online before attempting to sync. Affects all service templates across playbooks: - combined-mirror: cloudlinux-complete-mirror, cloudlinux-mirror, swng-mirror - complete-swng-rsync: swng-mirror - specific-version-rsync: swng-version-mirror - yum-reposync: swng-reposync Observed on a customer mirror host where post-reboot timer trigger hit a network race; a drop-in with the same fix resolved it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
systemd's network.target is passive — only signals that the network stack is loaded, not that the network is actually usable (interfaces configured, default route present, DNS responsive). Timers firing right after boot (especially with Persistent=true catching up missed runs) can race ahead of network readiness, causing rsync to exit 10 (socket I/O error) and the service to enter failed state until the next scheduled run.
Observed on a customer mirror host where post-reboot timer trigger hit a network race; a drop-in with the same fix resolved it.