[orbit-user] Problem with the sb5 nodes

Sanjit sanjitkaul at gmail.com
Fri Feb 13 16:05:53 EST 2009


You will have to explicitly switch the nodes ON after imaging succeeds 
using the command:

omf tell on [[1,1],[1,2]]

For the first case you mention in your mail, do you know what image was 
on the nodes? Had you imaged them?

Regards,
Sanjit

On 2/13/2009 4:01 PM, Emmanouil Koukoumidis (ekoukoum at Princeton.EDU) wrote:
> Hi,
>
> I am experiencing similar problems with sb2 and sb8....
> More specifically:
>
> I am having two problems:
> 1) I can't ssh to nodes
> 2) nodes go off just after imaging succeeds
>
> Thanks,
> Emmanouil
>
> ekoukoum at console.sb2:~$ orbit stat
> -----------------------------------------------
>   INFO Topology: Loading topology 'system:topo:all'.
>   Testbed : sb2
>   Node n_1_1 - State: POWERON
>   Node n_1_2 - State: POWERON
> -----------------------------------------------
> ekoukoum at console.sb2:~$ ssh root at node1-1
> ssh: connect to host node1-1 port 22: Connection refused
> ekoukoum at console.sb2:~$ ssh root at node1-2
> ssh: connect to host node1-2 port 22: No route to host
> ekoukoum at console.sb2:~$ orbit stat
> -----------------------------------------------
>   INFO Topology: Loading topology 'system:topo:all'.
>   Testbed : sb2
>   Node n_1_1 - State: POWERON
>   Node n_1_2 - State: POWERON
> -----------------------------------------------
>
>
>
> Or another case:
>
>   INFO exp:  Imaging Process Done
>   INFO exp:  - 2 node(s) succesfully imaged - See the topology file: 'system_topo_active_sb2.rb'
>   INFO exp:  -----------------------------
>   INFO Experiment: DONE!
>   INFO ExecApp: Application 'commServer' finished
>   INFO run: Experiment sb2_2009_02_13_15_44_57 finished after 9:23
> ekoukoum at console.sb2:~$ ssh root at node1-1
> ssh: connect to host node1-1 port 22: No route to host
> ekoukoum at console.sb2:~$ ssh root at node1-2
> ssh: connect to host node1-2 port 22: No route to host
> ekoukoum at console.sb2:~$ orbit stat
> -----------------------------------------------
>   INFO Topology: Loading topology 'system:topo:all'.
>   Testbed : sb2
>   Node n_1_1 - State: POWEROFF
>   Node n_1_2 - State: POWEROFF
> -----------------------------------------------
> ekoukoum at console.sb2:~$
>
>
>
>
>
> ----- Original Message -----
> From: Thierry Rakotoarivelo<Thierry.Rakotoarivelo at nicta.com.au>
> Date: Friday, February 13, 2009 1:44 am
> Subject: Re: [orbit-user] Problem with the sb5 nodes
> To: Orbit user discussion mailing list<orbit-user at orbit-lab.org>
>
>    
>> Hi Akash,
>>
>> You can use the command 'omf stat' (as explained on the tutorial
>> pages) to view
>> the status of the nodes:
>>
>> thierry at console.sb5:~$ omf stat
>> -----------------------------------------------
>>   INFO Topology: Loading topology 'system:topo:all'.
>>   Testbed : sb5
>>   Node n_1_1 - State: NODE NOT AVAILABLE
>>   Node n_1_2 - State: POWEROFF
>> -----------------------------------------------
>> thierry at console.sb5:~$
>>
>> It seems that Node [1,1] is experiencing some hardware or CM
>> issues. You need
>> someone at Winlab to go and check what's wrong with it.
>>
>> Did you turn your Node [1,2] ON before trying to ssh to it? (as the
>> omf stat
>> output shows it's currently OFF). You can do so by calling 'omf
>> tell on [1,2]'
>> (again explained in the tutorial pages).
>>
>> Regards,
>> Thierry.
>>
>> Akash Baid wrote:
>>      
>>> Hi,
>>>
>>> I was trying to use the sb5 nodes for gnuradio but am stuck right
>>>        
>> at the
>>      
>>> stage of loading the image to the nodes.
>>> Whenever I try to load the image 'gnuradio.ndz' in node [1,1],
>>>        
>> there's
>>      
>>> an error:
>>>
>>> "WARN -:topo:image: Ignoring missing node '1 at 1'
>>>   INFO whenAll: *: 'status[@value='UP']' fires
>>> FATAL service_call: Exception: ServiceException
>>> (http://cmc:5012/cmc/nodeSetOn?nodes=[])"
>>>
>>> I am using 'orbit load [1,1] gnuradio.ndz' as the command.
>>> Also I can't ssh to node1-2 after loading the image. It says
>>>        
>> "ssh:
>>      
>>> connect to host node1-2 port 22: No route to host"
>>>
>>> Can someone advise what's the problem. am new to orbit. Any help
>>>        
>> greatly
>>      
>>> appreciated.
>>>   - Akash
>>>
>>>        
>> _______________________________________________
>> orbit-user mailing list
>> orbit-user at orbit-lab.org
>> http://orbit-lab.org/cgi-bin/mailman/listinfo/orbit-user
>>
>>      
> _______________________________________________
> orbit-user mailing list
> orbit-user at orbit-lab.org
> http://orbit-lab.org/cgi-bin/mailman/listinfo/orbit-user
>    
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://orbit-lab.org/pipermail/orbit-user/attachments/20090213/83b01f28/attachment.htm>


More information about the orbit-user mailing list