planetlab-users Mailing List for PlanetLab
Brought to you by:
alklinga
Menu
▾
▴
planetlab-users — Discussion among PlanetLab users; but send trouble reports to planetlab-support
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(3) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(2) |
Feb
(2) |
Mar
(7) |
Apr
(6) |
May
(5) |
Jun
(8) |
Jul
|
Aug
(9) |
Sep
(18) |
Oct
(24) |
Nov
(46) |
Dec
(37) |
| 2004 |
Jan
(65) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
(2) |
Jul
(1) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2005 |
Jan
(2) |
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Jeff S. <je...@ee...> - 2005-04-19 17:29:09
|
Hi, I have put together a short survey asking about Planetlab resource usage and your opinions on what to do if PL resources are overloaded. http://www.surveymonkey.com/s.asp?u=906961000987 Your participation would be appreciated. Results will be shared at the upcoming Planetlab meeting in May. As further incentive, a "progressive pot" of money will be given away to a random survey participant (or their favorite charity). Thanks! jeff. |
|
From: Elisha Z. <ezi...@CS...> - 2005-01-13 19:51:54
|
On Wed, 12 Jan 2005 pla...@li... wrote: > Send Planetlab-users mailing list submissions to > pla...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/planetlab-users > or, via email, send a message with subject or body 'help' to > pla...@li... > > You can reach the person managing the list at > pla...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Planetlab-users digest..." > > > Today's Topics: > > 1. mapping a /proc/scout/ports/summary slice number to a slice name? (David L. Oppenheimer) > > --__--__-- > > Message: 1 > From: "David L. Oppenheimer" <dav...@cs...> > To: <pla...@li...> > Date: Wed, 12 Jan 2005 18:15:45 -0800 > Subject: [Planetlab-users] mapping a /proc/scout/ports/summary slice number to a slice name? > > How do I map a /proc/scout/ports/summary slice number to the name of the > corresponding slice? > > Thanks, > David > > > > > --__--__-- > > _______________________________________________ > Planetlab-users mailing list > Pla...@li... > https://lists.sourceforge.net/lists/listinfo/planetlab-users > > > End of Planetlab-users Digest > |
|
From: David L. O. <dav...@cs...> - 2005-01-13 02:15:48
|
How do I map a /proc/scout/ports/summary slice number to the name of the corresponding slice? Thanks, David |
|
From: David L. O. <dav...@cs...> - 2004-10-21 19:18:23
|
When analyzing historical logs taking by PlanetLab measurement tools, I have found it not uncommon for hosts to be identified by their hostname or IP address, but not both. This raises a difficulty when trying to correlate historical measurements taken at the same time on the same set of hosts, but by different tools. In particular, if one masurement tool logged measurements by hostname and the other logged by IP address, there is no good way to "join" the two datasets by node identity because the hostname<->IP mapping that DNS gives me today may be different from that which was current at the time the measurements were taken. As you might expect, the problem grows worse and worse the farther back in time you go (today's DNS mappings become less and less relevant). So my question is, has anyone kept track of the hostname<->IP mapping for all PlanetLab hosts over time? If one had a table that mapped (hostname, time) -> IP or (IP, time) -> hostname, then correlating node identities that were recorded as only hostname or only IP address would be possible. Thanks much, David |
|
From: David L. O. <dav...@cs...> - 2004-07-26 20:21:49
|
A technical report with full details on the SWORD wide-area resource discovery service is now available on the SWORD web page at http://www.swordrd.org/ or directly from http://www.swordrd.org/pubs/tr041334.pdf David |
|
From: Scott K. <sc...@CS...> - 2004-06-07 16:59:45
|
On Mon, Jun 07, 2004 at 09:17:37AM -0700, David L. Oppenheimer wrote: > Does anyone know the current status of the NOC sensor? Last I heard it was > running on port 33080, but it doesn't seem to be there anymore (at least on > the nodes that I checked). Hi David, It is currently running on 206 nodes out of about 303 active. I'll work on getting it deployed on more nodes. Scott |
|
From: David L. O. <dav...@cs...> - 2004-06-07 16:17:38
|
Does anyone know the current status of the NOC sensor? Last I heard it was running on port 33080, but it doesn't seem to be there anymore (at least on the nodes that I checked). Thanks, David |
|
From: Neil S. <ns...@cs...> - 2004-02-19 04:10:14
|
Aninda, Use Aaron K's script: > If you want to set up yum and python in your slice, you can simply run = =20 > this > line: > > curl --silent http://www.cs.princeton.edu/~alk/setup_yum.sh | = /bin/bash or mine (unofficial, but includes scriptroute client software): curl -O http://www.scriptroute.org/planetlab/planetlab-install && sh =20 ./planetlab-install both will install yum and setup your yum.conf to use =20 boot.planet-lab.org for packages. that your error messages include =20 mirror.dulug.duke.edu suggests to me that you've installed yum in some =20= other way that does not configure yum.conf. > My experiments will involve usage of quite a few nodes. Do I have to =20= > install these packages in all the nodes separately? yup. -neil On Feb 18, 2004, at 3:36 PM, Aninda Bhattacharya wrote: > Hi! > =A0 > I use the following command to install the packages in my slice: > =A0 > >>=A0yum -y install man gzip less gcc flex bison bc rpm-build =20 > linux-headers > =A0 > It exits after downloading some of the headers. The error message is: > =A0 > getting /var/cache/yum/base/headers/tcl-html-0-8.3.5-88.i386.hdr > retrygrab() failed for: > =A0 =20 > http://mirror.dulug.duke.edu/pub/yum-repository/redhat/9/i386//=20 > headers/tcl-html-0-8.3.5-88.i386.hdr > =A0 Executing failover method > failover: out of servers to try > Error getting file =20 > http://mirror.dulug.duke.edu/pub/yum-repository/redhat/9/i386//=20 > headers/tcl-html-0-8.3.5-88.i386.hdr > [Errno 7] HTTP Error (CannotSendRequest): > =A0 > How can I get rid of this error? > =A0 > My experiments will involve usage of quite a few nodes. Do I have to =20= > install these packages in all the nodes separately? > =A0 > Sincerely, > Aninda > > > |
|
From: Aninda B. <an...@ne...> - 2004-02-18 23:30:14
|
Hi! I use the following command to install the packages in my slice: >> yum -y install man gzip less gcc flex bison bc rpm-build = linux-headers It exits after downloading some of the headers. The error message is: getting /var/cache/yum/base/headers/tcl-html-0-8.3.5-88.i386.hdr retrygrab() failed for: = http://mirror.dulug.duke.edu/pub/yum-repository/redhat/9/i386//headers/tc= l-html-0-8.3.5-88.i386.hdr Executing failover method failover: out of servers to try Error getting file = http://mirror.dulug.duke.edu/pub/yum-repository/redhat/9/i386//headers/tc= l-html-0-8.3.5-88.i386.hdr [Errno 7] HTTP Error (CannotSendRequest):=20 How can I get rid of this error? My experiments will involve usage of quite a few nodes. Do I have to = install these packages in all the nodes separately? Sincerely, Aninda |
|
From: Sushant R. <rew...@cs...> - 2004-01-30 20:55:05
|
HI, I am a returning user to planetlab. I had scripts which used ping to collect some network state and when i tried running these recently on planet-lab they failed. I would like to know if this is a flaw or is this a security feature incorporated in Planet-lab. In case ping are no longer allowed on the network then is there any other way or working around this problem. Thank you Sushant Rewaskar |
|
From: Bowman, M. <mic...@in...> - 2004-01-28 20:04:28
|
I've started tracking some information about node status in a gnats db available at: http://mbowman-pldesk.nbgisp.com:8001/cgi-bin/gnatsweb.pl =20 To get information on the list of down nodes, login is "guest" with "planetlab" as the password, select the saved query "DownNodes" at the top of the page. =20 Note that there are no guarantees that this service will be continued. But I hope you find it useful for now. =20 --Mic =20 |
|
From: Sedayao, J. <jef...@in...> - 2004-01-28 17:12:43
|
PlanetLab Users, We are currently experiencing a problem with severe clock drift on a = number of PlanetLab servers (on the order of tens of seconds an hour on = some machines). Apparently the switch to a new kernel included a NTP = change that can't cope with the severe clock drift on some of the nodes. = The vast majority of problem nodes are Dell Precision 340 systems. We'll be putting in some short term measures to reduce the scale of the = problem and looking at some longer term measures to fix things more = thoroughly. Jeff Sedayao PlanetLab Support |
|
From: Yun M. <ma...@ci...> - 2004-01-28 15:27:36
|
Thanks. The new one works well. Before that I downloaded the
"-3_planetlab" version, and it turned out that I can't get it working.
Error msg:
$ yum
Traceback (most recent call last):
File "/usr/bin/yum", line 22, in ?
import yummain
File "yummain.py", line 21, in ?
File "clientStuff.py", line 25, in ?
File "pkgaction.py", line 24, in ?
File "rpmUtils.py", line 9, in ?
File "urlgrabber.py", line 5, in ?
ImportError: /usr/lib/python2.2/site-packages/pycurl.so: undefined symbol:
curl_version_info
The "2.0.4.noarch" works fine.
Yun
On Wed, 28 Jan 2004, Aaron Klingaman wrote:
> After realizing that my script probably doesn't need to install the planetlab
> specific yum (ending in -x_planetlab), i've updated it to install a regular
> version. This way, the script won't need to be updated when I change the
> version of yum that planetlab nodes use.
>
> Aaron
>
> On Tuesday 27 January 2004 08:36 pm, Neil Spring wrote:
> > On Tue, Jan 27, 2004 at 08:08:35PM -0500, Yun Mao wrote:
> > > http://boot.planet-lab.org/install-rpms/planetlab/yum-2.0.3-1_planetlab.n
> > >oarch.rpm Does it move to somewhere else? Thanks!
> >
> > -3 seems to exist.
> >
> > http://boot.planet-lab.org/install-rpms/planetlab/yum-2.0.3-3_planetlab.noa
> >rch.rpm
> >
> > heh,
> > -neil
> >
> >
> > -------------------------------------------------------
> > 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
>
>
>
> -------------------------------------------------------
> 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
>
|
|
From: Aaron K. <al...@CS...> - 2004-01-28 14:21:57
|
After realizing that my script probably doesn't need to install the planetlab specific yum (ending in -x_planetlab), i've updated it to install a regular version. This way, the script won't need to be updated when I change the version of yum that planetlab nodes use. Aaron On Tuesday 27 January 2004 08:36 pm, Neil Spring wrote: > On Tue, Jan 27, 2004 at 08:08:35PM -0500, Yun Mao wrote: > > http://boot.planet-lab.org/install-rpms/planetlab/yum-2.0.3-1_planetlab.n > >oarch.rpm Does it move to somewhere else? Thanks! > > -3 seems to exist. > > http://boot.planet-lab.org/install-rpms/planetlab/yum-2.0.3-3_planetlab.noa >rch.rpm > > heh, > -neil > > > ------------------------------------------------------- > 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 |
|
From: Aaron K. <al...@CS...> - 2004-01-28 13:53:41
|
Yeah, sorry, I forgot to update my script to reflect the recent yum upgrade. It should work as expected now. ak On Tuesday 27 January 2004 08:36 pm, Neil Spring wrote: > On Tue, Jan 27, 2004 at 08:08:35PM -0500, Yun Mao wrote: > > http://boot.planet-lab.org/install-rpms/planetlab/yum-2.0.3-1_planetlab.n > >oarch.rpm Does it move to somewhere else? Thanks! > > -3 seems to exist. > > http://boot.planet-lab.org/install-rpms/planetlab/yum-2.0.3-3_planetlab.noa >rch.rpm > > heh, > -neil |
|
From: Neil S. <ns...@cs...> - 2004-01-28 01:36:19
|
On Tue, Jan 27, 2004 at 08:08:35PM -0500, Yun Mao wrote: > http://boot.planet-lab.org/install-rpms/planetlab/yum-2.0.3-1_planetlab.noarch.rpm > Does it move to somewhere else? Thanks! -3 seems to exist. http://boot.planet-lab.org/install-rpms/planetlab/yum-2.0.3-3_planetlab.noarch.rpm heh, -neil |
|
From: Yun M. <ma...@ci...> - 2004-01-28 01:33:57
|
Finally figured out .. The yum has been upgraded, and depends on a new rpm pycurl at boot.planet-lab.org/install-rpms/3rdparty/pycurl-7.10.4-1.i386.rpm Hope this is useful. Yun On Tue, 27 Jan 2004, Yun Mao wrote: > Hi, > > I can't find > http://boot.planet-lab.org/install-rpms/planetlab/yum-2.0.3-1_planetlab.noarch.rpm > > Does it move to somewhere else? Thanks! > > Yun > |
|
From: Yun M. <ma...@ci...> - 2004-01-28 01:08:54
|
Hi, I can't find http://boot.planet-lab.org/install-rpms/planetlab/yum-2.0.3-1_planetlab.noarch.rpm Does it move to somewhere else? Thanks! Yun On Fri, 16 Jan 2004, Aaron Klingaman wrote: > If you want to set up yum and python in your slice, you can simply run this > line: > > curl --silent http://www.cs.princeton.edu/~alk/setup_yum.sh | /bin/bash > > Aaron > > > > ------------------------------------------------------- > 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 > |
|
From: Gary J. M. <gm...@it...> - 2004-01-26 15:40:12
|
The Kansas PlanetLab nodes will be powered off from approximately 10 AM CST and 3 PM CST on January 26, 2004 to allow us to update our building power system. Gary Minden |
|
From: Scott K. <sc...@CS...> - 2004-01-23 02:53:40
|
FYI, https is back online. Scott On Thu, Jan 22, 2004 at 05:22:11PM -0800, Sedayao, Jeff wrote: > The https portions of the PlanetLab website are currently down, and we are working to get this back up as soon as we can. > > Jeff Sedayao > PlanetLab Support |
|
From: Sedayao, J. <jef...@in...> - 2004-01-23 01:22:19
|
The https portions of the PlanetLab website are currently down, and we = are working to get this back up as soon as we can. Jeff Sedayao PlanetLab Support |
|
From: Aki N. <na...@cs...> - 2004-01-21 16:11:52
|
Okay, I seem to have been too cautious :) I thought you are working on ssh key distribution stuff too. I will be accessing the planetlab nodes then. I can send you my list if that helps you. Aki > -----Original Message----- > From: Steve Muir [mailto:sm...@CS...] > Sent: Wednesday, January 21, 2004 11:06 AM > To: Aki Nakao > Cc: pla...@li... > Subject: RE: [Planetlab-users] Reporting slice access problems > > > Aki, > > I wasn't soliciting a list of nodes that you can't access > from every user. I was just trying to let folks know how they > can help us get them a response to their questions in the > fastest time. Right now we are still in the process of > moving various servers over to Princeton - you should be able > to access PlanetLab nodes but not the various centralised services. > > cheers, > > steve > > > > On Wed, 21 Jan 2004, Aki Nakao wrote: > > > 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 > > > > > > > > > > > ------------------------------------------------------- > > 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 > > > |
|
From: Steve M. <sm...@cs...> - 2004-01-21 16:06:11
|
Aki, I wasn't soliciting a list of nodes that you can't access from every user. I was just trying to let folks know how they can help us get them a response to their questions in the fastest time. Right now we are still in the process of moving various servers over to Princeton - you should be able to access PlanetLab nodes but not the various centralised services. cheers, steve On Wed, 21 Jan 2004, Aki Nakao wrote: > 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 > > > > > > ------------------------------------------------------- > 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 > |
