...
Note |
---|
Whenever you need to change settings in the update |
Installation / upgrade incidents
...
Info | |||||
---|---|---|---|---|---|
| |||||
When:
What:
Why:
How to fix:
|
Info | ||
---|---|---|
| ||
When:
What:
Why:
How to fix:
|
...
Info | ||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||
When:
What:
Why:
How to fix:
|
...
Info | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||
When:
What:
Why:
How to fix:
|
...
Info | |||||
---|---|---|---|---|---|
| |||||
When:
What:
Why:
How to fix:
|
...
Info | |||||
---|---|---|---|---|---|
| |||||
When:
What:
Why:
How to fix:
|
...
Info | ||||||
---|---|---|---|---|---|---|
| ||||||
When:
What:
Why:
How to fix:
|
...
Info | ||
---|---|---|
| ||
When:
What:
Why:
How to fix:
|
...
Info | ||
---|---|---|
| ||
When:
What:
Why:
How to fix:
|
...
Info | ||
---|---|---|
| ||
When:
What:
Why:
How to fix:
|
...
Info | ||
---|---|---|
| ||
When:
What:
Why:
How to fix:
|
...
Info | |||||
---|---|---|---|---|---|
| |||||
When:
What:
Why:
How to fix:
|
...
Info | |||||
---|---|---|---|---|---|
| |||||
When:
What:
Why:
How to fix:
|
...
Info | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
When:
What:
Why:
How to fix:
|
...
Info | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||
When:
What:
Why:
How to fix:
|
...
Check from diagnostics logs if there are any warnings or errors, in particular the following ones. If you have followed the installation / upgrade process the broker URL host name should always be localhost and the port number should match with the one configured on the Accounting Service side.
Code Block language text 2019-05-03 16:48:18,707 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. javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616?connectionTimeout=10. Reason: java.net.SocketTimeoutException: connect timed out 2019-05-03 17:00:08,112 tech WARN Error in opening Accounting Service JMS connection, event cannot be sent. Accounting Service is a required component of SSO that needs to be functioning when running SSO. javax.jms.JMSException: Could not connect to broker URL: tcp://localhost:61616?connectionTimeout=10. Reason: java.net.SocketTimeoutException: connect timed out
Check from diagnostics logs if there is the following warning. It implies that you have not properly installed / upgraded SSO or the respective LDAP entry has been manually modified.
Code Block language text 2019-05-03 18:09:46,030 tech WARN MessageQueueSender missing Accounting Service broker URL. Accounting Service is a required component of SSO that needs to be functioning when running SSO.
If the connection is in tact and the Accounting Service is running SSO diagnostics log shows in the startup
Code Block language text 2019-05-03 13:00:03,998 init MessageQueueSender initialised with connection to Accounting Service broker URL: tcp://localhost:36161?connectionTimeout =10
If Accounting Service is not running start it.
If connection timeout is too short on your server change the respective Accounting Service setting in
file, follow instructions in here. Remember to update LDAP.win32.config
/unix.configIf the connection seems to be in tact change log level of
uas/tech
to DEBUG (see Management UI logging configuration) and check for the following messages in the diagnostics log. If the events are sent normally then the problem is on the Accounting Service receiving side.Code Block language text 2019-08-14 12:43:35,969 tech DEBUG Going to send JMS message to the queue: SSOEventQueue 2019-08-14 12:43:35,970 tech DEBUG Elapsed time in MessageQueueSender: 3377300 nanos (3 ms), enabled: true, message sent: true
In the end remember to set the SSO log level back to INFO
...
- Check from the Accounting Service health check (see finalise Accounting Service installation) that all the system components are 'UP'. System can be running without being able to handle events properly if
eventReceiver
is 'DOWN', the details will show the problem cause. You can find more details about the error situation in the Accounting Service application log. Check from the Accounting Service application log if there are any warnings or errors especially related to listener execution from which you could derive the reason for failure. It might be related to a database connection or secret key handling incident explained on this page.
Code Block language text 2019-08-24 06:34:35.166 WARN 55025 --- [DefaultMessageListenerContainer-5] o.s.j.l.DefaultMessageListenerContainer : Ex ecution of JMS message listener failed, and no ErrorHandler has been set. org.springframework.jms.listener.adapter.ListenerExecutionFailedException: Listener method 'public void com.ubisecure.ids .accounting.collector.SsoEventReceiver.receiveMessage(com.ubisecure.ids.accounting.event.SsoUserEvent)' threw exception;
If the JMS message handling fails the Accounting Service retries again for a configured amount of times and finally you can see the following info and error messages. Look for other error messages near these messages and try to fix the problem.
Code Block language text 2019-08-24 06:34:35.196 INFO 55025 --- [DefaultMessageListenerContainer-4] c.u.i.a.collector.SsoEventReceiver : Received message in Dead Letter Queue (DLQ) originated from: queue://SSOEventQueue ... 2019-08-24 06:35:05.203 ERROR 55025 --- [DefaultMessageListenerContainer-4] c.u.i.a.collector.SsoEventReceiver : Could not process the message in DLQ, setting event receiving down.
If you cannot identify the problem change the logging level to DEBUG (see Accounting Service logging / Changing log level while system is running) and look for the following messages in the Accounting Service application log. If you see only the first message then the problem lies with the pseudonymisation or database.
Code Block language text 2019-08-29 17:00:50.443 DEBUG 104774 --- [DefaultMessageListenerContainer-5] c.u.i.a.repository.EventDatabaseService : Starting to create event of type: TICKET_GRANTED. 2019-08-29 17:00:50.478 DEBUG 104774 --- [DefaultMessageListenerContainer-5] c.u.i.a.collector.SsoEventReceiver : Successfully stored a new received event with key: 35
You can set the logging level even to TRACE and look for the following pair of messages in the Accounting application log. If you don't see this log message the event sent by SSO has not for some reason reached Accounting JMS queue and you may need to look at the SSO side again. If you still don't see this message there can be a system error related to the JSM message conversion and you may contact Ubisecure support.
Code Block language text 2019-08-24 06:18:59.548 TRACE 55025 --- [DefaultMessageListenerContainer-3] c.u.i.a.collector.SsoEventReceiver : Received event of type: TICKET_GRANTED
In the end remember to set the Accounting Service log level back to INFO
...