Op Ma, 2009-04-20 om 13:39 +0800 skryf Olaf:
> OK, I think I may have found one hickup. This is something that occured
> a few times and may have lead to Pootle becoming unresponsive. In that
> case, CPU load goes down and nothing happens, Pootle does not respond.
> If it responds, it will always happen under a high CPU load.
>
> Anyway, this is what I found:
>
> 2009-04-14 15:41:06: Error handling request from ('10.1.2.253', 56180):
> error: (32, 'Broken pipe')
In my experience, this usually happens if an expensive operation was
necessary (for example calculating stats for the first time in a big
project) and it didn't complete before the browser time-out.
> 2009-04-14 15:41:06: Traceback follows:
> Traceback (most recent call last):
> File "/usr/lib/python2.5/SocketServer.py", line 222, in handle_request
> self.process_request(request, client_address)
> File "/usr/lib/python2.5/SocketServer.py", line 241, in process_request
> self.finish_request(request, client_address)
> File "/usr/lib/python2.5/SocketServer.py", line 254, in finish_request
> self.RequestHandlerClass(request, client_address, self)
> File
> "/usr/lib/python2.5/site-packages/jToolkit/web/simplewebserver.py", line
> 73, in __init__
> File "/usr/lib/python2.5/SocketServer.py", line 522, in __init__
> self.handle()
> File "/usr/lib/python2.5/BaseHTTPServer.py", line 316, in handle
> self.handle_one_request()
> File "/usr/lib/python2.5/BaseHTTPServer.py", line 310, in
> handle_one_request
> method()
> File
> "/usr/lib/python2.5/site-packages/jToolkit/web/simplewebserver.py", line
> 241, in do_GET
> File
> "/usr/lib/python2.5/site-packages/jToolkit/web/simplewebserver.py", line
> 194, in serve_request
> File
> "/usr/lib/python2.5/site-packages/jToolkit/web/simplewebserver.py", line
> 222, in sendpage
> File
> "/usr/lib/python2.5/site-packages/jToolkit/web/simplewebserver.py", line
> 441, in sendpage
> File "/usr/lib/python2.5/site-packages/Pootle/pootle.py", line 582,
> in sendpage
> File
> "/usr/lib/python2.5/site-packages/jToolkit/web/templateserver.py", line
> 139, in sendpage
> File "/usr/lib/python2.5/site-packages/jToolkit/web/server.py", line
> 333, in sendpage
> File
> "/usr/lib/python2.5/site-packages/jToolkit/web/simplewebserver.py", line
> 217, in sendfile
> File "/usr/lib/python2.5/socket.py", line 262, in write
> self.flush()
> File "/usr/lib/python2.5/socket.py", line 249, in flush
> self._sock.sendall(buffer)
> error: (32, 'Broken pipe')
This happened immediately after the first one, so it is likely that the
browser for this request simply timed out because of the preceding
request that was taking too long to respond.
> Does this look like something that could send Pootle sleeping under too
> many (about 15 at that time) users?
It is a bit hard without more context. If you are able to send a bigger
part of the log (privately might be best), I might be able to take a
more detailed look.
If you can send me the output of pocount over your po directory, that
might help as well (to get a good idea of the size of things).
The most useful information is likely just after this snippet in the
log, but if the 15 users are consecutively busy with many things that is
not a definite. We'll have to see if we can find more information.
Keep well
Friedel
--
Recently on my blog:
http://translate.org.za/blogs/friedel/en/content/monolingual-translation-formats-considered-harmful
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
Translate-pootle mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/translate-pootle
