Search the docs

Appendix B - Common Errors

Gfs-participant-add: Fails to Add a Site

Example Error Message
*> gfs-participant-add --share-name Apps --site-name "SITE Q" --site-username admin --site-password ***********

[NOTE]
gfs-participant-add: site 'SITE Q' not found.

This error indicates that the site cannot find the SITE Q identifier in the configuration that has been exchanged between the sites. This indicates that either the --site-name input was mis-spelled (note that input is case sensitive) or that a shared object storage volume has not been set up correctly between the sites.

Gfs-participant-add: SITE-B Is Already Participant 1 of Share Home

Example Error Message
*> gfs-participant-add --share-name Home --site-name "SITE B" --site-username admin --site-password ************

[NOTE]
gfs-participant-add: Site SITE B is already participant 1 of share Home.

The share Home is already replicating to the site labeled SITE B.

Error Message: Bad Credentials

Example Error Message
*> gfs-participant-add --share-name Apps --site-name "SITE C" --site-username admin --site-password ******

[NOTE]
gfs-participant-add: Unable to ascertain the software version running at 10.200.79.62. Cause: Remote site '10.200.79.62' returned error: bad credentials

The username or password was incorrect when running gfs-participant-add.

Share-replication-create: Remote Site Error: An Entity (Share) Named 'Home' Already Exists

Example Error Message
*> gfs-participant-add --share-name Apps --site-name "SITE C" --site-username admin --site-password **********

[NOTE]
Status message: Remote site '10.200.79.62' returned error: A share with name 'Apps' exists. Share names are case-insensitive.

It is not possible to establish a replication relationship with an already-existing share on the remote site. It is recommended to rename and move the share on the remote site to address this.