Archive for 2010



WordPress 3.0.4 Important Security Update

Thursday, December 30th, 2010

There is  a news for wordpress about a security update, Version 3.0.4 of WordPress, available immediately through the update page in your dashboard or for download here, is a very important update to apply to your sites as soon as possible because it fixes a core security bug in our HTML sanitation library, called KSES. I would rate this release as “critical.”

Official link : http://wordpress.org/news/2010/12/3-0-4-update/


Softaculous WHMCS Auto Install Module for cPanel and DirectAdmin

Sunday, November 14th, 2010

Softaculous have launched an Auto Script Installer for WHMCS which allow server owners to offer packages with pre-installed applications.

If you have softaculous on your server and selling wordpress hosting, imagine when client signup they don’t have to login to the server control panel to install wordpress, just signing up for an account could install wordpress for them. That’s great! Isn’t it?

For more information, kindly check the following link – http://www.softaculous.com/docs/WHMCS_Auto_Install_Module

At the moment, this auto script supports cPanel and DirectAdmin web based control panels.

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


Suhosin error on subdomain

Friday, August 20th, 2010

On a cPanel server, we were asked to install vbulletin on a subdomain and while doing so we came across errors which were not allowing us to install it. The errors were as below:

ERRORS :

[Wed Aug 11 13:58:17 2010] [error] [client 89.165.120.238] /usr/bin/php:

symbol lookup error:

/usr/local/lib/php/extensions/no-debug-non-zts-20060613/suhosin.so:

undefined symbol: zend_atol, referer:

http://forum.mydomain.com/install/install.php?step=2

[Wed Aug 11 13:58:17 2010] [error] [client 89.165.120.238] Premature end of script headers: install.php, referer:

http://forum.mydomain.com/install/install.php?step=2

To get this issue fixed, you can do the below steps:

It seems that Suhosin breaks the application. So need to disable the Suhosin for this domain. You can disable the suhosin by creating a php.ini file at /home/username/public_html/php.ini with the following code.

suhosin.simulation = On

If you are still getting same error then you need to create same php.ini file with same code (suhosin.simulation = On) at each directories. In this case at these paths also /home/username/public_html/php.ini, /home/username/public_html/forum/php.ini and /home/username/public_html/install/php.ini

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


Plesk – Error: Unable to remove client: mailmng failed: Some errors occured.

Saturday, August 7th, 2010

On a plesk dedicated server while removing a client we were facing problems, we were getting the error:

Error: Unable to remove client: mailmng failed: Some errors occured. See log for details

Couldn’t find anything specific in the logs.

Solution:

Stop mail service by the below command:

root# /usr/local/psa/admin/sbin/mailmng --stop-service

Find all corrupted mail headers using the following command. For example:

root# find /usr/local/psa/handlers/before-* -type f | while read h ; do [ ! -d /usr/local/psa/handlers/info/$(basename $h) ] && echo $h  ; done

Delete the file you have got in the output of the above command:

rm -f /usr/local/psa/handlers/before-local/recipient/email@somedomain1.com/11-spam-asdDemCa

Run utility mchk to recreate mail handlers by the below command:

root# /usr/local/psa/admin/sbin/mchk --with-spam

Then, Start the mail service after the reconfiguration is completed by the below command.

root# /usr/local/psa/admin/sbin/mailmng --start-service

This should fix the problem that you’re facing, if for some reason this doesn’t work for you backup the handlers directory.

root# mkdir /root/back
root# cp -a /usr/local/psa/handlers/before-* /root/back/
root# cp -a /usr/local/psa/handlers/info /root/back/

Then, delete all the email handlers:

root# rm -rf /usr/local/psa/handlers/before-*/*
root# rm -rf /usr/local/psa/handlers/info/*

Run utility mchk to recreate mail handlers by the below command:

root# /usr/local/psa/admin/sbin/mchk --with-spam

Then, Start the mail service after the reconfiguration is completed by the below command.

root# /usr/local/psa/admin/sbin/mailmng --start-service

This should surely fix the problems.

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


Mailman problem on cPanel dedicated server

Wednesday, June 30th, 2010

While installing or modifying mailinglist on cPanel server if you get the following error:

Bug in Mailman version 2.1.11

We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy
of this page to the webmaster for this site with a description of what
happened. Thanks!

To get this fixed, you can execute following command :

root# chmod 02775 -R /usr/local/cpanel/3rdparty/mailman/

That’s it!

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


Webmin is not working on a dedicated cPanel server

Thursday, April 22nd, 2010

Problem:
When we logged in the webmin with the admin user , none of the control panel components were displayed even after reinstalling the webmin control panel.

Solution :
What we did is reinstalled the package. But before reinstalling the webmin control panel we must need to kill previously running webmin processes. Then after give it a chance to reinstall the control panel package. It worked for me.

Hope this helps you.

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


SSH failed – PRNG is not seeded

Wednesday, March 3rd, 2010

On a linux based VPS, a client rebooted their system and could not get the SSH of their VPS. As this is a VPS, we entered to their VPS from the hardware node and tried to restart SSH but got the below errors:

root@localhost:/# /etc/init.d/ssh restart
PRNG is not seeded

After investigation we found that the /dev/urandom was not there on the VPS.

root@localhost:/dev# ls -al /dev/random
crw-r--r-- 1 root root 1, 8 Mar  2 19:28 /dev/random

root@localhost:/dev# ls -al /dev/urandom
ls: cannot access /dev/urandom: No such file or directory

By the below command, we created it and restarted SSH

root@localhost:/dev# mknod /dev/urandom c 1 9
root@localhost:/dev# /etc/init.d/ssh  restart
* Restarting OpenBSD Secure Shell server sshd
...done.

All is perfect now!

This article is released by SupportFacility.Com — the leaders in providing outsourced technical support, live chat support & help desk support for web hosts. Interested ? Opt for a trial now.


IonCube error on 64 bit server

Friday, January 22nd, 2010

On a 64 bit dedicated server we came accross an error:

[root@server ~]# php -v
Failed loading /usr/local/ioncube/ioncube_loader_lin_5.2.so:
/usr/local/ioncube/ioncube_loader_lin_5.2.so: wrong ELF class: ELFCLASS32

If you come across such issue it seems that you have installed the wrong version of the IonCube Loader. For 64 bit remember to use the path /usr/lib64/php/modules/ioncube

I hope this helps you!