starred/the-bastion
1
0
Fork 0
mirror of https://github.com/ovh/the-bastion.git synced 2026-05-09 16:35:33 +02:00
Code Issues 46 Projects Packages Wiki Activity

[GH-ISSUE #433] Synchronization between master and slave #113

New issue
Closed
opened 2026-05-07 00:19:05 +02:00 by BreizhHardware · 6 comments
BreizhHardware commented 2026-05-07 00:19:05 +02:00
Owner
Copy link

Originally created by @ElGigi on GitHub (Nov 15, 2023).
Original GitHub issue: https://github.com/ovh/the-bastion/issues/433

Hi,

An error occured during synchronization between master and slave:

Nov 15 10:24:51 bastion osh-sync-watcher.sh[33179]: Watching for changes (timeout: 120)...
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33198]: ... timed out, syncing just in case!
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33202]: Starting sync!
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33205]: 10.x.x.x: [Server 1/1 - Step 1/3] syncing needed data...
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33207]: rsync: [sender] Failed to exec -p: No such file or directory (2)
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33207]: rsync error: error in IPC code (code 14) at pipe.c(85) [sender=3.2.7]
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33206]: rsync: connection unexpectedly closed (0 bytes received so far) [sender]
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33206]: rsync error: error in IPC code (code 14) at io.c(231) [sender=3.2.7]
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33208]: 10.x.x.x: [Server 1/1 - Step 1/3] sync ended with return value 14
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33209]: 10.x.x.x: [Server 1/1 - Step 2/3] syncing lastlog files from master to slave, only if master version is newer...
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33211]: rsync: [sender] Failed to exec -p: No such file or directory (2)
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33211]: rsync error: error in IPC code (code 14) at pipe.c(85) [sender=3.2.7]
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33210]: rsync: connection unexpectedly closed (0 bytes received so far) [sender]
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33210]: rsync error: error in IPC code (code 14) at io.c(231) [sender=3.2.7]
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33212]: 10.x.x.x: [Server 1/1 - Step 2/3] sync ended with return value 14
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33213]: 10.x.x.x: [Server 1/1 - Step 3/3] syncing lastlog files from slave to master, only if slave version is newer...
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33216]: rsync: [Receiver] Failed to exec -p: No such file or directory (2)
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33216]: rsync error: error in IPC code (code 14) at pipe.c(85) [Receiver=3.2.7]
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33215]: rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33215]: rsync error: error in IPC code (code 14) at io.c(231) [Receiver=3.2.7]
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33217]: 10.x.x.x: [Server 1/1 - Step 3/3] sync ended with return value 14
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33218]: ERROR: Encountered 3 error(s) while synchronizing, see above
Nov 15 10:26:51 bastion osh-sync-watcher.sh[33219]: Watching for changes (timeout: 120)...

The manual synchronization works fine:

rsync -v --rsh "ssh -i /root/.ssh/id_master2slave" /etc/passwd /etc/group bastionsync@IP.OF.THE.SLAVE:/root/

The configuration file:

$ cat /etc/bastion/osh-sync-watcher.sh
###############################################################################
## Config for ``bin/admin/osh-sync-watcher.sh``
## As it'll be sourced, THIS FILE MUST BE A VALID SHELL SCRIPT.
##
#@ .. note::
#@
#@    This daemon is responsible for ensuring secondary bastions
#@    are synced up to their primary at all times.
#@    If you don't have such HA setup, you can ignore this config file.
#@    For more information, refer to
#@    :ref:`installation/advanced:clustering (high availability)`.
###############################################################################
#
# > Logging
# >> These options configure the way the script logs its actions
#
# logdir (string)
#    DESC: Directory where the logs will be written to. Note that using this configuration option, the script will directly write to a file, without using syslog. If empty, won't log directly to a file.
# DEFAULT: ""
logdir=""
#
# syslog (string)
#    DESC: The syslog facility to use for logging the script output. If set to the empty string, we'll not log through syslog at all. If this configuration option is missing from your config file altogether, the default value will be used (local6), which means that we'll log to syslog.
# DEFAULT: "local6"
syslog="local6"
#
# > Daemon setup
# >> These options configure whether the synchronization daemon is enabled
#
# enabled (int)
#    DESC: If set to anything else than ``1``, the daemon will refuse to start (e.g. you don't have secondary bastions). You can set this to ``1`` when you've configured and tested the primary/secondaries setup.
# DEFAULT: 0
enabled=1
#
# timeout (int > 0)
#    DESC: The maximum delay, in seconds, after which we'll forcefully synchronize our data to the secondaries, even if no change was detected.
# DEFAULT: 120
timeout=120
#
# > Remote synchronization
# >> These options configure how the primary bastion should push its configuration to the secondaries
#
# rshcmd (string)
#    DESC: This value will be passed as the ``--rsh`` parameter of ``rsync`` (don't use ``-p`` to specify the port heree, use the ``remotehostlist`` config below instead), this can be used to specify which SSH key to use, for example. Note that this option is mandatory (if you don't have anything to specify here, you can just say ``ssh``).
# DEFAULT: ""
# EXAMPLE: "ssh -q -i /root/.ssh/id_master2slave"
rshcmd=""
#
# remoteuser (string)
#    DESC: The remote user to connect as, using ``ssh`` while rsyncing to secondaries. You probably don't need to change this.
# DEFAULT: "bastionsync"
remoteuser="bastionsync"
#
# remotehostlist (space-separated list of strings, each string being either 'ip' or 'ip:port')
#    DESC: The list of the secondary bastions to push our data to. If this list is empty, the daemon won't do anything.
# DEFAULT: ""
# EXAMPLE: "192.0.2.17 192.0.2.12:2244"
remotehostlist="10.x.x.x"
Originally created by @ElGigi on GitHub (Nov 15, 2023). Original GitHub issue: https://github.com/ovh/the-bastion/issues/433 Hi, An error occured during synchronization between master and slave: > Nov 15 10:24:51 bastion osh-sync-watcher.sh[33179]: Watching for changes (timeout: 120)... > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33198]: ... timed out, syncing just in case! > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33202]: Starting sync! > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33205]: 10.x.x.x: [Server 1/1 - Step 1/3] syncing needed data... > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33207]: rsync: [sender] Failed to exec -p: No such file or directory (2) > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33207]: rsync error: error in IPC code (code 14) at pipe.c(85) [sender=3.2.7] > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33206]: rsync: connection unexpectedly closed (0 bytes received so far) [sender] > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33206]: rsync error: error in IPC code (code 14) at io.c(231) [sender=3.2.7] > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33208]: 10.x.x.x: [Server 1/1 - Step 1/3] sync ended with return value 14 > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33209]: 10.x.x.x: [Server 1/1 - Step 2/3] syncing lastlog files from master to slave, only if master version is newer... > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33211]: rsync: [sender] Failed to exec -p: No such file or directory (2) > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33211]: rsync error: error in IPC code (code 14) at pipe.c(85) [sender=3.2.7] > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33210]: rsync: connection unexpectedly closed (0 bytes received so far) [sender] > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33210]: rsync error: error in IPC code (code 14) at io.c(231) [sender=3.2.7] > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33212]: 10.x.x.x: [Server 1/1 - Step 2/3] sync ended with return value 14 > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33213]: 10.x.x.x: [Server 1/1 - Step 3/3] syncing lastlog files from slave to master, only if slave version is newer... > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33216]: rsync: [Receiver] Failed to exec -p: No such file or directory (2) > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33216]: rsync error: error in IPC code (code 14) at pipe.c(85) [Receiver=3.2.7] > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33215]: rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33215]: rsync error: error in IPC code (code 14) at io.c(231) [Receiver=3.2.7] > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33217]: 10.x.x.x: [Server 1/1 - Step 3/3] sync ended with return value 14 > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33218]: ERROR: Encountered 3 error(s) while synchronizing, see above > Nov 15 10:26:51 bastion osh-sync-watcher.sh[33219]: Watching for changes (timeout: 120)... The manual synchronization works fine: > rsync -v --rsh "ssh -i /root/.ssh/id_master2slave" /etc/passwd /etc/group bastionsync@IP.OF.THE.SLAVE:/root/ The configuration file: ```bash $ cat /etc/bastion/osh-sync-watcher.sh ############################################################################### ## Config for ``bin/admin/osh-sync-watcher.sh`` ## As it'll be sourced, THIS FILE MUST BE A VALID SHELL SCRIPT. ## #@ .. note:: #@ #@ This daemon is responsible for ensuring secondary bastions #@ are synced up to their primary at all times. #@ If you don't have such HA setup, you can ignore this config file. #@ For more information, refer to #@ :ref:`installation/advanced:clustering (high availability)`. ############################################################################### # # > Logging # >> These options configure the way the script logs its actions # # logdir (string) # DESC: Directory where the logs will be written to. Note that using this configuration option, the script will directly write to a file, without using syslog. If empty, won't log directly to a file. # DEFAULT: "" logdir="" # # syslog (string) # DESC: The syslog facility to use for logging the script output. If set to the empty string, we'll not log through syslog at all. If this configuration option is missing from your config file altogether, the default value will be used (local6), which means that we'll log to syslog. # DEFAULT: "local6" syslog="local6" # # > Daemon setup # >> These options configure whether the synchronization daemon is enabled # # enabled (int) # DESC: If set to anything else than ``1``, the daemon will refuse to start (e.g. you don't have secondary bastions). You can set this to ``1`` when you've configured and tested the primary/secondaries setup. # DEFAULT: 0 enabled=1 # # timeout (int > 0) # DESC: The maximum delay, in seconds, after which we'll forcefully synchronize our data to the secondaries, even if no change was detected. # DEFAULT: 120 timeout=120 # # > Remote synchronization # >> These options configure how the primary bastion should push its configuration to the secondaries # # rshcmd (string) # DESC: This value will be passed as the ``--rsh`` parameter of ``rsync`` (don't use ``-p`` to specify the port heree, use the ``remotehostlist`` config below instead), this can be used to specify which SSH key to use, for example. Note that this option is mandatory (if you don't have anything to specify here, you can just say ``ssh``). # DEFAULT: "" # EXAMPLE: "ssh -q -i /root/.ssh/id_master2slave" rshcmd="" # # remoteuser (string) # DESC: The remote user to connect as, using ``ssh`` while rsyncing to secondaries. You probably don't need to change this. # DEFAULT: "bastionsync" remoteuser="bastionsync" # # remotehostlist (space-separated list of strings, each string being either 'ip' or 'ip:port') # DESC: The list of the secondary bastions to push our data to. If this list is empty, the daemon won't do anything. # DEFAULT: "" # EXAMPLE: "192.0.2.17 192.0.2.12:2244" remotehostlist="10.x.x.x" ```
BreizhHardware commented 2026-05-07 00:19:06 +02:00
Author
Owner
Copy link

@ksourdrille commented on GitHub (Nov 17, 2023):

Hi @ElGigi , in your /etc/bastion/osh-sync-watcher.sh fill rshcmd="" like this rshcmd="ssh -i /root/.ssh/id_master2slave", and tell us if it's better

<!-- gh-comment-id:1816679493 --> @ksourdrille commented on GitHub (Nov 17, 2023): Hi @ElGigi , in your /etc/bastion/osh-sync-watcher.sh fill ```rshcmd=""``` like this ```rshcmd="ssh -i /root/.ssh/id_master2slave"```, and tell us if it's better
BreizhHardware commented 2026-05-07 00:19:06 +02:00
Author
Owner
Copy link

@ElGigi commented on GitHub (Nov 22, 2023):

Works fine, thx!

<!-- gh-comment-id:1822438435 --> @ElGigi commented on GitHub (Nov 22, 2023): Works fine, thx!
BreizhHardware commented 2026-05-07 00:19:07 +02:00
Author
Owner
Copy link

@ElGigi commented on GitHub (Nov 22, 2023):

Perhaps, update documentation?

<!-- gh-comment-id:1822439171 --> @ElGigi commented on GitHub (Nov 22, 2023): Perhaps, update documentation?
BreizhHardware commented 2026-05-07 00:19:07 +02:00
Author
Owner
Copy link

@ksourdrille commented on GitHub (Nov 22, 2023):

Maybe @speed47, can update the documentation ?

Kélian

<!-- gh-comment-id:1822443345 --> @ksourdrille commented on GitHub (Nov 22, 2023): Maybe @speed47, can update the documentation ? Kélian
BreizhHardware commented 2026-05-07 00:19:07 +02:00
Author
Owner
Copy link

@speed47 commented on GitHub (Jan 19, 2024):

Hey, sorry for the delay, and thanks for you report!

The documentation states that this value must be filled :

Note that this option is mandatory (if you don't have anything to specify here, you can just say ssh)

However, the script should check that and not even attempt to run the rsync but warn you and exit. That must be fixed.

I'll also try to make it more obvious in the documentation that this option needs to be looked into.
Do you feel that the default value in the unmodified dist config file should be ssh -q -i /root/.ssh/id_master2slave, hoping that this should work on systems using the default port 22 and the default key name setup during a standard install?

<!-- gh-comment-id:1900601101 --> @speed47 commented on GitHub (Jan 19, 2024): Hey, sorry for the delay, and thanks for you report! The documentation states that this value must be filled : > Note that this option is mandatory (if you don't have anything to specify here, you can just say ``ssh``) However, the script should check that and not even attempt to run the `rsync` but warn you and exit. That must be fixed. I'll also try to make it more obvious in the documentation that this option needs to be looked into. Do you feel that the default value in the unmodified dist config file should be `ssh -q -i /root/.ssh/id_master2slave`, hoping that this should work on systems using the default port 22 and the default key name setup during a standard install?
BreizhHardware commented 2026-05-07 00:19:07 +02:00
Author
Owner
Copy link

@ksourdrille commented on GitHub (Jan 19, 2024):

Hey @speed47, in my opinion, for a default installation, this is the right value to enter.

<!-- gh-comment-id:1900635694 --> @ksourdrille commented on GitHub (Jan 19, 2024): Hey @speed47, in my opinion, for a default installation, this is the right value to enter.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
expifix
groupcreate_fix_uid
fix_group_gid_fast
gh-pages
clush
expiration
jsonvalidator
v3.23.01
v3.23.00
v3.22.00
v3.21.00
v3.20.00
v3.19.01
v3.19.00
v3.18.99-rc1
v3.18.00
v3.17.01
v3.17.00
v3.16.99-rc3
v3.16.99-rc2
v3.16.99-rc1
v3.16.01
v3.16.00
v3.15.00
v3.14.16
v3.14.15
v3.14.00
v3.13.01
v3.13.00
v3.12.00
v3.11.02
v3.11.01
v3.11.00
v3.10.00
v3.09.02
v3.09.00-really
v3.09.00
v3.09.00-rc3
v3.09.00-rc2
v3.09.00-rc1
v3.08.01
v3.08.00
v3.07.00
v3.06.00
v3.05.01
v3.05.00
v3.04.00
v3.03.99-rc2
v3.03.99-rc1
v3.03.01
v3.03.00
v3.02.00
v3.01.99-rc4
v3.01.99-rc3
v3.01.99-rc2
v3.01.99-rc1
v3.01.03
v3.01.02
v3.01.01
v3.01.00
v3.00.02
v3.00.01
v3.00.00
Labels
Clear labels   
answered

   
bug

   
documentation

   
enhancement

   
enhancement

   
feature

   
feature

   
kept-open-for-info

   
pull-request
Mirrored from GitHub Pull Request

  
question
No labels
answered
bug
documentation
enhancement
enhancement
feature
feature
kept-open-for-info
pull-request
question
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/the-bastion#113
No description provided.