Lock service on server1 is not responding

Hi,

My data server is red hat AS3 and client is solaris 6, when I run icfb at
client terminal, I get such error:
Failed to lock log file: /home/michael/CDS.log.9
*WARNING* file /home/michael/CDS.log.9 (clscompatd): Lock service on server1
is not responding

How to resolve it? If the data server is solaris, I may run 'cdsd', but
since higher version cadence run CLS as the lock service and I cannot find
the command 'cdsd', I'm helpless now. Maybe I may run compatible mode to do
but where to set it? Thanks for your help!

Have a good day!

B.R.

Joffre

 

I don't know exactly if it solves your problem fully, but I can answer two
of your questions

The new locking daemon is called 'clsbd'.

I may be wrong but if you run in non compatibility mode
the clsbd has only to run on the clients.
In compatibility mode I think on file sever and the client.
The compatibility mode can be set through the env. variable

CLS_CDSD_COMPATIBILITY_LOCKING = YES

Bernd

 

You can try to simply delete your old CDS.log<1..9>

As far as I know cadence can't produce CDS.log10 and onwards ...

Regards,

Stefan

 

Try also to run 'clsAdminTool' inside your project directory
and in your home directory to see if there are locked files.

When running 'clsAdminTool' you will get a prompt. You can
type help to get the command list and usage.
"ale" and "are" are the commands that list and remove locks.

Regards,

======================
Kholdoun TORKI

http://cmp.imag.fr
=======================

 

This will delete the *.cdslck, you may do it by hand, but it's not the
question. It need one replacement of cdsd to run on data server.

 

It seems that I've tried it but have no effect.

Where I set it? the user's initialization files '.bashrc'? firstly I think
it in .cdsenv. I'll try it. Thanks for your help!

 

Actually you probably want to turn the compatibility locking off.

In IC445 a new locking system "CLS" was introduced to replace cdsd, the
old daemon-based locking system.

Unless you are using IC443 or before on the databases you're accessing, there
is absolutely no need to use cdsd still. For a period of time there was a
compatibility mode where locks were obtained in both systems (cdsd and CLS),
to ensure that edits on the database from cdsd-only releases were still safe.
This compatibility mode was on until the first release after IC443 stopped being
supported - IC5.0.

The environment variable that Bernd mentions allows you to override this. I
assume that you're either using IC446 or IC445, in which case you can safely
turn off compatibility mode. Or if using IC5.0 or later, somebody has set
the environment variable unnecessarily.

If using bash, you'd do:

export CLS_CDSD_COMPATIBILITY_LOCKING=NO

in the .bashrc. csh users would put:

setenv CLS_CDSD_COMPATIBILITY_LOCKING NO

in their .login or .cshrc

(or in your environment setup, however you do that).

If using a release before IC443, you'll probably need to set up a cdsd proxy.
This is covered in the documentation. It was possible to set up a server on
a supported platform which was acting as the cdsd daemon for file access to
an unsupported platform - for example, if you were using a netapp server where
you clearly can't run a daemon on the server itself.

Regards,

Andrew.

 

Thanks for your answer! I've read the document, it need to run cdsd daemon,
but the linux server mayn't
find this daemon. Do you mean set up one proxy server on another machine?
Then how should I
set up connection between the data server and the proxy machine?

 

You didn't say which version you're using - so I'm not sure whether you really
do need to run cdsd. I'll assume you're running IC443 or earlier (which is
pretty old now, so I hope you have a very good reason to do that!).

The documentation covers how to set up a proxy.

I used to have one set up by doing this:

setenv CDS_LICENSE_DIR /software/indep/cdsd_proxy/share/license

In that directory I defined a file called "proxy" which had the following
contents:

# Proxy definition for the netapp
cdsuk5 cdsuk7 /cdsuk5
cdsuk6 cdsuk7 /cdsuk6
bnnap1 cdsuk7 /bnnap1
bnnap2 cdsuk7 /bnnap2

What this says is that any access to the servers cdsuk5, cdsuk6, bnnap1, bnnap2
should send the lock request to server cdsuk7 (which was a Solaris server), and
that all paths from those machines should be stored in the lock data with a
prefix of /cdsuk5, /cdsuk6 etc.

You don't have to set CDS_LICENSE_DIR - you can simply put the file in the
share/license directory of your software installation - but this was a way of
making the proxy release independent.

In my case cdsuk5, cdsuk6, bnnap1 etc were Network Appliance File servers, but
it doesn't really matter. The idea is that the software sees this proxy file,
and then if it needs to lock something which is stored on one of the machines
in the proxy list, it sends the request to a different cdsd server instead.

Please read the documentation - it's fairly comprehensive on this.

Although the best solution is to use a version where you don't need to faff
around with setting up proxies...

Regards,

Andrew.

 

I'm using IC445 based on solaris 2.6. I need to run cdsd on the data server
when I'm using one
sun server, now it's replaced by one linux.

 

If you're using IC445, and aren't using an older release on the same data at the
same time, then the best thing is to just turn off cdsd compatibility mode. The
new locking system doesn't need a lock daemon running on the server, and this
avoids all the problems.

So, set the CLS_CDSD_COMPATIBILITY_LOCKING environment variable to NO,
as I suggested in a previous post in this thread, and your problem will be
resolved.

Regards,

Andrew.