Packet loss while using rsync to copy Smokeping configuration

[Pipeops]

We are using rsync to copy the Smokeping configuration from one server to another. We currently sync the config once a day, but this results in inaccurate data and back up server producing packet loss alarms for modified devices until the config from primary server is copied.

How do I improve the rsync process so that the configuration is updated more frequently (every 5 minutes) and the Smokeping daemon is restarted only when there is a configuration change?

Thanks,

-I

 

[MikeHalloran]

No matter what options I use, no matter how I hold my tongue, rsync just flat doesn't work for me.

Oh, it chugs along, and _appears_ to work okay, and reports a successful transfer, but the transferred file is never an exact copy of the original file. Attempts to convince rsync otherwise don't work, because it won't go farther than comparing the file sizes when asked to check its own work.

Maybe some ancient rsync worked as documented, but the current one doesn't.

 

[QatQat]

I disagree on rsync.
I use it for a lot of tasks without problems.
Perhaps the only unreliable option is the incremental transfer. Rather use the "--whole-file" option and overwrite older files.

Concerning your problem, rsync is not the right tool for the job. Try using FAM (file alteration monitor), it is a server and it is dedicated to that kind of tasks.


QatQat

If I could have sex each time I reboot my server, I would definitely prefer Windoz over Linux!