Getting the "System: 10061" message again....
I can ping ueservice and ueservice2, and telnet to ueservice
Telnet to ueservice2 fails - "Could not open a connection to the host..."
Search service status
Power outage struck due to severe weather at approximately 11:30AM GMT -5.
That wouldn't be too bad as the servers do have a battery backup which lasts about 1 to 2 hours. About 10 minutes into the power outage however, the internet service stopped as well. Power and internet just came on about 5 minutes ago.
Servers are both starting back up and search service should be operational in about another 5 to 10 minutes.
That wouldn't be too bad as the servers do have a battery backup which lasts about 1 to 2 hours. About 10 minutes into the power outage however, the internet service stopped as well. Power and internet just came on about 5 minutes ago.
Servers are both starting back up and search service should be operational in about another 5 to 10 minutes.
Server outage
Any further word on the outage - I'm still getting a "time-out" on my searches?
there was unrelated power outage at another server location due to a mechanical failure on a power plant about 28 hours ago.
there was noone to restart it right away and i wasn't notified in time (i'm not in place until May, 15 since work on v2.0 left some matters unattended which i have to take care of now). startup menu was somehow empty for that intance since i had to move database after one drive failed, i now set it up right, otherwise it would work 7 hours ago when the instances were restarted manually but not right which left one listening socket non-binded (with the instance still processing headers).
when i'm back i'll set up automated alert system so i'll be notified promptly if servers are down, the work on v2.0 is finished so i have time for that now.
there was noone to restart it right away and i wasn't notified in time (i'm not in place until May, 15 since work on v2.0 left some matters unattended which i have to take care of now). startup menu was somehow empty for that intance since i had to move database after one drive failed, i now set it up right, otherwise it would work 7 hours ago when the instances were restarted manually but not right which left one listening socket non-binded (with the instance still processing headers).
when i'm back i'll set up automated alert system so i'll be notified promptly if servers are down, the work on v2.0 is finished so i have time for that now.