Stats

  • Locked Locked
  • Replies 6
  • Subscribers 126
  • Views 14692
  • 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

IC5141usr6 on CentOS 4 in VMware

beschorn
Hi, I have a question regarding my installation of IC5141 in VMware: there is a long waiting circle, after every command I do (open a cell, creating a path, place am instance and so on). I thought, maybe there is a problem of the network connection to the license server, but even if I open cells in Read mode, I have the same problem. Is there a way, to get a log of messages from icfb (not the CDS.log), or is there a kind of debug option implemented? Configuration: IC5141usr6 installation OS: CentOS 4 (32bit) running in VMware Player 3.0.1 License server connected via network LAN Host System: Win7 64 bit Thanks for your help

  • Hi,

    First let me say that running under VMware is not officially supported, however, having said that, there are lots of folks doing this without problems (I don't really have any experience with this though).  You can trace system level calls using "strace", and potentially produce stack file every so often using "pstack". As an end user it might be difficult to glean any useful information from the output files though! Perhaps someone else on the forum has more experience with VMware?

    Sorry I am not helping much.

    Regards,

    Lawrence.

  • And also CentOS is not a supported Linux Distribution (although that's probably not the root cause)...

    I'd suggest contacting customer support - so we can then work with you to figure out what is going on.

    Best Regards,

    Andrew.

  • If you have a Skill Development license you can try to see what commands are causing delays by using tracef. I've debugged this kind of problem before by running tracef(t) in the CIW, then issuing the command or opening a cell. LOTS of data will be output to your CDS.log file, but often times, you can see the command in the CIW where Cadence is hanging. Most commands will fly by in the CIW, but those that hang will appear long enough for you to read them. Once you Cadence finishes processing the command, you can turn off the trace with untrace().

    Derek

  • Hi Derek, Thanx for your hint. I think, I have found the root cause. It seems, that the connection to the license server is slow or disconnected. It says in CIW: _deApplyTrigger(leEnableTrigger((nil checkOutLicenses t accessMode "a"))) after that I have to wait until true deApplyTrigger--> t Afterwards I can work without any problems until I start a new command (for example: drawing a path). Than I have again to wait. Do you think, there is a way, to exclusively lock the license? For example, if I want to work from home, I could take the license with me until the next day, when I connect again to the company network? Thank you for your help, Erich

  • We had a problem recently where the license access was slow for a particular setup. It turned out that our license file variable had a colon separated list of license files. One of the servers hosting one of those license files was not accessible from this particular machine. This caused an excessive wait until the license check timed out. When we changed our license file variable and restarted Cadence, all of the delays went away. You might want to check your CDS_LIC_FILE or LM_LICENSE_FILE variables for a similar issue.

    Derek

  • It should not be checking for a license on every operation - only if the license has been lost (due to network outage, license server restart, or timeouts on the license server) - normally it checks periodically for licenses, and even then it doesn't wait for a response (except the first time around).

    So something sounds amiss. You really should contact customer support so we can investigate this properly.

    License "borrowing" is not supported currently.

    Regards,

    Andrew.

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.