Project

General

Profile

Actions
Copy link

Bug #907

closed

mod_proxy_core fails if proxy-core.balancer is not set, but no warnings

Added by Anonymous about 18 years ago. Updated over 17 years ago.

Status:
Fixed
Priority:
Normal
Category:
core
Target version:
1.5.0
ASK QUESTIONS IN Forums:

Description

I was trying to get mod_proxy_core to work with the fastcgi magnet.c tool and kept running into:


src/mod_proxy_core.c.1288: (trace) backlog: all backends are down, putting /test.lua (4) into backlog

and such...

The revision is r1457 of /trunk.

However... after a stroke of genius, I put proxy-core.balancer = "round-robin" in the configuration file and it worked. There was no warning about the configurations, so I assumed it was correct.

Proposed resolutions:
  • A warning/error be issued when the balancer is not set.
  • A default balancer be set... perhaps based upon some ruleset such as protocol, # of backends/etc

-- Thomas Harning Jr. <harning

Actions
Copy link
 #1

Updated by Anonymous about 18 years ago

Example non-working config:


server.port = 8080
server.modules = ( "mod_proxy_core" )

$HTTP["url"] =~ "\.lua$" {
    proxy-core.protocol = "fastcgi" 
    proxy-core.backends = ("127.0.0.1:9000")
}

Example working config:


server.port = 8080
server.modules = ( "mod_proxy_core" )

$HTTP["url"] =~ "\.lua$" {
    proxy-core.balancer = "round-robin" 
    proxy-core.protocol = "fastcgi" 
    proxy-core.backends = ("127.0.0.1:9000")
}

-- Thomas Harning Jr. <harning

Actions
Copy link
 #2

Updated by jakabosky almost 18 years ago

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

fixed in r1520 lighttpd will not start if proxy-core.balancer is not set and proxy-core.protocol is set.

Actions
Copy link

Also available in: Atom