[Discuss-gnuradio] www.gnuradio.org (and git) is down

2012-02-18 Thread Marcus D. Leech
www.gnuradio.org appears to be dead, as is the GIT server. Sigh. -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org ___ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org

Re: [Discuss-gnuradio] www.gnuradio.org (and git) is down

2012-02-18 Thread Tom Rondeau
On Sat, Feb 18, 2012 at 11:59 AM, Marcus D. Leech mle...@ripnet.com wrote: www.gnuradio.org appears to be dead, as is the GIT server. Sigh. -- Marcus Leech Principal Investigator Shirleys Bay Radio Astronomy Consortium http://www.sbrac.org It's working for me. No reset required. Try

Re: [Discuss-gnuradio] www.gnuradio.org (and git) is down

2012-02-18 Thread John Coppens
On Sat, 18 Feb 2012 12:09:46 -0500 Tom Rondeau t...@trondeau.com wrote: It's working for me. No reset required. Try again. If redirecting is not enabled in the browser, it may not get to gnuradio.org. It seems www.gnuradio.org goes there through redirection. John

Re: [Discuss-gnuradio] www.gnuradio.org (and git) is down

2012-02-18 Thread Marcus D. Leech
On 02/18/2012 01:01 PM, John Coppens wrote: On Sat, 18 Feb 2012 12:09:46 -0500 Tom Rondeaut...@trondeau.com wrote: It's working for me. No reset required. Try again. If redirecting is not enabled in the browser, it may not get to gnuradio.org. It seems www.gnuradio.org goes there through

Re: [Discuss-gnuradio] www.gnuradio.org (and git) is down

2012-02-18 Thread Dan CaJacob
Tom, Am I correct in assuming you are running GR.org on AWS? I have noticed in my own use of AWS that they have occasional scheduled reboots of their hardware for upgrades, which naturally causes a reboot of your instance. These scheduled events are listed in the AWS console page. A

Re: [Discuss-gnuradio] www.gnuradio.org (and git) is down

2012-02-18 Thread Johnathan Corgan
On Sat, Feb 18, 2012 at 10:56, Dan CaJacob d...@spacequest.com wrote: A scheduled maintenance reboot may have caused the short outage Marcus saw. We get an email on boot from the instance, so we know when these happen (it didn't.) My guess was it was a transient network connectivity issue for