Stream Offline?

Discussion in 'Support' started by Radio Free Brooklyn, Mar 30, 2016.

  1. Radio Free Brooklyn

    Radio Free Brooklyn New Member

    Centova is saying my stream is offline. Message at the top of the page reads: " Station is offline (Unable to access account for radiofreebk: failsend|auto|tcok|reconnexc:Socket error during command transmission (failsend|noauto))"

    However, I am still able to hear the stream being broadcast from the studio. I just can't get any data from Centova, and even it's icon menu on the left of the page displays the server as being down (only "start" appears under the "Server" icon. But when I click start, it throws an error. What gives? I'm assuming it isn't collecting data while it's like this, which is problematic.

  2. More Support

    More Support Level 2 Support Staff Member

    Hi Tom

    Apologies for the issue. Some packet loss at the Dallas data centre caused the error you were seeing. The Icecast server itself was still online but the Centova cast control panel was inaccessible for us1 users. We have reset the us1 control daemon and its now working fine. Its likely your start page was affected during this time and not displaying in the directory either but its back now. According to our providers there was some sort of minor DDOS attack on their infrastructure. They say they are "currently working on mitigating this attack in order to restore service. "

    Today there has been a couple of hour long periods of instability and packet loss that appears to have gone away now. Hopefully they have mitigated the DDOS but we'll continue to monitor the situation.

    Screen Shot 2016-03-31 at 00.08.37.png
  3. soul central radio

    soul central radio New Member

    hi as of today iam getting this message on the start page failsend|auto|tcok|reconnexc:Socket error during command transmission (failsend|noauto) and cannot stream..
  4. Support

    Support Level 1 Support Staff Member

    Hi Soul Central Radio,

    Firstly, huge apologies for the inconvenience this has caused you and for the delay in our response whilst we looked into this matter.

    To explain what happened here, our UK3 server ran out of memory after our backups initiated yesterday and because the server didn't actually stop responding to pings we didn't pick up on the problem as quickly as we usually do.

    We have now corrected this issue and added extra memory to prevent this from happening again in the future.

    Once again, we really apologise for the downtime this has caused for your station.

Share This Page