Starting the DNS server fails. restarting named shows the following error:

service named restart
Stopping named: [ OK ]
Starting named:
Error in named configuration:
zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 20010622
zone domain1.com/IN: loaded serial 1415397236
zone domain2.org/IN: loaded serial 1415411359
zone domain3.com/IN: loaded serial 1415556389

Thats the okay part
And then you see this:


zone domain4.com/IN: NS 'ns2.domain4.com' has no address records (A or AAAA)
zone domain4.com/IN: not loaded due to errors.

Resolution:

Add an A record for the nameserver ns2.domain4.com in the zone DNS manager in plesk. The restart named.

# service named restart

Strict Standards: Declaration of Walker_Page::start_lvl() should be compatible with that of Walker::start_lvl() in /var/www/vhosts/mercedescourlandinteriors.com/httpdocs/wp-includes/post-template.php on line 1071

Path and other info here – https://wordpress.org/support/topic/fix-strict-standards-issues

For CentOS-6 the EPEL repository is carrying later NTFS packages. EPEL is also usable for CentOS-5. To install, after enabling the repo per the Repositories page:


# yum install ntfs-3g 

or if you prefer to leave EPEL disabled by default


# yum --enablerepo epel install ntfs-3g 

You may also want to


yum install ntfsprogs ntfsprogs-gnomevfs 

Suppose your ntfs filesystem is /dev/sda1 and you are going to mount it on /mymnt/win, do the following.

First, create a mount point.

# mkdir /mymnt/win 

Next, edit /etc/fstab as follows. To mount read-only:

# /dev/sda1       /mymnt/win   ntfs-3g  ro,umask=0222,defaults 0 0 

To mount read-write:

# /dev/sda1       /mymnt/win   ntfs-3g  rw,umask=0000,defaults 0 0 

You can now mount it by running:

# mount /mymnt/win 

https://wordpress.org/support/topic/too-many-mysql-connections-and-mysql-server-has-gone-away

Check the error logs:

[11-Nov-2014 11:04:24 UTC] WordPress database error MySQL server has gone away for query SELECT ID FROM wp_posts WHERE post_title = 'blog' AND post_type= 'page' made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/themes/cricket_new/page-templates/live_score.php'), include('/themes/cricket_new/includes/right_part.php'), get_page_by_title

Check Mysql

mysql> show status like '%onn%';
+--------------------------+---------+
| Variable_name            | Value   |
+--------------------------+---------+
| Aborted_connects         | 835     |
| Connections              | 3998523 |
| Max_used_connections     | 533     |
| Ssl_client_connects      | 0       |
| Ssl_connect_renegotiates | 0       |
| Ssl_finished_connects    | 0       |
| Threads_connected        | 3       |
+--------------------------+---------+

View Repos: http://wiki.centos.org/AdditionalResources/Repositories

Install the EPEL repository

You install the EPEL repository by downloading the appropriate RPM package for your system and installing it. The following instructions use the 64-bit packages that work with Rackspace Cloud Servers instances.
CentOS and Red Hat Enterprise Linux 5.x


wget http://dl.fedoraproject.org/pub/epel/5/x86_64/epel-release-5-4.noarch.rpm
sudo rpm -Uvh epel-release-5*.rpm

CentOS and Red Hat Enterprise Linux 6.x


wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
sudo rpm -Uvh epel-release-6*.rpm

CentOS and Red Hat Enterprise Linux 7.x


wget http://dl.fedoraproject.org/pub/epel/7/x86_64/e/epel-release-7-2.noarch.rpm
sudo rpm -Uvh epel-release-7*.rpm

If you get a File Not Found error message when trying to download the package, the version number might have changed. You can access the latest version of the RPM installer from the Fedora EPEL wiki page. The wiki page also includes additional instructions for Red Hat Network subscribers who are installing the EPEL repository.
Install the IUS repository (optional)

The IUS repository provides newer versions of some software in the official CentOS and Red Hat repositories. The IUS repository depends on the EPEL repository.

The package names in the IUS repository are different from the package names used in the official repositories. The difference helps to avoid unintentional conflicts or software version updates.

Note: Because IUS uses package names that are different from the package names in the official repositories, we recommend IUS over Remi for Rackspace customers with managed support levels that include server software. Managed servers automatically update nightly by default, which can cause unplanned upgrades if package names are the same in more than one enabled repository.

Installing the IUS repository is a matter of downloading the appropriate RPM package for your system and installing it. The instructions below use the 64-bit packages that work with our Cloud Server instances.
CentOS 5.x


wget http://dl.iuscommunity.org/pub/ius/stable/CentOS/5/x86_64/ius-release-1.0-13.ius.centos5.noarch.rpm
sudo rpm -Uvh ius-release*.rpm

CentOS 6.x


wget http://dl.iuscommunity.org/pub/ius/stable/CentOS/6/x86_64/ius-release-1.0-13.ius.centos6.noarch.rpm
sudo rpm -Uvh ius-release*.rpm

CentOS 7.x


wget http://dl.iuscommunity.org/pub/ius/stable/CentOS/7/x86_64/ius-release-1.0-13.ius.centos7.noarch.rpm
sudo rpm -Uvh ius-release*.rpm

Red Hat 5.x


wget http://dl.iuscommunity.org/pub/ius/stable/Redhat/5/x86_64/ius-release-1.0-13.ius.el5.noarch.rpm
sudo rpm -Uvh ius-release*.rpm

Red Hat 6.x


wget http://dl.iuscommunity.org/pub/ius/stable/RedHat/6/x86_64/ius-release-1.0-13.ius.el6.noarch.rpm
sudo rpm -Uvh ius-release*.rpm

Red Hat 7.x


wget http://dl.iuscommunity.org/pub/ius/stable/RedHat/7/x86_64/ius-release-1.0-13.ius.el7.noarch.rpm
sudo rpm -Uvh ius-release*.rpm

If you get a File Not Found error message when trying to download the RPM, the version number might have changed. You can access the latest version of the repository package from the IUS Release Packages Page.
Upgrade installed packages to IUS versions

If you already have a software package installed that you want to upgrade to a newer version in the IUS repository, install the IUS yum plug-in for package replacement to simplify the upgrade process.


sudo yum install yum-plugin-replace

The plug-in provides a yum replace command that replaces a specified package and installs any required dependencies at the same time. For example, to replace the installed PHP package with the PHP 5.3 package from the IUS repository, run the following command:


sudo yum replace php --replace-with php53

For more information, see the IUS Client Usage Guide.
Install the Remi repository (optional)

The Remi repository provides newer versions of the software in the core CentOS and Red Hat Enterprise Linux repositories. The Remi repository depends on the EPEL repository.

Package names in the Remi repository are the same as the package names used in the official repositories. This similarity can result in inadvertent package upgrades when you run an update with yum, so use the Remi repository with care.

Note: Because Remi uses package names that are the same as the package names in the official repositories, we do not recommend Remi for Rackspace customers with a managed level of support. Managed servers automatically update nightly by default, which can cause unplanned upgrades if the Remi repository is enabled. If you require the Remi repository or another repository with package name conflicts, contact Rackspace Support before applying any upgrades to ensure continued support for your server.

You install the Remi repository by downloading the appropriate RPM package for your system and installing it. The following instructions use the 64-bit packages that work with Cloud Servers instances.
CentOS and Red Hat Enterprise Linux 5.x


wget http://rpms.famillecollet.com/enterprise/remi-release-5.rpm
sudo rpm -Uvh remi-release-5*.rpm

CentOS and Red Hat Enterprise Linux 6.x


wget http://rpms.famillecollet.com/enterprise/remi-release-6.rpm 
sudo rpm -Uvh remi-release-6*.rpm

CentOS and Red Hat Enterprise Linux 7.x


wget http://rpms.famillecollet.com/enterprise/remi-release-7.rpm 
sudo rpm -Uvh remi-release-7*.rpm

If you get a File Not Found error message when trying to download the package, the version number might have changed. You can access the latest version of the RPM installer from the Remi Repository Configuration page. The configuration page also includes additional instructions for Red Hat Network subscribers who are installing the Remi repository.
Enable the Remi repository

The Remi repository is disabled by default.

To use the Remi repository only when you know you need it, use the –enablerepo=remi option when installing a package. For example:


sudo yum --enablerepo=remi install php-tcpdf

If you want to permanently enable the Remi repository, you need to edit the yum configuration file for Remi.

Open the repository configuration file by using a text editor of your choice:


sudo nano /etc/yum.repos.d/remi.repo
Edit the [remi] portion of the file to set the enabled option to 1. This action enables the Remi repository by default.
name=Les RPM de remi pour Enterprise Linux $releasever - $basearch
#baseurl=http://rpms.famillecollet.com/enterprise/$releasever/remi/$basearch/
mirrorlist=http://rpms.famillecollet.com/enterprise/$releasever/remi/mirror
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-remi
failovermethod=priority

Check available repositories

You can see if the repositories that you need are installed and enabled by running the following command:


yum repolist

Some repositories, like Remi, are disabled by default. To list disabled repositories, run the following command:


yum repolist disabled

Source: http://kb.sp.parallels.com/en/115472

My server is using the Postfix mail server. For some reason, all messages it sends contain unnecessary headers, like the following:

X-No-Relay: not in my network

or

X-No-Auth: unauthenticated sender

The number of headers is multiplied by the number of message recipients, e.g., the headers of a message sent to two recipients would look like this:

X-No-Relay: not in my network
X-No-Relay: not in my network

Cause
Postfix adds those headers from these files:

# ls /var/spool/postfix/plesk/*re
/var/spool/postfix/plesk/non_auth.re
/var/spool/postfix/plesk/no_relay.re

Resolution
The issue will be fixed in a future update for which a new Knowledgebase article will be created. You may subscribe to new articles on Parallels Plesk Panel products if you wish to receive notifications about their creation.

Workaround
If you do not want messages to contain the above headers, clean (empty) these files:

/var/spool/postfix/plesk/non_auth.re
/var/spool/postfix/plesk/no_relay.re

nano /var/spool/postfix/plesk/no_relay.re

/^/ PREPEND X-No-Relay: not in my network

To install mysqli using EachApache:

1. Login to WHM as ‘root’ user.

2. Either search for “EasyApache” or go to Software > EasyApache

3. Scroll down and select a build option (Default)

4. Click Start “Start customizing based on profile”

5. Select the version of Apache and click “Next Step”.

6. Select the version of PHP and click “Next Step”.

7. Chose additional options within the “Short Options List”

8. Select “Exhaustive Options List” and look for “MySQL Improved extension”

9. Click “Save and Build”

To check mysqli was installed:

Run the following command as ‘root’ in SSH:

php -i|grep -i mysqli


Startup Log:
     Starting proftpd: 2014-11-10 17:08:26,390 server4.atwaretech.com proftpd[24369]: mod_auth_file/1.0: unable to use world-readable AuthUserFile '/etc/proftpd/passwd.vhosts' (perms 0644): Operation not permitted
     2014-11-10 17:08:26,390 server4.atwaretech.com proftpd[24369]: fatal: AuthUserFile: unable to use /etc/proftpd/passwd.vhosts: Operation not permitted on line 7 of '/etc/proftpd.conf'
     [FAILED]

Check permissions

root@server4 [~]# cd /etc/proftpd/
root@server4 [/etc/proftpd]# ls -la
total 32
drwxr-x--x   2 root proftpd  4096 Nov 10 17:08 ./
drwxr-xr-x. 89 root root    12288 Nov 10 17:19 ../
-rw-r-----   1 root proftpd   180 Nov 10 17:08 atware
-rw-r-----   1 root proftpd   180 Nov 10 17:08 lennys
-rw-r--r--   1 root root     1180 Nov 10 17:08 passwd.vhosts
-rw-------   1 root root     1501 Nov 10 17:08 passwd.vhosts.cache

Change to owner read writable

root@server4 # chmod o-rwx /etc/proftpd/passwd.vhosts
root@server4 # service proftpd restart

Info: http://ubuntuforums.org/showthread.php?t=2238794