1st time I've installed IC6.15 on the RHEL5.4. Everything was OK.
For some reasons I nedded to change the OS for RHEL6.2. This time installation was OK, but next step - tool configuration - failed.
Inside of the iscape_log file I've found nothing, that I could explore to debug the problem. Below I've put the extract from escape log.
So, I've 2 questions:
1. Is configuration phase crucial for the tool functionnality ?
2. How can I debug this issue if there is no consistent diagnostic info ?
Thank you in advance.
P.S. Extract from escape_log (final part):
Running Configuration of components in GUI.Running:/bin/sh /opt/Cadence/IC615/install/tmp/slconfig.sh CSRCO07.24-p031lnx86Error::Return Value is:1Running:/bin/sh /opt/Cadence/IC615/install/tmp/slconfig.sh amsEnv06.15-p003lnx86Error::Return Value is:1Running:/bin/sh /opt/Cadence/IC615/install/tmp/slconfig.sh DFII_ncvhdl64b09.20-s030lnx86Error::Return Value is:1Running:/bin/sh /opt/Cadence/IC615/install/tmp/slconfig.sh CSRCOIndep07.24-p031Error::Return Value is:1Running:/bin/sh /opt/Cadence/IC615/install/tmp/slconfig.sh lfvhdComp02.85-a002lnx86Error::Return Value is:1Running:/bin/sh /opt/Cadence/IC615/install/tmp/slconfig.sh DFII_ncvhdl09.20-s030lnx86Error::Return Value is:1Running:/bin/sh /opt/Cadence/IC615/install/tmp/slconfig.sh oaRedist22.41-p004lnx86Error::Return Value is:1Running:/bin/sh /opt/Cadence/IC615/install/tmp/slconfig.sh ihdl06.15-p003lnx86Error::Return Value is:1
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?
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 anymedium, whether in whole or in part, without prior written permissionfrom Cadence Design Systems, Inc.=================================================================================== checkSysConf: Version 3.16 ====================Configuration checks failed, status is: FAILcheckSysConf cannot reliably parse your systems /etc/redhat-release fileIt would appear that the file is non-standard and does not contain releaseinformation 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, containingversion 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]# lmstatbash: /opt/Cadence/IC615/tools/bin/lmstat: /lib/ld-lsb.so.3: bad ELF interpreter: No such file or directory
Last time I installed some packages, that probably damaged installscape-related files. Actually I cannot run InstallScape:
[root@Missouri iscape]# sh ./bin/iscape.shInitializing InstallScape using JVM at /opt/Cadence/InstallScape/iscape/runtime/LNX86/bin/java. This might take some time...No protocol specifiedException 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.
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 ~]$ hostnameMissouri[Pavel@Missouri ~]$ ping Missouriping: 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 problem19:11:29 (lmgrd) and is not recommended.19:11:29 (lmgrd) Unknown host: Missouri19: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.