Project

General

Profile

Actions

Bug #104

closed

OSX (10.3.9) + fastcgi + rails socket connection failures

Added by Anonymous over 16 years ago. Updated about 13 years ago.

Status:
Invalid
Priority:
Normal
Category:
core
Target version:
-
ASK QUESTIONS IN Forums:

Description

Alright so let's get the version numbers out of the way: OS X 10.3.9, lighttpd-1.3.13 (ssl), ruby 1.8.2, ruby-fcgi 0.8.6.

Now after following a number of different tutorials to use Ruby/Rails dispatcher.fcgi with lighttpd, I kept seeing the following in the logs (with fastcgi debug turned on):


2005-04-21 16:34:18: (mod_fastcgi.c.1466) connect failed: 10 Connection refused 61 0 /tmp/weird_dev.socket-3  
....
2005-04-21 16:43:59: (mod_fastcgi.c.1921) unexpected end-of-file (perhaps the fastcgi process died): pid: 11258 fcgi-fd: 10 remote-fd: 8 
2005-04-21 16:43:59: (mod_fastcgi.c.2743) child exited, pid: 11258 status: 0 
2005-04-21 16:43:59: (mod_fastcgi.c.2782) response not sent, request sent: 841 connection-fd: 8 fcgi-fd: 10

So after going line-by-line commenting things out I narrowed it down to:

server.username = "www"

Where www is just a non-root user

server.groupname doesn't seem to hurt being enabled and non-root.

Again, so long as I run lighttpd as root, things work just fine so I'm assuming this isn't a config issue but rather some kind of setuid problem with lighttpd and OS X. (I have also tested running apache with cgi and fastcgi on this same machine, so I'm quite certain there are no permission problems with my docroot or anything).

-- michael

Actions #1

Updated by stbuehler about 13 years ago

  • Status changed from New to Fixed
  • Resolution set to invalid

Looks like a permission problem with the socket.

Actions #2

Updated by stbuehler about 13 years ago

  • Status changed from Fixed to Invalid
Actions

Also available in: Atom