I used the Automatic Plugin and everything seemed to work great UNFORTUNATELY my webhost started shutting down my blog on and off since I did the upgrade 2 days ago. I called them and they pointed me to the logs and it looks like it is an issue with wp-cron. I'm not sure what wp-cron is and what I can do to fix the problem...? Anyone encounter this or have a fix?
Yeah definitely. I encounter the error pretty much every time I make a new post or go back and edit an old post. You can see the error HERE. I called bluehost & they said it was happening do to high cpu usage and pointed me to the logs in my TMP folder. It was being caused by the wp-cron file. Any help is much appreciated.
This happens to me regularly... When I contacted them. this is the reply ...... CPU Quota/Suspension Errors are triggered by a single process taking more than 30 CPU seconds to run or if your total processes take more than 40 CPU seconds in any 60 second window. They are set up like this to avoid server lockups if too many people are logging on to the same server at once. Your site will generally come back up after 5-10 minutes of suspension. If this is a repetetive issue we encourage you to investigate further the reason you are receiving these CPU Quota Suspension/Errors. Please have the Site Administrator or Programer review your log files: You can locate these log files by: * 1. Log into your HostMonster Control Panel. * 2. Locate the Files menu. * 3. Locate and click on the File Manager icon. * 4. When the Directory Selection menu loads select the Home Directory option. * 5. This will take you to the Root(/) directory of your File Manager. * 6. Locate and double click on the tmp folder. * 7. Inside this folder there are two folders that may have information pertaining to this issue; the cpu_exceeded_logs and mysql_slow_queries. * 8. The cpu_exceeded_logs folder will contain individual log files listed in order by date. If you wish to view the details of these log files right click on the file you would like to open and select View from the drop down list. Important: The cpu_exceeded_logs contain important information about which processes you were running and their lengths that co-inside with your cpu exceeded errors. Example: Fri Jul 7 17:07:36 2006: used 716.27 seconds of cpu time for HTTP Request: yourdomain.com: GET /img_yourproducts/shop_images_026.jpg HTTP/1.1 Fri Jul 7 17:07:37 2006: used 0.18 seconds of cpu time for HTTP Request: yourdomain.com: GET /img_yourproducts/shop_images_027.jpg HTTP/1.1 * 9. The mysql_slow_queries folder will contain individual log files listed in order by date. If you wish to view the details of these log files right click on the file you would like to open and select View from the drop down list. Important: The mysql_slow_queries contain important information about which queries you were running and their lengths that co-inside with your mysql_slow_queries errors. These will appear much like the above logs only providing details on your particular mysql queries. This happens for me often .... they say that is due to high running length of the visitor. So I'm also looking for the solution. This is not related to the wordpress upgradation....but is surely because of wordpress mysql files. Ok..Lets solve this problem.