Trac totally disabled due to error after debian unstable upgrade.

[mark@…]

Running Debian unstable

Subversion 1.3.1-1
Trac 0.9.4-2
mod_python 3.1.3-3
python 2.3.5-5
python2.3-subversion 1.3.1-1

I get this error in my error.log when going to a trac site.

   1.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend: Traceback (most recent call last):
   2.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/mod_python/apache.py", line 299, in HandlerDispatch\n    result = object(req)
   3.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/web/modpython_frontend.py", line 86, in handler\n    gateway.run(dispatch_request)
   4.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/web/wsgi.py", line 87, in run\n    response = application(self.environ, self._start_response)
   5.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 288, in dispatch_request\n    env = _open_environment(env_path, run_once=environ['wsgi.run_once'])
   6.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 54, in _open_environment\n    env_cache[env_path] = open_environment(env_path)
   7.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/env.py", line 432, in open_environment\n    if env.needs_upgrade():
   8.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/env.py", line 291, in needs_upgrade\n    if participant.environment_needs_upgrade(db):
   9.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/env.py", line 344, in environment_needs_upgrade\n    dbver = self.env.get_version(db)
  10.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/env.py", line 204, in get_version\n    cursor.execute("SELECT value FROM system WHERE name='database_version'")
  11.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/db/util.py", line 48, in execute\n    return self.cursor.execute(sql)
  12.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/db/sqlite_backend.py", line 39, in execute\n    args or [])
  13.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend:   File "/usr/lib/python2.3/site-packages/trac/db/sqlite_backend.py", line 31, in _rollback_on_error\n    return function(self, *args, **kwargs)
  14.
      [Thu Apr 06 20:23:29 2006] [error] [client 192.168.0.2] PythonHandler trac.web.modpython_frontend: Warning: You can only execute one statement at a time. 

"You can only execute one statement at a time" is also given on any attempt at using trac-admin. No matter what I do with it it always says that.

[Christian Boos]

Well, it also happened to me this afternoon, after I upgraded to pysqlite-2.2.0 … It's typically an error which happens when the pysqlite package you're using is loading a sqlite3.so library having a different version than the one against which pysqlite was built.

More specifically in my case, I did set the LD_LIBRARY_PATH to point to the sqlite-3.3.4 sqlite3.so library, but did a mistake in setting the PYTHONPATH: instead of my brand new pysqlite-2.2.0, an "old" pysqlite-2.1.3 egg (compiled against sqlite-3.2.8) was found…

Please don't forget to close this as worksforme once you solved the issue.

[Emmanuel Blot]

See also #2879.