{"id":16127,"date":"2023-06-22T09:10:28","date_gmt":"2023-06-22T09:10:28","guid":{"rendered":"https:\/\/webhostinggeeks.com\/howto\/?p=16127"},"modified":"2023-09-18T16:03:53","modified_gmt":"2023-09-18T16:03:53","slug":"how-to-enable-mod_status-apache-module-on-ubuntu-centos","status":"publish","type":"post","link":"https:\/\/webhostinggeeks.com\/howto\/how-to-enable-mod_status-apache-module-on-ubuntu-centos\/","title":{"rendered":"How to Enable mod_status Apache module on Ubuntu\/CentOS"},"content":{"rendered":"

\"How<\/p>\n

Apache stands as one of the most widely used and versatile options available in the world of web servers. It offers a range of modules that enhance its functionality, one of which is the mod_status module. This module provides valuable insights into server activity and performance, making it an essential tool for server administrators.<\/p>\n

In this tutorial, we will guide you on how to enable the mod_status Apache module on Ubuntu<\/a> and CentOS<\/a> systems.<\/p>\n

Before we dive into the tutorial, it’s worth noting that there are several types of web servers available, each with its unique features and benefits. For a comprehensive comparison and to find the best web servers<\/a> for your needs, you can check our detailed guide.<\/p>\n

Understanding Apache mod_status Module<\/h2>\n

The Apache mod_status module provides a server administrator with insights into how well their server is performing. It presents a HTML page with current server statistics in an easily readable form.<\/p>\n

\"Apache<\/p>\n

The details provided include the number of workers serving requests, the number of idle workers, the status of each worker, the number of requests that worker has performed, the total number of bytes served by the worker, and more.<\/p>\n

For more detailed information on the Apache server, you can refer to our in-depth article on Apache HTTP Server<\/a>.<\/p>\n

Enabling mod_status Apache Module on Ubuntu\/CentOS<\/h2>\n

To enable the mod_status module on your Apache server, you need to follow these steps:<\/p>\n

Step 1: Check if mod_status is enabled<\/h3>\n

First, you need to check if the mod_status module is already enabled on your Apache server. You can do this by running the following command:<\/p>\n

\r\napachectl -M | grep status\r\n<\/pre>\n
If the module is enabled, you will see ‘status_module (shared)’ in the output. If not, you need to enable it.<\/p>\n
\r\ndimitri@geekapi:~# apachectl -M | grep status\r\nstatus_module (shared)\r\ndimitri@geekapi:~#   \r\n<\/pre>\n
Step 2: Enable mod_status<\/h3>\n
On Ubuntu, you can enable the mod_status module by running the following command:<\/p>\n
\r\nsudo a2enmod status\r\n<\/pre>\n
On CentOS, the mod_status module is usually enabled by default. If it’s not, you can enable it by uncommenting the ‘LoadModule status_module modules\/mod_status.so’ line in the httpd.conf file.<\/p>\n
Here’s how you can enable the mod_status module on CentOS by uncommenting the appropriate line in the httpd.conf file:<\/p>\n
First, you need to open the httpd.conf file. This file is usually located in the \/etc\/httpd\/ directory. You can open it using a text editor like vi or nano. Here’s how to do it with vi:<\/p>\n
\r\nsudo vi \/etc\/httpd\/conf\/httpd.conf\r\n<\/pre>\n
Next, you need to search for the line that loads the mod_status module. In vi, you can do this by pressing ‘\/’ and then typing the part of the line you’re looking for, like so:<\/p>\n
\r\n\/LoadModule status_module\r\n<\/pre>\n
This should highlight the line ‘LoadModule status_module modules\/mod_status.so’.<\/p>\n
If the line is commented out (i.e., if it starts with a ‘#’), you need to uncomment it. In vi, you can do this by moving the cursor to the ‘#’ character and then pressing ‘x’. This will delete the ‘#’ character and uncomment the line.<\/p>\n
After uncommenting the line, you need to save the changes and exit the text editor. In vi, you can do this by pressing ‘:’, then typing ‘wq’, and finally pressing ‘Enter’. This will write the changes to the file (w) and quit the text editor (q).<\/p>\n
\r\n:wq\r\n<\/pre>\n
Finally, you need to restart your Apache server for the changes to take effect. You can do this by running the following command:<\/p>\n
\r\nsudo systemctl restart httpd\r\n<\/pre>\n
Now, the mod_status module should be enabled on your CentOS Apache server.<\/p>\n
Step 3: Configure mod_status<\/h3>\n
To configure mod_status, you need to add a specific code block to your Apache configuration file. This block will allow status reports only for browsers from a specific domain. Here is an example:<\/p>\n
\r\n<Location \"\/server-status\">\r\n SetHandler server-status\r\n Require host example.com\r\n<\/Location>\r\n<\/pre>\n
Replace ‘example.com’ with your domain. After adding this block, you can access server statistics by using a web browser to access the page http:\/\/your.server.name\/server-status.<\/p>\n
Step 4: Restart Apache<\/h3>\n
After enabling and configuring the mod_status module, you need to restart your Apache server for the changes to take effect. You can do this by running the following command:<\/p>\n
On Ubuntu:<\/p>\n
\r\nsudo systemctl restart apache2\r\n<\/pre>\n
On CentOS:<\/p>\n
\r\nsudo systemctl restart httpd\r\n<\/pre>\n
Now, you should be able to access the server status page at http:\/\/your.server.name\/server-status.<\/p>\n
Using mod_status for Troubleshooting<\/h2>\n
The server-status page can be used as a starting point for troubleshooting situations where your server is consuming all available resources (CPU or memory), and you wish to identify which requests or clients are causing the problem.<\/p>\n
First, ensure that you have ExtendedStatus set on, so that you can see the full request and client information for each child or thread. Now look in your process list (using top, or similar process viewing utility) to identify the specific processes that are the main culprits. Order the output of top by CPU usage, or memory usage, depending on what problem you’re trying to address.<\/p>\n
Reload the server-status page, and look for those process ids, and you’ll be able to see what request is being served by that process, for what client. Requests are transient, so you may need to try several times before you catch it in the act, so to speak.<\/p>\n
This process should give you some idea of what client, or what type of requests, are primarily responsible for your load problems. Often you will identify a particular web application that is misbehaving, or a particular client that is attacking your site.<\/p>\n
Commands Mentioned<\/h2>\n