There was an error manipulating the password file. This generally means you entered your old password incorrectly.

While changing the cPanel password from cPanel >> Preferences >> Change password, you might face the following error

There was an error manipulating the password file. This generally means you entered your old password incorrectly.

Even if you confirm the old password used is correct, still you might face this problem.

This problem is faced due to inappropriate permissions set for the file /usr/bin/passwd.

To sort this error you can do a simple trick (which worked for me! )

To sort this error login to the server as root and change the permissions for the file to 4511.

[root@server~] # chmod 4511 /usr/bin/passwd

Once done, try to change the password again from the cPanel. It should work!

 

no version information available (required by php)

I was facing  following error when I was trying to view the php version on the server:

============

root@server [~]# php -v
php: /usr/lib/libmysqlclient.so.15: version `libmysqlclient_15′ not found (required by php)
php: /opt/xml2/lib/libxml2.so.2: no version information available (required by php)
php: /opt/xml2/lib/libxml2.so.2: no version information available (required by php)
php: /opt/xml2/lib/libxml2.so.2: no version information available (required by php)
php: /opt/xml2/lib/libxml2.so.2: no version information available (required by php)
php: /opt/xml2/lib/libxml2.so.2: no version information available (required by php)
============

You might get this error even if the apache on the cpanel server is recompiled. To sort this error just follow following simple step:

root@server [~]# mv /opt/xml2 /opt/xml2.bak

Then re execute EasyApache from WHM > EasyApache (Apache Update) or via shell using the command /scripts/easyapache –force

This should now sort the problem.

 

rndc: connect failed: 127.0.0.1#953: connection refused

Your servers named service may start to go unresponsive with the following error logs:

===========

[root@server ~]# service named restart
Stopping named: …………………………………….[FAILED]
Starting named: named: already running                     [FAILED]

rndc: connect failed: 127.0.0.1#953: connection refused

===========

This problem arises due the the servers configuration accepting the DNS as chrooted instead of plain DNS.

For correcting check the file /etc/sysconfig/named. You can locate the following line:

ROOTDIR=”/var/named/chroot/”

Comment the above statement

#ROOTDIR=”/var/named/chroot/”

Now restart the named service on the server.

Clearing cache with different OS

Filed under: General by Snehalk — Leave a comment

October 28, 2010

A lot of times we deal difficulty in accessing a number of URL’s due to corrupted local DNS cache. Following are the steps to clear local machine cache for various operating systems:

A) Windows XP/Windows Vista/Windows 7:

1)  Click on Start >> All Programs >> Accessories.
2)Open Command Prompt.
3) In the Command Prompt window type in the following command:

C:\>ipconfig /flushdns

4) If it displays a message “Successfully flushed the DNS Resolver Cache” It has removed the DNS cache for your local machine now.

B ) Linux:

1) One of the most commonly used DNS caching Linux applications is NSCD (Name Service Caching Daemon).

2)If you have NSCD installed you can clear the local DNS cache by running one of the following commands in  terminal/shell :

a)To Clear local DNS cache for current user.

# nscd -i hosts

b) To Clear local DNS cache for all users.

#nscd -I hosts

C) Mac OS X 10.5.2 and above /Mac OS X Leopard:

1) Click on the Finder icon in your dock >> Open Applications folder.
2) Inside the Applications folder >> click on Utilities >> Terminal.
3)Type the following command in the Terminal:

# dscacheutil -flushcache

D) Mac OS X 10.5.1 and below:

1) Click on the Finder icon in your dock  >> Open  Applications folder.
2)Inside the Applications folder >> click on Utilities >> Terminal.
3 )Type the following command in the Terminal:

# lookupd -flushcache

Increasing the number of filelistings in pureftpd

By default in cPanel the limits number of files and sub directory trees is 2,000 files till 8 levels.
If you have a large amount of files to be listed (more than 2000) you need to make some changes in the pure-ftpd’s configuration file.
Following are the steps for the same.

1) Login to the server as root.

2) Open the configuration file for pure-ftpd.

[root@server~]# vi /etc/pure-ftpd.conf

3) Locate the line which says :

LimitRecursion 2000 8

This is ‘ls’ recursion limits. The first argument is the maximum number of files to be displayed and the second one is the max subdirectories depth.

4) Edit the mentioned line to the limits as needed. For Eg I would like to list 3000 files to a subdirectory depth of 6 the setting will be as follows:

LimitRecursion 3000 6

5) Now just restart the pure-ftpd service on the server.

[root@server~]# /etc/init.d/pure-ftpd restart

Now you can view the difference in listing.

Disable suhosin

Suhosin for a domain can be disabled by 2 methods.

1) Using php.ini

2) Using .htaccess.

Following are the steps in order to

A. Disable suhosin using php.ini.

1) Login to the server as root

2) Copy the servers customized php.ini file to the document root of the domain.

[root@server]# php -i | grep php.ini
Configuration File (php.ini) Path => /usr/local/lib
Loaded Configuration File => /usr/local/lib/php.ini

[root@server]# cp /usr/local/lib/php.ini /home/username/public_html

3) Open the php.ini file and add the following code to the file:

[suhosin]
; Misc Options
suhosin.simulation = On

[On indicates disabled, Off indicates enabled]

4) Save and quit the file. Restart apache.  That’s it. Suhosin for a domain will now be disabled.

B. Disable SUHOSIN via .htaccess

1) Go to the document root for the domain and open the .htaccess file for the domain.

2)Now enter the following code in the file.

php_flag suhosin.simulation On

3) If the server is configured to use suphp try entering following code in .htaccess.

<Files “.ht*”>
deny from all
</Files>

suPHP_ConfigPath /home/username

4)Save and quit the file. Restart apache.  That’s it. Suhosin for a domain will now be disabled.

Share this: