Logo Background RSS

» httpd

  • Stop Coredump file
    By on March 23rd, 2009 | 10 Comments10 Comments Comments

    Many webmasters ask me how to stop core dump files in Apache.. Now today i will tell you how to stop core dump file in apache.  This is basically happens when System Crashes it makes a coredump file in the public_html Directory.

    The possible reason for the core files getting generated is when a php process is killed, apache creates core files under your account .

    On phpSuexec servers this may cause due to incorrect php.ini file placed in your account and if it is caused due to php/apache then you can get rid off those core files by editing the httpd startup file on the server end .

    Lets start

    Code:
    root@server [~]# vi /etc/init.d/httpd

    Search for ulimit lines .For eg : you can see these lines

    Code:
    ulimit -n 1024
    ulimit -n 4096
    ulimit -n 8192
    ulimit -n 16384

    You need to add ulimit -c 0 at the end .Which will look like :

    Code:
    ulimit -n 1024
    ulimit -n 4096
    ulimit -n 8192
    ulimit -n 16384
    ulimit -c 0

    root@server [~]# :wq

    Save changes and quit.
    Now kill / stop apache service and then start apache service on the server .

    Code:
    root@server [~]# service httpd stop
    root@server [~]# service httpd stop
    httpd (no pid file) not running
    root@server [~]# service httpd startssl
    root@server [~]# service httpd startssl
    httpd (pid 21154) already running

    Finished :D

    It works most of the OS.

    Self tested on CENTOS 5.2 i686 on standard

  • All about httpd.conf
    By on January 24th, 2009 | No Comments Comments
    This  httpd.conf file to set itself up for this particular configuration setup with:
    ServerType standalone

    The option ServerType specifies how Apache should run on the system. You can run it from the super-server inetd, or as standalone daemon. It’s highly recommended to run Apache in standalone type for better performance and speed.

    ServerRoot “/etc/httpd”

    The option ServerRoot specifies the directory in which the configuration files of the Apache server lives. It allows Apache to know where it can find its configuration files when it starts.

    PidFile /var/run/httpd.pid

    The option PidFile specifies the location where the server will record the process id of the daemon when it starts. This option is only required when you configure Apache in standalone mode.

    ResourceConfig /dev/null

    The option ResourceConfig specifies the location of the old srm.conf file that Apache read after it finished reading the httpd.conf file. When you set the location to /dev/null, Apache allows you to include the content of this file in httpd.conf file, and in this manner, you have just one file that handles all your configuration parameters for simplicity.

    AccessConfig /dev/null

    The option AccessConfig specifies the location of the old access.conf file that Apache read after it finished reading the srm.conf file. When you set the location to /dev/null, Apache allows you to include the content of this file in httpd.conf file, and in this manner, you have just one file that handles all your configuration parameters for simplicity.

    Timeout 300

    The option Timeout specifies the amount of time Apache will wait for a GET, POST, PUT request and ACKs on transmissions. You can safely leave this option on its default values.

    KeepAlive On

    The option KeepAlive, if set to On, specifies enabling persistent connections on this web server. For better performance, it’s recommended to set this option to On, and allow more than one request per connection.

    MaxKeepAliveRequests 0

    The option MaxKeepAliveRequests specifies the number of requests allowed per connection when the KeepAlive option above is set to On. When the value of this option is set to 0 then unlimited requests are allowed on the server. For server performance, it’s recommended to allow unlimited requests.

    KeepAliveTimeout 15

    The option KeepAliveTimeout specifies how much time, in seconds, Apache will wait for a subsequent request before closing the connection. The value of 15 seconds is a good average for server performance.

    MinSpareServers 16

    The option MinSpareServers specifies the minimum number of idle child server processes for Apache, which is not handling a request. This is an important tuning parameter regarding the performance of the Apache web server. For high load operation, a value of 16 is recommended by various benchmarks on the Internet.

    MaxSpareServers 64

    The option MaxSpareServers specifies the maximum number of idle child server processes for Apache, which is not handling a request. This is also an important tuning parameter regarding the performance of the Apache web server. For high load operation, a value of 64 is recommended by various benchmarks on the Internet.

    StartServers 16

    The option StartServers specifies the number of child server processes that will be created by Apache on start-up. This is, again, an important tuning parameter regarding the performance of the Apache web server. For high load operation, a value of 16 is recommended by various benchmarks on the Internet.

    MaxClients 512

    The option MaxClients specifies the number of simultaneous requests that can be supported by Apache. This too is an important tuning parameter regarding the performance of the Apache web server. For high load operation, a value of 512 is recommended by various benchmarks on the Internet.

    MaxRequestsPerChild 100000

    The option MaxRequestsPerChild specifies the number of requests that an individual child server process will handle. This too is an important tuning parameter regarding the performance of the Apache web server.

    User www

    The option User specifies the UID that Apache server will run as. It’s important to create a new user that has minimal access to the system, and functions just for the purpose of running the web server daemon.

    Group www

    The option Group specifies the GID the Apache server will run as. It’s important to create a new group that has minimal access to the system and functions just for the purpose of running the web server daemon.

    DirectoryIndex index.htm index.html index.php index.php3 default.html index.cgi

    The option DirectoryIndex specifies the files to use by Apache as a pre-written HTML directory index. In other words, if Apache can’t find the default index page to display, it’ll try the next entry in this parameter, if available. To improve performance of your web server it’s recommended to list the most used default index pages of your web site first.

    Include conf/mmap.conf

    The option Include specifies the location of other files that you can include from within the server configuration files httpd.conf. In our case, we include the mmap.conf file located under /etc/httpd/conf directory. This file mmap.conf maps files into memory for faster serving.

    HostnameLookups Off

    The option HostnameLookups, if set to Off, specifies the disabling of DNS lookups. It’s recommended to set this option to Off in order to save the network traffic time, and to improve the performance of your Apache web server.