• 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. Custom IC Design
  3. Unable to run Monte-Carlo simulation on ADE-XL

Stats

  • Replies 32
  • Subscribers 125
  • Views 2624
  • Members are here 0

Unable to run Monte-Carlo simulation on ADE-XL

rtyuy
rtyuy 1 month ago

Dear Friends,

I am using cadence virtuoso  (SUB VERSION: IC6.1.7-64b.500.19 (64-bit addresses)). Earlier Monte Carlo was running fine. but now when i run MC on ADEXL, it is showing following  error :

ADEXL-1921: failed to start new job after 3 attempts . Possible reasons could be

1. The machine selected in the current job set up policy is not reachable 

2. The cadence hierarchy is not detected, not installed properly, or not compatible on the machine selected in the current job set up policy.

3. Job start script /home/vlsi2/laxman/.temp_vlsi2/.cmddir0/runICRP17 is not found in the remote machine.

          Do you want to retry with the current set up? Selecting no will abort the current session.

Please  help me in finding the solution  of this problem.

i have  also  tried to change the license but it is still not working.

  • Sign in to reply
  • Cancel
Parents
  • Andrew Beckett
    Andrew Beckett 1 month ago

    I merged your posts (please read the forum guidelines - the pinned post at the top of each forum - as this tells you not to post duplicate posts in different forums; this will increase the chance of your post being ignored, not reduce it!)

    Anyway, what does your job policy look like? Can you run "virtuoso -nograph" on the machine it is launching to (the current machine if local)?

    Andrew

    • Cancel
    • Vote Up +1 Vote Down
    • Sign in to reply
    • Cancel
  • rtyuy
    rtyuy 1 month ago in reply to Andrew Beckett

    Andrew Beckett , thanks for the response i am unable to get it .It will be very kind of you if you can help me to solve this issue with more details.

    in job policy setup distribution method is local and it was run fine with it ealier from last 2 years.

    do you mean  run  a command  "virtuoso -nograph " on the terminal ???

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to rtyuy
    rtyuy said:
    do you mean  run  a command  "virtuoso -nograph " on the terminal ?

    Yes.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • rtyuy
    rtyuy 1 month ago in reply to Andrew Beckett

     Andrew Beckett , i dont know if i am doing correct , but output comes as follow

    Welcome to Cadence Tools Suite

    [vlsi2@eeiitj123 ~/laxman]$ virtuoso -nograph
    2025/07/19 18:56:22 WARNING This OS does not appear to be a Cadence supported Linux configuration.
    2025/07/19 18:56:22 For more info, please run CheckSysConf in <cdsRoot/tools.lnx86/bin/checkSysConf <productId>
    *WARNING* Could not open display eeiitj123.iitj.ac.in:80.  If no X server is running for this display,
    *WARNING* remove the file /tmp/.X80-lock: owner vlsi2, last modified Fri Jul 18 12:00:30 2025

    Trying another display...
    *WARNING* Could not open display eeiitj123.iitj.ac.in:81.  If no X server is running for this display,
    *WARNING* remove the file /tmp/.X81-lock: owner vlsi2, last modified Fri Jul 18 12:00:48 2025

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to rtyuy

    You're using a rather old version of Virtuoso (over 7 years old) and since then we've moved to a different way of creating the hidden X display used to support non-graphical mode. The older approach was shared between different sessions and then used locking to avoid things interfering with each other.

    I would suggest that (assuming you don't have any running virtuoso -nograph sessions on the machine) that you do:

    cd /tmp
    ls -al .X*-lock

    having checked these, do:

    rm .X*-lock

    and then try the "virtuoso -nograph".

    Usually it only tries 10 different displays and then gives up - so if they are all locked with stranded locks, it will fail. That's quite likely what is causing the problem.

    Better would be to move to a newer version - at least the latest IC6.1.8 hotfix or better still IC23.1.With IC23.1 you'd have to move to Assembler as ADE XL is no longer available (we've had quite a few years for people to adopt the newer generation ADE tools; it will prompt you to migrate to ADE Assembler if you try to open an adexl view though).

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • rtyuy
    rtyuy 1 month ago in reply to Andrew Beckett

    Andrew Beckett , i tried above commands and deleted the files. when i run thre virtuoso -nograph again , following error appears.

    WARNING* Could not open display eeiitj123.iitj.ac.in:81.  If no X server is running for this display,
    *WARNING* remove the file /tmp/.X11-unix/X81: owner vlsi2, last modified Fri Jul 18 12:00:48 2025

    Trying another display...
    *WARNING* Could not open display eeiitj123.iitj.ac.in:82.  If no X server is running for this display,
    *WARNING* remove the file /tmp/.X11-unix/X82: owner vlsi2, last modified Fri Jul 18 12:01:43 2025

    .

    .

    .

    .

    Trying another display...
    *WARNING* Could not open display eeiitj123.iitj.ac.in:89.  If no X server is running for this display,
    *WARNING* remove the file /tmp/.X11-unix/X89: owner vlsi2, last modified Fri Jul 18 12:14:03 2025

    *WARNING* Giving up after trying 10 displays.
    *WARNING* Unable to connect to a non-graphical X Window Display server.
    *WARNING* Try using the -vncTenbase option or the CDS_XVNC_TENBASE environment variable to specify a different set of 10 displ

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to rtyuy

    Try running "cdsXvnc" and seeing if that reports any errors.

    What OS are you running on (try running "lsb_release -a")?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Reply
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to rtyuy

    Try running "cdsXvnc" and seeing if that reports any errors.

    What OS are you running on (try running "lsb_release -a")?

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
Children
  • rtyuy
    rtyuy 1 month ago in reply to Andrew Beckett

    Andrew Beckett 

    OS INFORMATION

    LSB Version:    :core-4.1-amd64:core-4.1-ia32:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-ia32:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-ia32:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch
    Distributor ID:    CentOS
    Description:    CentOS Linux release 7.9.2009 (Core)
    Release:    7.9.2009
    Codename:    Core

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to rtyuy

    I saw this (before you added a mention of me just now), but you didn't answer my other question:

    Andrew Beckett said:

    Try running "cdsXvnc" and seeing if that reports any errors.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • rtyuy
    rtyuy 1 month ago in reply to Andrew Beckett

    Andrew Beckett  please find 

    Welcome to Cadence Tools Suite

    [inder@eeiitj123 ~/parm_tsmc65]$ cdsXvnc
    cdsXvnc: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to rtyuy

    OK, that means this machine needs to have another package installed (this is why -nograph is failing). The RPM (on my RHEL7.6 machine) is:

    compat-libstdc++-33-3.2.3-72.el7.i686

    I can see this from:

    myuser> rpm -q -f /usr/lib/libstdc++.so.5
    compat-libstdc++-33-3.2.3-72.el7.i686

    You might also want to consider moving to a more recent IC version - for example the latest IC6.1.8 hotfix (ISR36). cdsXvnc is no longer used in the later IC6.1.8 versions.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • rtyuy
    rtyuy 1 month ago in reply to Andrew Beckett

    Thank you for the response andrew, , actually right now the person who install cadence is not present in the lab so cant move to recent version.

    however can you please explain more about the package need to install, may be it help somewhat

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to rtyuy

    The package (RPM) is called compat-libstdc++ - you'd need to install this on the OS using yum, rpm or whatever is normally done. You'll need whoever looks after the OS (with root access) to do this. Anyone who knows about Linux admin should know what these packages are.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • rtyuy
    rtyuy 1 month ago in reply to Andrew Beckett

    Andrew Beckett  , i have installed the package

    user> rpm -q compat-libstdc++-33
    compat-libstdc++-33-3.2.3-72.el7.x86_64

    but when i run "cdsXvnc" again, i get

    user> cdsXvnc
    cdsXvnc: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory

    but if run

    root> sudo find / -name libstdc++.so.5 2>/dev/null
    /home/install/IC617/tools.lnx86/lib/64bit/libstdc++.so.5
    /home/install/IC617/tools.lnx86/lib/vnclibs/libstdc++.so.5
    ...

    .

    .

    /home/install/EXT181/tools.lnx86/lib/vnclibs/libstdc++.so.5
    /home/install/ASSURA41/tools.lnx86/lib/vnclibs/libstdc++.so.5

    Please let me know , how can i figure out this issue now?

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to rtyuy

    You've installed the 64-bit RPM - you need the 32-bit RPM as cdsXvnc is a 32-bit executable.

    However, you can probably workaround it by doing:

    setenv LD_LIBRARY_PATH $CDSHOME/tools/lib/vnclibs:$LD_LIBRARY_PATH

    (you might not have $CDSHOME set - this is a placeholder for your IC installation). I've also assumed csh - you might need equivalent export statement for bash/ksh or other Bourne-like shells.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • rtyuy
    rtyuy 1 month ago in reply to Andrew Beckett

    Andrew Beckett , dear can you please explain it more , where can i "setenv LD_LIBRARY_PATH $CDSHOME/tools/lib/vnclibs:$LD_LIBRARY_PATH" do this statement.

    and also how to go for it

    (you might not have $CDSHOME set - this is a placeholder for your IC installation). I've also assumed csh - you might need equivalent export statement for bash/ksh or other Bourne-like shells.

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • Cancel
  • Andrew Beckett
    Andrew Beckett 1 month ago in reply to rtyuy

    In the terminal before you start Virtuoso (where you are trying to run cdsXvnc) either type:

    setenv LD_LIBRARY_PATH /home/install/IC617/tools.lnx86/lib/vnclibs:$LD_LIBRARY_PATH

    or:

    export LD_LIBRARY_PATH=/home/install/IC617/tools.lnx86/lib/vnclibs:$LD_LIBRARY_PATH

    depending on which shell you're using. If it complains about LD_LIBRARY_PATH not being defined, try the command with the part from the colon (:) onwards missing (e.g. setenv LD_LIBRARY_PATH /home/install/IC617/tools.lnx86/lib/vnclibs )

    Then in the same terminal, run cdsXvnc (and if that works - it will probably complain about the display not being set), then try "virtuoso -nograph" and see whether that starts (you'll need to type exit() to quit that).

    Ultimately you'd put the setenv/export in whatever startup script you use to set up your environment.

    Andrew

    • Cancel
    • Vote Up 0 Vote Down
    • Sign in to reply
    • 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