Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • I ISPConfig 3
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 550
    • Issues 550
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 41
    • Merge requests 41
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ISPConfig
  • ISPConfig 3
  • Issues
  • #1542

Closed
Open
Created Aug 29, 2011 by pititis@pititis

fastcgi FcgidIdleTimeout

Hi,

Well, this is not a ispconfig related bug BUT we are using fastcgi as default php mode for apache.

The fastcgi FcgidIdleTimeout Directive takes no effect (deafult is set to 300 seg). This issue causes that php-cgi process are always on memory ignoring the idle timeout. High numbers of process = lack of memory = ...

If we set a value manually in the apache directive or in the .php-fcgi-starter file for the site it work and process are close after the idleTimeout.

I found this issue in Ubuntu Server 10.04.3 LTS, libapache2-mod-fcgid 2.3.4-2

Please check it

Assignee
Assign to
Time tracking