tom | 9 Nov 14:04 2007
Picon

a debian question

hey guys,

I have a debian box with lighttpd, php4-cgi and php4-sqlite installed,
and everything works as expected.  When I tried to upgrade to php5
nothing worked.  What's the difference?  Do any debian folks have any
suggestions?

Thanks.

Oliver Peter | 9 Nov 18:30 2007
Picon

Re: a debian question

Hi Tom,

On Fri, Nov 09, 2007 at 07:04:37AM -0600, tom wrote:
> hey guys,
> 
> I have a debian box with lighttpd, php4-cgi and php4-sqlite installed,
> and everything works as expected.  When I tried to upgrade to php5
> nothing worked.  What's the difference?  Do any debian folks have any
> suggestions?

Could you please provide some error messages you receive after
you have updated to php5?

Bye
Ollie

--

-- 
Oliver PETER, eMail: hoschi <at> mouhaha.de, ICQ# 113969174
"Worker bees can leave.  Even drones can fly away.
                         The Queen is their slave."
S. Lazaro | 11 Nov 09:37 2007
Picon

About Addtype/Addicon

Hi to all,

I want to set dir listing enabled with icons similar to apache Addicon 
and AddType. I not found any from lighttpd doc.. I think that only can 
set with a external php file for example, adding icon whe get the mime 
type from file. ¿How it's the best/secure/fast method?.

Thanks to all!

Oliver Peter | 11 Nov 19:42 2007
Picon

Re: a debian question

Please make sure that you also send your reply back to the list
lighttpd <at> lists.kneschke.de.

On Fri, Nov 09, 2007 at 02:42:58PM -0600, tom wrote:
> is there a "debug" switch I can flip somewhere?  when I try php5,
> "anypage.php" just shows a blank white page.  Same thing with
> "phpinfo.php"  That makes me think fastcgi is just not running.  Does
> that sound right?

What does you errorlog say?

Look in the file which you have defined in lighttpd.conf:

## where to send error-messages to
server.errorlog             = "/var/log/lighttpd.error.log"

> Other than that, what error messages would you like? Where exactly
> would error messages concerning php and lighttpd be written?  Right at
> this moment checking syslog on the machine in question would be very
> slow.

See above.

--

-- 
Oliver PETER, eMail: hoschi <at> mouhaha.de, ICQ# 113969174
"Worker bees can leave.  Even drones can fly away.
                         The Queen is their slave."
scrawler | 13 Nov 23:23 2007
Picon

Re: a debian question

On Sun, 11 Nov 2007 19:42:46 +0100
Oliver Peter <hoschi <at> mouhaha.de> wrote:

> Please make sure that you also send your reply back to the list
> lighttpd <at> lists.kneschke.de.
> 

Sorry, I was using gmail's web interface and didn't check the right
boxes.

The error log basically told me fastcgi wasn't running. I got it
working, however, by removing and purging all php5-related packages and
reinstalling them.  I tweeked php.ini and now everything works.

Thank you very much for your patience.

--

-- 

signature in pain: "ouch!"
-tom

Rolando Abarca | 14 Nov 19:36 2007
Picon

lighty 1.5.0 fastcgi question

I was happy using lighty 1.4 on my vps, but suddenly the request to  
create a proxy to a subversion repository appeared and so, we had to  
install lighty 1.5, because of the proxy-core.rewrite-request option  
(the svn repository required setting the appropiate Host header).
Now, we have the following config for fastcgi:

$HTTP["host"] == "my.domain.com" {
         url.rewrite-once = ("^$" => "index.html")
         proxy-core.balancer = "round-robin"
         proxy-core.allow-x-sendfile = "enable"
         proxy-core.protocol = "fastcgi"
         proxy-core.backends = ( "unix:/tmp/my_domain_com.sock" )
         proxy-core.max-pool-size = 16
}

this works, but it's sending all requests to the fastcgi process. What  
I would like to do, is to send only those requests of files that do  
not exists to the fastcgi process.
What's the 1.5-way to do this? (or is there a way to add the correct  
Host header in the proxy forward of light 1.4?)

regards,
--

-- 
Rolando Abarca
Phone: +56-9 97851962

Mathieu Lecarme | 20 Nov 14:07 2007
Picon

JkEnvVar on Lighty

mod_jk use a strange instruction in mod_jk : JkEnvVar
http://tomcat.apache.org/connectors-doc-archive/jk2/jk/printer/aphowto.html

With that you can set a value in the web server and use it in tomcat
with javax.servlet.ServletRequest.getAttribute(String name)
How can I do that with lighty?

M.

Robert Locke | 21 Nov 04:03 2007
Picon

all's quiet on the western front...

Hello all,

This list has been so quiet for the last several months.  Is that 
because lighty just works so flawlessly that there's nothing to report? 
  No news is good news, I suppose. =)

Best wishes from the Philippines,

Rob

Florian Lohoff | 22 Nov 11:37 2007

inotify stat cache


Hi,
i have found some inotify stat cache via google as i stumbled upon
the FAM 1024 watches/fds limit which makes the whole FAM issue
obsolete for me. 

I checked out the svn trunk and discovered that the inotify
expiry has mostly been removed and remainders beeing disabled.

Is there a reason for this or was it simply removed because of bugs,
incomplete implementation or lack of interest?

Flo
--

-- 
Florian Lohoff                  flo <at> rfc822.org             +49-171-2280134
	Those who would give up a little freedom to get a little 
          security shall soon have neither - Benjamin Franklin
Christian Kujau | 26 Nov 02:58 2007
Picon

mod_proxy_core not creating sockets

Hi,

I'm using lighttpd-1.4.18 with mod_fastcgi.so for serving .php documents.
Every now and then I try to use the latests -svn build to do the same, but 
somehow I fail to do so: lighttpd starts up, but when asked to serve a 
.php page (just calling phpinfo()), the errorlog shows:

mod_proxy_core.c.2324: (trace) selected backend: unix:/tmp/php-fastcgi.sock, state: 1
mod_proxy_core.c.1406: (trace) proxy_state_engine: state=0
mod_proxy_core.c.940: (error) connect(unix:/tmp/php-fastcgi.sock) failed: No such file or
directory (2)
mod_proxy_core.c.1455: (trace) connecting to address unix:/tmp/php-fastcgi.sock (0x808aca0)
failed, disabling for 60 sec
mod_proxy_core.c.2416: (trace) write failed, restarting request
mod_proxy_core.c.2324: (trace) selected backend: unix:/tmp/php-fastcgi.sock, state: 1
mod_proxy_core.c.2336: (trace) backlog: all addresses are down, putting /phpinfo.php (6) into the
backlog, retry = 1

And indeed: the sockets that mod_proxy_core should connect to do NOT 
exist. The lighttpd.conf for lighttpd-1.5 is the *same* as the one for 1.4
except of course the changes needed for mod_proxy_backend_fastcgi to work:
http://nerdbynature.de/bits/lighttpd-svn/2026/

When starting lighttpd-1.4, the socket files are created almost 
instantly, with 1.5, no sockets are created. I tried to take the configuration 
examples from the website[0] as well as a .conf from #922, but to no 
avail. I still suspect a configuration issue on my side, but I dunno where 
to look.

Thanks for ideas,
(Continue reading)


Gmane