ORBIT-USER: Node always reset and iperf problem inside spatial switching image

[Arinto Murdopo]

Actually I'm not the one who aborted it at that time. It is aborted
automatically. How to set up these two parameters?

Thank you

Arinto

On 2/17/07, Max Ott <max at semandex.net> wrote:
>
> Your iperf is most likely working perfectly. It has been OMLifed and
> therefore is looking for OML configuration information which you
> aren't providing. It most likley shouldn't abort but that's a choice
> made by whoever made the OML related modifications.
>
> Now as why nodehandler want recognize the two nodes checking in.
> Unfortunately, the log files are being cleaned up to quickly - Can
> somebody please change the cleaning procedure to be less eager - and
> are already gone.
>
> Sorry for not being able to help you more here, but I doubt that the
> problem lies with iperf.
>
> -max
>
> On 2/15/07, Arinto Murdopo <arinto at gmail.com> wrote:
> > Sorry, I forgot to attach the ExpIperf.rb
> >
> > here they are
> >
> >
> > On 2/15/07, Arinto Murdopo <arinto at gmail.com> wrote:
> > > Dear all,
> > >
> > > I try to run example in iperf experiment script from
> >
> http://www.orbit-lab.org/wiki/Documentation/OtherApps/Iperf/ExperimentScript
> > using spatial switching image click-2.4.26-20051204.ndz. However, during
> the
> > experiment, the node in sanbox always reset. I attach the expriment file
> in
> > this email. Do I need to reconfigure iperf inside Click image? Here is
> the
> > detailed output of the experiment:
> > >
> > > command: nodehandler ExpIperf.rb
> > >
> > > experiment ID = sb1_2007_02_15_00_01_03
> > >
> > > Using logfile /etc/nodehandler/nodehandler_log.xml
> > >  INFO init: NodeHandler Version 3.6.4-1 (849)
> > >  INFO init: Experiment ID: sb1_2007_02_15_00_01_03
> > >  INFO Experiment: load system:exp:stdlib
> > >  INFO prop.resetDelay: resetDelay = 180:Fixnum
> > >  INFO Experiment: load ExpIperf
> > > /tmp/eee.661/lib/util/communication.rb:127: warning:
> > Insecure world writable dir /tmp, mode 041777
> > >  INFO n_1_1: Checked in as /ip/10.11.1.1 booting off UNKNOWN
> > >  INFO n_1_2: Checked in as /ip/10.11.1.2 booting off UNKNOWN
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  WARN stdlib: Resetting node n_1_1
> > >  INFO n_1_1: Resseting node
> > >  WARN stdlib: Resetting node n_1_2
> > >  INFO n_1_2: Resseting node
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  WARN stdlib: Resetting node n_1_1
> > >  INFO n_1_1: Resseting node
> > >  WARN stdlib: Resetting node n_1_2
> > >  INFO n_1_2: Resseting node
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  INFO stdlib: 2 out of 2 node(s) still down n_1_1,n_1_2
> > >  WARN stdlib: Resetting node n_1_1
> > >  INFO n_1_1: Resseting node
> > >  WARN stdlib: Resetting node n_1_2
> > >  INFO n_1_2: Resseting node
> > >
> > > And also I found some error when I try to run iperf using ssh in
> node1-1
> > or node 1-2. This node using spatial switching image. Here is the output
> > >
> > > node1-2:~/iperf# iperf -s
> > > ERROR(oml) Could not get either OML_NAME or OML_CONFIG from env
> > > terminate called after throwing an instance of 'int'
> > > Aborted
> > >
> > > What happen with above iperf? Any explanation about this?
> > >
> > > Thank you
> > >
> > > Arinto
> > >
> > >
> > >
> >
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://orbit-lab.org/pipermail/orbit-user/attachments/20070218/1f6b6c10/attachment.htm