|
List Info
Thread: LAM: problems getting LAM to boot
|
|
| LAM: problems getting LAM to boot |
|
2006-10-16 13:47:23 |
|
Hello everybody,
I'm trying to start the parallel environment in our cluster; for testing purposes I've chosen two nodes, 192.168.25.32 and 192.168.25.33, 32 being the node where the lamboot command is launched.
Both the commands
recon -v -b lamhost
lamboot -v -b lamhost
give more or less the following message:
ssi:boot:base:linear: booting n0 (192.168.25.32)
ssi:boot:base:linear: booting n1 (192.168.25.33)
ERROR: LAM/MPI unexpectedly received the following on stderr:
TERM environment variable not set.
Followed by the standard stuff:
LAM attempted to execute a process on the remote node "192.168.25.33",
but received some output on the standard error. This heuristic
assumes that any output on the standard error indicates a fatal error,
and therefore aborts. You can disable this behavior (i.e., have LAM
ignore output on standard error) in the rsh boot module by setting the
SSI parameter
boot_rsh_ignore_stderr to 1.
You have any idea what TERM it actually wants? Or how to specify it? My .bashrc has TERM set as xterm.
For the coarse-natured the penance of self-denial is the only effective purge.
 
Get your own web address for just $1.99/1st yr. We'll help. Yahoo! Small Business.
|
[1]
|
|
|
about | contact Other archives ( Real Estate discussion Medical topics )
|