MaxClients set to appropriate level, but ISPconfig is crashing from it (I think)

Discussion in 'Server Operation' started by bpmee, Jan 10, 2007.

  1. bpmee

    bpmee Member

    Hi All,

    I running ISPConfig and have set my maxclients setting in httpd.conf to an appropriate level: appropriate level meaning my total RAM divided by 2-3 Mbs for each client.

    In my case this works out to 2000.

    Lately ISPconfig has been crashing - and when I checked the error log I saw notes that "MAX Clients has been reached" and the server goes down. :(

    Is there any way of turning off the function that shuts the server down? Or, a way to set up Max Clients so that the server can accomodate the requests?

    Maybe something with Swap? :confused:

    Thanks
     
  2. Ben

    Ben Active Member Moderator

    So where did you change the settings? Cause the maxClientSetting on the "webserving" apache should not affect the apache used by ISPConfig for Administration.
     
  3. edge

    edge Active Member Moderator

    Please note (as Ben mentioned) the ISPconfig Apache server (port 81) is not the same as the Apache server that is showing your webpages (port 80), so make sure you are editing the correct httpd.conf!

    Also. The maxclients problem should not crash your Apache server. It will only slow pages down (a lot!)

    Are you sure Apache is crashing?
     
  4. bpmee

    bpmee Member

    Thanks for the reply -

    Hi Guys,

    Thanks for your replies!

    I'm editting the Apache Conf in /etc/httpd/httpd.conf (I think that's close to the correct path).

    I edited the section where the "max clients" section is...

    Is there another httpd.conf that runs with ISPconfig that I can adjust? :confused:

    This would be a great help since ISPconfig "webserver" is always crashing, almost hourly. My sites become inaccessible!
     
  5. edge

    edge Active Member Moderator

    The ISPconfig "webserver" does not serve your webpages!
    it's ONLY for the ISPconfig control panel, maybe webmail and maybe awstats! So NO NEED to change anything in it!

    What OS are you using, and what version of Apache are you using?
     
    Last edited: Jan 11, 2007
  6. bpmee

    bpmee Member

    Ok,

    but why does my server continue to crash? Here is a copy of my "top" output:

    Code:
    top - 08:14:40 up 9 min,  1 user,  load average: 0.57, 0.65, 0.35
    Tasks: 916 total,   1 running, 914 sleeping,   0 stopped,   1 zombie
    Cpu(s):  8.4% us,  1.8% sy,  0.0% ni, 83.3% id,  5.7% wa,  0.2% hi,  0.7% si,
    Mem:   5974676k total,  2009752k used,  3964924k free,    36968k buffers
    Swap:  2031608k total,        0k used,  2031608k free,   235924k cached
    
      PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
     2455 apache    15   0 33072  14m 4384 S    3  0.2   0:03.67 httpd
     2293 apache    16   0 33036  14m 4392 S    3  0.2   0:03.34 httpd
     2292 apache    15   0 32988  14m 4396 S    2  0.2   0:03.30 httpd
     2972 apache    15   0 32296  13m 4244 S    1  0.2   0:00.11 httpd
     3636 root      15   0  2776 1572  780 R    1  0.0   0:02.23 top
     2850 apache    15   0 32208  13m 4244 S    1  0.2   0:00.06 httpd
     3027 apache    15   0 32448  13m 4272 S    1  0.2   0:00.11 httpd
     3549 apache    15   0 32244  13m 4244 S    1  0.2   0:00.07 httpd
     2296 apache    15   0 32324  13m 4276 S    0  0.2   0:00.23 httpd
     2414 apache    15   0 32320  13m 4280 S    0  0.2   0:00.17 httpd
     2460 apache    15   0 32952  14m 4380 S    0  0.2   0:02.78 httpd
     2622 apache    15   0 32232  13m 4248 S    0  0.2   0:00.08 httpd
     2700 apache    15   0 32292  13m 4240 S    0  0.2   0:00.09 httpd
     2752 apache    15   0 32280  13m 4256 S    0  0.2   0:00.10 httpd
     2757 apache    16   0 32300  13m 4260 S    0  0.2   0:00.10 httpd
     2851 apache    15   0 32284  13m 4248 S    0  0.2   0:00.06 httpd
     2951 apache    15   0 32204  13m 4240 S    0  0.2   0:00.04 httpd
     3003 apache    15   0 32260  13m 4264 S    0  0.2   0:00.09 httpd
     3146 apache    15   0 32144  13m 4240 S    0  0.2   0:00.06 httpd
     3226 apache    15   0 32316  13m 4248 S    0  0.2   0:00.12 httpd
     3236 apache    15   0 32256  13m 4252 S    0  0.2   0:00.07 httpd
     3275 apache    15   0 32284  13m 4244 S    0  0.2   0:00.15 httpd
     3449 apache    15   0 32260  13m 4264 S    0  0.2   0:00.09 httpd
     3466 apache    15   0 32228  13m 4248 S    0  0.2   0:00.06 httpd
        1 root      15   0  2012  684  588 S    0  0.0   0:00.92 init
        2 root      RT   0     0    0    0 S    0  0.0   0:00.00 migration/0
        3 root      34  19     0    0    0 S    0  0.0   0:00.00 ksoftirqd/0
        4 root      RT   0     0    0    0 S    0  0.0   0:00.00 watchdog/0
        5 root      RT   0     0    0    0 S    0  0.0   0:00.00 migration/1
        6 root      34  19     0    0    0 S    0  0.0   0:00.00 ksoftirqd/1
        7 root      RT   0     0    0    0 S    0  0.0   0:00.00 watchdog/1
        8 root      10  -5     0    0    0 S    0  0.0   0:00.00 events/0
        9 root      10  -5     0    0    0 S    0  0.0   0:00.00 events/1
       10 root      10  -5     0    0    0 S    0  0.0   0:00.00 khelper
       11 root      10  -5     0    0    0 S    0  0.0   0:00.00 kthread
       15 root      10  -5     0    0    0 S    0  0.0   0:00.00 kblockd/0
    
     
  7. falko

    falko Super Moderator Howtoforge Staff

    I think this is pretty much. If your web sites use PHP and MySQL, a child can use up to 20MB, not just 2 or 3. This would mean your swap space would get full, and if that happens, you must reset the server.
    To tweak your Apache, have a look here: http://www.howtoforge.com/configuring_apache_for_maximum_performance
     

Share This Page