robster Posted April 1, 2013 Share Posted April 1, 2013 (edited) I upgrade my WHMCS install to 5.2.2 the oter day and now the daily cron job will not run. If i try to run it manually I get: 500 Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request........ Can anybody suggest what has happened? This cron job has run for many months if not years and has 'survived' a couple of WHMCS upgrades in the past without issue. Thanks. Edited April 1, 2013 by robster SOLVED SOLVED SOLVED 0 Quote Link to comment Share on other sites More sharing options...
LDHosting Posted April 1, 2013 Share Posted April 1, 2013 A 500 error is a generic error message from the webserver and doesn't really give any clues as to the cause. You will need to check your error logs which should shed more light on the issue. 0 Quote Link to comment Share on other sites More sharing options...
robster Posted April 1, 2013 Author Share Posted April 1, 2013 Hi. This is what the server company said: root@vps [/home/xxxxxx/public_html/clientarea/admin]# php -q cron.php Segmentation fault In addition, this is currently generating core dump files, below is the extracted information from them: Core was generated by `/usr/bin/php /home/xxxxxx/public_html/clientarea/admin/cron.php'. Program terminated with signal 11, Segmentation fault. Is this any help? Rob 0 Quote Link to comment Share on other sites More sharing options...
robster Posted April 1, 2013 Author Share Posted April 1, 2013 I got it working by recompiling the php - go figure! 0 Quote Link to comment Share on other sites More sharing options...
october Posted April 1, 2013 Share Posted April 1, 2013 Wish someone could mark threads like this as solved, or even "mistake", cause it wastes time for those of us searching through the forums for real issues. P.S. I'm not faulting the original poster for posting this, I would do the same. Just wish it could be cleaned up, after its discovered that it's not really a WHMCS issue. 0 Quote Link to comment Share on other sites More sharing options...
robster Posted April 1, 2013 Author Share Posted April 1, 2013 Wish someone could mark threads like this as solved, or even "mistake", cause it wastes time for those of us searching through the forums for real issues. P.S. I'm not faulting the original poster for posting this, I would do the same. Just wish it could be cleaned up, after its discovered that it's not really a WHMCS issue. Dear God, it's less than 10 hours since I started this thread. WTF! This was a REAL issue and one that had me stumped for most of the day. This is also not a mistake - I still do not know what caused this issue that I had to recomplile PHP - it could well be a WHMCS issue! but there has hardly been time enough for anybody to comment yet. I would have thought that me stating that I got it working after recompiling PHP would be actually useful in case some other member had this same REAL issue. OK, just for you then SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED SOLVED 0 Quote Link to comment Share on other sites More sharing options...
epretorious Posted April 1, 2013 Share Posted April 1, 2013 Wish someone could mark threads like this as solved, or even "mistake", cause it wastes time for those of us searching through the forums for real issues. P.S. I'm not faulting the original poster for posting this, I would do the same. Just wish it could be cleaned up, after its discovered that it's not really a WHMCS issue. I doubt that it's monitored by WHMCS, but the Forum Help & Reports Forum would probably be the right place to make this suggestion. 0 Quote Link to comment Share on other sites More sharing options...
kokyew Posted May 20, 2013 Share Posted May 20, 2013 This thread has helped me immensely!! Thanks robster 0 Quote Link to comment Share on other sites More sharing options...
robster Posted May 21, 2013 Author Share Posted May 21, 2013 @ kokyew: Glad it was a help to someone - lol. Rob 0 Quote Link to comment Share on other sites More sharing options...
Niclas Posted May 21, 2013 Share Posted May 21, 2013 I got it working by recompiling the php - go figure! Got the same problem after updating. Thanks for the tip, it works fine now. 0 Quote Link to comment Share on other sites More sharing options...
khurramalvi Posted August 16, 2013 Share Posted August 16, 2013 Save my life. I was trying to fix this issue from last three days along with server admin and WHMCS team. WHMCS had no clue about error. I got it working by recompiling the php - go figure! 0 Quote Link to comment Share on other sites More sharing options...
Dicko_md Posted October 5, 2013 Share Posted October 5, 2013 Mine hasnt worked in 5.2.7 is any one else having this issue still ? How did you recompile php via easy apache in whm ? Im upgrading to 5.2.8 but dont expect this to be fixed as its a security fix. Thanks Martyn 0 Quote Link to comment Share on other sites More sharing options...
hemangjoshi37a Posted June 7, 2020 Share Posted June 7, 2020 I have php7.4 please tell me how to recompile it?? I am a noob. Please help me. 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.