Unable to run Monte-Carlo simulation on ADE-XL

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

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 ???

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

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

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

Andrew

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

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

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

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

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

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

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?

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

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

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.

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

Andrew Beckett 

[user@eeiitj123 ~]$ setenv LD_LIBRARY_PATH /home/install/IC617/tools.lnx86/lib/vnclibs:$LD_LIBRARY_PATH
LD_LIBRARY_PATH: Undefined variable.
[user@eeiitj123 ~]$ export LD_LIBRARY_PATH=/home/install/IC617/tools.lnx86/lib/vnclibs:$LD_LIBRARY_PATH
LD_LIBRARY_PATH: Undefined variable.
[user@eeiitj123 ~]$ setenv LD_LIBRARY_PATH /home/install/IC617/tools.lnx86/lib/vnclibs
[user@eeiitj123 ~]$ cd parm_65phd/
[user@eeiitj123 ~/parm_65phd]$ csh
[user@eeiitj123 ~/parm_65phd]$ source /home/install/cshrc

Welcome to Cadence Tools Suite

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

still the error occurs!

My guess is that the /home/install/cshrc is resetting LD_LIBRARY_PATH - so perhaps you should set it after sourcing that file.

Note, the right thing is to install the 32-bit compat package, but this may give you a workaround. Also, the really right thing is not to be using such an old and unsupported version of Virtuoso...

Andrew

Andrew Beckett if do source /home/install/cshrc

i move to 

Welcome to Cadence Tools Suite

[user@eeiitj123 ~/parm_65phd]$ export LD_LIBRARY_PATH=/home/install/IC617/tools.lnx86/lib/vnclibs:$LD_LIBRARY_PATH
export: Command not found.

(I understand that i am using older version but i have no  other option as i told earlier  :(  )
 

Since you were starting csh earlier, you will need to use the "setenv" approach instead. export is for bash/ksh type shells.

Andrew

 Andrew Beckett ,  i have done

[user@eeiitj123 ~/parm_65phd]$ setenv LD_LIBRARY_PATH /home/install/IC617/tools.lnx86/lib/vnclibs:$LD_LIBRARY_PATH
[user@eeiitj123 ~/parm_65phd]$ setenv LD_LIBRARY_PATH /home/install/IC617/tools.lnx86/lib/vnclibs

user@eeiitj123 ~/parm_65phd]$ cdsXvnc
Couldn't open RGB_DB '/usr/X11R6/lib/X11/rgb'
23/07/25 02:55:27 Xvnc version 3.3.7 - built May 31 2004 15:31:52
23/07/25 02:55:27 Copyright (C) 2002-2003 RealVNC Ltd.
23/07/25 02:55:27 Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
23/07/25 02:55:27 All Rights Reserved.
23/07/25 02:55:27 See http://www.realvnc.com for information on VNC
23/07/25 02:55:27 Desktop name 'x11' (:0)
23/07/25 02:55:27 Protocol version supported 3.3
23/07/25 02:55:27 Listening for VNC connections on TCP port 5900

Fatal server error:
Couldn't add screen

That's expected - as I said earlier:

Andrew Beckett said:

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

Hopefully if that is all successful, then you'll be able to run simulations in ADE XL or Assembler.

Andrew

 Andrew Beckett  again same problem

Welcome to Cadence Tools Suite

[user@eeiitj123 ~/parm_65phd]$ virtuoso -nograph
2025/07/23 12:15:13 WARNING This OS does not appear to be a Cadence supported Linux configuration.
2025/07/23 12:15:13 For more info, please run CheckSysConf in <cdsRoot/tools.lnx86/bin/checkSysConf <productId>
*WARNING* Unable to open -nograph X Window Display "eeiitj123.iitj.ac.in:80"
*WARNING* (using "exec /home/install/IC617/tools.lnx86/dfII/../bin/cdsVncserver :80 -co /usr/share/X11/rgb&").
*WARNING* cdsXvnc output may be found in file $HOME/.vnc-cds/eeiitj123.iitj.ac.in:80.log
Trying another display...
*WARNING* Unable to open -nograph X Window Display "eeiitj123.iitj.ac.in:81"
*WARNING* (using "exec /home/install/IC617/tools.lnx86/dfII/../bin/cdsVncserver :81 -co /usr/share/X11/rgb&").
*WARNING* cdsXvnc output may be found in file $HOME/.vnc-cds/eeiitj123.iitj.ac.in:81.log
Trying another display...

rtyuy said:

*WARNING* cdsXvnc output may be found in file $HOME/.vnc-cds/eeiitj123.iitj.ac.in:80.log

Since it is telling you that there's a problem and it created a log file, can you share the log file?