[Planetlab-devel] Re:Re:help for booting the node!

[Thierry Parmentelat]

OK, you're experiencing the issue that is being discussed in the 'nodes booting' thread
This seems to be fixed in today's builds, so you should try upgrading to the very latest release
(the issue is with the bootmanager, make sure to use bootmanager-5.0-12)

-- thierry


On Aug 27, 2010, at 5:04 AM, liyong 00164768 wrote:

> Thanks very much for your replay!The attachments are our boot-management log-file  and myplc-release,please help us to look over the inconsistencies in the myplc-release and cause for failing boot in the boot-management log-file, thanks very much!
> PS:1.The root context we are using is CentOS 5.4
>   2.The sql datebase we are using is planetlab5
>   3.The myplc we are using is 4.3 
> *****************************************************
>> Message: 3
>> Date: Thu, 26 Aug 2010 12:24:47 +0200
>> From: Thierry Parmentelat <thierry.parmentelat at sophia.inria.fr>
>> Subject: Re: [Planetlab-devel] Help for boot a node!
>> To: PlanetLab Development <devel at planet-lab.org>
>> Message-ID: <CBC0DB16-C762-4AD5-B926-7226D815D846 at sophia.inria.fr>
>> Content-Type: text/plain; charset=us-ascii
>> 
>> hi there
>> 
>> bootmanager logs are in principle uploaded on the myplc side in 
>> /var/log/bmraw log files are stored in raw/ and then symlinks are 
>> created in the other subdirs to help navigating in the mess :)
>> 
>> the bm logic is to first start a failsafe sshd instance, that runs 
>> in the context of the bootcd
>> the regular sshd, that runs in the context of the hard-drive, can 
>> be triggered only later on, after a successful kexec can be 
>> triggered from the installed hdd
>> 
>> the failsafe sshd uses the key from /etc/planetlab/debug_ssh_key*, 
>> while the regular sshd accepts connections using any public key 
>> attached to an administrator, as well as the one from  
>> /etc/planetlab/root_ssh_key*You should thus try these keys 
>> according to the stage where the installation failed
>> 
>> this being said, if the node could not use a network interface at 
>> all, then of course you're out of luck with any of this; but it 
>> might also be that the bootCD could setup the interface and the 
>> hard-drive install could not..
>> 
>> 
>> in any case, for any further assistance, please provide your 
>> precise release info, as found in /etc/myplc-release
>> 
>> hope this helps -- thierry
>> 
>> On Aug 26, 2010, at 9:27 AM, liyong 00164768 wrote:
>> 
>>> 
>>> Hi all:
>>>   When we boot the node using the ISO file downloaded from our 
>> MyPLC webpage,some errors
>>> always occurs, such as: 
>>>   1.failed to bring up the eth0!
>>>   2.no such files :/etc/resolv.conf
>>>   3.there is no server to be used!
>>> PS:these errors occurs at different stage in the boot process.
>>>   Finally, when the boot process end, the message of "This node 
>> is not fully booted!Try to 
>>> login with root!" and when we login with root and the 
>> corresponding password, the state of 
>>> the node in the MyPLC webpage still remain "failboot"! Could 
>> anyone tell us how to resolve 
>>> this problem and boot the node successfully? or could someone 
>> tell us where I can find out 
>>> the log file of this boot process?
>>>   Thanks a lot!
>>> 
>>> _______________________________________________
>>> Devel mailing list
>>> Devel at lists.planet-lab.org
>>> https://lists.planet-lab.org/mailman/listinfo/devel
>> 
>> 
>> 
>> 
>> ------------------------------
>> 
>> _______________________________________________
>> Devel mailing list
>> Devel at lists.planet-lab.org
>> https://lists.planet-lab.org/mailman/listinfo/devel
>> 
>> 
>> End of Devel Digest, Vol 76, Issue 3
>> ************************************
>> 
> <2010-08-26-08-32-myplc6.fano.cn-192.168.0.196.txt><myplc-release>_______________________________________________
> Devel mailing list
> Devel at lists.planet-lab.org
> https://lists.planet-lab.org/mailman/listinfo/devel