Troubleshooting GemFire XD online backup

Products

• Pivotal GemFire XD

Issue/Introduction

Case-1: -

ERROR: Operation "backup" failed because: java.sql.SQLException(XJ040): Failed to start database 'gemfirexd', see the cause for details.

Caused by: com.gemstone.gemfire.security.AuthenticationFailedException: Failed to find credentials in JOIN_REQ message.

Solution: - Make sure gemfirexd.properties file is available inside the directory where you are running the gfxd backup command. If Authentication is enabled, the users must be listed in the gemfirexd.properties file.

 

Case-2: -

ERROR: Operation "backup" failed because: java.sql.SQLException(XJ040): Failed to start database 'gemfirexd', see the cause for details.

Caused by: java.sql.SQLNonTransientConnectionException(08001): User id can not be null.

Solution: - Authentication is enabled in the system. Add user and password argument to backup command.

gfxd backup ./backuplocation -locators=pdx2-office-dhcp0.eng.vmware.com[10334] -user=locatoradmin -password=v33b6043d5aa8f36541ebb39d55f69cb4b849a108eab11c2d33b917556a7214f75121

 

Case-3: -

ERROR: Operation "backup" failed because: java.sql.SQLException(XJ040): Failed to start database 'gemfirexd', see the cause for details.

Caused by: java.net.BindException: Address already in use

Solution: - Address already in use error may appear when ‘jmx-manager=true’ configured in the gemfirexd.properties available in directory where backup command is being executed. The backup command will try to bind jmx manager server port that is already used by a running member to cause this error. Either set jmx-manager=false in gemfirexd.properties file or explicitly pass jmx-manager=false in backup command.

 

gfxd backup ./backuplocation -locators=pdx2-office-dhcp0.eng.vmware.com[10334] -user=locatoradmin -password=v33b6043d5aa8f36541ebb39d55f69cb4b849a108eab11c2d33b917556a7214f75121 -jmx-manager=false

 

Case-4: -

ERROR: Operation "backup" failed because: java.sql.SQLNonTransientConnectionException(08004): Database connection refused.

Caused by: java.sql.SQLNonTransientConnectionException(08004): Database connection refused.

Solution: - This error could appear if the property ‘gemfirexd.authz-default-connection-mode’ is defined in the gemfirexd.properties. This property has no effect if it is inside gemfirexd.properties file. This must be added as member statup argument.

-J-Dgemfirexd.authz-default-connection-mode=NOACCESS

 

Case-5: -

ERROR: Operation "backup" failed because: java.sql.SQLException(XJ040): Failed to start database 'gemfirexd', see the cause for details. 
Caused by: com.gemstone.gemfire.GemFireConfigException: Unable to contact a Locator service. Operation either timed out or Locator does not exist. Configured list of locators is "[3.34.95.239()<v0>:1526, 3.34.95.238()<v0>:1526]".

 

Solution: - This error appears when locator’s client-port is used in the backup command. The peer discovery port (10334) must be used for locator’s address.

gfxd backup ./backuplocation -locators=pdx2-office-dhcp0.eng.vmware.com[10334]