ORBIT-USER: error in exp

[Max Ott]

How do you know you used nodehandler4? The snippet you sent clearly
indicates V3:

farhan at console.grid:~/Ruby-Script$ nodehandler iperf5
Using config /etc/nodehandler/grid.cfg
/etc/nodehandler/grid.cfg:20: warning: Insecure world writable dir
/tmp, mode 040777
Using logfile /etc/nodehandler/nodehandler_log.xml
 INFO init: NodeHandler Version 3.6.4-1 (849)
                                              ^^^^^^^

Please try 'nodehandler4' and if that fails again, please also include
the experiment files you wrote so we can better understand what's
going wrong.

Thanks,

-max


On 7/30/07, Farhan Zaheer <Farhan.Zaheer at nicta.com.au> wrote:
>
>
>
>
> I used nodehandler4.
>
>
>
>
> From: owner-orbit-user at winlab.rutgers.edu [mailto:owner-orbit-user at winlab.rutgers.edu] On Behalf Of Sanjit Kaul
>  Sent: Monday, July 30, 2007 2:54 PM
>  To: orbit-user at winlab.rutgers.edu
>  Subject: Re: ORBIT-USER: error in exp
>
>
>
>
> Please try nodehandler4 instead of nodehandler.
>
>
> On 7/29/07, Farhan Zaheer <Farhan.Zaheer at nicta.com.au > wrote:
>
>
>
> Hi,
>
> Can anyone suggest what this error means? I am running iperf and tcpdump on the same nodes.
>
>
>
>
>
> farhan at console.grid:~/Ruby-Script$ nodehandler iperf5
>
> Using config /etc/nodehandler/grid.cfg
>
> /etc/nodehandler/grid.cfg:20: warning: Insecure world writable dir /tmp, mode 040777
>
> Using logfile /etc/nodehandler/nodehandler_log.xml
>
>  INFO init: NodeHandler Version 3.6.4-1 (849)
>
>  INFO init: Experiment ID: grid_2007_07_29_22_57_11
>
>  INFO Experiment: load system:exp:stdlib
>
>  INFO prop.resetDelay: resetDelay = 180:Fixnum
>
>  INFO Experiment: load iperf5
>
> /tmp/eee.126/lib/util/communication.rb:127: warning: Insecure world writable dir /tmp, mode 040777
>
>  INFO stdlib: 4 out of 4 node(s) still down n_20_3,n_20_4,n_20_4
>
>  INFO stdlib: 4 out of 4 node(s) still down n_20_3,n_20_4,n_20_4
>
>  INFO stdlib: 4 out of 4 node(s) still down n_20_3,n_20_4,n_20_4
>
>  INFO stdlib: 4 out of 4 node(s) still down n_20_3,n_20_4,n_20_4
>
>  INFO stdlib: 4 out of 4 node(s) still down n_20_3,n_20_4,n_20_4
>
>  INFO stdlib: 4 out of 4 node(s) still down n_20_3,n_20_4,n_20_4
>
>  INFO stdlib: 4 out of 4 node(s) still down n_20_3,n_20_4,n_20_4
>
>  INFO stdlib: 4 out of 4 node(s) still down n_20_3,n_20_4,n_20_4
>
>  INFO stdlib: 4 out of 4 node(s) still down n_20_3,n_20_4,n_20_4
>
>  INFO stdlib: 4 out of 4 node(s) still down n_20_3,n_20_4,n_20_4
>
>  INFO n_20_3: Checked in as /ip/10.10.20.3 booting off baseline:1.0.9
>
>  INFO stdlib: 2 out of 4 node(s) still down n_20_4,n_20_4
>
>  INFO n_20_4: Checked in as /ip/10.10.20.4 booting off baseline:1.0.9
>
> ERROR CONFIGURE_ERROR: Couldn't configure 'net/w0/mode' on 'n_20_4':
>
>  INFO whenAll: _ALL_: 'apps/app/status[text()='INSTALLED.OK']' fires
>
>  INFO n_20_3: Device 'net/w0' reported 00:00:00:00:00:00
>
>  INFO n_20_4: Device 'net/w0' reported 00:00:00:00:00:00
>
>  INFO OML: Started: {"port"=>"7000", "iface"=>"eth1", "addr"=>"224.0.0.6"}
>
> ERROR NodeApp: ERROR(oml) Could not get either OML_NAME or OML_CONFIG from env
>
> ERROR NodeApp: connect failed: No route to host
>
> ERROR NodeApp: write1 failed: Broken pipe
>
> ERROR NodeApp: write2 failed: Broken pipe
>
> ERROR NodeApp: tcpdump: ioctl: No such device
>
> ERROR NodeApp: tcpdump: /home/farhan/tcpdumpfile: No such file or directory
>
>  INFO Experiment: DONE!
>
>  INFO run: Experiment grid_2007_07_29_22_57_11 finished after 3:32
>
>
>
>
>
>
>
>
>
>
>
> Regards,
>  _________________________
>  Farhan Zaheer
>
> Thesis Student
>  Network & Pervasive Computing
>  (National ICT Australia Ltd.)
>
>
>
>
>
>
>
>



-- 
Dr. Max Ott
Research Program Leader - Network and Pervasive Computing, NICTA Australia
Founder & CTO, Semandex Networks
Research Professor, WINLAB, Rutgers University
Senior Visiting Fellow, School of EE&T, UNSW