[PL #6755] updates - planetlab in a box discussion
Thierry Parmentelat via RT
devel at planet-lab.org
Thu Nov 10 11:59:38 EST 2005
Email Recipients (see http://www.planet-lab.org/Support)
Owner: alk
Requestor: alk at absarokasoft.com
Ticket Ccs: Thierry.Parmentelat at sophia.inria.fr, abedma at mail.hadassah-col.ac.il, abenda at cs.huji.ac.il, alk at absarokasoft.com, alsbergt at cs.huji.ac.il, daniel51 at cs.huji.ac.il, devel-community at lists.planet-lab.org, jaffe at cs.huji.ac.il, jeff.sedayao at intel.com, nakao at iii.u-tokyo.ac.jp, renault.john at epfl.ch, smuir at cs.princeton.edu, winson.c.chan at intel.com
==================================================
Here is a patch for working around this issue :
plc_api/mod_pythonXMLRPC.py
< source = req.connection.remote_addr
---
> # source = req.connection.remote_addr
> (dummy,port) = req.connection.remote_addr
> source = (req.connection.remote_ip,port)
I have ipv6 up and running
It turns out that remote_ip is correctly set, while the ip part of
connection_addr is indeed 0.0.0.0
If nobody objects I'd like to commit this, after I have checked it still works
on all configs (fc2/fc4 -- ipv6 on/off)
Thierry
On Tuesday 08 November 2005 07:32 pm, Aaron Klingaman via RT wrote:
> Email Recipients (see http://www.planet-lab.org/Support)
> Owner: alk
> Requestor: alk at absarokasoft.com
> Ticket Ccs: Thierry.Parmentelat at sophia.inria.fr,
> abedma at mail.hadassah-col.ac.il, abenda at cs.huji.ac.il, alk at absarokasoft.com,
> alsbergt at cs.huji.ac.il, daniel51 at cs.huji.ac.il,
> devel-community at lists.planet-lab.org, jaffe at cs.huji.ac.il,
> jeff.sedayao at intel.com, nakao at iii.u-tokyo.ac.jp, renault.john at epfl.ch,
> smuir at cs.princeton.edu, winson.c.chan at intel.com
>
> ==================================================
>
> The requestor IP 0.0.0.0 is the IPv6/mod_python issue that was the
> reason for disabling IPv6. I have not looked into how to fix it.
>
> Aaron
>
> Thierry Parmentelat via RT wrote:
> > Email Recipients (see http://www.planet-lab.org/Support)
> > Owner: alk
> > Requestor: alk at absarokasoft.com
> > Ticket Ccs: Thierry.Parmentelat at sophia.inria.fr,
> > abedma at mail.hadassah-col.ac.il, abenda at cs.huji.ac.il,
> > alk at absarokasoft.com, alsbergt at cs.huji.ac.il, daniel51 at cs.huji.ac.il,
> > devel-community at lists.planet-lab.org, jaffe at cs.huji.ac.il,
> > jeff.sedayao at intel.com, nakao at iii.u-tokyo.ac.jp, renault.john at epfl.ch,
> > smuir at cs.princeton.edu, winson.c.chan at intel.com
> >
> > ==================================================
> >
> > Just a note on my progress on the fc4 server
> >
> > (*) I committed two more changes lately, that have to do with ssl
> > authentication: rpm mod_ssl was still missing (?) and the cert/key for
> > the https server are now located in a new place under /etc/pki/tls
> >
> > (*) I am now facing a new issue that, I believe, is not related with my
> > changes
> >
> > As opposed to what happens on the fc2 server that I also run (setup end
> > july), now when I declare a host I am still required to provide an IP
> > address, but it is *not* inserted in the plnode.txt file anymore. Anyway
> > when the node boots up, it fails to authenticate
> > Please find below
> > -) the alpina log file
> > -) the mail that I notifies me of the issue
> >
> > my node runs on address 138.96.250.186 (and I can ping it now that it
> > runs in debug mode) and this matches the ip I entered into the DB.
> > Since this sounds like a new feature to me, I'd like to know whether it
> > is supposed to work at all before I try to get this fixed.
> > I am especially puzzled by the mention of "Requestor IP 0.0.0.0" ...
> > ah, and I also must say I inserted plnode.txt on the CD itself under
> > /boot, could that be the issue ?
> >
> > Any additional background would be most helpful. Thanks
> >
> > =============== alpina log
> > Install log created on: 11/04/05 12:42:45
> >
> >>From node:
> >
> > node_id=7
> > submitter_ip=138.96.250.186
> > -----------------
> >
> > BootManager started at: Fri, 04 Nov 2005 13:48:08 +0000
> > Running version 3.1.8 of BootManager.
> >
> >
> > Step: Initializing the BootManager.
> > Opening connection to API server
> > Running on boot cd version: (3, 1)
> >
> >
> > Step: Reading node configuration file.
> > Checking standard floppy disk for plnode.txt file.
> > Mounting /dev/fd0 on /tmp/conffilemount
> > Checking for existence of /tmp/conffilemount/plnode.txt
> > Read in contents of file /tmp/conffilemount/plnode.txt
> > Successfully read and parsed node configuration file.
> > Got mac address 00:C0:FD:02:18:41 for device eth0
> > Checking that hostname anegada.inria.fr resolves
> > Hostname anegada.inria.fr correctly resolves to 138.96.250.186:
> >
> >
> > Step: Authenticating node with PLC.
> > Authentication failed: API Fault: <Fault 103: 'Authentication failure
> > (Requestor ip 0.0.0.0 does not match node ip 138.96.250.186).'>.
> > Maximum number of authentication failures reached.
> > Canceling boot process and going into debug mode.
> >
> >
> > Step: Starting debug mode.
> > Starting debug environment
> > Creating ssh host keys
> > Generating public/private rsa1 key pair.
> > Your identification has been saved in /etc/ssh//ssh_host_key.
> > Your public key has been saved in /etc/ssh//ssh_host_key.pub.
> > The key fingerprint is:
> > 9d:2e:89:36:e6:23:71:a8:d9:43:80:9b:b8:4d:14:73 root at anegada
> > Generating public/private rsa key pair.
> > Your identification has been saved in /etc/ssh//ssh_host_rsa_key.
> > Your public key has been saved in /etc/ssh//ssh_host_rsa_key.pub.
> > The key fingerprint is:
> > 1c:41:89:e0:fe:a6:bd:4d:77:b4:c9:16:4a:3f:82:96 root at anegada
> > Generating public/private dsa key pair.
> > Your identification has been saved in /etc/ssh//ssh_host_dsa_key.
> > Your public key has been saved in /etc/ssh//ssh_host_dsa_key.pub.
> > The key fingerprint is:
> > 5a:74:13:68:ef:11:a6:81:a9:03:2a:3d:d5:b7:44:e8 root at anegada
> > Installing debug ssh key for root user
> > Starting sshd
> > Starting sshd:[ OK ]
> >
> >
> >
> > Exception while running: Unable to authenticate node.
> >
> > Done!
> > BootManager finished at: Fri, 04 Nov 2005 13:48:17 +0000
> > Uploading logs to http://bellami.inria.fr/alpina-logs/upload.php
> >
> >
> > ===============
> > This is an automated message to inform you of an
> > error that occured during a recent PlanetLab node
> > authentication attempt.
> >
> > The node anguilla.inria.fr failed to authenticate.
> >
> > The most common reasons for this are:
> >
> > 1. The node ip in the PLC records does not match the requestor ip
> > (is the node behind a firewall or nat?)
> >
> > To fix, move the node to a publicly routable network,
> > and update the configuration file and the PLC records.
> >
> > 2. The node does not have a primary network interface configured
> > at PLC
> >
> > To fix, login to PLC, and mark one of the network interfaces
> > for this node as the primary one, then update the configuration
> > file.
> >
> > 3. If the configuration file contains a node key and/or node id
> > value, they do not match what PLC has on record.
> >
> > To fix, regenerate the configuration file, and update the floppy.
> >
> > If this has already been done and you are still seeing
> > this error, please notify PlanetLab Support so we can
> > investigate the problem.
> >
> > Thank you,
> >
> > PlanetLab Support Team
> > thierry.parmentelat at sophia.inria.fr
> > ===============
More information about the Devel-community
mailing list