Problem wuth tool configuring after installation (IC6.15)

Pavel,

You probably don't strictly need to run the configuration, but the above shouldn't happen. Maybe there's some package missing on your machine? I just ran it successfully on a RHEL6.1 machine (I'd be surprised if 6.2 was significantly different).

BTW, RHEL6 is not yet supported for IC615 - hopefully we should be supporting it from IC615 ISR12 onwards.

Perhaps you should contact Cadence Customer Support?

Andrew.

Andrew,

Thank you for response. It seems that my OS in some manner "isn't understood" by the cadence tools. Here is output of the command  checkSysConf IC6.1:

 =====================================================================
[Copyright 2002-2010] Cadence Design Systems, Inc. All rights reserved.

This  program and online  documentation  may not be copied, modified,
re-published, uploaded,  executed, or  distributed in any way, in any
medium, whether in whole or in part, without prior written permission
from Cadence Design Systems, Inc.
=====================================================================


============== checkSysConf:  Version 3.16 ====================



Configuration checks failed, status is: FAIL

checkSysConf cannot reliably parse your systems /etc/redhat-release file
It would appear that the file is non-standard and does not contain release
information in the standard readable format.

The contents of your /etc/redhat-release is listed below between
<RELEASE_FILE> tags.
A 'correct' release file should have only one line of content, containing
version information in a standard format.

<RELEASE_FILE>
Red Hat Enterprise Linux Client release 6.3 (Santiago)
</RELEASE_FILE>

Please check/correct your /etc/redhat-release file and try again.
There is no OEM datafile for IC6.1 for the Linux platform.

Valid OEM images are :  
foreach: No match.

Moreover I'm not sure, that license manager is run. Here is output of the lmstat:

[root@Missouri PIXIE-III]# lmstat
bash: /opt/Cadence/IC615/tools/bin/lmstat: /lib/ld-lsb.so.3: bad ELF interpreter: No such file or directory

Regards,

Pavel.

 Last time I installed some packages, that probably damaged installscape-related files. Actually I cannot run InstallScape:

[root@Missouri iscape]# sh ./bin/iscape.sh
Initializing InstallScape using JVM at /opt/Cadence/InstallScape/iscape/runtime/LNX86/bin/java. This might take some time...
No protocol specified
Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
    at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
    at sun.awt.X11GraphicsEnvironment.access$100(Unknown Source)
    at sun.awt.X11GraphicsEnvironment$1.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at sun.awt.X11GraphicsEnvironment.<clinit>(Unknown Source)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Unknown Source)
    at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(Unknown Source)
    at sun.awt.X11.XToolkit.<clinit>(Unknown Source)
    at java.lang.Class.forName0(Native Method)
    at java.lang.Class.forName(Unknown Source)
    at java.awt.Toolkit$2.run(Unknown Source)
    at java.security.AccessController.doPrivileged(Native Method)
    at java.awt.Toolkit.getDefaultToolkit(Unknown Source)
    at com.khanpur.installer.gui.InstallerUI.main(InstallerUI.java:88)
[root@Missouri iscape]#

That just suggests that it can't open an X window because it can't contact the X server. I get that if I don't have permissions to access the display - so this might just need you to do "xhost +" or something before trying to run it.

As I said, it's an unsupport platform, so checkSysConf won't be able to check required patches (because there's no list, because it's not supported).

As I said, contacting customer support is your best bet.

Andrew.

 Andrew,

I've advanced in my investigations - I think it's isn't Cadence issue, but rather RHEL. Obviously the problem comes from hostname. When I worked with RHEL5.2, there were no specific hostname - the output of the hostname command was localhost.localname or something like this. When I intalled RHEL6.2 I specified hostname - now it's Missouri. But surprisingly this hostname isn't completely recognized by system. When I do hostname, it's Ok, but ping doesn't work:

[Pavel@Missouri ~]$ hostname
Missouri
[Pavel@Missouri ~]$ ping Missouri
ping: unknown host Missouri

Moreover when I force to run license manager and see log file, I constate that my hostname is unknown:

 $CDS_ROOT/tools/bin/lmgrd -c $LM_LICENSE_FILE -l /var/log/ic615_debug.log

Here is extract from .log file:

19:11:29 (lmgrd) The license server manager (lmgrd) running as root:
19:11:29 (lmgrd)     This is a potential security problem
19:11:29 (lmgrd)     and is not recommended.
19:11:29 (lmgrd) Unknown host: Missouri
19:11:29 (lmgrd) EXITING DUE TO SIGNAL 33 Exit reason 1

I searched on the inet for the similar issues and found following solution - add my hostname in the /etc/resolv.conf.  I tried it, but without success.

Regards.

Pavel.

Pavel,

What do you have in /etc/hosts ?

Andrew

 Andrew,

Here is hosts content:

127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

You probably need to ensure the machine name is in the file. For example:

 127.0.0.1  Missouri Missouri.whateveryourdomainnameis localhost localhost.localdomain

Andrew.

Finally I decided to return to RHEL5.4.

It's Ok once more.

Thanks Andrew.

Hey man, this might be far out in left field, but I had a problem with my IC6.15.011 on RHEL 6.3 and this was one of the symptoms I was Googling. Dunno if this'll help, but maybe it'll help someone like me. My problem was that I could open a new Virtuoso Schematic Editor XL window, but when I tried to instantiate an instance, the system would hang and I'd see the following error message in the /root/CDS.log console:

> *WARNING* ddsInvokeBrowser: Unable to connect to library browser (60 tries) 

Someone online suggested taking a look at the Library Path Editor and when I tried to open this application I would get the following error message in the /root/CDS.log console:

> /root/cadence/installs/IC615/tools/dfII/bin/32bit/libManager: error while loading shared libraries: libXi.so.6: cannot open shared object file: No such file or directory

Well, I had had to install about a million 32-bit packages (to wit: libGL.so.1, libGLU.so.1, libelf.so.1, libXrender.so.1, libXp.so.6, libXi.so.6, libXext.so.6) on my 64-bit system manually just to get InstallScape and then Cadence to launch, so perhaps this was just one more I needed. I installed the binary 32-bit package for libXi from here:

http://pkgs.org/centos-6-rhel-6/centos-rhel-i386/libXi-1.3-3.el6.i686.rpm/download/ 

After that, the Library Path Editor would launch, but it would prompt for the creation of a new cds.lib file. Smelling a rat, I cancelled the dialog and went back to the Virtuoso Schematic Editor XL cell view and tried to place another instance, browsing for the appropriate library once again. This time, presto! The Library Browser - Add Instance dialog popped up and all the basic libraries were there! Problem solved! (for now)

Hooray for hidden library dependancies that only show up during runtime with totally worthless error messages! This whole installation has been a nightmare. For the record:

> uname -a 

Linux localhost 2.6.32-279.11.1.el6.x86_64 #1 SMP Sat Sep 22 07:10:26 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux