[SAC] [OSGeo] #357: random server errors

Committees SAC mailing list
1

#357: random server errors
-------------------+--------------------------------------------------------
Reporter: pcav | Owner: sac@lists.osgeo.org
    Type: defect | Status: new
Priority: normal | Component: SAC
Keywords: |
-------------------+--------------------------------------------------------
I get random errors:

Internal Server Error

The server encountered an internal error or misconfiguration and was
unable to complete your request.

Please contact the server administrator, root@localhost and inform them
of the time the error occurred, and anything you might have done that
may have caused the error.

More information about this error may be available in the server error
log.
Apache/2.0.52 (Red Hat) Server at trac.osgeo.org Port 443

and

===
Oops…
Trac detected an internal error:

Traceback (most recent call last):
   File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 387, in
dispatch_request
     dispatcher.dispatch(req)
   File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 191, in
dispatch
     chosen_handler = self._pre_process_request(req, chosen_handler)
   File "/usr/lib/python2.3/site-packages/trac/web/main.py", line 263, in
_pre_process_request
     chosen_handler = f.pre_process_request(req, chosen_handler)
   File "/usr/lib/python2.3/site-packages/trac/versioncontrol/api.py",
line 73, in pre_process_request
     self.get_repository(req.authname) # triggers a sync if applicable
   File "/usr/lib/python2.3/site-packages/trac/versioncontrol/api.py",
line 101, in get_repository
     repos = self._connector.get_repository(rtype, rdir, authname)
   File "/usr/lib/python2.3/site-packages/trac/versioncontrol/svn_fs.py",
line 260, in get_repository
     crepos = CachedRepository(self.env.get_db_cnx(), repos, None,
self.log)
   File "/usr/lib/python2.3/site-packages/trac/versioncontrol/cache.py",
line 34, in __init__
     self.sync()
   File "/usr/lib/python2.3/site-packages/trac/versioncontrol/cache.py",
line 56, in sync
     cursor.execute("SELECT value FROM system WHERE name='repository_dir'")
   File "/usr/lib/python2.3/site-packages/trac/db/util.py", line 51, in
execute
     return self.cursor.execute(sql)
   File "/usr/lib/python2.3/site-packages/sqlite/main.py", line 244, in
execute
     self.rs = self.con.db.execute(SQL)
OperationalError: database is locked

More generally, the server is quite slow. Also, it appears partly
misconfigured, and based on a rather old apache. And very old python.

--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/357&gt;
OSGeo <http://www.osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

2

#357: random server errors
---------------------+------------------------------------------------------
  Reporter: pcav | Owner: sac@lists.osgeo.org
      Type: defect | Status: new
  Priority: normal | Component: SAC
Resolution: | Keywords:
---------------------+------------------------------------------------------
Comment (by neteler):

While I no longer observe outages as reported in this ticket, still trac
is often very slow.
Was the announced SQLite update implemented?

--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/357#comment:1&gt;
OSGeo <http://www.osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

3

#357: random server errors
---------------------+------------------------------------------------------
  Reporter: pcav | Owner: sac@lists.osgeo.org
      Type: defect | Status: new
  Priority: normal | Component: SAC
Resolution: | Keywords:
---------------------+------------------------------------------------------
Comment (by wildintellect):

Internal Server Error showed up again, port 80 and 443
OSSIM, Mapserver, QGIS - OSGEO4w seemed to load but slowly

Time of outage
May 18 23:30 -23:39 PST (California)
UTC Tuesday, May 19, 2009 at 06:30:00

Observed by both Pcav in Italy and me in California.

I'm curious if this is related to trac setup(do we use mod_python),
apache(are we running multi-threaded) setup or high cpu or disk load by
another process. Can someone at least check the log files to see if
anything came up at the noted time in either apache or trac?

--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/357#comment:3&gt;
OSGeo <http://www.osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

4

#357: random server errors
---------------------+------------------------------------------------------
  Reporter: pcav | Owner: sac@lists.osgeo.org
      Type: defect | Status: new
  Priority: major | Component: SAC
Resolution: | Keywords:
---------------------+------------------------------------------------------
Changes (by pcav):

  * priority: normal => major

Comment:

Still getting frequent errors, sometimes the trac is almost unusable,
always very slow.

--
Ticket URL: <http://trac.osgeo.org/osgeo/ticket/357#comment:4&gt;
OSGeo <http://www.osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.

5

#357: random server errors
---------------------+------------------------------------------------------
  Reporter: pcav | Owner: sac@…
      Type: defect | Status: closed
  Priority: major | Component: Systems Admin
Resolution: fixed | Keywords:
---------------------+------------------------------------------------------
Changes (by crschmidt):

  * status: new => closed
  * resolution: => fixed

Comment:

Trac is:
  1. Not on sqlite anymore.
  2. Not on the same server anymore.

--
Ticket URL: <http://newtrac.osgeo.org/osgeo/ticket/357#comment:5&gt;
OSGeo <http://www.osgeo.org/&gt;
OSGeo committee and general foundation issue tracker.