Home > Community > Forums > Digital Implementation > Distributed Computing in SoC Encounter

Email

* Required Fields

Recipients email * (separate multiple addresses with commas)

Your name *

Your email *

Message *

Contact Us

* Required Fields
First Name *

Last Name *

Email *

Company / Institution *

Comments: *

 Distributed Computing in SoC Encounter 

Last post Tue, Jun 21 2011 10:18 PM by trav1s. 1 replies.
Started by trav1s 21 Jun 2011 10:08 PM. Topic has 1 replies and 1270 views
Page 1 of 1 (2 items)
Sort Posts:
  • Tue, Jun 21 2011 10:08 PM

    • trav1s
    • Not Ranked
    • Joined on Sun, Mar 6 2011
    • Posts 3
    • Points 30
    Distributed Computing in SoC Encounter Reply

    Version: Encounter v09.12-s159_1 (64bit)

    Flow: Foundation Flow

    OS: Linux CentOS 5.4

    Hi, I am trying to use superthreading in SoC Encounter through rsh, but I am getting this error:

    <FF> SETTING UP MULTI PROCESS DISTRIBUTION AND THREADING
    <FF> Running rsh on rfic19
    The time out for a rsh remote host to respond is 5 seconds.
    The time out for a remote job to respond is 30 seconds.
    rsh list of machines is  rfic19
    rsh attempted on rfic19
    rsh machine rfic19 is unavailable or not responding, removing from list. A higher value of -rshTimeout in the setDistributeHost command may resolve this issue
    "touch /home/travis/sensor_dma/backend/SCRIPTS/job_rfic19_7761_check" did not create a file as expected on machine rfic19
    new rsh list of machines is

    **ERROR: (ENCSYT-6692): [/home/travis/sensor_dma/backend/template/SCRIPTS/EDI/run_place.tcl]: Invalid return code while executing "/home/travis/sensor_dma/backend/template/SCRIPTS/EDI/run_place.tcl"
    **ERROR: (ENCSYT-6693): None of the specified machines are reachable.

     

    Why is the machine unreachable? Here is the output when I run a test command "pwd" in terminal:

    • Post Points: 5
  • Tue, Jun 21 2011 10:18 PM

    • trav1s
    • Not Ranked
    • Joined on Sun, Mar 6 2011
    • Posts 3
    • Points 30
    Re: Distributed Computing in SoC Encounter Reply

     [travis@rfic18 ~]$ rsh rfic19 pwd
    connect to address 192.168.40.19: Connection refused
    Trying krb4 rsh...
    connect to address 192.168.40.19: Connection refused
    trying normal rsh (/usr/bin/rsh)
    /home/travis

    So rsh seems to work, at least with the right rsh. I tried extending the timeout, but that didn't work.

    • Post Points: 5
Page 1 of 1 (2 items)
Sort Posts:
Started by trav1s at 21 Jun 2011 10:08 PM. Topic has 1 replies.