Blog

Server Issues on Saturday 14th November

Unfortunately on Saturday we had some access problems related to a recent update to provide a heartbeat monitor.

After successful streams over the last few weeks the update performed this week didn`t perform as expected, for which we apologise profusely.
The issue seemed to cause some access problems, just prior to kick-off, to the website as the server appeared unresponsive to some users. It appears to be related to DNS access issues which we believe to caused by the heartbeat monitor.

At the beginning of this week we found a purchase from a well know pirate site. Brian decided to provide an update to combat access and onward streaming. This meant adding a heartbeat monitor every 60-90 seconds for further checking and verification.

We had anticipated this having little effect on the CPU processing capability of the servers, looking at the pictures below backs up our understanding of that.

However, there does appear to be web access problems to users shortly before kick off. Users already logged in were unaffected. The update was reverted at 3pm.

After reseting the software at 3pm there still appeared to be access problems after this for quite a bit of the first half preventing some users gaining access. The reason for this is that existing users heartbeat software was still running. We have removed this software and will approach this in a different way in future.

Our bandwidth download was nearly 3,000 GB`s of data so the majority of viewers continued to watch the stream.

Of course for those that didn`t get access it was very frustrating and again we apologise to those people affected.

[TITLE]

The Server CPU utilisation graphs showing a peak around the match time but at a maximum of 4% cpu there was a lot of spare capacity.

[TITLE]

[TITLE]