- Community Home
- >
- Storage
- >
- Legacy
- >
- Storage Software
- >
- Problem with 3.5.1.0414 ¿Certificates?
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2013 09:45 AM
09-04-2013 09:45 AM
Problem with 3.5.1.0414 ¿Certificates?
Hi
We had an old Polyserve system on 2 Linux HP ProLiant nodes serving a filesystem to all the nodes in our cluster.
After a general shutdown and reboot, I observed a strange behavior: some nodes were able to NFS mount and work with the filesystem as usual, but some other mounted the filesystem but an 'ls' command lasted more than 2 minutes:
- nodes at 192.168.4.* work as usual
- node 192.168.2.100 works fine but nodes 192.168.2.[1-10] doesn't
- node 192.168.0.100 works fine but nodes 192.168.2.* doesn't. All nodes have Scientific Linux 5 installed. But in this subnet, we have one node (192.168.0.3) with Scientific Linux 6 who mounts and uses the filesystem without any problem.
When I checked the situation with mxconsole, I saw no problem but the Export Group where a certificate error appears (attached capture). The log file (mx.0.log.0) is:
Sep 4, 2013 5:24:19 PM com.polyserve.cecomm.CECommManager postToCE SEVERE: IOException - sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed Sep 4, 2013 5:24:19 PM com.polyserve.nfs.ExportRecordsConfiguration loadExportRecordsFromCE SEVERE: Failed to communicate to CE javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed Sep 4, 2013 5:24:19 PM com.polyserve.nfs.ui.NFSClusterDeviceMonitorDialog loadError SEVERE: Failed to communicate to CE javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed
I read here about the problem with certificates ending in 2012 ¿can that be causing our problems? I've tried to check HP's FTP site to find new certificates or a solution to our problem but I haven't found any.
Can any one suggest me a possible solution? Our storage system has always been a black box for us (just shutdown and restart operations).
Thanks in advance.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
09-04-2013 09:27 PM - edited 09-04-2013 09:30 PM
09-04-2013 09:27 PM - edited 09-04-2013 09:30 PM
Re: Problem with 3.5.1.0414 Certificates?
>Our storage system has always been a black box for us
If you haven't used mxconsole in a year, after the certificates expired, it could be that reason.
Your log looks like: