Bom zabbix com 12 servidores OFF todos em dallas softlayer....
E... Até softlayer.com offline:
Location Result Page Size Response time KB/sec IP Partner
Received responses: 4 Ok 47 Fail Average: 0.48 sec 0.00
Scranton, PA, US Ok 0 0.10 sec 0.00 66.228.118.53 TheJetHost.com
Moscow, RU Ok 0 0.81 sec 0.00 66.228.118.53 HOSTLEX
Montreal, CA Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 TUWEBHOST
Minsk, Belarus Ok 0 0.53 sec 0.00 66.228.118.53 BelInfoNet Ltd.
Donetsk, Ukraine Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 HostLife
Falkenstein, German Ok 0 0.47 sec 0.00 66.228.118.53 Hosting Hutor.com
Orlando, FL, US Failure("Domain lookup failure:softlayer.com Exception:Not_found") Apto Hosting
Moscow, Russia Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 10.05 sec 66.228.118.53 JustHost
Haarlem, Netherlands Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 33.01 sec 66.228.118.53 Steadyhost
Muenchen, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 PersianWhois
Medan, Indonesia Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 Rajawali Nusa Media
Nuremberg, Germany Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 21.00 sec 66.228.118.53 OneTux.org
Kansas City, MO, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 HostPojok.Com
Dallas, TX, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 80.50 sec 66.228.118.53 Provisov.Net
Kiev, Ukraine Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Network is unreachable") 0.00 sec 66.228.118.53 ABCname
London, UK Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 29.01 sec 66.228.118.53 VirtualSplits
SPb, RU Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 51.56 sec 66.228.118.53 SpaceWeb
Kiev, Ukraine Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 GiperHost
Falkenstein, Germany Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 24.94 sec 66.228.118.53 GEM Hosting
Kiev, Ukraine Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 21.45 sec 66.228.118.53 ITQua
Nuremberg, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 VPS-server.ru
Gunzenhausen, Germany Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 aBajt
Fort Lee,NJ,US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 ProGoldHost.net
Amsterdam, Netherlands Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 23.08 sec 66.228.118.53 PDhost
Kharkiv, Ukraine Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 ITL
Nuremberg, Germany Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 24.99 sec 66.228.118.53 Sunny Hosting
Seattle, WA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 OH Web Hosting
Montreal, Quebec, Ca Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 XP-Hosting.com
Amsterdam, Netherlands Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 Hostmaster, Ltd.
Kansas City, MO, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 JWN Media
Montreal, Quebec, Ca Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 NordGate networks
Lansing, MI, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.00 sec 66.228.118.53 Rioserver
Fremont, CA, US Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 21.00 sec 66.228.118.53 IndoNet, Inc.
Kiev, Ukraine Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 21.99 sec 66.228.118.53 Hvosting
Scranton, PA, US Http error:Http_client.Bad_message("Unknown reason (e.g. unexpected eof, timeout)") 40.08 sec 66.228.118.53 Valkira
Atlanta, GA, US Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 20.99 sec 66.228.118.53 MoonSoft Systems
East Lansing, MI, US Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 21.00 sec 66.228.118.53 NIMHOST
Riga, Latvia Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 21.00 sec 66.228.118.53 EuroBit.EU
Moscow, Russia Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:No route to host") 2.05 sec 66.228.118.53 NTCom LLC
London, UK Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:No route to host") 0.00 sec 66.228.118.53 HostLinc
Hampshire, UK Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 21.00 sec 66.228.118.53 PremiumReseller
Amsterdam, Netherlands Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:No route to host") 3.00 sec 66.228.118.53 ServerClub
SPb, Russia Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Network is unreachable") 0.00 sec 66.228.118.53 Indahost
Moscow, Russia Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 23.01 sec 66.228.118.53 OpenHosting
Erfurt, Germany Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 21.00 sec 66.228.118.53 VHosting Solution LLC
Tarnowskie Gory, Poland Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Network is unreachable") 4.03 sec 66.228.118.53 aBajt
Frankfurt, Germany Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 9.02 sec 66.228.118.53 SarTelekom.ru
Bloomsburg, PA, US Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 21.00 sec 66.228.118.53 indonetmedia
Gdansk, Poland Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:No route to host") 3.00 sec 66.228.118.53 HCX Hosting
Toronto, ON, CA Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Connection timed out") 21.00 sec 66.228.118.53 OnyxNetUa
Zaporozhye, Ukraine Http error:Unix.Unix_error(_, "check_connect", "softlayer.com:80:Network is unreachable") 0.00 sec 66.228.118.53 Alpha V

Page 1 of 1
Softlayer OFFLINE Dallas offline inclusive softlayer.com
#2
Posted 13 setembro 2011 - 01:51
Ola,
Gostaria de entender como isto pode acontecer!
Os DC´s vendem idéais de terem vários serviços de "Redundância" etc e tal mas como pode ficar totalmente fora do ar ?
Obrigado
Gostaria de entender como isto pode acontecer!
Os DC´s vendem idéais de terem vários serviços de "Redundância" etc e tal mas como pode ficar totalmente fora do ar ?
Obrigado
#3
Posted 13 setembro 2011 - 04:54
Pelo erro "Network is unreachable" parece erro de roteamento (provavelmente alguma zica com o router(s) BGP deles).
Pode acontecer... se configurar algo errado pode parar tudo, não importando o nível de redundancia.
Pode acontecer... se configurar algo errado pode parar tudo, não importando o nível de redundancia.
#4
Posted 10 outubro 2011 - 06:37
Pois é, mas pelo meu ponto de vista isso não deveria acontecer.
Para que tantos níveis de redundância e sistemas de segurança se um DC fica fora do ar.
Se cai um servidor entra outro e por ai vai.
Se fosse devido a alguma catástrofe natural até vai.
Não sou entendido, apenas é meu ponto de vista pois para o tipo de serviço prestado não deveria ocorrer isto em nenhum DC de primeira qualidade mas acontece.
Flw
Para que tantos níveis de redundância e sistemas de segurança se um DC fica fora do ar.
Se cai um servidor entra outro e por ai vai.
Se fosse devido a alguma catástrofe natural até vai.
Não sou entendido, apenas é meu ponto de vista pois para o tipo de serviço prestado não deveria ocorrer isto em nenhum DC de primeira qualidade mas acontece.
Flw
Share this topic:
Page 1 of 1

Help










