SugarCRM Upgrade Frozen?

sugarcrmdevelopers —  October 26, 2011

SugarCRM Upgrades often mention that, well, they can take a while. But recently I got the feeling that it was simply taking too long and must have crashed behind-the-scenes somewhere. Where can we check? We definitely don’t want to interrupt the process, in case it is progressing as normal. Here’s the trick I found: the Sugar Upgrade process will generate a log file, typically upgradeWizard.log found within the SugarCRM installation’s root directory.

Upgrade may take some time

This file, as you might imagine, logs the upgrade process step-by-step. If you’re not familiar with the process’s messages (like myself…) open the file and check the line number of the bottom-most line. Then close and reopen the file (or simply reload, if your editor supports it) and check again. If they differ, you know you’re making progress.

For the record, the last several lines of the updater process (before the clean-up actions, but after the database changes are made) will look like this:

Sun, 23 Oct 2011 19:29:54 -0400 [UpgradeWizard] - post_install() done.
Sun, 23 Oct 2011 19:29:54 -0400 [UpgradeWizard] - check to see if new modules exist
Sun, 23 Oct 2011 19:29:54 -0400 [UpgradeWizard] - new modules to add are array (
)
Sun, 23 Oct 2011 19:29:54 -0400 [UpgradeWizard] - module tabs updated
Sun, 23 Oct 2011 19:29:54 -0400 [UpgradeWizard] - Registering upgrade with UpgradeHistory
Sun, 23 Oct 2011 19:29:55 -0400 [UpgradeWizard] - Resetting error_reporting() to system level.
Sun, 23 Oct 2011 19:30:34 -0400 [UpgradeWizard] - setting session variables...
Sun, 23 Oct 2011 19:30:37 -0400 [UpgradeWizard] - [At end.php]
Sun, 23 Oct 2011 19:30:37 -0400 [UpgradeWizard] - Start Rebuilding the config file again
Sun, 23 Oct 2011 19:30:37 -0400 [UpgradeWizard] - Finish Rebuilding the config file again

Be patient during the process but if you do find yourself timing out and having issues, try the silent-upgrade scripts.

upgrade debrief message