ghc's trac is wedged

[Simon Marlow]

Gregory Wright wrote:

> This morning (13 March 2008) the ghc trac wedged reporting
> 
> Trac detected an internal error:
> 
> with the python traceback
> 
> Traceback (most recent call last):
>   File "/var/lib/python-support/python2.4/trac/web/main.py", line 387, 
> in dispatch_request
>     dispatcher.dispatch(req)
>   File "/var/lib/python-support/python2.4/trac/web/main.py", line 237, 
> in dispatch
>     resp = chosen_handler.process_request(req)
>   File "/var/lib/python-support/python2.4/trac/web/auth.py", line 100, 
> in process_request
>     self._do_login(req)
>   File "/var/lib/python-support/python2.4/trac/web/auth.py", line 139, 
> in _do_login
>     "VALUES (%s, %s, %s, %s)", (cookie, remote_user,
>   File "/var/lib/python-support/python2.4/trac/db/util.py", line 50, in 
> execute
>     return self.cursor.execute(sql_escape_percent(sql), args)
>   File "/usr/lib/python2.4/site-packages/sqlite/main.py", line 237, in 
> execute
>     self.con._begin()
>   File "/usr/lib/python2.4/site-packages/sqlite/main.py", line 503, in 
> _begin
>     self.db.execute("BEGIN")
> OperationalError: database is locked
> 
> 
> Please let me know if there is a more direct way to report failures such 
> as this one,
> instead of posting to the list.

This happens from time to time for me too, usually it goes away with a 
retry.

Cheers,
	Simon