Unable to connect to centera

Hi Patrick,

Error Code "-10153" as informed is related to authentication issue. The issue could be due to several reasons from change in the IP address to pea file issues. I also found that as per the Primus ID "emc138065" the authentication error "-10153" could also happen if the Cluster is in replication environment and though the pool and profile might not be used for replication still has to be exported and imported on the Target and the source. Please try the same.

Regards

Satish N Kutty

Hi,

I asked the customer to enable the SDK debug and was lucky this time because it was working (no error when connecting) and I got the debug file...

Then I asked to restart the application server (Im interested in the debug file when it doesn't work). It didnt connect (Error Code "-10153") and the SDK debug log file is empty !

I attached the debug file that was procuded when it worked.

I found one strange info:

  POOLSERVER_SEGMENT_SIZE type=long value=104857600  POOLSERVER_IDLE_TIMEOUT type=long value=300000  POOLSERVER_ACCESS_PORT type=integer value=11200  POOLSERVER_PROBE_ALL type=stringarray value=[210.1.51.2(0), 10.1.51.1(1)]

the connect string I use is  10.1.51.2,10.1.51.1?/xxx/peaFilename.pea , not 210.1.51.2 ...

Once its connected, we get the following informations from the application (by using SDK...):

Library Versions:

          Native SDK library version:            3.2.661

          Java SDK version:                      3.2.661

          Cluster Time:                          7/16/12 1:07:24 PM GMT

Pool Information:

          Cluster ID:                            adc603c6-1dd1-11b2-80be-91db594fbde1

          Cluster Name:                          cc01

          CentraStar software version:           4.2.0-3881-0-0

          Cluster Capacity (Bytes):              107374182400

          Cluster Free Space (Bytes):            107179030778

          Cluster Replica Address:               10.1.51.101,10.1.51.102

Pool Capabilities:

          Read   Operation Allowed:              true

          Write  Operation Allowed:              true

          Delete Operation Allowed:              true

          Purge  Operation Allowed:              false

          Privileged Delete Operation Allowed:   false

          Existence Checking Operation Allowed:  true

          Monitor Operation Allowed:             false

          Query   Operation Allowed:             true

          Default Retention Period:              0

          Event Based Retention supported:       unsupported

          Retention Hold supported:              unsupported

          Default Blob Naming Scheme:            MD5,MG

          Deletion logging enabled:              true

          Min/Max Enabled:                       unsupported

          tRetention Variable Min:               0

          Retention Variable Max:                -1

          Retetion Fixed Min:                    0

          Retention Fixed Max :                  -1

          Retention Default:                     0

Global Pool Options:

          Max pool connections:                  100

          Retry count:                           6

          Sleep duration between retries:        -1

          Cluster unavailable time:              600

          Embedded blob threshold(bytes):        0

          Pool open strategy:                    FP_LAZY_OPEN

Pool Options:

          Buffersize:                            16384

          Pool connection timeout:               120000

          Multicluster failover enabled:         True

                    Read failover strategy:        2

                    Read cluster strategy:         3

                    Write failover strategy:       0

                    Write cluster strategy:        0

                    Delete failover strategy:      0

                    Delete cluster strategy:       0

                    Exists failover strategy:      1

                    Exists cluster strategy:       3

                    Query failover strategy:       1

                    Query cluster strategy:        3

          Collision avoidance enabled:           True

          Prefetch buffer size:                  32768

Cluster Retention Classes:

          0 retention class is defined on the cluster.

Zero retention classes are defined.|#]

Again, I know nothing about centera administration or configuration... Im developer...

Could this "210.1.51.1" address reflect a configuration problem ? why did we get an empty debug file on the second startup ?

Hi

The log only shows two warnings:

1342444431541 2012-07-16 13:13:51.541 [debug] 23555.54 [LIB] Attempting to load MD5 lib: "libFPMD5_Lib32.so"

1342444431542 2012-07-16 13:13:51.542 [warn] 23555.54 [LIB] MD5 lib not found! Using internal MD5 algorithm instead.

1342444431542 2012-07-16 13:13:51.542 [debug] 23555.54 [LIB] Attempting to load SHA256 lib: "libFPSHA256_Lib32.so"

1342444431542 2012-07-16 13:13:51.542 [warn] 23555.54 [LIB] SHA256 lib not found! Using internal SHA256 algorithm instead.

1342444431542 2012-07-16 13:13:51.542 [debug] 23555.54 [LIB] Attempting to load FPIntercept lib: "libFPIntercept32.so"

1342444431543 2012-07-16 13:13:51.543 [debug] 23555.54 [LIB] FPIntercept lib not found! (Using all default API calls.)

Please check why your application is unable to load the SDK correctly.

Best regards, Holger

Hi

Thanks for your reply.

I think the SDK is correctly loaded (actually, it worked with the attached debug file)...

If I check the libraries in the SDK, I don't see any library related to MD5 or sha256

libFPCore32.so.3.2.661*    

libFPParser32.so.3.2.47*   

libFPUtils32.so.3.2.661* 

libPAI_module32.so.3.2.97*

libFPLibrary32.so.3.2.661* 

libFPStreams32.so.3.2.661* 

libFPXML32.so.3.2.661*

From where could I get libFPMD5_Lib32.so and libFPSHA256_Lib32.so ?

I dont think its an issue as its logged as "warning" and it says that it will use internal algorithm instead.. (might be slower....)

What about this "210.1.51.1" ip address ?? Where could it come from ?

Regards

Patrick

Hi Patrick -

The MD5 and SHA256 dlls are optional platform-specific plugins that are not normally loaded, so these warnings are not really problems.

That IP address issue is just an artifact of how 'array' values are printed in the SDK logs; they are preceded with a length value (which is 2 in this case). So no problem there either.

We had seen issues a few years back with application servers attempting to load the SDK DLLs multiple times and having windows fail the subsequent load calls; I think these might have been addressed in SDK 3.2.705. It would be worth upgrading just to see if the behavior improves.

Good Luck,

Mike Horgan

Hi Patrick,

Would keep you posted once I get an update on the issue,could you also try posting the query under the Developer community where issues with SDK's are also discussed "ECN > Developer Network > Centera".

Regards

Satish N Kutty

Hi Mike,

Acually, we are using a unix server (solaris 10 on sparc). They tried to use the latest SDK with no success...

What about the empty SDK debug file (the file is created, and we get the "FP_AUTHENTICATION_FAILED_ERR" but the file is empty...) ? I don't know how they are doing (I don't have access to the machine...)

Im really desesperate....

Patrick Magon

Hi Satish,

I reposted the message here: https://community.emc.com/message/647367#647367

thanks

Patrick Magon

Hi Patrick,

Any updates on the issue....

Regards

Satish N Kutty

Hi Satish,

Nothing new... for now, most people are on holliday... will see in 2 weeks

Patrick Magon