• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Digital Implementation
  3. Distributed Computing in SoC Encounter

Stats

  • Locked Locked
  • Replies 1
  • Subscribers 91
  • Views 12945
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Distributed Computing in SoC Encounter

trav1s
trav1s over 14 years ago

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:

  • Cancel
  • trav1s
    trav1s over 14 years ago

     [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.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information