Start ArchiveToBoulder.bash Wed Jun 16 02:00:01 UTC 2010 Sending log files to Boulder ssh: connect to host 140.172.38.113 port 22: Connection timed out lost connection Sending quicklooks to Boulder CAPABL20100615quicklook.jpg Sending quicklooks to Boulder smtmmcrm3ql.20100615.000000.png Sending summary files to Boulder smtqclog.20100615.000000.txt Sending Radiosonde dc3db files to Boulder SMT_20100614_233520.dc3db SMT_20100615_111918.dc3db No Radiosonde edt files Sending Radiosonde wmo file to Boulder BGST100608105131.wmo Read from socket failed: Connection reset by peer lost connection BGST100608132222.wmo BGST100609015451.wmo BGST100609155534.wmo BGST100610012426.wmo Read from remote host 140.172.38.113: Connection reset by peer ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection BGST100613005833.wmo BGST100613154941.wmo Read from socket failed: Connection reset by peer lost connection BGST100614010010.wmo Connection closed by 140.172.38.113 lost connection BGST100614134918.wmo Start ArchiveToBoulder.bash Wed Jun 16 03:00:01 UTC 2010 Sending log files to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Did not send quicklooks to Boulder Did not send quicklooks to Boulder Did not send summary files to Boulder No Radiosonde dc3db files No Radiosonde edt files Sending Radiosonde wmo file to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Read from remote host 140.172.38.113: Connection reset by peer lost connection BGST100611014150.wmo BGST100611131433.wmo Start ArchiveToBoulder.bash Wed Jun 16 04:00:01 UTC 2010 Sending log files to Boulder Icecaps.20100615.log Did not send quicklooks to Boulder Did not send quicklooks to Boulder Did not send summary files to Boulder No Radiosonde dc3db files No Radiosonde edt files Sending Radiosonde wmo file to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Sending MWR files to Boulder reverse mapping checking getaddrinfo for tiksiingest.esrl.noaa.gov failed - POSSIBLE BREAK-IN ATTEMPT! 10061500.ATN.NC 10061500.BRT.NC Read from remote host 140.172.38.113: Connection reset by peer lost connection Start ArchiveToBoulder.bash Wed Jun 16 05:00:01 UTC 2010 Did not send log files to Boulder. Did not send quicklooks to Boulder Did not send quicklooks to Boulder Did not send summary files to Boulder No Radiosonde dc3db files No Radiosonde edt files Sending Radiosonde wmo file to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Sending MWR files to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Connection closed by 140.172.38.113 lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection 10061501.LV0.NC Read from remote host 140.172.38.113: Connection reset by peer 10061501.MET.NC ssh: connect to host 140.172.38.113 port 22: Connection timed out lost connection 10061501.SL.HKD.NC Read from remote host 140.172.38.113: Connection reset by peer lost connection Read from socket failed: Connection reset by peer lost connection Connection closed by 140.172.38.113 lost connection 10061502.BRT.NC ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection 10061504.MET.NC 10061504.SL.HKD.NC 10061505.ATN.NC 10061505.BRT.NC Read from socket failed: Connection reset by peer lost connection Read from socket failed: Connection reset by peer lost connection 10061505.IRT.NC 10061505.LV0.NC 10061505.MET.NC Read from socket failed: Connection reset by peer lost connection 10061505.SL.HKD.NC 10061506.ATN.NC 10061506.BRT.NC Start ArchiveToBoulder.bash Wed Jun 16 06:00:01 UTC 2010 Did not send log files to Boulder. Did not send quicklooks to Boulder Did not send quicklooks to Boulder Did not send summary files to Boulder No Radiosonde dc3db files No Radiosonde edt files Sending Radiosonde wmo file to Boulder BGST100610135730.wmo BGST100612005410.wmo Read from socket failed: Connection reset by peer lost connection Start ArchiveToBoulder.bash Wed Jun 16 07:00:01 UTC 2010 Did not send log files to Boulder. Did not send quicklooks to Boulder Did not send quicklooks to Boulder Did not send summary files to Boulder No Radiosonde dc3db files No Radiosonde edt files Sending Radiosonde wmo file to Boulder BGST100612140142.wmo BGST100615010923.wmo BGST100615140320.wmo Sending MWR files to Boulder 10061500.HKD.NC 10061500.IRT.NC 10061500.LV0.NC 10061500.MET.NC 10061500.SL.HKD.NC 10061501.ATN.NC 10061501.BRT.NC 10061501.HKD.NC 10061501.IRT.NC 10061502.ATN.NC 10061502.HKD.NC 10061502.IRT.NC 10061502.LV0.NC 10061502.MET.NC Start ArchiveToBoulder.bash Wed Jun 16 08:00:01 UTC 2010 Did not send log files to Boulder. Did not send quicklooks to Boulder Did not send quicklooks to Boulder Did not send summary files to Boulder No Radiosonde dc3db files No Radiosonde edt files No Radiosonde wmo files Sending MWR files to Boulder 10061502.SL.HKD.NC Read from socket failed: Connection reset by peer lost connection Read from remote host 140.172.38.113: Connection reset by peer 10061503.ATN.NC 10061503.BRT.NC 10061503.HKD.NC 10061503.IRT.NC Start ArchiveToBoulder.bash Wed Jun 16 09:00:01 UTC 2010 Did not send log files to Boulder. Did not send quicklooks to Boulder Did not send quicklooks to Boulder Did not send summary files to Boulder No Radiosonde dc3db files No Radiosonde edt files No Radiosonde wmo files Sending MWR files to Boulder ssh: connect to host 140.172.38.113 port 22: Connection timed out lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection 10061508.HKD.NC 10061508.IRT.NC 10061508.LV0.NC 10061508.MET.NC 10061508.SL.HKD.NC 10061509.ATN.NC 10061509.BRT.NC Read from socket failed: Connection reset by peer lost connection 10061509.HKD.NC Read from remote host 140.172.38.113: Connection reset by peer lost connection Start ArchiveToBoulder.bash Wed Jun 16 10:00:01 UTC 2010 Did not send log files to Boulder. Did not send quicklooks to Boulder Did not send quicklooks to Boulder Did not send summary files to Boulder No Radiosonde dc3db files No Radiosonde edt files No Radiosonde wmo files Sending MWR files to Boulder Connection closed by 140.172.38.113 lost connection 10061503.LV0.NC 10061503.MET.NC 10061503.SL.HKD.NC ssh_exchange_identification: read: Connection reset by peer lost connection 10061504.ATN.NC 10061504.BRT.NC 10061504.HKD.NC Start ArchiveToBoulder.bash Wed Jun 16 11:00:01 UTC 2010 Did not send log files to Boulder. Did not send quicklooks to Boulder Did not send quicklooks to Boulder Did not send summary files to Boulder No Radiosonde dc3db files No Radiosonde edt files No Radiosonde wmo files Sending MWR files to Boulder 10061504.IRT.NC 10061504.LV0.NC 10061505.HKD.NC 10061506.HKD.NC 10061506.IRT.NC Read from remote host 140.172.38.113: Connection reset by peer lost connection 10061506.LV0.NC 10061506.MET.NC 10061506.SL.HKD.NC 10061507.ATN.NC 10061507.BRT.NC Read from socket failed: Connection reset by peer lost connection Start ArchiveToBoulder.bash Wed Jun 16 12:00:01 UTC 2010 Did not send log files to Boulder. Did not send quicklooks to Boulder Did not send quicklooks to Boulder Did not send summary files to Boulder No Radiosonde dc3db files No Radiosonde edt files No Radiosonde wmo files Sending MWR files to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection No PAERI files to send Sending Health.txt files to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Sending MMCRMom.nc.zip data to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Sending CABABL data to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Sending Ceilometer data to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Read from socket failed: Connection timed out lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Sending MPL data to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Sending Sodar data to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Sending Sodar jpgs to Boulder ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection ssh: connect to host 140.172.38.113 port 22: No route to host lost connection Stop ArchiveToBoulder.bash Wed Jun 16 12:24:31 UTC 2010 Read from socket failed: Connection reset by peer lost connection