Modify ↓
      
Opened 16 years ago
Closed 16 years ago
#9173 closed defect (duplicate)
Internal Server Error introduced in 0.11.7
| Reported by: | anonymous | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | general | Version: | 0.11-stable | 
| Severity: | normal | Keywords: | |
| Cc: | Branch: | ||
| Release Notes: | |||
| API Changes: | |||
| Internal Changes: | |||
Description
After upgrading to 0.11.7 I am seeing internal server errors in the log. This is running on CentOS 5.4 with python 2.4. The database backend is postgresql 8.3 with bindings psycopg2-2.0.9. The version system is svn 1.6.9.
It's not clear if this is having any real effect on the system as it still seems to work, but I've noticed slower performance recently (perhaps unrelated to this issue).
 Trac[main] ERROR: Internal Server Error:
Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/Trac-0.11.7-py2.4.egg/trac/web/main.py", line 450, in _dispatch_request
    dispatcher.dispatch(req)
  File "/usr/lib/python2.4/site-packages/Trac-0.11.7-py2.4.egg/trac/web/main.py", line 230, in dispatch
    req.send(output, content_type or 'text/html')
  File "/usr/lib/python2.4/site-packages/Trac-0.11.7-py2.4.egg/trac/web/api.py", line 358, in send
    self.write(content)
  File "/usr/lib/python2.4/site-packages/Trac-0.11.7-py2.4.egg/trac/web/api.py", line 464, in write
    except (IOError, socket.error), e:
NameError: global name 'socket' is not defined
      Attachments (0)
  Note:
 See   TracTickets
 for help on using tickets.
    


  
Yep, it's #9103. I don't think this can affect performance.