Forums » Bugs
Update server connection error
Just had this error and could not connect for 10 min.
Error message:
Connecting to cloud.patchstorm.com:21024... Connection timeout!
Connecting to update2.vendetta-online.com:21024...
getaddrinfo error: nodename nor servname provided, or not known Connection timeout!
Can't reach any Guild Software update server!
After 10 min I managed to establish connection:
Connecting to cloud.patchstorm.com:21024...
Connection timeout!
Connecting to update2.vendetta-online.com:21024...
Latest version: vendetta-1.8.351
Version is current; verifying files...
Connecting to cloud.patchstorm.com:21024...
Connection timeout!
Connecting to update2.vendetta-online.com:21024...
Welcome to Vendetta Online 1.8.351
Error message:
Connecting to cloud.patchstorm.com:21024... Connection timeout!
Connecting to update2.vendetta-online.com:21024...
getaddrinfo error: nodename nor servname provided, or not known Connection timeout!
Can't reach any Guild Software update server!
After 10 min I managed to establish connection:
Connecting to cloud.patchstorm.com:21024...
Connection timeout!
Connecting to update2.vendetta-online.com:21024...
Latest version: vendetta-1.8.351
Version is current; verifying files...
Connecting to cloud.patchstorm.com:21024...
Connection timeout!
Connecting to update2.vendetta-online.com:21024...
Welcome to Vendetta Online 1.8.351
Same
What OS?
Does a reboot resolve the issue?
Does a reboot resolve the issue?
I use an Android 4.4.4 KitKat
No, reboot doesn't resolve the issue
No, reboot doesn't resolve the issue
OSX, reboot did not resolve the issues but I suspect it was related to part of the cloud going down, noticed I also lost connection to dropbox server too and it became available again in about 20 min.
So, the weird thing here is the degree of failure. The first patchstorm.com cloud uses a few dozen nameservers, co-located around the world. But, hey, ok, a failure is possible. That's why we have a fallback system.
But the second vendetta-online.com host is served by our internal nameservers, with the primary in milwaukee and the secondary in manhattan, both on completely unrelated and diverse network connections. They have nothing to do with the patchstorm stuff, at all.
The chances of all of them accidentally failing is.. extremely unlikely. On the order of "the whole freaking internet is down".
However, if your local network(s) prevented you from reaching your device/computer's configured nameservers for a period of time (even a few seconds), this same visible "issue" would happen. But it would be local to you (or your device, even).
Bojan's comment about a dropbox going away at the same time would lend support to this.
The suspicious thing is two reports coming from opposite sides of the planet on the same day. I mean, there's always the possibility of a bug in the game updater, but it would be.. a little surprising, as we specifically wrote this stuff to be as bulletproof-simple as possible, and tested the living hell out of it prior to release.
Huge, international network problems also can happen (daily). But, I checked NANOG and other sources of "what's broken on the internet now?", and didn't see anything particularly relevant standing out.
On the other hand, this improved updater is relatively a new experience for people, launched only in the last couple of months. So, where the old updater would have just stalled-out and frozen if it couldn't look up the server(s), the new one times out and shows errors. So, this "problem" could actually be the unfamiliarity of these errors, just giving more information that seems like a "new issue" but is actually just behaving in a better way about an "existing issue".
So, I guess I would say.. please keep an eye on this. Post if it keeps happening. But when it does happen, try and use the web to go to a new site you haven't visited before (something that your device's nameservice has not looked up recently, and thus won't be cached.. maybe try googling some weird random search terms, and going to sites you've never heard of). If that fails, you have a bigger problem than just us, and the updater is simply doing its job and telling you that there is a network issue of some kind.
But the second vendetta-online.com host is served by our internal nameservers, with the primary in milwaukee and the secondary in manhattan, both on completely unrelated and diverse network connections. They have nothing to do with the patchstorm stuff, at all.
The chances of all of them accidentally failing is.. extremely unlikely. On the order of "the whole freaking internet is down".
However, if your local network(s) prevented you from reaching your device/computer's configured nameservers for a period of time (even a few seconds), this same visible "issue" would happen. But it would be local to you (or your device, even).
Bojan's comment about a dropbox going away at the same time would lend support to this.
The suspicious thing is two reports coming from opposite sides of the planet on the same day. I mean, there's always the possibility of a bug in the game updater, but it would be.. a little surprising, as we specifically wrote this stuff to be as bulletproof-simple as possible, and tested the living hell out of it prior to release.
Huge, international network problems also can happen (daily). But, I checked NANOG and other sources of "what's broken on the internet now?", and didn't see anything particularly relevant standing out.
On the other hand, this improved updater is relatively a new experience for people, launched only in the last couple of months. So, where the old updater would have just stalled-out and frozen if it couldn't look up the server(s), the new one times out and shows errors. So, this "problem" could actually be the unfamiliarity of these errors, just giving more information that seems like a "new issue" but is actually just behaving in a better way about an "existing issue".
So, I guess I would say.. please keep an eye on this. Post if it keeps happening. But when it does happen, try and use the web to go to a new site you haven't visited before (something that your device's nameservice has not looked up recently, and thus won't be cached.. maybe try googling some weird random search terms, and going to sites you've never heard of). If that fails, you have a bigger problem than just us, and the updater is simply doing its job and telling you that there is a network issue of some kind.