Change default pm.max_children config sites

Discussion in 'Installation/Configuration' started by Fran17, May 23, 2025.

  1. Fran17

    Fran17 New Member

    Hi,
    I need to change the default pm.max_children value for php-fpm when creating a new site, but I can't find where it is.
    I'm using version 3.3.0p1 of ISPConfig on Debian 12 with Apache.
    Can you tell me where I can make the change?
    Thanks!
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    Change the default of the database column in web_domain table using e.g. phpmyadmin.
     
  3. Fran17

    Fran17 New Member

    but in the web_domain table it appears when you have created it, when there is no site created or you create a new one, where does it get the default value of 10 for pm_max_children?
     
  4. till

    till Super Moderator Staff Member ISPConfig Developer

    Edit the column default using phpmyadmin. The default value is set as default for the database column in mysql.
     
  5. Fran17

    Fran17 New Member

    Sorry, but I don't see what you're telling me.
    In the web_domain table, the pm_max_children column appears, but only when the site is created, and I can change it either from here or from the dashboard.
    upload_2025-5-23_12-3-1.png

    When I create a new site, the default value for that column is 10, but I want the default value to be 40 instead of 10 when a new site is created.
    I've been searching through ISPConfig configuration files and haven't found where to change that value.
    Forgive me if I'm not explaining myself well.
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Please use Google search if you are unfamiliar with phpmyadmin and editing database field defaults with it, there should be plenty of guides and videos on how to use phpmyadmin out there. This is not ISPConfig specific btw.
     
  7. Fran17

    Fran17 New Member

    Okay, I understand you now.
    Sorry. I was looking for a default template. I didn't understand what it was in the web_domain table structure.
     

Share This Page