• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Custom IC Design
  3. Freezing error when working in IC6.15

Stats

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

Freezing error when working in IC6.15

Kabal
Kabal over 12 years ago

 Hello, there are different machines we have with IC6.15 setup. I sometimes take hard drive with own cadence files startup folder, and attach it on one machine, start off IC6.15 from my directory in harddrive, work there, then save stuff. Sometimes I attach it to other machines and do same.

 What happens is, sometimes when I work on one machine, and do some operation (Open schematic cell, or for example open adexl cell), the following error comes up:

WARNING (ADEXL-1924): Could not get the status of ICRP process owning the log file /media/cadence/logs_kabal/Job0.log.
Reason : cls: Unable to connect to clsbd on host "ptdes.01".
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.
.
Trying the next index for the log file.

 

 This error pops up in CIW, ptdes.01 is one machine on which I worked previously (and maybe saved some stuff on my harddrive etc), and currently I am on another machine.

When this happens, I see some freezing for about maybe 8 seconds or so, but then it all works just fine. I dont have any other problems, its just this delay occurs sometimes due to this error.

 From what I understand, it wants for some reason to check out some stuff with machine on which I worked on before, then it cannot of course, and I can continue work on new machine.

 

So basically how can I ask IC6.15 not to do those checks? (and this not give me those freezing sometimes) 

 

  • Cancel
  • theopaone
    theopaone over 12 years ago

    The problem is in the error message, there is an existing .cdslck file for the log file left over from your last session. It cannot determine if it could reuse the log file. The .cdslck file contains the name of the system, which is displayed in the error message:

    Unable to connect to clsbd on host "ptdes.01".

    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.

    If you set the environment variable CDS_LOG_VERSION to sequential or pid, it should fix the problem.

    Ted

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kabal
    Kabal over 12 years ago

     I tried the following:

    1) Remove the lock files when I am done working on one machine, and when I moved to another machine those lock files were not there, however; same error again popped up.

     

    2) I tried both:

    setenv CDS_LOG_VERSION pid

    setenv CDS_LOG_VERSION sequential

    And that did not fix the problem either, any other thoughts?

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kabal
    Kabal over 12 years ago

     I also tried this:

    setenv CLS_CDSD_COMPATIBILITY_LOCKING NO
    setenv DD_DONT_DO_OS_LOCKS

     Nothing helps, still same error I get when I move from one machine to another (again simulation and everything else works just fine, its just this error pops up from time to time and makes things freeze for around 6-9 seconds)

     

    What else could be root of the problem?

     

    OFF TOPIC: How come I see annoying commercial pop-up videos on this website..

     

    P.S. Someone copied my topic to another in this forum, and Andrew helped out there, I guess this thread can be deleted now.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    A few comments (I don't see a copy of your topic to another one, by the way - unless you're talking about /forums/T/24537.aspx - which appears to have been created by you too?).

    1. I gave an explanation of how locking works in /forums/p/25778/1322020.aspx#1322020
    2. CLS_CDSD_COMPATIBILITY_LOCKING does nothing these days - it was used in older versions which had to coexist with the old "cdsd" locking mechanism - that finally went away in about IC50 - so something like 10 years ago.
    3. The env vars to control sequential logs and suffixes are not used for the ADE XL "ICRP" job log files - they're always stored in the logs_userName dir.
    4. Your use model of physically moving the disk is a bit odd, to say the least - don't you have networked machines?
    5. My guess is  that you're pulling the disk when something is still running, and hence the lock files remain (see the other post that I referenced), and then the new machine has no network access to the original and hence clsbd can't be talked to? Or that you shut down the original machine and when rebooted clsbd is no longer running?

    I don't see commercial popup-videos, by the way. Have you got something intercepting your internet connection and adding stuff around web pages?

    Regards,

    Andrew.

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Kabal
    Kabal over 12 years ago

     OK, now that is too weird. Yes, commercials were due to some stuff accidentally installed with some software, I removed it and got rid of those.

     But that topic, No! I did NOT create it! 

    I just thought that Admins re-created my post, my post was "Freezing error when working in IC6.15" and definitely not "Schematic slows down while readin unnecessary logs" I have no idea how did that pop up there!

     

     

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
  • Andrew Beckett
    Andrew Beckett over 12 years ago

    It wasn't me either - and I do most of the moderation on the Custom IC and RF forums - maybe one of the system admins did it for some reason (don't know why though).

    Very odd!

    Oh well - hopefully OK in the end.

    Andrew. 

    • Cancel
    • Vote Up 0 Vote Down
    • Cancel

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.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information