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.

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.

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.

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.

If you’re looking to upgrade your Wordpress blog, please check this URL.

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.

While working on a quota issue for a domain on a plesk dedicated server, we found that the disk usage for the domain in the plesk control panel was overused. When checked from SSH the actual disk usage showed very low. The problem here was due to stats not getting updated for this particular domain.

To get this issue fix, you need to update the statistic logs for this domain on the plesk.

First of all login in to the server by the root access, use the below command to update the statistics for all the domains on the server.

/usr/local/psa/admin/sbin/statistics

Later, we updated the stats for the domain by the below command:

/usr/local/psa/admin/sbin/statistics --calculate-one --domain-name=domain.com

This fixed the statistics issue, as well as everything in the plesk control panel for disk usage shows fine now for the domain.

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.

On a shared cPanel web server, we came around below error:

some-email@gmail.com cannot be resolved at this time: host lookup did not complete

So while troubleshooting this error, we found that the problem was in /etc/resolv.conf

There were invalid IPs there, just changing them the right ones fixed the problem for us.

Hope this helps guys who come around this error. If anyone has come around such error and have a different way to fix it – you can reply here with your solution!

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.