Shouldn't we be accessing planetlab machines now ?
Is it fine now to access them ?
Or is it the list you got before this downtime ?
Aki
> -----Original Message-----
> From: pla...@li...
> [mailto:pla...@li...] On
> Behalf Of Ming Zhang
> Sent: Wednesday, January 21, 2004 10:50 AM
> To: Steve Muir
> Cc: pla...@li...
> Subject: Re: [Planetlab-users] Reporting slice access problems
>
>
> Hi Steve,
>
> Here is the list of nodes that I can't access and reason:
>
> 1) Permission denied (publickey,keyboard-interactive):
>
> planetlab0.ias.csusb.edu
> planetlab10.millennium.berkeley.edu
> planetlab11.millennium.berkeley.edu
> planetlab-02.bu.edu
> righthand.eecs.harvard.edu
> planetlab1.cs.virginia.edu
> kupl1.ittc.ku.edu
> planetlab2.unl.edu
> planetlab2.mnlab.cti.depaul.edu
> planetlab1.netlab.uky.edu
> inez.cse.ogi.edu
> planetlab5.nbgisp.com
> pli1-pa-1.hpl.hp.com
> pli1-pa-2.hpl.hp.com
> pl1.swri.org
> planetlab2.enel.ucalgary.ca
> planet2.cs.huji.ac.il
> planetlab1.tau.ac.il
> planetlab2.mini.pw.edu.pl
> planet2.ics.forth.gr
>
> 2) SSH Connection refused:
>
> planlab1.cs.caltech.edu
> planetlab6.cs.berkeley.edu
> planetlab7.cs.berkeley.edu
> planetlab2.ece.ucdavis.edu
> planetlab-1.cmcl.cs.cmu.edu
> planetlab2.cs.cornell.edu
> planetlab3.lcs.mit.edu
> planetlab-1.cs.princeton.edu
> planetlab-2.cs.princeton.edu
> planetlab2.rutgers.edu
> planetlab1.cse.msu.edu
> planetlab2.cse.msu.edu
> planetlab1.cse.nd.edu
> planetlab2.cse.nd.edu
> planetlab1.cs.purdue.edu
> planetlab2.cs.purdue.edu
> planetlab1.cs.unc.edu
> planetlab3.cs.duke.edu
> pli1-pa-2.hpl.hp.com
> pli1-crl-1.crl.hpl.hp.com
> pli1-crl-2.crl.hpl.hp.com
> pli1-crl-3.crl.hpl.hp.com
> plab2.nec-labs.com
> pl1.ece.toronto.edu
> planetlab1.eurecom.fr
> pl1.6test.edu.cn
> csplanetlab2.kaist.ac.kr
> planetlab1.mini.pw.edu.pl
> planetlab1.cs.msu.su
>
> 3) SSH Connection timed out:
>
> planetlab2.ucsd.edu
> planetlab3.ucsd.edu
> planetslug1.cse.ucsc.edu
> planetlab-01.bu.edu
> planetlab1.comet.columbia.edu
> planetlab1.cs.dartmouth.edu
> planetlab8.lcs.mit.edu
> planetlab2.cs.virginia.edu
> planetlab2.cs.northwestern.edu
> planetlab1.cs.uchicago.edu
> planetlab2.cs.uchicago.edu
> planetlab3.cs.uchicago.edu
> planetlab1.cs.uiuc.edu
> planetlab2.cs.uiuc.edu
> planetlab1.eecs.umich.edu
> planetlab1.tamu.edu
> ricepl-1.cs.rice.edu
> ricepl-2.cs.rice.edu
> planetlab1.csres.utexas.edu
> planetlab2.csres.utexas.edu
> ricepl-3.cs.rice.edu
> pl1.unm.edu
> pl3.unm.edu
> planetlab1.cs.uoregon.edu
> planetlab01.cs.washington.edu
> pl1.cs.utk.edu
> pl2.cs.utk.edu
> planetlab2.cs.unc.edu
> planetlab2.cs.duke.edu
> planetlab4.nbgisp.com
> planetlab1.sanjose.equinix.planet-lab.org
> planetlab2.sanjose.equinix.planet-lab.org
> planetlab2.eurecom.fr
> planetlab1.sics.se
> planetlab2.sics.se
> pl2.6test.edu.cn
> planetlab1.iis.sinica.edu.tw
> planetlab2.iis.sinica.edu.tw
> planetlab1.koganei.wide.ad.jp
> planetlab2.koganei.wide.ad.jp
> csplanetlab3.kaist.ac.kr
> recall.snu.ac.kr
> planetlab1.canterbury.ac.nz
> planetlab2.canterbury.ac.nz
> planet4.cs.huji.ac.il
>
> 4) No route to host:
>
> planetlab1.ece.ucdavis.edu planetlab3.ashburn.equinix.planet-lab.org
> pl2.ece.toronto.edu
> planetlab1.cs.unibo.it
> planetlab2.cs.unibo.it
>
> 5) Temporary failure in name resolution:
>
> planetlab1.gti-dsl.nodes.planet-lab.org
> planetlab2.gti-dsl.nodes.planet-lab.org
> planet1.halifax.canet4.nodes.planet-lab.org
> planet2.halifax.canet4.nodes.planet-lab.org
> uw1.accretive-dsl.nodes.planet-lab.org
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim,
> CA. http://www.eclipsecon.org/osdn
> _______________________________________________
> Planetlab-users mailing list Pla...@li...
> https://lists.sourceforge.net/lists/listinfo/planetlab-users
>
|
