Bug #1157: Lighttpd crashes when I restart all my backends, and makes monkey noises (literally!) - Lighttpd - lighty labs

Actions

Copy link

Bug #1157

closed

Lighttpd crashes when I restart all my backends, and makes monkey noises (literally!)

Added by Anonymous over 17 years ago. Updated over 8 years ago.

Status:

Obsolete

Priority:

Normal

Category:

mod_proxy_core

Target version:

1.5.0

ASK QUESTIONS IN Forums:

Description

Yep, that's right. Monkey noises.

When all of my backends are restarted, lighttpd usually crashes immediately, and I get this message in my lighty.error.log.

"Ooh, Ooh, Ooh. Something is not good ... going down."

Some of the log leading up that it is below:

mod_proxy_core.c.2307: (trace) connecting backends timed out, retry limit reached: 28
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8006 refused us, disabling for 2 sec
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8001 refused us, disabling for 2 sec
mod_proxy_core.c.2301: (trace) backlog: all addresses are down, putting /xml/connect (7) into the backlog, retry = 29
mod_proxy_core.c.2307: (trace) connecting backends timed out, retry limit reached: 29
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8003 refused us, disabling for 2 sec
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8005 refused us, disabling for 2 sec
mod_proxy_core.c.2301: (trace) backlog: all addresses are down, putting /xml/connect (7) into the backlog, retry = 30
mod_proxy_core.c.2307: (trace) connecting backends timed out, retry limit reached: 30
log.c.148: (trace) server started
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8002 refused us, disabling for 2 sec
mod_proxy_core.c.2301: (trace) backlog: all addresses are down, putting / (7) into the backlog, retry = 1
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8006 refused us, disabling for 2 sec
mod_proxy_core.c.2301: (trace) backlog: all addresses are down, putting / (7) into the backlog, retry = 2
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8004 refused us, disabling for 2 sec
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8002 refused us, disabling for 2 sec
mod_proxy_core.c.2301: (trace) backlog: all addresses are down, putting / (7) into the backlog, retry = 3
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8001 refused us, disabling for 2 sec
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8006 refused us, disabling for 2 sec
mod_proxy_core.c.2301: (trace) backlog: all addresses are down, putting / (7) into the backlog, retry = 4
mod_proxy_core.c.1460: (trace) address 127.0.0.1:8005 refused us, disabling for 2 sec
mod_proxy_core.c.2330: (trace) connecting backends timed out, retry limit reached: 5
fdevent_poll.c.25: (error) (fdevent-poll-del) out of range 11045 6

fdevent_poll.c.26: (error) Ooh, Ooh, Ooh. Something is not good ... going down

-- pete

Actions

Copy link

Updated by Anonymous over 17 years ago

Same problem over here. Additionally, Lighttpd crashes 30-40 times a day. It seems like this depends on the load. I am using 6 Mongrel backends and the Lighttpd snapshot r1857.

error.log before the crash (URL replaced):


..
mod_proxy_core.c.1491: (trace) address 127.0.0.1:11303 refused us, disabling for 2 sec
mod_proxy_core.c.2332: (trace) backlog: all addresses are down, putting /bla/blablabla (18) into the backlog, retry = 2
fdevent_poll.c.75: (crashing) (fdevent-poll-add) (0, 4)

Please let me know how I can help solve this nasty bug!

-- maze

Actions

Copy link