December 7, 2006 in Feedback
Hello,I initialized my upgarde from 2.1.7 to 2.2.0 this morning and part-way through the process my server stopped responding. After contacting tech support they were able to reboot the server. I thought perhaps it was an error on their part so I tried to continue the upgrade by manually running the queries one by one. Part way through the queries the server began overloading again and was timing out.So I'm partially through my upgrade and my site is completely down.Does anyone have any idea what could have caused this?Thanks in advance for any help!
Hello,Please submit a ticket so our technicians can respond to your inquiry.Note that if your database is large, the queries may need to be run from the command line.
I have a dumb question.What do you consider to be a "large database"? Mine is just a little over 100MB... and during the upgrade to 2.1.7, it was just around 90MB and ran just fine. So I'm wondering when I should start to consider command-line upgrades.
That is one thing we will clarify in our minor tweaks to upgrader in 2.2.1 actually.
Just an update: We're trying to restore to a DB backup from Dec 5. As of now the forum is not functional as it's half way through the upgrade.I think listing the hardware specs will be helpful.Any idea about possibly implementing some way of fixing this to be able to upgrade? As it stands now I'm pretty much unable to upgrade to the new software.
I have a dumb question.
What do you consider to be a "large database"? Mine is just a little over 100MB... and during the upgrade to 2.1.7, it was just around 90MB and ran just fine. So I'm wondering when I should start to consider command-line upgrades.
I did a test upgrade on a virtual machine on my computer.The database is 700MB and it took about 20 minutes to work, using command line queries. The vm has 256mb RAM.
This topic is now archived and is closed to further replies.
Started 1 hour ago
Started 35 minutes ago
Started 2 hours ago