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
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
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
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
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
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.
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
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
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
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.
+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
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
12 matches
Mail list logo
