Summary
It has been reported by the 24 7 team that when accessing the supportal application and trying to view the authentication logs that they are receiving an error message Authentication Logs unavailable due to an error.
Â
N/A
Latest Update Wintel team have been engaged to provide a update on this case. A further update will be provided once more information and feedback is given. Â
Latest Update We have engaged Network Systems at the request of the engineers to be able to investigate further. As soon as any new information can be provided, we will advise.
Latest Update We have engaged Network Systems at the request of the engineers to be able to investigate further. As soon as any new information can be provided, we will advise.
Latest Update Investigations by OSS support found that the StrategicRadiusAuthLogsDB was returning an âTable stratRadiusAuthLogs does not existâ exception when users attempted to view authentication logs via the Supportal application. Further investigation by the Network Systems team identified that the exception was being returned due to the radauthdb1msp server being down. Network Systems have now restored service to the radauthdb1msp server and the OSS Support team have been engaged to confirm that they can now connect to the StrategicRadiusAuthLogsDB. A further update will be provided once testing has been completed. Â
Latest Update Investigations by OSS support found that the StrategicRadiusAuthLogsDB was returning an âTable stratRadiusAuthLogs does not existâ exception when users attempted to view authentication logs via the Supportal application. Further investigation by the Network Systems team identified that the exception was being returned due to the radauthdb1msp server being down. Network Systems have now restored service to the radauthdb1msp server and the OSS Support team have been engaged to confirm that they can now connect to the StrategicRadiusAuthLogsDB. A further update will be provided once testing has been completed. Â
Latest Update Investigations by OSS support found that the StrategicRadiusAuthLogsDB was returning an âTable stratRadiusAuthLogs does not existâ exception when users attempted to view authentication logs via the Supportal application. Further investigation by the Network Systems team identified that the exception was being returned due to the radauthdb1msp server being down. Network Systems have now restored service to the radauthdb1msp server and the OSS Support team have been engaged to confirm that they can now connect to the StrategicRadiusAuthLogsDB. A further update will be provided once testing has been completed. Â
Latest Update The OSS Support team have confirmed that the exceptions are still being observed. A meeting has been scheduled for 13:45 with OSS Support and Network Systems team to continue troubleshooting. A further update will be provided following conclusion of the meeting. Â
Latest Update Investigations by the Network Systems and OSS Support teams have identified that the logs from the authentication platform have not been populated on the authlog1 master DB or it slave databases (radauthlog1, 2 and 3) since the 25th May. Supportal calls the radauthlog2 database to retrieve auth logs however exceptions are being thrown as no data current exists in the tables. The Network Systems team are currently in the process of populating authlog1 with the missing auth log data. Once this is completed its slave databases will then be syncâd with the master. A further update will be provided once all data has been populated and salve DBs resyncâd. Â
Latest Update The Network Systems team have advised that the populating of authlog1 with the missing authlog data is continuing to progress and is expected to complete overnight. Once this is completed the slave databases will then be syncâd with the master. A checkpoint meeting with Network Systems and OSS Support teams has been scheduled for 10:00 (30/05). A further update will be provided following conclusion of the meeting. Â
Latest Update The Network Systems team have now re pointed Supportal to call authlog1 to retrieve auth log data as a workaround. Testing has been successfully completed by Users and and the OSS support team. Network Systems will now populate the 3 slave DBs and repoint to radauthlog2 once all have been populated. This is expected to take approx. 24 hours to complete. Â
Latest Update The Network Systems team have now re pointed Supportal to call authlog1 to retrieve auth log data as a workaround. Testing has been successfully completed by Users and and the OSS support team. Network Systems will now populate the 3 slave DBs and repoint to radauthlog2 once all have been populated. This is expected to take approx. 24 hours to complete. Â
Latest Update Next update will be sent by the MIMS during normal working hours. Â
Technical / Suspected Root Cause It was reported users attempting to view authentication logs via Supportal were receiving an Authentication Logs unavailable due to an error message. Investigations by Network Systems and OSS support teams identified that logs from the authentication platform have not been populated on the authlog1 master DB or it slave databases (radauthlog1, 2 and 3) since the 25th May. To restore service the Network Systems team populated the authlog1 master DB and then syncd the 3 slave databases with authlog1. Retesting has since been completed with no further issues being observed. This incident will now be closed with any further root cause analysis being completed via the problem management process. Â