It's OK for me (from Paris). Do you still have any issue?
Eric.
--
You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-devel/XMvRoZvEVIQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-devel+...@googlegroups.com.
To post to this group, send email to sage-...@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
On Jun 16, 2016 00:05, "William Stein" <wst...@gmail.com> wrote:
>
> On Wed, Jun 15, 2016 at 4:45 PM, Paul Masson <paulm...@comcast.net> wrote:
> > Is there a firm plan in place to move this database to a hosting service?
> > It's discouraging to spend time trying to help, only to run into machine
> > issues.
> >
>
> Yes. Everything is mostly setup and ready to go on Google Compute
> engine, ... but Erik Bray I guess still hasn't given the green light.
>
> You can test out the server he has staged here:
>
> http://104.197.143.230/
>
> I have also rebooted the live actual trac.sagemath.org server now.
> Hopefully this will make it faster...
Yup. I'm actively working on it. I'm just finishing up some updates to Sage's Trac plugin to fix some issues (particularly with the SSH key handling) that I wasn't satisfied with in the process of reconstructing the existing Trac + git setup.
Should have it done soon.
--
You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-devel/XMvRoZvEVIQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-devel+...@googlegroups.com.
On Jun 17, 2016 16:52, "Volker Braun" <vbrau...@gmail.com> wrote:
>
> Possibly because trac static assets need to be served by the web server instead of trac's own handler? Otherwise trac is really slow, we had that before.
No it has nothing to do with that. Need to dig a little deeper, but I'm going home for the night. I put some debug code in the mod_wsgi script to see what's going on but it's not telling me much. It blocks on reading environ['wsgi.input'] [1], which is a file-like handle to the form post data in the body of the request.
This happens regardless of whether Trac tries to read or my own code. The request body just never makes it, like Apache is just dropping the connection before the request body can be read. I wonder if we're being DoS'd (except GETs are working just fine).
http://wsgi.readthedocs.io/en/latest/definitions.html#envvar-wsgi.input
> On Friday, June 17, 2016 at 4:39:22 PM UTC+2, Erik Bray wrote:
>>
>> On Fri, Jun 17, 2016 at 1:52 PM, Jeroen Demeyer <jdem...@cage.ugent.be> wrote:
>> > On 2016-06-16 09:09, Jeroen Demeyer wrote:
>> >>
>> >> On 2016-06-16 00:05, William Stein wrote:
>> >>>
>> >>> I have also rebooted the live actual trac.sagemath.org server now.
>> >>> Hopefully this will make it faster...
>> >>
>> >>
>> >> It still doesn't work. I am not able to change the description of ticket
>> >> #20686 for example.
>> >
>> >
>> > For what it's worth: it really seems to depend on the ticket number. Most
>> > tickets work without problems, but #20686 for example is still broken.
>>
>> Bizarrely I was able to update this ticket fine over SSL, but not without SSL.
>>
>> Wasn't someone talking about doing something with CloudFlare? Could
>> that be related?
>
It blocks on reading environ['wsgi.input'] [1], which is a file-like handle to the form post data in the body of the request. This happens regardless of whether Trac tries to read or my own code. The request body just never makes it, like Apache is just dropping the connection before the request body can be read.
On Jun 17, 2016 6:17 PM, "Volker Braun" <vbrau...@gmail.com> wrote:
>
> On Friday, June 17, 2016 at 5:35:06 PM UTC+2, Erik Bray wrote:
>>
>> It blocks on reading environ['wsgi.input'] [1], which is a file-like handle to the form post data in the body of the request. This happens regardless of whether Trac tries to read or my own code. The request body just never makes it, like Apache is just dropping the connection before the request body can be read.
>
>
> Sounds like the client is too slow, possibly due to packet loss / retransmission (we had that at UW at one point, easy to see in packet trace);
Maybe but that would seem to implicate something on UW's end if multiple people outside their network are having issues.
> Reading input is blocking. There are some speed limits depending on web server setup (e.g. mod_reqtimeout). That would explain why SSL works (data likely arrives in bigger chunks).
I played around quite a bit with the mod_reqtimeout settings but it didn't seem to make a difference.
--
You received this message because you are subscribed to a topic in the Google Groups "sage-devel" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sage-devel/XMvRoZvEVIQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sage-devel+...@googlegroups.com.
That's because I took down the SSL site before leaving work yesterday while just trying things. I guess I didn't put it back up again.
I just noticed that the #17790 problem is user-specific because tmonteilcould change the description yesterday while I can still not do so.