Can you provide more details on the issue you see on a newer thread? The
thread you are posting on is almost 5 years old, so the issue you may be
facing may not be because of what is listed in this old thread. In any
case, this is the code referenced in this old thread:
https://github.com/web2p
I got too many of this error lately. And its getting worse every day. I
have no idea what to do to stop these errors. I have to reset rocket every
few hours.
Was this fix eventually reverted ? Someone knows the file it is this
workaround?
--
Resources:
- http://web2py.com
- http://web2py.com/
On Jun 27, 2012, at 4:02 PM, Massimo Di Pierro wrote:
> I agree. Please check.
That's better; thanks.
>
> On Wednesday, 27 June 2012 17:53:25 UTC-5, Jonathan Lundell wrote:
> On Jun 27, 2012, at 3:45 PM, Massimo Di Pierro wrote:
>> ok.please check the solution in trunk.
>
> OK, but I think that
I agree. Please check.
On Wednesday, 27 June 2012 17:53:25 UTC-5, Jonathan Lundell wrote:
>
> On Jun 27, 2012, at 3:45 PM, Massimo Di Pierro wrote:
>
> ok.please check the solution in trunk.
>
>
> OK, but I think that SocketClosed might be a better exception. And maybe a
> comment pointing to thi
On Jun 27, 2012, at 3:45 PM, Massimo Di Pierro wrote:
> ok.please check the solution in trunk.
OK, but I think that SocketClosed might be a better exception. And maybe a
comment pointing to this thread or something else explaining what it's doing
there (it's a pretty odd piece of code otherwise)
ok.please check the solution in trunk.
On Wednesday, 27 June 2012 08:20:12 UTC-5, Jonathan Lundell wrote:
>
> On Jun 27, 2012, at 6:12 AM, Massimo Di Pierro wrote:
>
> We acn catch it but what do we do? Report "this is a python bug"?
>
>
> The crash is a python bug. The connection failure isn't (n
On Jun 27, 2012, at 6:12 AM, Massimo Di Pierro wrote:
> We acn catch it but what do we do? Report "this is a python bug"?
The crash is a python bug. The connection failure isn't (near as I can tell).
Just treat it as a dropped connection.
>
> On Tuesday, 26 June 2012 20:01:49 UTC-5, Jonathan Lu
We acn catch it but what do we do? Report "this is a python bug"?
On Tuesday, 26 June 2012 20:01:49 UTC-5, Jonathan Lundell wrote:
>
> On Jun 26, 2012, at 5:25 PM, Massimo Di Pierro wrote:
>
> Looks like a buggy socket.py or ssl.py. Is this an occasional error (which
> may depend on parameters su
On Jun 26, 2012, at 5:25 PM, Massimo Di Pierro wrote:
> Looks like a buggy socket.py or ssl.py. Is this an occasional error (which
> may depend on parameters such as certificates) or it reproducible?
This was fixed in Python 2.7. The underlying error is "Transport endpoint is
not connected", whi
It happens rather frequently. At least a few times a day, which
consequently causes web2py to hang and forces me to restart it. I can't
reproduce it manually.
On Tuesday, June 26, 2012 5:25:43 PM UTC-7, Massimo Di Pierro wrote:
>
> Looks like a buggy socket.py or ssl.py. Is this an occasional er
Looks like a buggy socket.py or ssl.py. Is this an occasional error (which
may depend on parameters such as certificates) or it reproducible?
On Tuesday, 26 June 2012 12:30:58 UTC-5, msmagoo wrote:
>
> Hi all,
>
> I have a healthcheck web2py application that simply reads healthcheck
> informatio
Let us know what you discover.
On May 7, 3:57 pm, David Zejda wrote:
> Yes, vanilla hardware (some dual core Intel). I'm running the latest
> web2py now, but it was crashing even with about half year old version
> (1.73 or so), so the issue is probably not webserver specific. The
> process is in
Yes, vanilla hardware (some dual core Intel). I'm running the latest
web2py now, but it was crashing even with about half year old version
(1.73 or so), so the issue is probably not webserver specific. The
process is in ps ax no more when crashes. Currently the server is
being accessed through Apac
Is this standard hardware? The only place I've seen Python crash is on
non-standard hardware (AS400) with a non-supported build of Python.
Web2py recent switched from Cherrypy's wsgiserver to Rocket (which I
wrote) as of version 1.77.2 (I think). Which version are you running?
With built-in
AFAIK web2py uses cherrypy webserver, which listens as a daemon on
certain port. With crashing I mean that the listening process (web2py
with cherrypy at the background) suddenly terminates. I use standard
Python v 2.5.2 as packaged for Debian.
David
On May 7, 2:52 pm, Timothy Farrell wrote:
> C
15 matches
Mail list logo
