Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

SMGR 6.2 Error 1

Status
Not open for further replies.

7deedtz

Technical User
Apr 20, 2009
241
0
16
ZA
Hi All

We had the following yesterday after trying to commit any changes. SIP Users could not be populated either under User management.

• The following errors have occurred:
• Detailed Cause: java.security.cert.CertificateExpiredException: NotAfter: Sat Oct 04 19:33:49 SAST 20149. NotAfter: Sat Oct 04 19:33:49 SAST 2014 [java.security.cert.CertificateExpiredException] java.security.cert.CertPathValidatorException: timestamp check failed8. timestamp check failed [java.security.cert.CertPathValidatorException] sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed7. PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed [sun.security.validator.ValidatorException] javax.net.ssl.SSLHandshakeException: sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed6. sun.security.validator.ValidatorException: PKIX path validation failed: java.security.cert.CertPathValidatorException: timestamp check failed [javax.net.ssl.SSLHandshakeException] org.postgresql.util.PSQLException: The connection attempt failed.5. The connection attempt failed. [org.postgresql.util.PSQLException] org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.postgresql.util.PSQLException: The connection attempt failed.)4. Could not create connection; - nested throwable: (org.postgresql.util.PSQLException: The connection attempt failed.) [org.jboss.resource.JBossResourceException] org.jboss.util.NestedSQLException: Could not create connection; - nested throwable: (org.postgresql.util.PSQLException: The connection attempt failed.); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.postgresql.util.PSQLException: The connection attempt failed.))3. Could not create connection; - nested throwable: (org.postgresql.util.PSQLException: The connection attempt failed.); - nested throwable: (org.jboss.resource.JBossResourceException: Could not create connection; - nested throwable: (org.postgresql.util.PSQLException: The connection attempt failed.)) [org.jboss.util.NestedSQLException] org.hibernate.exception.GenericJDBCException: Cannot open connection2. Cannot open connection [org.hibernate.exception.GenericJDBCException] javax.persistence.PersistenceException: org.hibernate.exception.GenericJDBCException: Cannot open connection1. org.hibernate.exception.GenericJDBCException: Cannot open connection [javax.persistence.PersistenceException] -

We Gave the SMGR a reboot, we are not even able to Login to SMGR. On System platform all Seems up and running

and below is the current error when i try to login

/pages/Welcome.xhtml @70,67 value="": Error reading 'model' on type com.avaya.mgmt.console.framework.bean.ClientNavigationTree_$$_javassist_seam_6
Some internal error has occurred in the service. Please contact the support team.

ANy Suggestions?
 
The error means:
Certificate Expired Exception.
This is thrown whenever the current Date or the specified Date is after the not After date/time specified in the validity period of the certificate.

Looks like you got a certificate error,
I have no clue how to fix that one, but I think it says what to do at the bottom :-(
Nothing in the Avaya database on this specific error, but looking at other certificate issues at this level,
they say it has to be fixed by an Avaya tech with root level access
 
Patch it, or set the date backwards in System Platform (if you're using that).

Fun thing to note is if you ever have to recover from a release more than 2 years old on System Platform, you have to lie and put a date on installation of <2 years from GA date, then install, then patch, then put the current date otherwise you hit the same sort of error upon installation - it relies on those certs too.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top