Known Problems and Solutions in Cadence Application Infrastructure

This document describes the known issues with Cadence^® Application Infrastructure and suggests the workarounds for these issues. Each issue is identified by a Cadence Change Request (CCR) number.

Related Topics

Introduction to the Cadence Infrastructure

What’s New in Cadence Application Infrastructure

General Issues

Problem: Application hangs on lock request to a remote system

Solution: Check whether the network lock daemons lockd and statd are running on the remote system. lockd and statd must always be running on every UNIX system that runs Cadence applications or stores data. Some applications that use read and write locks use the operating system’s fcntl function, which relies on lockd and statd daemons. (CLS Edit locks no longer use fcntl.) If the daemons are running, but calls to them still hang, verify that you have the latest operating system patches.

For DFII applications, you can also try the following workaround:

• Set the following environment variable:
  

  DD_DONT_DO_OS_LOCKS

Problem: Locking requests to a Linux machine fail

Description: Locking requests to a Linux machine fail with the following error:

“No locks available”

While CLS Edit locks no longer use fcntl, some applications that use read and write locks do use the operating system’s fcntl function. Locking requests to a Linux machine will fail if the Linux NFS server does not support locking.

Solution: Upgrade your NFS software to a version that supports locking. For DFII applications, you can also use the following workaround:

• Set the following environment variable:
  

  DD_DONT_DO_OS_LOCKS

Problem: Malformed Lock-Stake file

Description: Your Cadence application does not run and you get the following error:

*Warning* file /usr/xyz/CDS.log Malformed Lock-Stake file.

Failed to lock log file: /usr/xyz/CDS.log

Solution: A “Malformed Lock-Stake File” error message indicates that the Lock-Stake file is either empty or corrupted. A Lock-Stake file can be empty if it was created when the disk was full. A Lock-Stake file can be corrupted if it was manually edited or if the application or system exited abnormally.

Resolve the cause of the problem, for example, a full disk. If it is safe to remove the lock on the file, remove the Lock-Stake file (filename.cdslck) manually or with clsAdminTool.