11.7. Troubleshooting Geo-replication

This section describes the most common troubleshooting scenarios related to Geo-replication.

11.7.1. Locating Log Files

For every Geo-replication session, the following three log files are associated to it (four, if the slave is a Red Hat Storage volume):
  • Master-log-file - log file for the process which monitors the Master volume
  • Slave-log-file - log file for process which initiates the changes in slave
  • Master-gluster-log-file - log file for the maintenance mount point that Geo-replication module uses to monitor the master volume
  • Slave-gluster-log-file - is the slave's counterpart of it
Master Log File
To get the Master-log-file for geo-replication, use the following command:
# gluster volume geo-replication MASTER SLAVE config log-file
For example:
# gluster volume geo-replication Volume1 example.com:/data/remote_dir config log-file
Slave Log File
To get the log file for Geo-replication on slave (glusterd must be running on slave machine), use the following commands:
  1. On master, run the following command:
    # gluster volume geo-replication Volume1 example.com:/data/remote_dir config session-owner 5f6e5200-756f-11e0-a1f0-0800200c9a66
    Displays the session owner details.
  2. On slave, run the following command:
    # gluster volume geo-replication /data/remote_dir config log-file /var/log/gluster/${session-owner}:remote-mirror.log
  3. Replace the session owner details (output of Step 1) to the output of the Step 2 to get the location of the log file.
    /var/log/gluster/5f6e5200-756f-11e0-a1f0-0800200c9a66:remote-mirror.log