I let the search sit for a while and it did finally return an error:
"Search failed Select timeout error"
Search timeout (external en route connectivity problem)
yes i later realized you can check only one case.
if it is backup server and not both i could engage backup server only but it would be 50 day retention (need to restart it in the backup mode), but most users can access everything without problem, it is not a server problem affecting everyone.
i think the problem should be gone by itself as connectivity has been restored.
if it is backup server and not both i could engage backup server only but it would be 50 day retention (need to restart it in the backup mode), but most users can access everything without problem, it is not a server problem affecting everyone.
i think the problem should be gone by itself as connectivity has been restored.
The proxy you PMed is hanging for a while then timing out.
I think there is just a problem somewhere in the route to the server, that would explain why it works for some. Like you said, it will probably clear itself up in a while.
I appreciate all your help, let me know if there is anything else you'd like to test. If not, I'll post tomorrow and let you know if it's back up.
Thanks again for all,
John
I think there is just a problem somewhere in the route to the server, that would explain why it works for some. Like you said, it will probably clear itself up in a while.
I appreciate all your help, let me know if there is anything else you'd like to test. If not, I'll post tomorrow and let you know if it's back up.
Thanks again for all,
John
if tests were done right
hang when testing through hosts file means you are not able to connect to the other server.
hang when testing through the proxy means you are not able to connect to the backup server as well (it is completely different physical location).
also it cannot be dns caching on your computer since you were able to make a short search.
need to wait maybe it will clears out until tomorrow.
hang when testing through hosts file means you are not able to connect to the other server.
hang when testing through the proxy means you are not able to connect to the backup server as well (it is completely different physical location).
also it cannot be dns caching on your computer since you were able to make a short search.
need to wait maybe it will clears out until tomorrow.
good. i got confirmation it works from elsewhere as well. so connectivity is restored, it is first time it happened with a route to the server (added in august).
as to the test through proxy i now found out search service doesn't go through the local proxy, checked it in debug, since our results were too weird, almost contradictory. the china proxy wasn't functional, it was only accepting connections, i just was thinking it goes through proxy here when it didn't, - it always used direct connection instead which was working from here all the time.
as to ability to go through proxy - maybe i'll add check box in the search section in properties (or better in proxy section since almost noone would use it, or just go through the local proxy always) to make it definite, the standard provision in the current code is local+access proxies, it is just not engaged.
so in fact the backup server was ok, but only the connectivity to the other server has been affected/congested, probably some major backbone on the way to the server ISP.
as to the test through proxy i now found out search service doesn't go through the local proxy, checked it in debug, since our results were too weird, almost contradictory. the china proxy wasn't functional, it was only accepting connections, i just was thinking it goes through proxy here when it didn't, - it always used direct connection instead which was working from here all the time.
as to ability to go through proxy - maybe i'll add check box in the search section in properties (or better in proxy section since almost noone would use it, or just go through the local proxy always) to make it definite, the standard provision in the current code is local+access proxies, it is just not engaged.
so in fact the backup server was ok, but only the connectivity to the other server has been affected/congested, probably some major backbone on the way to the server ISP.
