RadioReference on Facebook   RadioReference on Twitter   RadioReference Blog
 

Go Back   The RadioReference.com Forums > Site Administration Forums > Broadcastify/Live Audio Administration

Broadcastify/Live Audio Administration - Administration topics for live audio broadcasting on Broadcastify.com. This forum is for feed providers to get support. Other audio questions go here: Streaming /Broadcasting / Audio Recording forum

Reply
 
LinkBack Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old 12-08-2016, 9:40 AM
blantonl's Avatar
Founder and CEO
  RadioReference Database Admininstrator
Database Admin
Audio Feed Provider
Audio Feed Provider
 
Join Date: Dec 2000
Location: San Antonio, TX
Posts: 8,828
Default audio3 outage - 12/8/2016

Good morning folks.

Audio3 has been experiencing a DOS (denial of service) attack - to mitigate the issue we've failed over to a hot standby and implemented firewalling procedures to mitigate the problem.

The failover will take a couple hours to completely propagate the new DNS information across the Internet. However we're already seeing feeds coming back online on the new server so it will be a gradual process.

Thanks,
__________________
Lindsay C. Blanton III
CEO - RadioReference.com / Broadcastify
Facebook: RadioReference | Broadcastify | Twitter: @RadioReference
Reply With Quote
Sponsored links
  #2 (permalink)  
Old 12-08-2016, 11:52 AM
SenorMoofer's Avatar
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Aug 2010
Location: Kentucky
Posts: 3
Default

Quote:
Originally Posted by blantonl View Post
Good morning folks.

Audio3 has been experiencing a DOS (denial of service) attack - to mitigate the issue we've failed over to a hot standby and implemented firewalling procedures to mitigate the problem.

The failover will take a couple hours to completely propagate the new DNS information across the Internet. However we're already seeing feeds coming back online on the new server so it will be a gradual process.

Thanks,
Thanks for the quick action. Keep up the good work!
Reply With Quote
  #3 (permalink)  
Old 12-08-2016, 2:33 PM
Mylan's Avatar
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Oct 2004
Location: Wheeling, WV
Posts: 460
Default

I have to manually reconnect my feed when it goes down.... I just tried and it is still not connecting. ..Can someone possibly post to this thread when the audio3 is back in business or we are otherwise good to go. Thanks in advance!
Reply With Quote
  #4 (permalink)  
Old 12-08-2016, 3:28 PM
n0nhp's Avatar
Member
  Audio Feed Provider
Audio Feed Provider
Amateur Radio Operator
Amateur Radio
 
Join Date: Dec 2005
Location: Grand Junction
Posts: 656
Default

Audio 3 has been working for me for 4 or more hours, I did find that I had to change the DNS server on my feed machine to get the new IP address.
Changing to the Google server 8.8.4.4 resolved the problem immediately. My router (which the server was pointing to) using my ISP's DNS server would not resolve to the new address. Rather than bomb my working feed with re-assigning the DNS server in the router, I just pointed the computer at the new server and connected on the first try.

Bruce
.
__________________
N0NHP
Reply With Quote
  #5 (permalink)  
Old 12-08-2016, 3:52 PM
Member
  Audio Feed Provider
Audio Feed Provider
Amateur Radio Operator
Amateur Radio
 
Join Date: Sep 2005
Location: Berkeley, CA
Posts: 9
Default

Still no joy out here in the SF Bay Area
Reply With Quote
Sponsored links
  #6 (permalink)  
Old 12-08-2016, 5:00 PM
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Jul 2009
Location: Perth, Western Australia
Posts: 9
Default

Still down this morning here in Australia. :-(
Reply With Quote
  #7 (permalink)  
Old 12-08-2016, 6:55 PM
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Mar 2009
Location: Tolland County, CT
Posts: 239
Default

No dice here either. Flushed dns and did serveral nslookups against different dns servers and all resolved same ip.

Sent from my SAMSUNG-SM-G930A using Tapatalk
Reply With Quote
  #8 (permalink)  
Old 12-08-2016, 7:17 PM
Scan-Denver's Avatar
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Oct 2004
Location: Denver, CO - USA
Posts: 1,586
Default

So my feed (Denver Police, Fire, & EMS) is also on the audio 3 server. I had to re-populate the server information in RadioFeed client (RadioFeed does this automatically by entering in your login info) and it started working again (6:17PM Denver Time).
__________________
Bill
Email
Scanning/Streaming Denver Police, Fire, & EMS Online
GRE PSR 500 (2), RTL-SDR, AirSpy
Reply With Quote
  #9 (permalink)  
Old 12-08-2016, 7:20 PM
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Jul 2009
Location: Perth, Western Australia
Posts: 9
Default

I can't even ping audio3, let alone log in to it.
Reply With Quote
Sponsored links
  #10 (permalink)  
Old 12-08-2016, 7:23 PM
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Mar 2009
Location: Tolland County, CT
Posts: 239
Default

Try pinging audio3.broadcastify.com. my feed was pointed to radioreference. I did a auto configuration again, it went to broadcastify and then connected ok.

Sent from my SAMSUNG-SM-G930A using Tapatalk
Reply With Quote
  #11 (permalink)  
Old 12-08-2016, 7:26 PM
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Jul 2009
Location: Perth, Western Australia
Posts: 9
Default

Champion. That was exactly the problem. Changed servers and it's happy again.
Reply With Quote
  #12 (permalink)  
Old 12-08-2016, 8:49 PM
Member
  Premium Subscriber
Premium Subscriber
 
Join Date: Dec 2008
Posts: 12
Default

For someone that is showing that the server is up and responding, can you ping the address you're using and let me know? I'm getting 174.37.110.68 and I can't ping the server. I cannot connect to the service port either but I can connect without a problem to audio1:

root@radio:/home/x# nc -v -w 10 audio3.radioreference.com 80
nc: connect to audio3.radioreference.com port 80 (tcp) timed out: Operation now in progress
root@radio:/home/x# nc -v -w 10 audio1.radioreference.com 80
Connection to audio1.radioreference.com 80 port [tcp/http] succeeded!

Thanks for any help!
Reply With Quote
  #13 (permalink)  
Old 12-08-2016, 8:50 PM
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Mar 2009
Location: Tolland County, CT
Posts: 239
Default

You need to point to audio3.broadcastify.com

Sent from my SAMSUNG-SM-G930A using Tapatalk
Reply With Quote
  #14 (permalink)  
Old 12-08-2016, 8:54 PM
Member
  Premium Subscriber
Premium Subscriber
 
Join Date: Dec 2008
Posts: 12
Default

Not the reply I was expecting but I definitely appreciate it. I hadn't noticed that my technicals had changed to broadcastify.com. My feeds back up now. Thanks!
Reply With Quote
  #15 (permalink)  
Old 12-08-2016, 8:58 PM
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Mar 2009
Location: Tolland County, CT
Posts: 239
Default

Excellent. Sorry I could not ping from phone to tell you. I guess they didn't update dns for old rr domain name.

Sent from my SAMSUNG-SM-G930A using Tapatalk
Reply With Quote
Sponsored links
  #16 (permalink)  
Old 12-08-2016, 9:13 PM
Mylan's Avatar
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Oct 2004
Location: Wheeling, WV
Posts: 460
Default

Thank you Rob_K..... I would have never figured that out on my own...
Reply With Quote
  #17 (permalink)  
Old 12-09-2016, 8:26 AM
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Mar 2009
Location: Tolland County, CT
Posts: 239
Default

Quote:
Originally Posted by Mylan View Post
Thank you Rob_K..... I would have never figured that out on my own...
Thanks Scan-Denver

I would not have been able to fix mine without his post!
Reply With Quote
  #18 (permalink)  
Old 12-09-2016, 10:05 AM
Member
  Audio Feed Provider
Audio Feed Provider
Amateur Radio Operator
Amateur Radio
 
Join Date: Sep 2005
Location: Berkeley, CA
Posts: 9
Default

It seems as if they changed the domain (radioreference --> broadcastify) at some point. This caused me an extra 3-4 hours of downtime
Reply With Quote
  #19 (permalink)  
Old 12-09-2016, 10:26 AM
Member
  Audio Feed Provider
Audio Feed Provider
 
Join Date: Mar 2009
Location: Tolland County, CT
Posts: 239
Default

Quote:
Originally Posted by jj358mhz View Post
It seems as if they changed the domain (radioreference --> broadcastify) at some point. This caused me an extra 3-4 hours of downtime
My feeds are run off an HP thin client and I have the write filter enabled. Anytime I reboot, it reverts back to original config. I only reboot it once a year and I haven't updated the config in at least 3 years. Next time I reboot, it's going to revert back to RR domain name and I'll need to remember why it won't connect!
Reply With Quote
  #20 (permalink)  
Old 12-09-2016, 2:05 PM
thinder's Avatar
Member
  Audio Feed Provider
Audio Feed Provider
Amateur Radio Operator
Amateur Radio
 
Join Date: Mar 2007
Location: Silverdale WA
Posts: 89
Default Audio 3

Thanks for heads up, Kitsap WA back up
Reply With Quote
Reply

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On



All times are GMT -5. The time now is 12:29 PM.


Powered by vBulletin® Version 3.8.2
Copyright ©2000 - 2017, vBulletin Solutions, Inc.
All information here is Copyright 2012 by RadioReference.com LLC and Lindsay C. Blanton III.Ad Management by RedTyger
Copyright 2015 by RadioReference.com LLC Privacy Policy  |  Terms and Conditions