ServerBuddies Support Blog

cPanel/WHM Update and Service Status Logs

Contains all output from each upcp. Named with the timestamp from which the upcp process was executed.

Service Status Logs

The service monitoring daemon (chkservd) logs all service checks here. Failed services are represented with a [-], and active are represented with [+].

Most commonly accessed cpanel log files.

When investigating any issue, the first thing you should always do is check the log files, as they generally provide insight as to what’s causing the erroneous behavior.

The following is a break down of the most commonly accessed log files, for cPanel and cPanel managed services:

cPanel logs any error it incurs here. This should always be the first place you look when you encounter errors or strange behavior in cPanel/WHM.

All license update attempts are logged here. If you run into any license errors when logging in, check here.

The stats daemon (cpanellogd) logs the output from all stats generators (Awstats, Webalizer, Analog) here.

General information pertaining to cPanel requests is logged here (Client Information, Request URI)

Easy Apache 3 & PHP

cPanel recommends that only one version of PHP is selected so that configuration and management is simplified.

When only one version of PHP is installed, a CGI binary is installed to /usr/bin/php and a CLI binary is installed to /usr/local/bin/php.

When both PHP4 and PHP5 are enabled, PHP5 will be installed to the standard locations /usr/bin/php and /usr/local/bin/php. PHP4 will be installed in /usr/php4/bin/php and /usr/local/php4/bin/php.

EasyApache 3 includes the ability to install, uninstall or update several popular PHP extensions as part of the Apache and PHP build process. When EasyApache runs it will automatically determine which extensions are active in main php.ini file at /usr/local/lib/php.ini. Active extensions will automatically be selected in the EasyApache 3 interface.

Rerunning EasyApache 3 is not required to enable or disable the standard PHP extensions. cPanel 11 provides a tool called /scripts/phpextensionmgr that can also be used for installation or removal.

Run the below command for detailed information.

Configuring Reverse DNS in WHM

Reverse DNS uses pointer records (PTR) to convert IP addresses into domain names. This is the opposite of forward DNS, which uses A records to convert domain names into IP addresses.

First, add a new DNS zone file. You can accomplish this using the Add a DNS Zone feature in the DNS Functions section of your WHM interface (Main >> DNS Functions >> Add a DNS Zone).

To continue, enter the IP address and proper reverse DNS zone name in the appropriate fields.

To properly format the Domain field in the interface.

Take the first 3 octets of the IP address, Reverse them, and Affix in-addr.arpa to the end. So, for example, the reverse DNS entry for 192.168.0.1 is 0.168.192.in-addr.arpa. After you have filled out these 2 fields, click the Add Zone button.

One you have created your zone file, you can edit it. You can do this using the WHM Edit DNS Zone screen (Main >> DNS Functions >> Edit DNS Zone). Your zone file should already contain an NS entry for every authoritative nameserver associated with your server. To finish this process, we need to add a PTR record for each IP address we wish to name in the last octet of 192.168.0.

After the reverse DNS zone has propagated, run a test to ensure that you have properly configured reverse DNS. To do so, you can use the following command:

If you have properly configured your reverse DNS zone file, the output should resemble the following:

Ruby on Rails and rubygems install on CentOS

Ruby on Rails install on CentOS

Once you have the development tools package installed. You can go ahead and install Ruby on Rails. The main ruby packages and dependencies will be installed using the ‘yum’ package manager, but rubygems will be installed from source. Rubygems is not readily available through the repositories in yum.

Install ruby.

Main Ruby on Rails packages can be installed using the below method.

Once done, we can have a look at the Ruby version.

Installing rubygems for Rails installation.

Download from: http://rubyforge.org/projects/rubygems/

Now unpack it and move into the newly created folder.

Now we can go through the simple process of compiling it:

Once done, we can check the gem version with a:

NOTE:

http://rubygems.org is now the default source for downloading gems.