Page 1 of 1

Search service status

Posted: Thu May 08, 2008 10:10 pm
by wa5rrh
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..."

10061

Posted: Fri May 09, 2008 2:10 am
by seaniekaye
Yup, I'm getting that too : (

Posted: Fri May 09, 2008 5:09 am
by dwhite32
same here

Posted: Fri May 09, 2008 2:43 pm
by prusiner
Me too

Posted: Fri May 09, 2008 6:08 pm
by dengle
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.

Posted: Fri May 09, 2008 8:54 pm
by bassie
maybe something still wrong?

Because it does not seem to work here at the moment.

8)

Posted: Fri May 09, 2008 9:01 pm
by jdr1700
Yeah - it's still broke.

24+ hours now?

Posted: Fri May 09, 2008 9:48 pm
by dengle
ah, I missed the start time. I thought it was due to the power outage at my location. Researching the cause.

Posted: Fri May 09, 2008 10:20 pm
by jdr1700
Just out of curiosity, what is the general location of the servers and of the people who fix things when they break?

Server outage

Posted: Sat May 10, 2008 12:13 am
by mrw02536
Any further word on the outage - I'm still getting a "time-out" on my searches?

Posted: Sat May 10, 2008 1:50 am
by alex
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.