Looks OK after reboot.
On Saturday, June 2, 2018 at 8:16:36 AM UTC+2, Frédéric Chapoton wrote:
>
> This morning, the trac server seems to be down with
>
> ERR_TIMED_OUT
>
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this gr
I'm not sure either. It's definitely a connection issue locally. I'm just
going to use a different connection. Thanks.
On Tuesday, December 20, 2016 at 5:54:14 PM UTC-6, Volker Braun wrote:
>
> Clearly its a network connectivity issue on your side... don't know whats
> causing it though. For the
Clearly its a network connectivity issue on your side... don't know whats
causing it though. For the record, here is a tracerout. Anything past hop
#7 is google infrastructure.
$ traceroute trac.sagemath.org
traceroute to trac.sagemath.org (104.197.143.230), 30 hops max, 60 byte
packets
1 rou
I'm still having trouble accessing the trac server by web and over ssh.
Here is the output when I run "ssh -vvv g...@trac.sagemath.org info":
OpenSSH_7.2p2 Ubuntu-4ubuntu2.1, OpenSSL 1.0.2g 1 Mar 2016
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: /etc/ssh/ssh_config line 19: Ap
works for me, too
On Sunday, December 18, 2016 at 11:55:31 PM UTC+1, William wrote:
>
> The trac website is up for me and my uptimerobot monitor hasn't shown any
> downtime.
>
> On Sun, Dec 18, 2016 at 2:17 PM Maxie Schmidt > wrote:
>
>> The trac server ssh and website are still down when I che
The server has been down for me since yesterday afternoon. I'm getting
connection timed out messages over ssh and from my web browser.
On Dec 18, 2016 4:55 PM, "William Stein" wrote:
The trac website is up for me and my uptimerobot monitor hasn't shown any
downtime.
On Sun, Dec 18, 2016 at 2:17
The trac website is up for me and my uptimerobot monitor hasn't shown any
downtime.
On Sun, Dec 18, 2016 at 2:17 PM Maxie Schmidt wrote:
> The trac server ssh and website are still down when I check them as well.
>
>
> On Sunday, December 18, 2016 at 8:06:38 AM UTC-6, Ralf Stephan wrote:
>
> Sit
The trac server ssh and website are still down when I check them as well.
On Sunday, December 18, 2016 at 8:06:38 AM UTC-6, Ralf Stephan wrote:
>
> Site unreachable. Maybe that causes the SSH key problem in another thread
> as well.
>
--
You received this message because you are subscribed to t
On Apr 7, 2:25 pm, David Harvey <[EMAIL PROTECTED]> wrote:
> david
Yeah, ran out of disc space. It is fixed now, but only a question of
time until it will happen again.
Cheers,
Michael
--~--~-~--~~~---~--~~
To post to this group, send email to sage-devel@google
Down again!
{{{
Python Traceback
Traceback (most recent call last):
File "/var/lib/python-support/python2.4/trac/web/main.py", line 387,
in dispatch_request
dispatcher.dispatch(req)
File "/var/lib/python-support/python2.4/trac/web/main.py", line 237,
in dispatch
resp = chosen_handler.
Trac is back. (I restarted it.)
William
On Mon, Mar 3, 2008 at 8:10 AM, David Harvey <[EMAIL PROTECTED]> wrote:
>
> Proxy Error
>
> The proxy server received an invalid response from an upstream server.
> The proxy server could not handle the request GET /sage_trac/.
>
> Reason: Error reading f
11 matches
Mail list logo
