Project

General

Profile

Actions

Bug #535

closed

Disabled fastcgi backends never re-enabled

Added by Anonymous about 15 years ago. Updated over 14 years ago.

Status:
Fixed
Priority:
High
Category:
mod_fastcgi
Target version:
-
ASK QUESTIONS IN Forums:

Description

When a fastcgi backend is disabled, it is never re-enabled; have confirmed with 20 minutes in disabled status.

Workaround has been to restart lighttpd when backends show up as disabled.

Fastcgi internal statistics:


fastcgi.active-requests: 1
fastcgi.backend.localhost.0.connected: 69697
fastcgi.backend.localhost.0.died: 0
fastcgi.backend.localhost.0.disabled: 1
fastcgi.backend.localhost.0.load: -1
fastcgi.backend.localhost.0.overloaded: 1
fastcgi.backend.localhost.1.connected: 69550
fastcgi.backend.localhost.1.died: 0
fastcgi.backend.localhost.1.disabled: 1
fastcgi.backend.localhost.1.load: 0
fastcgi.backend.localhost.1.overloaded: 1
fastcgi.requests: 139247

Log snippet:


2006-02-21 02:10:40: (mod_fastcgi.c.2866) backend is overloaded, we disable it for a 2 seconds and send the request to another backend instead: reconnects: 0 load: 279 /tmp/php-fastcgi.socket
2006-02-21 02:10:40: (mod_fastcgi.c.2866) backend is overloaded, we disable it for a 2 seconds and send the request to another backend instead: reconnects: 1 load: 279 /tmp/php-fastcgi.socket
2006-02-21 02:10:40: (mod_fastcgi.c.3523) no fcgi-handler found for: /forum/forum.php
...
2006-02-21 02:10:48: (mod_fastcgi.c.3523) no fcgi-handler found for: /forum/forum.php
...

continues indefinitely.

-- moorman

Actions #1

Updated by jan about 15 years ago

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

fixed in r1031

Actions

Also available in: Atom