Re: [sage-devel] Re: Trac down

On 2017-05-08 12:23, Dima Pasechnik wrote: > Works for me. A particular link you have problem there? I had the same troubles a couple of hours ago; now it seem to work again. Daniel -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe

Re: [sage-devel] Re: Trac down

On Mon, 8 May 2017, Dima Pasechnik wrote: Works for me. A particular link you have problem there? Seems to work again. At least these had problems: https://trac.sagemath.org/ticket/22773 https://trac.sagemath.org/ticket/22674 -- Jori Mäntysalo

[sage-devel] Re: Trac down

Works for me. A particular link you have problem there? On Monday, May 8, 2017 at 9:25:16 AM UTC+1, Jori Mäntysalo wrote: > > Trac gives the Internal server error, and even that after waiting a > minute. > > -- > Jori Mäntysalo > -- You received this message because you are subscribed to the

Re: [sage-devel] Re: trac down?

Le samedi 22 octobre 2016 15:16:40 UTC+2, William a écrit : > > Hi, > > I recreated trac on a VM with much, much more RAM and cpu. It seems > to be working well now. > Thank you very much! Indeed it works well. Eric. -- You received this message because you are subscribed to the Google Grou

Re: [sage-devel] Re: trac down?

I recreated the machine and the digital signature and other ssh keys were reset. On Sat, Oct 22, 2016 at 8:19 AM, Ralf Stephan wrote: > Is that correct (when trying to git trac push): > STDERR: The fingerprint for the ECDSA key sent by the remote host is > STDERR: SHA256:4Op/q3b5792x+F1lH

Re: [sage-devel] Re: trac down?

Is that correct (when trying to git trac push): STDERR: The fingerprint for the ECDSA key sent by the remote host is STDERR: SHA256:4Op/q3b5792x+F1lHSKRi5UIORAPDlIFVA5cUq9YVXI. STDERR: Please contact your system administrator. On Saturday, October 22, 2016 at 3:16:40 PM UTC+2, William

Re: [sage-devel] Re: trac down?

Hi, I recreated trac on a VM with much, much more RAM and cpu. It seems to be working well now. William On Sat, Oct 22, 2016 at 5:49 AM, William Stein wrote: > Hi, > > trac is definitely down (according to my monitor). I tried rebooting > it which failed as well. I'm going to recreate it wit

Re: [sage-devel] Re: trac down?

Hi, trac is definitely down (according to my monitor). I tried rebooting it which failed as well. I'm going to recreate it with a more powerful/expensive VM (or otherwise fix it), and we'll see how that goes. William On Sat, Oct 22, 2016 at 3:40 AM, Eric Gourgoulhon wrote: > Hi, > > From Fran

Re: [sage-devel] Re: trac down?

Hi, >From France, it seems that we still cannot connect to https://trac.sagemath.org/ while the rest of Internet seems OK (including http://www.sagemath.org/ and github). I could push a new commit to trac though (the response was very slow but it seemed to have worked). Eric. Le vendredi 21 o

Re: [sage-devel] Re: trac down?

*GitHub Status* ‏@githubstatus 50m50 minutes ago We have migrated to an unaffected DNS provider. Some users may experience problems with cached results as the change propagates. On Friday, October 2

Re: [sage-devel] Re: trac down?

Github.com didn't resolve for me earlier, that might mess with the trac plugins... On Friday, October 21, 2016 at 8:10:41 PM UTC+2, William wrote: > > Half the internet is down right now... > > > http://gizmodo.com/this-is-probably-why-half-the-internet-shut-down-today-1788062835 > > > I

Re: [sage-devel] Re: trac down?

Half the internet is down right now... http://gizmodo.com/this-is-probably-why-half-the-internet-shut-down-today-1788062835 I don't see why this would impact trac.sagemath.org though... On Fri, Oct 21, 2016 at 9:49 AM, Lennart Jern wrote: > On Thursday, October 20, 2016 at 10:38:01 AM UTC+2,

[sage-devel] Re: trac down?

On Thursday, October 20, 2016 at 10:38:01 AM UTC+2, Dima Pasechnik wrote: > > I can neither see tickets, nor even ssh into the server. > Looks like a reboot will be needed. > > Dima > Not just trac, I get DNS resolution error when trying to reach sagemath.org. -- You received this message beca

[sage-devel] Re: trac down?

I just installed updates and rebooted it... On Saturday, August 20, 2016 at 7:20:53 PM UTC+1, Jean-Pierre Flori wrote: > > Nevermind, it seems up. > > On Saturday, August 20, 2016 at 7:47:17 PM UTC+2, Jean-Pierre Flori wrote: >> >> trac down? >> > -- You received this message because you are sub

[sage-devel] Re: trac down?

Nevermind, it seems up. On Saturday, August 20, 2016 at 7:47:17 PM UTC+2, Jean-Pierre Flori wrote: > > trac down? > -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email t

Re: [sage-devel] Re: Trac down again

Thanks! The trac<->git changeset browser obviously has to grind through the repo all the time, so this is the likely candidate for io load. But the repo isn't all that large all things considered, it should easily fit into memory. Some filesystem tuning might be really benefitial, in particular

Re: [sage-devel] Re: Trac down again

The physical machine that Trac is running has been experiencing heavy disk IO from different processes for the past 3 days, which is likely contributing to the problems. The image file is also located on a ZFS volume, and I've seen odd issues with ZFS recently. I think I will move Trac to the n

Re: [sage-devel] Re: Trac down again

Yes, we should allow indexing of tickets but not of the timeline and the changeset browser. On Friday, October 11, 2013 8:32:15 PM UTC+1, William wrote: > > On Fri, Oct 11, 2013 at 11:55 AM, Volker Braun > > > wrote: > > Trac isn't using any swap. It is pulling quite a lot of CPU load. > Loo

Re: [sage-devel] Re: Trac down again

On Fri, Oct 11, 2013 at 11:55 AM, Volker Braun wrote: > Trac isn't using any swap. It is pulling quite a lot of CPU load. Looking at > the log, it seems somebody is indexing trac and pulling up old changesets > and timeline (both are notoriously slow in trac). For example: > > http://trac.sagemath

Re: [sage-devel] Re: Trac down again

Trac isn't using any swap. It is pulling quite a lot of CPU load. Looking at the log, it seems somebody is indexing trac and pulling up old changesets and timeline (both are notoriously slow in trac). For example: http://trac.sagemath.org/timeline?from=2009-05-06T13%3A17%3A39-07%3A00&precision=s

Re: [sage-devel] Re: Trac down again

On Fri, Oct 11, 2013 at 9:52 AM, William Stein wrote: > On Fri, Oct 11, 2013 at 9:39 AM, Jean-Pierre Flori wrote: >> Is it down again ? > > It's down. At the moment, I think Keith is the only one who knows how > to fix it easily, so we should probably wait for him to wake up / > check his email.

Re: [sage-devel] Re: Trac down again

On Fri, Oct 11, 2013 at 9:39 AM, Jean-Pierre Flori wrote: > Is it down again ? It's down. At the moment, I think Keith is the only one who knows how to fix it easily, so we should probably wait for him to wake up / check his email. I'm sure he'll take additional steps today to make trac more r

[sage-devel] Re: Trac down again

Is it down again ? -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googleg

[sage-devel] Re: Trac down again

Thanks! Hopefully youll find what the real problem was. On Thursday, October 10, 2013 8:00:52 PM UTC+2, Keith Clawson wrote: > > Trac is back up. Something causes Trac to use nearly 100% CPU and memory > after running for a few weeks, and eventually it becomes impossible to ssh > into the VM run

[sage-devel] Re: Trac down again

Trac is back up. Something causes Trac to use nearly 100% CPU and memory after running for a few weeks, and eventually it becomes impossible to ssh into the VM running it. For the time being I'll put a monitor on Trac's memory use and try to restart it before it gets to the point of locking up.

[sage-devel] Re: Trac down again

+1 :-/ And I also noticed that Feedly had not been refreshing sage-devel's rss feed for weeks T_T Nathann On Thursday, October 10, 2013 11:57:46 AM UTC+2, Jean-Pierre Flori wrote: > > Same here... > It was down at some point this morning, then came back to life and is down > again now. > > On

[sage-devel] Re: Trac down again

Same here... It was down at some point this morning, then came back to life and is down again now. On Thursday, October 10, 2013 11:50:15 AM UTC+2, Jeroen Demeyer wrote: > > Trac is not responding at all, I get 504 Gateway Time-out. > -- You received this message because you are subscribed to

[sage-devel] Re: trac down?

On Jan 17, 4:12 am, Dima Pasechnik wrote: > ok, it works now for me. > Seems to be down again. I got "ProgrammingError: could not write to hash-join temporary file: No space left on device". David -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this

[sage-devel] Re: trac down?

ok, it works now for me. On Jan 17, 11:42 am, William Stein wrote: > On Sun, Jan 16, 2011 at 12:15 PM, Dima Pasechnik wrote: > > I get the following messages while trying to access tickets.. > > Notification codes:     (1, > > INTERNAL_ERROR,http://trac.sagemath.org/sage_trac/ticket/6391) > > I

[sage-devel] Re: trac down

Jason Grout wrote: > When trying to pull up http://trac.sagemath.org/ > > I get: > > Bad Gateway > > The proxy server received an invalid response from an upstream server. > > Additionally, a 502 Bad Gateway error was encountered while trying to > use an ErrorDocument to handle the request.

[sage-devel] Re: trac down at the moment

On Feb 10, 2008 3:24 PM, mabshoff <[EMAIL PROTECTED]> wrote: > > Hi, > > trac is down at the moment. I am on the road, so I probably won't fix > it any time soon. I restarted it and it works fine now. -- William > > Cheers, > > Michael > > > -- William Stein Associate Professor of Mathema