genious Posted April 22, 2013 Share Posted April 22, 2013 Hello, We opened a ticket 10 days ago ( #SBD-267211 ) regarding the cron not executing, the problem happened 18th March just after the upgrade, the latest cron was executed 17th March, so as you know, the cron hasn't been running for over a month now. It means that our clients don't get any notice regarding their renewal, no account is being suspended, so we are LOOSING MONEY, and we also have expiring domain names without notices to our clients. I want you to SERIOUSLY consider this thread, because it's been over a week that I'm being ignored like it's my fault or something. We can't take this any longer, your support is getting worse day after day. I'm expecting this issue to be resolved and not just getting an answer saying that we are investigating the issue as it's been 10 DAYS now that you're aware of this. The new ticket id we just opened is #UCG-877488 Thank you, 0 Quote Link to comment Share on other sites More sharing options...
durangod Posted April 22, 2013 Share Posted April 22, 2013 (edited) I just updated from 5.1.3 to 5.1.5 and then to 5.2.3 and all of it was done yesterday and my cron ran just fine last night, well i dont know honestly about overdue invoices or suspensions because i had none. Very strange yes i hope you get this corrected Edited April 22, 2013 by durangod 0 Quote Link to comment Share on other sites More sharing options...
gerrybakker Posted April 25, 2013 Share Posted April 25, 2013 The solution to this problem was too easy - all I had to do was "save" the "Setup/Automation Settings" to make things work again. Apparently a number of flags changed in the WHMCS back end and nobody at WHMCS bothered to let us all know that we should be re-saving our settings to rewrite those variables so the new CRON.php would know what to do with them. It was "segfaulting" when the cron job ran before those settings were saved. Once settings were re-saved the cron job performed perfectly. WHMCS developers should have anticipated this and forced a re-save of those settings during the upgrade process to 5.2.X to prevent this horrifying result. I'm glad it was easy to resolve. 0 Quote Link to comment Share on other sites More sharing options...
muntazir Posted May 3, 2013 Share Posted May 3, 2013 I have the same issue. I have opened the ticket but havent received any satisfactory result yet. As per the above info i have saved the "Setup/Automation Settings" but still the cron does not get saved. I have upgraded from 5.1 to 5.2.4. The cron was running fine on 5.1 but as soon as i upgraded to 5.2.4 it stopped. Even when i run that cron via browser, it gives me the fllowing error. my ticket number is VKL-377961 Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, webmaster@------- and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request. 0 Quote Link to comment Share on other sites More sharing options...
Damo Posted May 4, 2013 Share Posted May 4, 2013 What's in your error logs? Seeing it's a 500 error being generated your logs will tell you more about it. Probably a permissions setting on the file. 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.