Stats

  • Locked Locked
  • Replies 1
  • Subscribers 126
  • Views 9751
  • 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

Is that OK to use clsdb from different version of cadence tool

Kian Boon

Hi,

I'm current using network machine "nc grid" for job submission and frequently bumped into below error message:


*WARNING* file /nfs/proj/sires/sidisp/user/wjguo/WARD_N7/CDS.log.28 cls: Unable to connect to clsbd on host "snc9-arvrgrid-09-05-03.thefacebook.com".
Check if clsbd is running on the host. If the host is not valid remove
the ".cdslck" lock file. The connect timeout length can be set using
the CLS_CLSBD_CONNECT_TIMEOUT environment variable.

Wondering what could be the root cause for this issue to happen, since the cellview are close correctly.

Further tracing, found that the clsbd is from cadence sigrity but not from cadence.

[kianboon@snc-arvrusr8867 N7_TEST]$ which clsbd
/nfs/tools/cadence/sigrity/SIGRITY2019/tools/bin/clsbd
[kianboon@snc-arvrusr8867 N7_TEST]$ which virtuoso
/nfs/tools/cadence/virtuoso/ICADVM21.10.190/tools/dfII/bin/virtuoso
 

Question: Is there OK for the use model above?

-Kian Boon-

Parents

  • Kian,

    The clsbd daemon is a very lightweight daemon that hasn't really changed in many years. It doesn't retain state - it's whole purpose in life is to answer questions about whether a process is alive or not - so the protocol to talk to it is simple and so any version would do.

    If clsbd is running on snc9-arvrgrid-09-05-03.thefacebook.com (note it's the machine recorded in the cdslck file that matters - the idea is that a process aiming to get the lock asks the boolean daemon (clsbd) on the machine that had the lock whether the process locking the file is still running to determine whether the lock can be safely recovered), then the most likely issue is that something in your network is blocking the port it uses. The normal port that clsbd uses is 16723 (this talks about how you change it, but that has to be done absolutely everywhere for this to be useful/safe): Cadence Application Infrastructure User Guide -- Cadence Locking System - Changing the CLS Boolean Daemon's Port Number

    If this doesn't help, I would suggest contacting customer support.

    Andrew

Reply

  • Kian,

    The clsbd daemon is a very lightweight daemon that hasn't really changed in many years. It doesn't retain state - it's whole purpose in life is to answer questions about whether a process is alive or not - so the protocol to talk to it is simple and so any version would do.

    If clsbd is running on snc9-arvrgrid-09-05-03.thefacebook.com (note it's the machine recorded in the cdslck file that matters - the idea is that a process aiming to get the lock asks the boolean daemon (clsbd) on the machine that had the lock whether the process locking the file is still running to determine whether the lock can be safely recovered), then the most likely issue is that something in your network is blocking the port it uses. The normal port that clsbd uses is 16723 (this talks about how you change it, but that has to be done absolutely everywhere for this to be useful/safe): Cadence Application Infrastructure User Guide -- Cadence Locking System - Changing the CLS Boolean Daemon's Port Number

    If this doesn't help, I would suggest contacting customer support.

    Andrew

Children
No Data

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.