Re: fcgi - lighttpd 1.2.7 problems as well

On Sat, Sep 04, 2004 at 04:18:38PM -0500, Paul Mackiewicz wrote:
> it WAS/IS a socket...however, I must not understand something about unix
> sockets, or the spawn-php.sh script?
> 
> When i run the spawn-php.sh script or just run the spawn-fcgi binary
> directly, stating that i want the socket path to be "/tmp/socket.abc",
> it creates the socket as "/tmp/socket.ab" truncating the last character.

I'll upload a new spawn-fcgi version which should fix it. I hope that it
is the SUN_LEN() issue and nothing else.

>  Can someone tell me why this would be?
> 
> On lighttpd 1.2.5, in my config file I'd still use "socket" => 
> "/tmp/socket.abc"
>  and everything would be fine, until i got to running the large POST,
> at which point I'd get a 503 and...
> 
> 2004-09-04 15:11:08: (fcgi.c.1247) write failed: Broken pipe -1
> 2004-09-04 15:11:08: (fcgi.c.1289) fcgi-server disabled:  0 15
> 
> ...in the error log.
> 
> on lighttpd 1.2.7 - I can't process any php through fcgi through Unix
> sockets, and I get a 503 with...
> 
> 2004-09-04 15:15:28: (fcgi.c.612) connect failed: 10 No such file or
> directory 2
> 2004-09-04 15:15:28: (fcgi.c.1301) fcgi-server disabled:  0 -1
> 
> ...in the error log, as it would appear that it doesn't find the
> /tmp/socket.abc.  So when running 1.2.7 I'd have to change my config
> file to "tmp/socket.ab" in order to process any PHP.  Still I get the
> 503 on large POST with:
> 
> 2004-09-04 15:32:11: (fcgi.c.1259) write failed: Broken pipe -1
> 2004-09-04 15:32:11: (fcgi.c.1301) fcgi-server disabled:  0 23
> 
> in the error log.
> 
> Did the way lighttpd 'parsed' the config file change between 1.2.5 and
> 1.2.7, since 1.2.5 could still process most php through that socket?

In lighttpd 1.2.6 the usage of the SUN_LEN() macro was introduced but
spawn-fcgi wasn't updated yet. In other words: in lighttpd 1.2.5
spawn-fcgi and lighttpd both did the calculation of the path length
wrong on your platform. 

lighttpd 1.2.6 fixed it for lighttpd, but spawn-fcgi wasn't updated yet.
 
> BTW I tried runnng fastcgi through TCP/IP, on lighttpd 1.2.7 and I 
> can finally do a large POST! :)

    Jan
  
-- 
Jan Kneschke                                     http://jan.kneschke.de/
Perhaps you want to say 'thank you, jan':    http://jk.123.org/wishlist/