Unsolved
This post is more than 5 years old
11 Posts
0
3884
Unable to connect to centera
NOTE: this is a duplicate of the following post:
https://community.emc.com/message/646677#646677
Hi,
We have 2 applications running on the same server and accessing the same centera.
Both are java applications. One running as a "standard" java program and the second one running in an application server (glassfish).
No problem with the "standard" java application: we can connect, read, write.... No problem with JCenteraVerify...
With the glassfish application, we get the following error:
Error code: -10153
Error string: FP_AUTHENTICATION_FAILED_ERR
System error code: 4
com.filepool.fplibrary.FPLibraryException: Failed to authenticate PEA data
at com.filepool.fplibrary.FPPool. (Unknown Source)
The first strange thing is that sometimes it works...
The second strange thing is that if I give a unexisting PEA file in the connect string, I get the same error !
Both application use the same connect string and PEA file...
How to know the real reason of the error (differentiate a "file not found" or "real authentication failure") ? Does the error comes from the sdk or from centera server ? Can we see authentication failure (and reason) on some "audit logs" on centera box ?
Im not a centera specialist and I never had access to "real" centera box (I developed and tested with "online centera clusters")
I highly suspect a problem while loading the PEA file.
We asked our customer to activate the SDK logs and I will post it when I have it.... (Not easy to investigate as I dont have a remote access to their environment... )
Thanks in advance
PS:
It use to work whithout replicate (in testing environment) but then they changed the configuration, IPs and PEA file. Since then, it works "sometimes"...
mckeown_paul
409 Posts
0
July 18th, 2012 08:00
I hate it when it works "sometimes"
My first guess was that from glassfish your PATH wasnt set properly so that finding the PEA was the issue, but then you said "sometimes"
Do you use the full pathname of the PEA file?
If you are on windows trying geting the processinfo tool (or is it called processmon) from www.sysinternals.com (I know msoft bought them but I only ever remember this URL it'll redirect) and watch to see what files your process attempts to open and fails with
if you arent windows there is probably similar tools for other operating systems.
Community challenge, guys what is it for linux's solaris etc?
patrick_magon
11 Posts
0
July 18th, 2012 09:00
Hi Paul,
"I hate it when it works "sometimes""
Me too
"My first guess was that from glassfish your PATH wasnt set properly so that finding the PEA was the issue"
I would love to see a "File not found" or "cannot read file" instead of an "authentication failed" error...
"Do you use the full pathname of the PEA file?"
Yes and I can see it in the glassfish log file as I log it...
Some "*NIX tools"
For linux: strace, auditd, eventually check lastAccessTime of the file...
For solaris: truss, dtrace...
I will try to use these tools in my environment and ask the customer to do the same...
Can we see authentication failure (and reason) on some "audit logs" on centera box ?
Thanks
patrick_magon
11 Posts
0
August 10th, 2012 02:00
Hi,
I attached the sdk debug logs that show the behavior when it works and when it doesn't.... (no configuration change)
An interesting message:
A sdk developper could maybe tell me what is the root cause ??
Thanks
2 Attachments
centera_ok.log
centera_notok.log
prodejna_biz
1 Message
0
November 23rd, 2016 03:00
Try to use libPai_module64.so.3.4.108 instead of libPai_module64.so.3.4.107