Beta Update issue

[DM|Mag]

Now that I've gotten the right link and found my key and such, I hit "Update" as it was a big red thing, it's been doing it's thing for about 25 minutes. I come back:

"Checking package 3.5E for updates
3.5E updating
Error: Cannot Resolve destination host
3.5E Decompression"

"Update Progress (3.5E): (3/16)"

Please Advise what to do.

Full Log: Attached

[deer_buster]

Yep, database is overloaded with requests right now

[DM|Mag]

Yeah I figured it might be that, but in case not, should post the log.

[deer_buster]

I blame Zacchaeus' proclivity for downloading haggis prep videos over the SW network for the problems.

[Zacchaeus]

I resemble that! :D

[DM|Mag]

Those hill folk and their haggis. Smh.

[DM|Mag]

Hah! I've got prep to do for campaigns, so I'll wait patiently then!

[deer_buster]

Might have been better to release beta AFTER the weekly update tomorrow, like by 1 or 2 days...this might be an ongoing problem

[DM|Mag]

I'll just leave it running on a 3rd monitor and see if it solves itself. >.<

[GKEnialb]

It keeps hanging for me, with this in the logs:

30 Response received: Could not connect to the database
e: HandlePackage - Could not parse manifest: Could not connect to the database

Figure it's the same as the above - would be good to have that in the status of the UI and/or the ability to retry without stopping and restarting.

[DM|Mag]

I ran out for a 6 pack to glare at the bar properly with. Cheers.

[ddavison]

We are going to take the new updater server offline to resize it and then we will bring it back online. Expected downtime is 10-20 minutes. If you can wait a few hours (or tomorrow) to retry that would be even better.

[DM|Mag]

Thanks for the update, will do. I can check tomorrow, have a good night man!

[Stadlerc]

They might want to think about creating an update queue if the servers become overwhelmed..

[Zetesofos]

Error: HTTP/1.1 521 Unknown HTTP status
Beginning Update

I'm presumming this is also a "too many people trying to update" error?

[kalmarjan]

We are going to take the new updater server offline to resize it and then we will bring it back online. Expected downtime is 10-20 minutes. If you can wait a few hours (or tomorrow) to retry that would be even better.

That explains why it suddenly hung on me. I'll wait for tomorrow. So EXCITED!

[Eru the One]

We are going to take the new updater server offline to resize it and then we will bring it back online. Expected downtime is 10-20 minutes. If you can wait a few hours (or tomorrow) to retry that would be even better.

@Zetesofos Probably down right now

[Stadlerc]

If all else fails.. we have discovered that FGU is subject to DDoS attacks threw the update mechanism

[Gezzer]

It would be nice if the updater was a bit more newb user friendly. I more than understand how the servers are being hammered due to the release, But even then, a staggered release might of been a better idea to mitigate that somewhat.
My problem was I waited an hour until it even occurred to me to check the logs. And even then I had to Google to find out what was happening. Not everyone is a server admin you know. An actual error code instead of looking like it had froze would of been nice.

Speaking about freezing, the updater actually does freeze when I cancel the update and the only way to fix it is to close the program. I know betas are supposed to be rough and all, but this rough?

[ddavison]

The new update server is now online.

[DM|Mag]

Testing, and it hung a few min on one ruleset, but completed fine thanks! Will look into it soon as it's late.