Unsolved
This post is more than 5 years old
1 Message
0
1228
February 23rd, 2018 05:00
CenteraPing cannot execute binary file issue on Linux 64bit
I am running a 64 bit Linux application server and we are unable to connect to our Centera cluster.
I have successfully run the JCenteraVerify tool from Linux this generates a FP_NO_POOL_ERR -10020.
Our network people have checked TCP and UDP have been setup on port 3218 to and from the cluster.
I thought I would check the CenteraPing tool as well but this seems to be a 32 bit binary and cannot be run on a 64 bit Linux server.
Do I need to add the i386 architecture to be able to use this tool?
If I can run JCenteraVerify is there any point in running CenteraPing?
This is the output from our JCenteraVerify log:
**************************************************************
************** Start of JCenteraVerify log ******************
**************************************************************
--------------------- General information -----------------------
Time: Thu Feb 22 12:28:24 GMT 2018
Tool Version: 3.2.23
SDK Version: 3.3.719
--------------------- User configuration ------------------------
TOOL SETTINGS
Number Of Files: 3
FileSize (KB): 1, 10, 100
Working Dir: ./Temp
Restore Dir: ./Temp/Retrieve
Log File: ./JCenteraVerify.log
Delete temp Files: false
SDK SETTINGS
Number of Retries: -1
Retry Sleep: -1
----------------- JCenteraVerify test results -------------------
ACCESS NODE CONNECTIVITY CHECK
##.###.#.### is not available.
FP_NO_POOL_ERR -10020
##.###.#.### is not available.
FP_NO_POOL_ERR -10020
##.###.#.###?/u01/app/jboss/product/emc/GRP_PoC_test.pea is not available.
FP_NO_POOL_ERR -10020
Unable to run: No active pool connection to continue..
**************************************************************
***************** End of JCenteraVerify log ****************
**************************************************************