Update - 12:30PM
Hoopla support was able to identify and resolve the issue that was impacting our SIP2 server. They have restored Addison's authentication and we're no longer seeing excessive requests.
Thanks for everyone's patience!
Update 8/28 - 9AM
Hoopla support identified a configuration issue on their end that was causing Addison's account to make an unusual number of calls very rapidly, which overwhelmed the SIP2 service and slowed our Symphony server down significantly. Hoopla has temporarily removed Addison from the authentication pool while they investigate on their side.
We have reenabled Hoopla access to SWAN and are continuing to monitor the system for excessive connections. We'll provide an update on Addison's access when we hear back from Hoopla.
This afternoon, our Symphony server became unresponsive. SWAN and SirsiDynix support was able to identify excessive SIP2 connections over Hoopla's port. When our SIP2 server came online, Hoopla's port immediately claimed nearly 70% of our available SIP2 connections. This caused significant delays on our Production server, resulting in the downtime experienced.
We have disabled the SIP2 connection until we are able to troubleshoot this issue with Hoopla support. Hoopla authentication is unavailable until we're able to determine the root cause for the outage this afternoon. We will provide updates as more information becomes available.
Thank you for your patience as we worked through this, WorkFlows is now up.
This issue was caused by excessive calls to the Symphony server by Hoopla, we have temporarily suspended their access. As a result the Hoopla service is currently down.
Please report any connectivity issues you may encounter.
Symphony WorkFlows is currently down. We are troubleshooting the issue with SirsiDynix and will update the Known Issue on our SWAN support site as we have more information. Please use the Offline Circulation module while we troubleshoot the issue.
