Hmm... I just spotted this:
Exception happened during processing of request from ('207.7.108.189', 58229)
Traceback (most recent call last):
File "/usr/local/lib/python2.4/SocketServer.py", line 463, in
process_request_thread
self.finish_request(request, client_address)
File "/usr/local/lib/python2.4/SocketServer.py", line 254, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/local/lib/python2.4/SocketServer.py", line 521, in __init__
self.handle()
File "/usr/local/lib/python2.4/BaseHTTPServer.py", line 314, in handle
self.handle_one_request()
File "/usr/local/lib/python2.4/BaseHTTPServer.py", line 308, in
handle_one_request
method()
File "/usr/local/bin/tracd", line 227, in do_GET
self.do_trac_req()
File "/usr/local/bin/tracd", line 238, in do_trac_req
trac.core.send_pretty_error(e, self.env, self)
File "/usr/local/lib/python2.4/site-packages/trac/core.py", line
500, in send_pretty_error
req.send_response(500)
File "/usr/local/lib/python2.4/BaseHTTPServer.py", line 364, in send_response
self.wfile.write("%s %d %s\r\n" %
File "/usr/local/lib/python2.4/socket.py", line 256, in write
self.flush()
File "/usr/local/lib/python2.4/socket.py", line 243, in flush
self._sock.sendall(buffer)
error: (32, 'Broken pipe')
----------------------------------------
Assertion failed: (!inMutex), function sqliteOsEnterMutex, file
./src/os.c, line 1751.
diff: write error
I'm upgrading to Trac 0.9.1 right now... we'll see what that does for us.
Kevin
On 12/2/05, Krys Wilken <[EMAIL PROTECTED]> wrote:
>
> Hey,
>
> Trac seems down again (1:34 AM EST).
>
> I get bad gateway errors.
>
> Question: Does Trac have a history of stability problems? I want to
> use it at work, but if its unreliable, then I may have to reconsider.
> Or is this a TextDrive thing?
>
> Thanks,
> Krys
>
--
Kevin Dangoor
Author of the Zesty News RSS newsreader
email: [EMAIL PROTECTED]
company: http://www.BlazingThings.com
blog: http://www.BlueSkyOnMars.com
