Troubleshooting
Problem
The resilient-filesync service does not run after enabling IBM QRadar SOAR Disaster Recovery (DR).
Symptom
Files are not synchronised between the master and receiver servers.
When checking the status of the resilient-filesync service an error is returned on the master.
sudo systemctl status resilient-filesync
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol dat astream (code 12) at io.c(226) [sender=3.1.3]
bash: rsync: command not found
bash: rsync: command not found
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol dat astream (code 12) at io.c(226) [sender=3.1.3]
rsync error: error in rsync protocol dat astream (code 12) at io.c(226) [sender=3.1.3]
resilient-filesync.service: Main process exited, code=exited, status=255/n/a
resilient-filesync.service: Failed with result 'exit-code'.
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSA230","label":"IBM Security QRadar SOAR"},"ARM Category":[{"code":"a8m0z000000cvfMAAQ","label":"Resilient Core-\u003EDisaster Recovery"}],"ARM Case Number":"TS017703377","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Log InLog in to view more of this document
This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.
Was this topic helpful?
Document Information
Modified date:
04 November 2024
UID
ibm17174727