Jump to content

Upgrade hangs at step2


Pima

Recommended Posts

I attempted to upgrade from v5.3.14 to v6.1.1

I backed up all current files and the DB

I uploaded/overwrote the files with v6.1.1

 

When visiting whmcs-path/install it shows installation/upgrade screen (Step 1),

I am then able to proceed to Step 2 which says

 

Upgrade Your Installation

 

We have detected that you are currently running WHMCS Version 5.3.14

 

This update process will upgrade your installation to 6.1.1

 

But there is no clickable link nor the script proceeds automatically, it just hangs on that page

Step 2

 

What is the Issue if anyone knows

Link to comment
Share on other sites

I also attempted an upgrade by unpacking the full distribution into a folder

adding my configuration.php file

renaming my current folder to something else

renaming the folder containing the full distribution to what the current install was named

loading it in the browser

 

I am presented with the same sequence of events

It proceeds to step 2 - then there is no way to proceed

Link to comment
Share on other sites

Here is what I see

Notice: [color="#FF0000"][b]Undefined index: adminid in /home/account/public_html/secure/init.php on line 0[/b][/color]

Down for Maintenance (Err 3)
We are currently performing maintenance and will be back shortly

Link to comment
Share on other sites

I ended up moving the new files from the subdomain to a directory under the root domain

The upgrade completed

Then moved the files back to the subdomain - as this is where the license is pointed

 

Thank You for chiming in

Link to comment
Share on other sites

I ended up moving the new files from the subdomain to a directory under the root domain

The upgrade completed

Then moved the files back to the subdomain - as this is where the license is pointed

 

Thank You for chiming in

I was going to ask you to check the installer log file it may have further information. :idea:

Link to comment
Share on other sites

  • 4 months later...
I was going to ask you to check the installer log file it may have further information.

 

I have the same problem with getting stuck on step 2. I added `$display_errors = E_ALL;` to my configuration file. The installer log only has:

 

[2016-03-25 12:15:24][WHMCS Installer] DEBUG: Installer bootstrapped []

[2016-03-25 12:15:28][WHMCS Installer] DEBUG: Installer bootstrapped []

[2016-03-25 12:15:28][WHMCS Installer] INFO: Previous install detected []

[2016-03-25 12:15:28][WHMCS Installer] DEBUG: An upgrade from 5.3.14-release.1 to 6.2.2-release.1 will be attempted. []

Link to comment
Share on other sites

  • WHMCS Support Manager

Hi,

Please restore your pre-upgrade backup. Then from the server command line, execute the following command:

 

php -f /path/to/whmcs/install/bin/installer.php -- -u -v

 

Replace /path/to/whmcs with the path of your WHMCS installation.

Please let me know what output you get.

Link to comment
Share on other sites

Thank you for that suggestion! We get actual error messages now:

 

########################################################################
### ERROR ###
########################################################################
Unable to connect to the database. in /public_html/account/includes/classes/WHMCS/Database.php at 0
#0 /public_html/account/includes/classes/WHMCS/Database.php(0): WHMCS\Database::connect()
#1 /public_html/account/includes/classes/WHMCS/Database.php(0): WHMCS\Database->connect()
#2 /public_html/account/includes/classes/WHMCS/Utility/Bootstrap/Installer.php(0): WHMCS\Database->__construct()
#3 /public_html/account/vendor/illuminate/container/Illuminate/Container/Container.php(498): WHMCS\Utility\Bootstrap\Installer::WHMCS\Utility\Bootstrap\{closure}(Object(WHMCS\Container), Array)
#4 /public_html/account/vendor/illuminate/container/Illuminate/Container/Container.php(425): Illuminate\Container\Container->build(Object(Closure), Array)
#5 /public_html/account/vendor/illuminate/support/Illuminate/Support/Facades/Facade.php(208): Illuminate\Container\Container->make('db')
#6 /public_html/account/includes/classes/WHMCS/Installer/Installer.php(0): Illuminate\Support\Facades\Facade::__callStatic('make', Array)
#7 /public_html/account/includes/classes/WHMCS/Installer/Cli/Application.php(0): WHMCS\Installer\Installer->runUpgrades()
#8 /public_html/account/install/bin/installer.php(0): WHMCS\Installer\Cli\Application->upgrade()
#9 {main}

########################################################################

 

I see the 'cannot connect to db' piece. Note that version 5.3.14 is running just fine.

Edited by swinghosting
Add code tag
Link to comment
Share on other sites

  • WHMCS Support Manager

Hi,

Thanks for that information. This sounds like your MySQL user password is using the old_password method.

 

Please change the MySQL user password, update the configuration.php file accordingly, then run the upgrade command again.

This should cause it to be hashed using modern techniques so WHMCS v6.x can connect.

Link to comment
Share on other sites

Yes, that must have been it. The upgrade was successful after creating a new installation, installing, importing the old database, running the upgrade, performing a few db commands manually, then running the upgrade again. Lots of hoops. Guess I'm spoiled by…pretty much every other CMS on the planet with their single-click upgrades.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated