Edgewall Software
Modify

Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#10046 closed defect (wontfix)

[IOError: Client read error (Timeout?)] Only editing default reporters #1 and #2. The reports #3-#8 are ok.

Reported by: anonymous Owned by:
Priority: high Milestone:
Component: general Version: 0.12.2
Severity: major Keywords:
Cc: klaux1@… Branch:
Release Notes:
API Changes:
Internal Changes:

Description

Only editing default reports #1 and #2. The environment is new (initenv) and database is sqlite. Using database PostgreSQL 8.4 same error.

  • IOError: Client read error (Timeout?)
    2011-02-25 10:05:37,052 Trac[main] ERROR: Internal Server Error: 
    Traceback (most recent call last):
      File "/usr/local/lib/python2.6/dist-packages/Trac-0.12.2-py2.6.egg/trac/web/main.py", line 511, in _dispatch_request
        dispatcher.dispatch(req)
      File "/usr/local/lib/python2.6/dist-packages/Trac-0.12.2-py2.6.egg/trac/web/main.py", line 193, in dispatch
        if handler.match_request(req):
      File "/usr/local/lib/python2.6/dist-packages/Trac-0.12.2-py2.6.egg/trac/ticket/report.py", line 88, in match_request
        req.args['id'] = match.group(1)
      File "/usr/local/lib/python2.6/dist-packages/Trac-0.12.2-py2.6.egg/trac/web/api.py", line 216, in __getattr__
        value = self.callbacks[name](self)
      File "/usr/local/lib/python2.6/dist-packages/Trac-0.12.2-py2.6.egg/trac/web/api.py", line 199, in <lambda>
        'args': lambda req: arg_list_to_args(req.arg_list),
      File "/usr/local/lib/python2.6/dist-packages/Trac-0.12.2-py2.6.egg/trac/web/api.py", line 216, in __getattr__
        value = self.callbacks[name](self)
      File "/usr/local/lib/python2.6/dist-packages/Trac-0.12.2-py2.6.egg/trac/web/api.py", line 564, in _parse_arg_list
        fs = cgi.FieldStorage(fp, environ=self.environ, keep_blank_values=True)
      File "/usr/lib/python2.6/cgi.py", line 506, in __init__
        self.read_urlencoded()
      File "/usr/lib/python2.6/cgi.py", line 607, in read_urlencoded
        qs = self.fp.read(self.length)
      File "/usr/local/lib/python2.6/dist-packages/Trac-0.12.2-py2.6.egg/trac/web/modpython_frontend.py", line 47, in read
        return self.req.read(size)
    IOError: Client read error (Timeout?)
    
  • report #1 (edit produce ERROR)
    SELECT p.value AS __color__,
       id AS ticket, summary, component, version, milestone, t.type AS type, 
       owner, status,
       time AS created,
       changetime AS _changetime, description AS _description,
       reporter AS _reporter
      FROM ticket t
      LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority'
      WHERE status <> 'closed'
      ORDER BY CAST(p.value AS integer), milestone, t.type, time
    
  • report #2 (edit produce ERROR)
    SELECT p.value AS __color__,
       version AS __group__,
       id AS ticket, summary, component, version, t.type AS type, 
       owner, status,
       time AS created,
       changetime AS _changetime, description AS _description,
       reporter AS _reporter
      FROM ticket t
      LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority'
      WHERE status <> 'closed'
      ORDER BY (version IS NULL),version, CAST(p.value AS integer), t.type, time
    

report #3 and others …#8 (edit is ok)

SELECT p.value AS __color__,
   'Milestone '||milestone AS __group__,
   id AS ticket, summary, component, version, t.type AS type, 
   owner, status,
   time AS created,
   changetime AS _changetime, description AS _description,
   reporter AS _reporter
  FROM ticket t
  LEFT JOIN enum p ON p.name = t.priority AND p.type = 'priority'
  WHERE status <> 'closed' 
  ORDER BY (milestone IS NULL),milestone, CAST(p.value AS integer), t.type, time
  • My system
    trac@XXXX:~$ uname -a
    Linux XXXX 2.6.32-5-amd64 #1 SMP Wed Jan 12 03:40:32 UTC 2011 x86_64 GNU/Linux
    
    
    System Information
    Trac 	        0.12.2
    Trac 	        0.12.2
    Babel 	        0.9.5
    Genshi 	        0.6
    mod_python 	3.3.1
    pysqlite 	2.4.1
    Python 	        2.6.6 (r266:84292, Dec 26 2010, 22:48:11) [GCC 4.4.5]
    Python 	        2.6.6 (r266:84292, Dec 26 2010, 22:48:11) [GCC 4.4.5]
    setuptools 	0.6
    setuptools 	0.6
    SQLite 	        3.7.3
    Subversion 	1.6.12 (r955767)
    jQuery:	        1.4.2
    
    Installed Plugins
    TracCAS 	2.0.1 	/usr/local/lib/python2.6/dist-packages/TracCAS-2.0.1-py2.6.egg
    

Attachments (0)

Change History (7)

comment:1 by anonymous, 14 years ago

Summary: Only editing default reporters !#1 and !#2. The reports !#3-!#8 are ok.[IOError: Client read error (Timeout?)] Only editing default reporters #1 and #2. The reports #3-#8 are ok.

comment:2 by Remy Blank, 14 years ago

Resolution: wontfix
Status: newclosed

You shouldn't be using the CGI backend. Go for mod_wsgi or FCGI if you can, or mod_python or tracd if you must.

What seems to happen here is that environment startup time plus the time required to execute reports {1} or {2} is longer than the browser timeout.

This is an InstallationIssue.

comment:3 by Christian Boos, 14 years ago

Well, it seems he was using mod_python (3.3.1). Furthermore, the read error happens very early (when retrieving the report id).

So I have no idea what's going on here, but definitely not a timeout while waiting for the report execution ;-)

Last edited 14 years ago by Christian Boos (previous) (diff)

comment:4 by Remy Blank, 14 years ago

Oh, right, I was mislead by the cgi.py in the traceback, but it comes from Python, not Trac. Apologies for the wrong analysis.

Probably the only good advice from comment:2 is to try mod_wsgi :)

in reply to:  4 ; comment:5 by klaux1@…, 14 years ago

Replying to rblank:

Oh, right, I was mislead by the cgi.py in the traceback, but it comes from Python, not Trac. Apologies for the wrong analysis.

Probably the only good advice from comment:2 is to try mod_wsgi :)

Dear, just for the record!

The problem was not in Trac, in Python or in any plugin. It was an IPS detects a possible vulnerability for SQLInjection in the first two reports.

Thx

— KlauX

in reply to:  5 ; comment:6 by Remy Blank, 14 years ago

Replying to klaux1@…:

It was an IPS detects a possible vulnerability for SQLInjection in the first two reports.

Interesting. Can you give us details about the vulnerability? If it's not a false positive, we would be very interested in fixing it.

in reply to:  6 comment:7 by anonymous, 14 years ago

Replying to rblank:

Replying to klaux1@…:

It was an IPS detects a possible vulnerability for SQLInjection in the first two reports.

Interesting. Can you give us details about the vulnerability? If it's not a false positive, we would be very interested in fixing it.

It is a false positive of the IPS tool. The difference of the standard reports of the Trac #1-#2 and #3-#8 is none. The rule that gave an alarm can only be viewed by the support of the black box (non free software). I requested to include an exception on the server until the staff to solve the problem.

Thx

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The ticket will remain with no owner.
The resolution will be deleted. Next status will be 'reopened'.
to The owner will be changed from (none) to the specified user.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.