- Status Closed
- Percent Complete
- Task Type Bug Report
- Category Engine → Misc
-
Assigned To
Tristan Cragnolini - Operating System
- Severity Low
- Priority
- Reported Version
- Due in Version Undecided
-
Due Date
Undecided
- Votes
- Private
Opened by Elvors Amenoras - 03.05.2008
Last edited by Lanarel - 16.08.2009
FS#1465 - Client fails to detect if server becomes available again
How to reproduce:
Boot client machine while disconnected from the network.
Start PS client.
Client lists the Fragnetics server as “Failed” (OK).
Reconnect client to network.
Client continues to list Fragnetics as “Failed”. It should detect that the server has become available.
Workaround:
Restart client.
Speculation:
I suspect this is because the client caches the response of the initial DNS query, which returns NXDOMAIN in the described situation.
An alternative cause might be that the networking code somehow already knows the IP address but gives up permanently due to a “no route to host” error message.
Suggestion:
Make the networking code generally re-request DNS information whenever the server becomes unreachable.
This would not only cover the situation described above, but would also remove one obstacle to running the PS server on a dyndns-managed host.
| ID | Project | Summary | Priority | Severity | Assigned To | Progress | |
|---|---|---|---|---|---|---|---|
| 1808 | PlaneShift | Critical |
16.08.2009 09:50
Reason for closing:
Additional comments about closing:
Fixed by Kougaro
I've seen this before.
Me too, I have to relaunch PS in order to look again for server.
I did a search before posting my duplicate report, but didn't find anything related.
Anyhow, it isn't only related to not being connected to the Internet, it happens often when the server crashes, with the person having had an Internet connection the whole time.
I'll paste in the
FS#1808, it is short:— Very often when the login screen receives a "Failed" to connect status, it will never again check to see if the server is back.
This hasn't caused me problems personally, as I figured this out years ago and simply restart the client every time I get a "Failed" message.
However I've often waited half an hour or more for other people to connect, who are sitting there waiting for the server to come back on… but it never will show up. Only once they restart their PlaneShift does it show it as available again.
—
It also relates to the
FS#1807feature request about an option to automatically reconnect after the server crashes. I recommended having the client recheck server status every 30 seconds + randomly picked 1 to 20 seconds.At the very least there should be a button to manually recheck the server, in the login window. Currently there is no way to do that without restarting PlaneShift.
I second Qia's feature request.
assigning Kougaro
Fixed in r4060
Not fixed.
I did as above:
- switched of LAN
- REBOOTED computer. THis may be essential in this test
- started client. All servers fail. Especially not the messages in the console that laanx.fragnetics.com etc could not be resolved.
- reconnected network.
- still all fails.
So there should be a sort of retry on resolving.
Retested today with the same steps, and it now works.