Edgewall Software
Modify

Ticket #5907 (closed defect: wontfix)

Opened 4 years ago

Last modified 3 years ago

first fcgi request fails under lighttpd

Reported by: kevin@… Owned by:
Priority: normal Milestone:
Component: web frontend Version: 0.10.3.1
Severity: normal Keywords: fcgi lighttpd needinfo
Cc:
Release Notes:
API Changes:

Description

lighttpd-1.4.13, trac 0.10.3.1

I have lighttpd starting trac with a configuration like this:

    fastcgi.server = ("/trac" =>
        ("trac" =>
            ("socket" => "/tmp/trac.socket",
             "bin-path" => "/usr/share/trac/cgi-bin/trac.fcgi",
             "check-local" => "disable",
             "bin-environment" =>
                 ("TRAC_ENV" => "/home/trac/trac",
                  "PYTHON_EGG_CACHE" => "/home/trac/egg-cache")
            )))

The first time I try to load trac, lighttpd returns 500 and something like this in error.log:

2007-08-21 17:38:33: (mod_fastcgi.c.2879) got proc: pid: 5748 socket: unix:/tmp/trac.socket-3 load: 1
2007-08-21 17:38:34: (mod_fastcgi.c.2409) unexpected end-of-file (perhaps the fastcgi process died): pid: 5748 socket: unix:/tmp/trac.socket-3
2007-08-21 17:38:34: (mod_fastcgi.c.3194) response not received, request sent: 1229 on socket: unix:/tmp/trac.socket-3 for /trac , closing connection
2007-08-21 17:38:34: (mod_fastcgi.c.1490) released proc: pid: 5748 socket: unix:/tmp/trac.socket-3 load: 0

cranking up the debug level in web._fcgi gave me this, but it doesn't appear to look any different for failing vs succeeding requests:

Aug 21 17:38:34 fcgi: read: fd = 2, type = 1, requestId = 1, contentLength = 8
Aug 21 17:38:34 fcgi: read: fd = 2, type = 4, requestId = 1, contentLength = 1189
Aug 21 17:38:34 fcgi: read: fd = 2, type = 4, requestId = 1, contentLength = 0
Aug 21 17:38:34 fcgi: write: fd = 2, type = 6, requestId = 1, contentLength = 151
Aug 21 17:38:34 fcgi: write: fd = 2, type = 6, requestId = 1, contentLength = 4057
Aug 21 17:38:34 fcgi: protocolStatus = 0, appStatus = 0
Aug 21 17:38:34 fcgi: write: fd = 2, type = 6, requestId = 1, contentLength = 0
Aug 21 17:38:34 fcgi: write: fd = 2, type = 3, requestId = 1, contentLength = 8
Aug 21 17:38:34 fcgi: end_request: flags = 0

trac.log doesn't seem to report any errors, saying just

2007-08-21 17:38:34,519 Trac[loader] DEBUG: Loading egg plugin openidauth.auth from /usr/lib/python2.5/site-packages/OpenIDAuth-0.1dev-py2.5.egg
2007-08-21 17:38:34,627 Trac[loader] DEBUG: Loading egg plugin openidauth.auth from /home/trac/trac/plugins/OpenIDAuth-0.1dev-py2.5.egg

The error seems to happen once for each trac.fcgi spawned. Subsequent requests to that fcgi server work fine.

Is there anywhere I can get more logging to find out why lighttpd got an unexpected EoF?

Attachments

Change History

comment:1 Changed 4 years ago by anonymous

also reported as http://trac.lighttpd.net/trac/ticket/1311 , as I really can't tell which of the two is at fault.

comment:2 Changed 4 years ago by thatch

  • Component changed from general to web frontend
  • Keywords needinfo added
  • Owner jonas deleted
  • Version set to 0.10.3.1

Does the problem persist if you remove the openidauth plugin? I notice it's loading from two different locations.

comment:3 Changed 3 years ago by cboos

  • Resolution set to wontfix
  • Status changed from new to closed

No feedback given, closing.

Also, seems that lighttpd is switching to RedMine and their old Trac ticket 1311 redirects to a redmine server which is not yet up...

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
The resolution will be deleted. Next status will be 'reopened'
to The owner will be changed from (none). Next status will be 'closed'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.