If you’re visiting the main website at www.rollernet.us today (and in the future) it’s possible that you’ve noticed it’s now sporting an entirely new design.
Phone System Bug Fixed
We tracked down and fixed an intermittent bug in our Asterisk dialplan where a call could be dropped when using one of the group dial options (i.e. “press 2 for sales”). The issue was that one of our internal IAX peers was answering and dropping the call if it couldn’t establish a SIP channel rather than sending unavailable/congestion. We’ve altered our dialplan to send congestion explicitly when warranted.
This issue did not affect the 24-hour pager option since it always goes directly to a special voicemail box rather than a group dial, nor were direct dial extensions affected.
Eaton Service Visit
We have an unplanned Eaton service visit today at 17:00 UTC-8. There was an odd behavior with the UPS the resulted in a utility feed side breaker trip, so we’re having them come inspect the equipment, download logs, etc. The result was that the affected UPS ran on battery for about 5 minutes while we investigated and reset the utility feed breaker; there was no impact to our facility operations.
This event is a good example of where batteries have an advantage over a flywheel system. Since the input breaker tripped, the UPS was relying on its DC supply (whether it’s batteries or flywheels) to support the protected load. A flywheel would not have lasted the 5 minutes it took us to check everything. Flywheels, of course, have a lower long term maintenance cost since batteries are consumable items that need to be replaced on a regular basis. The tradeoff is that flywheels do not have the run time endurance of batteries.
UPDATE: No anomalies were found in the UPS performance monitors.
IP Address Change for rollernetstatus.com
We had to do an unplanned change of the IP addresses for the rollernetstatus.com site due to chronic packet loss issues that were resulting in excessive false pages from NagiosĀ (typically during the early morning hours). The VPS host says this should fix the problem, so we’ll see.
- IPv4 176.58.89.17
- IPv6 2a00:dd80:3c::1e
UPDATE: So far it’s been well behaved without the false pages.
Now Running PowerDNS 3.0 for Primary DNS
As previously mentioned, we planned to upgrade to PowerDNS 3.0 to support some outstanding requests. We’re pleased to announce that this upgrade has been completed. As always, feel free to contact us with any questions.
