Versions Compared

Old Version 3

changes.mady.by.user Former user

Saved on

compared with

New Version Current

changes.mady.by.user John Jellema

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Verify that Ubisecure SSO starts without errors. If you see the following kind of entry in the ubilogin/logs/sso_diag.YYYY-MM-DD.log  file you have probably not updated LDAP with the new accounting.ldif added to the SSO 8.4. version and you need to return to this step in the installation / upgrade process and execute at least the import-changes script.

    Code Block
    languagetext
    YYYY-MM-DD hh:mm:ss,SSS uas init ERROR Server startup UAS: control.ServiceUnavailableException: UAS: login.InitException: Invalid SSO Accounting Service installation.
YYYY-MM-DD hh:mm:ss,SSS uas init INFO Ubilogin Authentication Server 9.1.0-SNAPSHOT stopped


  2. If you see the following kind of entry in the ubilogin/logs/sso_diag.YYYY-MM-DD.log  file Accounting Service has not properly started, check Troubleshooting Accounting Service.

    Code Block
    languagetext
    YYYY-MM-DD hh:mm:ss,SSS uas init WARN Error in opening Accounting Service JMS connection in SSO startup. Accounting Service is a required component of SSO that needs to be functioning when running SSO. Could not connect to broker URL: tcp://localhost:36161?connectionTimeout=10. Reason: java.net.SocketTimeoutException: connect timed out: javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:36161?connectionTimeout=10. Reason: java.net.SocketTimeoutException: connect timed out: java.net.SocketTimeoutException: connect timed out
YYYY-MM-DD hh:mm:ss,SSS uas init INFO MessageQueueSender initialised with connection to Accounting Service broker URL: tcp://localhost:36161?connectionTimeout=10


  3. See Accounting Service finalization for the additional steps to accomplish.

...