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.

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.

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.

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.

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.

[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!

For some reason we were having problems with the datacenter and we were asked to remove the IP using KVM. In this case, we entered the KVM and checked the if the IP was listed on the server by using ifconfig – we found that the IP was listed there. To remove the IP edit the file.

root@server# nano /etc/ips

and now remove the line of the IP and then restart the ipaliases service by the command

root@server# service ipaliases restart

It will show failed, you can ignore those warnings. And you can recheck if the IP has gone by using the command ifconfig. You’ll see the IP is not seen in the ifconfig output. Now, you can ask the datacenter to get the server online and then if you check from the WHM you will see that the IP is not available there.

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.

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.

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.

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.