ORBIT-USER: Error: Nodes do not come up

[Vijay Subramanian]

Hi,
Thanks for the confirmation. I commented out
"allNodes.startApplications" and the parse errors disapperared.
However, the TCP connect calls still failed when I tried this morning.
I tried changing ports and tried both 'a' and 'b' channels.

The last few lines of output and the script are below. Any help you
can provide is appreciated.
The script I am using is at
http://poisson.ecse.rpi.edu/~vijay/orbit-scripts/tcpmanytomany.rb

Exp ID:
Experiment grid_2007_08_01_07_49_40 finished after 10:28


Last lines of Output:
INFO stdlib: Waiting for nodes (Up/Down/Total): 7/3/10 - (still down:
n_4_6,n_17_16,n_11_1)
 WARN stdlib: Giving up on node n_4_6
 WARN stdlib: Giving up on node n_17_16
 WARN stdlib: Giving up on node n_11_1
 INFO stdlib: Waiting for nodes (Up/Down/Total): 7/3/10 - (still down:
n_4_6,n_17_16,n_11_1)
 INFO whenAll: *: 'apps/app/status[@value='INSTALLED.OK']' fires
starting soon
 INFO OML: Started: {"port"=>"7600", "iface"=>"eth2", "addr"=>"224.0.0.6"}
ERROR NodeApp: connect: Connection refused
ERROR NodeApp: Exception:Connect to TCP server failed
ERROR NodeApp: connect: Connection refused
ERROR NodeApp: Exception:Connect to TCP server failed
ERROR NodeApp: connect: Connection refused
ERROR NodeApp: connect: Connection refused
ERROR NodeApp: Exception:Connect to TCP server failed
ERROR NodeApp: Exception:Connect to TCP server failed
ERROR NodeApp: connect: Connection refused
ERROR NodeApp: Exception:Connect to TCP server failed
 INFO Experiment: DONE!
 INFO ExecApp: Application 'commServer' finished
 INFO run: Experiment grid_2007_08_01_07_49_40 finished after 10:28





On 31/07/07, Max Ott <max at semandex.net> wrote:
> Yes, theres seems to be a problem with the script or the way it is
> interpreted. What you basically seeing is the creation of a malformed
> configuration file for OML. Can you please send us the script you are
> using?
>
> Thanks,
>
> -max
>


-- 
Networks Lab, RPI
http://poisson.ecse.rpi.edu/~vijay