https://discord.umbraco.com logo
Join Discord
Powered by
Umbraco upgrade v10 - v13 Timeouts and errors Azur...
# help-with-umbraco
s
I keep hitting 500 - The request timed out. The web server failed to respond within the specified time. Can anyone explain 1) The process continues even if I see the error on the front end (I think it does from the logs) 2) If it does continue will it complete succcessfully - I can't seem to wait long enough 3) If I hit the /install again what happens - will it pickup from where it left off or start again. Can I cause database issues? 4) I assume I'm hitting the 240 seconds Azure hard timeout - if this is the case shouldn't the upgrader break the task into smaller chunks so one request doesn't do the full upgrade?! If anyone has any tips on how to get around some of this I'd be keen to hear.
s
Never seen this and the installer doesn't even take 240 seconds on my slowest Raspberry Pi. 😅 Try an unattended install as well, I would guess that would time out too, as it seems to me that something else is wrong.
s
Not sure it's wrong - just big databases! These are clean v10s upgraded to v13. The common thing is Azure - they take time locally but always complete. I know Azure has a hard command timeout.
s
Ah, you said it was installing, which means an empty db to me 😂
Still, unattended upgrades could help, but in this case I'd start with doing the upgrade on my local machine, with the connection string set to the remote database.. easier to debug.
> shouldn't the upgrader break the task into smaller chunks so one request doesn't do the full upgrade?! It's already doing them in the smallest chunks, but databases can be huge - we need to be able to rollback if something fails, which means we need to do certain things in a transaction, with a lot of data, everything needs to be migrated in 1 transaction, which can take a long time.
Oh, maybe before you try anything else, try and really beef up the SQL Azure database so that it can go full steam ahead instead of being limited and slowed down. Remember to turn it back down to normal after so you don't run into wild costs.
s
I did boost them but I'll go bigger. Looking forward to a 6am start to do this now.
Gave the big DBs all the DTUs and it worked much more smoothly. Only checked 7 times that I'd scaled it back down again. there were a lot of zeros on that monthly estimate...
s
Yay, so glad to hear!!
Ps. Did you check one more time you scaled it back? 😉
k
We only use SQL Server in VMs and containers for Umbraco Azure (cost being the main reason). Besides upgrades, there's not much SQL activity at all for our Umbracos.
s
Yes - Azure SQL seems very expensive and very hobbled for what you get. I kinda miss VM SQL Server.
s
I think you could change perspective and say it's appropriately limited until you need more power. And if you have many SQL Azure databases you can put them in a pool that will balance the load where needed without paying so much (I believe that's how Umbraco Cloud still does it to keep the costs low for us).
As @kdx-perbol says - if you're not upgrading, SQL is really not doing anything.. maybe if you publish a lot.. so you can dial it all the way down most of the time.
s
Hmm does seem to get very pricey very quickly though. Mine (well client's) sites are basically ecommerce. So lots of basket work - the db does some lifting. I have on my list of improvements to separate these into a different DB (and eventually not DB).
Just checking again
j
Umbraco upgrades are extremely database intensive - we should probably put that in the docs.
134 Views
PreviousNext
Powered by