BEGIN failed–compilation aborted at /usr/lib/perl5/site_perl/5.8.8/Template/Stash/XS.pm line 31.
Compilation failed in require at /scripts/cPScript/Template.pm line 14.
BEGIN failed–compilation aborted at /scripts/cPScript/Template.pm line 14.
Compilation failed in require at /scripts/cPScript/AdvConfig.pm line 9.
BEGIN failed–compilation aborted at /scripts/cPScript/AdvConfig.pm line 9.
Compilation failed in require at /scripts/cPScript/AdvConfig/apache.pm line 19.
BEGIN failed–compilation aborted at /scripts/cPScript/AdvConfig/apache.pm line 19.
Compilation failed in require at /scripts/cPScript/EditHttpdconf.pm line 37.
BEGIN failed–compilation aborted at /scripts/cPScript/EditHttpdconf.pm line 37.
Compilation failed in require at /scripts/fixmailmanwithsuexec line 14.
BEGIN failed–compilation aborted at /scripts/fixmailmanwithsuexec line 14.
======================================================

Recently while trying to login into a VPS; SSH was not accepting Password for the user root. So, I logged into the VPS from Hardware Node (Host Server) and checked /var/log/messages to get exact Error. Following are the logs which were stored in /var/log/messages file

Feb 23 23:51:10 server PAM-shells[13512]: /etc/shells is either world writable or not a normal file
Feb 23 23:51:14 server PAM-shells[13512]: /etc/shells is either world writable or not a normal file
Feb 23 23:51:17 server PAM-shells[13535]: /etc/shells is either world writable or not a normal file
Feb 23 23:52:49 server sshd(pam_unix)[15414]: authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=server.example.com user=root

When I checked the permissions of the file /etc/shells and it was set to 777 (universal writable).

I have checked and found that gcc and cpp modules are already installed on the server. This can be checked using command “rpm -qa | grep gcc” “rpm -qa | grep cpp“. I have searched on many websites and found that glibc-headers were not installed on the server. I have installed glibc-headers using command “yum install glibc-headers“. If you face this problem please make sure that following components are installed on the server:

Certificate Signing Request (CSR) contains all the information regarding certificate application. It also includes the Public key.

Following steps will show how to generate a pair of private key and public Certificate Signing Request (CSR) for a webserver, “server” using Apache mod_ssl/OpenSSL.

root@vps [~]# openssl req -new -nodes -keyout vps.key -out vps.csr

This creates a two files. The file vps.key contains a private key;

Following is the output from the above command, you will have to fill some of the fields here:

root@vps [~]# openssl req -new -nodes -keyout vps.key -out vps.csr

Generating a 1024 bit RSA private key
……………++++++
……++++++
writing new private key to ‘vps.key’
—–
You are about to be asked to enter information that will be incorporated
into your certificate request.
What you are about to enter is what is called a Distinguished Name or a DN.
There are quite a few fields but you can leave some blank
For some fields there will be a default value,
If you enter ‘.’, the field will be left blank.
—–
Country Name (2 letter code) [GB]:GB
State or Province Name (full name) [Berkshire]:Berkshire
Locality Name (eg, city) [Newbury]:Newbury
Organization Name (eg, company) [My Company Ltd]:Trulymanaged
Organizational Unit Name (eg, section) []:Webhosting
Common Name (eg, your name or your server’s hostname) []:vps.server.com
Email Address []:vps@server.com

Please enter the following ‘extra’ attributes
to be sent with your certificate request
A challenge password []:sdfhsdfj
An optional company name []:

Your CSR will now have been created. Open the vps.csr in a text editor and copy and paste the contents into the online enrollment form when requested.

ErrorApache Web Server was not passing servlet requests to Apache Tomcat. It served 404 errors to jsp pages, even though the Apache Tomcat was auto-configured by the WHM / Cpanel installation.

SEVERE: Error starting static Resources java.lang.IllegalArgumentException: Document base Ã§Ã§Ã§ does not exist or is not a readable directory at org.apache.naming.resources.FileDirContext.setDocBase(FileDirContext.java:141)

CauseThis was occurring because Tomcat could not read from the “public_html” directory for the site. This was a result of file protect being enabled in easyapache. This option causes all public_html directories to be owned by the user and the group nobody, leaving all other users unable to index those directories. Unfortunately this leaves tomcat, which runs as the user tomcat, unable to access those files as well.

What is SPF? [Sender Policy Framework]SPF (Sender Policy Framework) is a standard that was created in order to stop and eliminate the forged or spoofed sender email addresses in the mail envelope SMTP MAIL FROM or Return-Path that commonly used in spam message. SPF is not directly about stopping spam – junk email. SPF works as an extension to the Simple Mail Transfer Protocol (SMTP), and allows relay MTA (Mail Transport Agent) to identify and reject those e-mail spam sent from unauthorized and unapproved mail server. SPF was created in 2003 to help close loopholes in email delivery systems that allow spammers to “spoof” or steal your email address to send hundreds, thousands or even millions of emails illicitly.

How SPF Work?SPF enable domain’s email delivery operation works in such a way, Owner of an Internet domain name defines SPF records using a special format of TXT records in the domain zone DNS name server. The SPF specifies which machines are authorized to transmit e-mail for that domain. When an email is received by a mail server, the MTA will query the SPF records from DNS resolver to determine whether the email is originated from a legitimate server. If SPF PASS result is returned, the email is accepted and got delivered. Else if SPF FAIL result is returned, the email is rejected and bounced.

Is SPF is Must?SPF records is not must, but it’s a good to set up the SPF records to stop spam fault from illegally spoofing. If your domain does not have an SPF record. This means that spammers can easily send out E-mail that looks like it came from your domain, which can make your domain look bad (if the recipient thinks you really sent it), and can cost you money (when people complain to you, rather than the spammer).
Now many mail servers such as AOL and Hotmail now require valid SPF record for inclusion in their whitelist program so if you don’t have one your email will probably not be delivered to that server.

How to Set up SPF record for a domain?The major issue for SPF records are how to write and create a properly SPF record which is valid and correct for the domains, as all SMTP server that sends email for the domains must be defined.

For SPF to work you have to add, to each DNS zone a record similar to this:

domain.com. 14400 IN TXT "v=spf1 a mx -all"

note:- “.” is necessary after the “domain.com” otherwise SPF fails to work.
“domain.com” is the domain for which you were adding SPF record.Syntax used is as follows,You will notice that all SPF record start with v=spf1. “v=” defines the version of SPF used, and is mandatory to identify it’s the SPF record. Currently only the only version supported is spf1.A :- If the domain name has an A record corresponding to the sender’s address, it will match. (That is, the mail comes directly from the domain name.)MX :- If the domain name has an MX record resolving to the sender’s address, it will match. (That is, the mail comes from one of the domain’s mail servers)ALL :- Matches always, used for a default result like -all for no other IP’s are allowed to send emails.

You can read all the options that you have by visiting: http://www.openspf.org/SPF_Record_Syntax