8.0 install timeout

Question

0

8.0 install timeout

Seth Thomas posted 6 Years Ago

This morning I began upgrading to 8.0. Unfortunately 2 hours later it seems the install is hung up. Now when I refresh the browser I'm getting this page...

Updates in Progress...

Our website is unavailable for the moment. We'll be back and running before long so please try again soon.

Thanks for your patience!

I'm assuming the install shouldn't take 2 hours. Any thoughts/suggestions/helps? We're hosted at Winhost.com

Thanks,

Seth

northeastchristian.org

rock.northeastchristian.org

1
- Seth Thomas replied 6 Years Ago
Thanks Jim. I ended up paying Winhost $30 to restore our site from a 12AM backup they did yesterday morning. And its up and running. Lesson learned. Will backup prior to future upgrades.
Edit Answer

Thanks Jim. I ended up paying Winhost $30 to restore our site from a 12AM backup they did yesterday morning. And its up and running. Lesson learned. Will backup prior to future upgrades.
Thanks Jim. I ended up paying Winhost $30 to restore our site from a 12AM backup they did yesterday morning. And its up and running. Lesson learned. Will backup prior to future upgrades.
Thanks Jim. I ended up paying Winhost $30 to restore our site from a 12AM backup they did yesterday morning. And its up and running. Lesson learned. Will backup prior to future upgrades.
Save Cancel
0
- Seth Thomas replied 6 Years Ago
Thanks Jim. I checked that file but nothing was logged since a few weeks ago. Are you suggesting Winhost may be underpowered and something may have happened during the install on their server and it "crashed"?
Edit Answer

Thanks Jim. I checked that file but nothing was logged since a few weeks ago. Are you suggesting Winhost may be underpowered and something may have happened during the install on their server and it "crashed"?
Thanks Jim. I checked that file but nothing was logged since a few weeks ago. Are you suggesting Winhost may be underpowered and something may have happened during the install on their server and it "crashed"?
Thanks Jim. I checked that file but nothing was logged since a few weeks ago. Are you suggesting Winhost may be underpowered and something may have happened during the install on their server and it "crashed"?
Save Cancel
0
- Jim Michael replied 6 Years Ago
I'm mostly grasping at straws since I have no familiarity with your platform. I *have* heard of issues with prior upgrades that went bad because the host didn't have enough memory and/or enough SQL horsepower... but that's pure conjecture. Unfortunately Winhost is not a super-popular platform for running Rock, so you may be the first person to even try it. You might ask in the Rock Slack (https://www.rockrms.com/slack to join) to see if anyone there has tried it, yet.

In any case, I think your system is in a bad state and you'll need to roll back to your backup to 1) get going again, and 2) before you can try again.
Edit Answer

I'm mostly grasping at straws since I have no familiarity with your platform. I *have* heard of issues with prior upgrades that went bad because the host didn't have enough memory and/or enough SQL horsepower... but that's pure conjecture. Unfortunately Winhost is not a super-popular platform for running Rock, so you may be the first person to even try it. You might ask in the Rock Slack (https://www.rockrms.com/slack to join) to see if anyone there has tried it, yet. In any case, I think your system is in a bad state and you'll need to roll back to your backup to 1) get going again, and 2) before you can try again.
I'm mostly grasping at straws since I have no familiarity with your platform. I *have* heard of issues with prior upgrades that went bad because the host didn't have enough memory and/or enough SQL horsepower... but that's pure conjecture. Unfortunately Winhost is not a super-popular platform for running Rock, so you may be the first person to even try it. You might ask in the Rock Slack (https://www.rockrms.com/slack to join) to see if anyone there has tried it, yet. In any case, I think your system is in a bad state and you'll need to roll back to your backup to 1) get going again, and 2) before you can try again.
I'm mostly grasping at straws since I have no familiarity with your platform. I *have* heard of issues with prior upgrades that went bad because the host didn't have enough memory and/or enough SQL horsepower... but that's pure conjecture. Unfortunately Winhost is not a super-popular platform for running Rock, so you may be the first person to even try it. You might ask in the Rock Slack (https://www.rockrms.com/slack to join) to see if anyone there has tried it, yet. In any case, I think your system is in a bad state and you'll need to roll back to your backup to 1) get going again, and 2) before you can try again.
Save Cancel
0
- Seth Thomas replied 6 Years Ago
Jim. I'm a bit "in over my head here." Do you know if I can perform a backup of data now, reinstall Rock... and then update with the new backup... or would I likely have to roll back to a prior backup? Please don't ask why I'm asking that... :-)
Edit Answer

Jim. I'm a bit "in over my head here." Do you know if I can perform a backup of data now, reinstall Rock... and then update with the new backup... or would I likely have to roll back to a prior backup? Please don't ask why I'm asking that... :-)
Jim. I'm a bit "in over my head here." Do you know if I can perform a backup of data now, reinstall Rock... and then update with the new backup... or would I likely have to roll back to a prior backup? Please don't ask why I'm asking that... :-)
Jim. I'm a bit "in over my head here." Do you know if I can perform a backup of data now, reinstall Rock... and then update with the new backup... or would I likely have to roll back to a prior backup? Please don't ask why I'm asking that... :-)
Save Cancel
0
- Jim Michael replied 6 Years Ago
Unfortunately you can't really back up after the fact. And it's important to know/remember that Rock is really two distinct parts: The web server file system, and the database itself. Both must "match" and be the same version for things to run properly. :-/
Edit Answer

Unfortunately you can't really back up after the fact. And it's important to know/remember that Rock is really two distinct parts: The web server file system, and the database itself. Both must "match" and be the same version for things to run properly. :-/
Unfortunately you can't really back up after the fact. And it's important to know/remember that Rock is really two distinct parts: The web server file system, and the database itself. Both must "match" and be the same version for things to run properly. :-/
Unfortunately you can't really back up after the fact. And it's important to know/remember that Rock is really two distinct parts: The web server file system, and the database itself. Both must "match" and be the same version for things to run properly. :-/
Save Cancel

Jim Michael · Accepted Answer · 2018-09-18T12:32-07:00

0

Jim Michael replied 6 Years Ago

Two hours is definitely abnormal and likely indicates something went wrong. First thing I would look at is the exception log under /App_Data/Logs on your Rock file system. That might give you a clue. Can't say for sure, but a likely curlprit is an underpowered server (especially memory) as upgrades can *really* tax a marginal setup.

Question

0

8.0 install timeout

0

1

0

0

0

0