Bug summary
__
Summary for 2009-03-15 through 2009-03-22
Bugs opened: 5Bugs closed: 7 Total open bugs: 1049 (-2)
|== Type Changes |== Priority Changes |== Component Changes
|Defect: -2 |Highest: +0 |Conch: -1
|Enhancement: +0 |Nor
I have been operating a busy twisted TCP server for quite some time (1
year+).
Yesterday, it strangely crashed under peak load for that day (it has been
under more load in the past).
# grep segfault /var/log/messages
Mar 20 19:12:15 serv2 kernel: [17687209.144548] twistd[10701]: segfault at
On Sat, 2009-03-21 at 20:02 -0700, Alec Matusis wrote:
> File "/nail/live/im/myserv/service.py", line 1199, in logout
>
> if self.nick in session.sellers:
>
> exceptions.AttributeError: WLResultSet instance has no
> attribute 'sellers'
>
>
>
> This last error re
On Sun, Mar 22, 2009 at 10:32 AM, Itamar Shtull-Trauring
wrote:
> On Sat, 2009-03-21 at 20:02 -0700, Alec Matusis wrote:
>
>> File "/nail/live/im/myserv/service.py", line 1199, in logout
>>
>> if self.nick in session.sellers:
>>
>> exceptions.AttributeError: WLResultS
We also had a similar problem like this on one of our long running servers
although I didn't find some time to archive the logs. I'm not sure if it's
related; but I can see clearly that you're using python2.4 and it has some
funky issues with its memory management (
http://evanjones.ca/python-memor
Hi Simon:
--- On Sat, 3/21/09, stackless-requ...@stackless.com
wrote:
> As more updates are sent zone->hub, per second, the
> incoming client->hub->zone messages take SECONDS to get thru!
> This is with approx 50 messages per second between a single zone and the >hub.
> Is this the sort of p
Hi,
Now I am first to admit my problem lies within my app design somewhere,
but I thought I'd raise it here for advice.
I have a server made from a central stackless python hub, with a boost
python c++ interface, to which c++ clients connect.
This hub is 'surrounded' by stackless python zon
On Fri, 20 Mar 2009 18:16:47 +, Simon Pickles
wrote:
[snip]
As more updates are sent zone->hub, per second, the incoming
client->hub->zone messages take SECONDS to get thru! This is with approx 50
messages per second between a single zone and the hub.
"message" is a very non-specific u
On Sun, 22 Mar 2009 18:32:30 -0500, Jean-Paul Calderone
wrote:
On Fri, 20 Mar 2009 18:16:47 +, Simon Pickles
wrote:
[snip]
As more updates are sent zone->hub, per second, the incoming
client->hub->zone messages take SECONDS to get thru! This is with approx 50
messages per second betwee
