harveygwa Posted November 7, 2010 Share Posted November 7, 2010 Right iv been using WHMCS for about 2 mouths now and had it all setup working fine. the cron job was sending invoces creating accounts and everything then about 3-4 days ago some how i dont know how my girlfriend how was sorting some stuff out for me as i was out managed to suspend my hole domain. i had to get my host provider to unsuspend me. (im using a reseller account at the moment) ever since then the cron job has not been working right. well im lead to belive this is the problem. i tested it buy setting up a dummy account and it sends me the welcome email, invoice/invoice paid email but wont create the account and send out account info email...... i had the cron job output to a email address and it send me: "php: symbol lookup error: /usr/local/lib/php/extensions/no-debug-non-zts-20060613/suhosin.so: undefined symbol: zend_atol" does anyone know what this means?? help please. 0 Quote Link to comment Share on other sites More sharing options...
GORF Posted November 7, 2010 Share Posted November 7, 2010 Sounds like a corrupt file from the restore of your account. - Delete and recreate the cron job in your cPanel. - Re-upload (binary) cron.php. (I would probably re-upload all of the admin side files) 0 Quote Link to comment Share on other sites More sharing options...
GGWH-James Posted November 7, 2010 Share Posted November 7, 2010 (edited) That error generally occurs when an application is not compatible with Suhosin or sometime when software is upgraded. You can do one of the following: Put "suhosin.simulation = On" into a php.ini file in the WHMCS Web root. Put "php_flag suhosin.simulation On" into a .htaccess file in the WHMCS Web root. By doing one of the above, violations will be logged as per usual, but nothing will get blocked or removed from the request though. With that said, I would suggest reinstalling Suhosin first though to see if your error is resolved. If not, the above workaround should get it working again for you. Edited November 7, 2010 by GGWH-James 0 Quote Link to comment Share on other sites More sharing options...
harveygwa Posted November 9, 2010 Author Share Posted November 9, 2010 i opened a support ticket with my web host about this issue and he could not see what was wrong. about an hour later he mailed me again saying that now a few people on the server were having the same problem and had mantainers looking into it. its just started working agin so i belive what ever the problem was it was server wide and they managed to sort it out. im trying to find out from them what the exacte problem was and will repost here when i find out. thanks for the help people. 0 Quote Link to comment Share on other sites More sharing options...
Austdata Posted November 9, 2010 Share Posted November 9, 2010 The cron daemon, crond, was probably having a hissy fit and needed restarting. There are some important technical points that need to be explained. Hissy fit is a real Unix error. Like cannot stat and panic, double panic and the ubiquitous triple panic. Restarting something in Unix or any Unix like operating system is the official debug and fix soloution and one never, ever need look any further into a problem. I started in computing 30 years ago when operating systems were stable, bugs were fixed and Microsoft hadn't poisoned everyone's expectation in computing. I miss those days. 0 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.