Hello,
We are attempting to upgrade a few test servers from Horizon View 7.0.3 to 7.4.0 by using the upgrade process without a full reinstallation. The upgrade itself appears to be successful yet access to the web console/admin console does not appear to work. Various browsers produce various errors all suggesting the website on the upgraded server is not available.
The best clue we have detected so far has to do with certs. We have tried multiple cert configurations but are not able to access the admin console including:
- Generate new self-signed cert, then upgrade
- Remove self-signed cert, then upgrade
- Generated new signed cert from internal CA, then upgrade
The logs on the server look like this:
2018-02-12T10:42:48.801-06:00 WARN (0C44-1240) <SwiftMQ-jms.connection-3> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv
2018-02-12T10:42:48.803-06:00 WARN (0C44-1240) <SwiftMQ-jms.connection-3> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv
2018-02-12T10:42:48.804-06:00 WARN (0C44-1238) <SwiftMQ-jms.connection-1> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv
2018-02-12T10:42:48.804-06:00 WARN (0C44-1238) <SwiftMQ-jms.connection-1> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv
2018-02-12T10:42:53.881-06:00 ERROR (1450-168C) <SwiftMQ-ConnectorPool-5> [JMSTunnelSSLSocketFactory] Certificate thumbprint verification failed, no router thumbprints available. Presented identity: router/testsrv
2018-02-12T10:42:53.881-06:00 ERROR (1450-168C) <SwiftMQ-ConnectorPool-5> [JMSTunnelSSLSocketFactory] General error occurred: No known thumbprints: router/testsrv
2018-02-12T10:42:53.965-06:00 ERROR (1450-1688) <SwiftMQ-ConnectorPool-4> [JMSTunnelSSLSocketFactory] Certificate thumbprint verification failed, no router thumbprints available. Presented identity: router/testsrv
2018-02-12T10:42:53.965-06:00 ERROR (1450-1688) <SwiftMQ-ConnectorPool-4> [JMSTunnelSSLSocketFactory] General error occurred: No known thumbprints: router/testsrv
2018-02-12T10:42:54.041-06:00 ERROR (1450-1684) <SwiftMQ-ConnectorPool-3> [JMSTunnelSSLSocketFactory] Certificate thumbprint verification failed, no router thumbprints available. Presented identity: router/testsrv
2018-02-12T10:42:54.041-06:00 ERROR (1450-1684) <SwiftMQ-ConnectorPool-3> [JMSTunnelSSLSocketFactory] General error occurred: No known thumbprints: router/testsrv
2018-02-12T10:42:54.116-06:00 WARN (0C44-1248) <SwiftMQ-jms.connection-5> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv
2018-02-12T10:42:54.116-06:00 ERROR (1450-16E0) <SwiftMQ-ConnectorPool-6> [JMSTunnelSSLSocketFactory] Certificate thumbprint verification failed, no router thumbprints available. Presented identity: router/testsrv
2018-02-12T10:42:54.116-06:00 ERROR (1450-16E0) <SwiftMQ-ConnectorPool-6> [JMSTunnelSSLSocketFactory] General error occurred: No known thumbprints: router/testsrv
2018-02-12T10:42:54.189-06:00 ERROR (1450-1120) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] Certificate thumbprint verification failed, no router thumbprints available. Presented identity: router/testsrv
2018-02-12T10:42:54.189-06:00 ERROR (1450-1120) <SwiftMQ-ConnectorPool-1> [JMSTunnelSSLSocketFactory] General error occurred: No known thumbprints: router/testsrv
2018-02-12T10:42:54.191-06:00 WARN (0C44-1240) <SwiftMQ-jms.connection-3> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv
2018-02-12T10:42:54.191-06:00 WARN (0C44-1244) <SwiftMQ-jms.connection-4> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv
2018-02-12T10:42:54.192-06:00 WARN (0C44-1248) <SwiftMQ-jms.connection-5> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv
2018-02-12T10:42:54.247-06:00 WARN (0C44-1244) <SwiftMQ-jms.connection-4> [JMSAuthenticationSwiftlet] No certificate presented by user broker/testsrv
2018-02-12T10:42:54.866-06:00 WARN (1450-16A0) <Thread-2> [bo] Item enqueued on "Outbound JMS Forwarder" but there are no workers available to process it. Busy workers = 0, queue length = 130
Any thoughts on what else we could try that would impact the cert or allow us to regain access to the admin console after an upgrade?