Stats

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

 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) 

 

Parents
  • Andrew Beckett

    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.

Reply
  • Andrew Beckett

    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.

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.