cmviewcl not working for normal user,

[jeevarajkn]

Dear Guru's

OS--HP UX 11.23--rx6600

I am not able to excute the cmviewcl command by using normal user.

Permission denied to 127.0.0.1
cmviewcl: Cannot view the cluster configuration: Permission denied.
This user doesn't have access to view the cluster configuration.



I already add the entry in /etc/cmcluster/cmclnodelist.

But still problem existing.

Can anybody help me...

[Ivan Krastev]

Is your syntax correct, as described here - http://docs.hp.com/en/B5158-90024/ch05s01.html

Format is :
hostname username

regards,
ivan

[vjta]

Hi jeeva
can u post ur cmclnodelist contents here

you can add
hostname or
+
for other users

regards
vjta

[Jeeshan]

check this relevant link

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=971667

[Duncan Edmonstone · Accepted solution]

I'm going to make 2 assumptions based on what you've told us:

i) cmviewcl *does* work for the root user
ii) this node is already configured into a Serviceguard cluster

Serviceguard ignores the cmclnodelist file once the cluster node is configured and you then need to define rols in the package configuration files. This is described in the manual here:

http://docs.hp.com/en/B3936-90117/ch05s01.html#cacjcidg

scroll down to the section titled "Setting Access Controls for Configured Cluster Nodes"

HTH

Duncan

[Avinash20]

<<< I am not able to excute the cmviewcl command by using normal user. >>> ??

Jeevan: It is working fine for the root user ??
If not, then
Please see that nslookup to hostname or fully qualified domain names works.

Eg: If A and B are two nodes, then see that

# nslookup A
# nslookup B

## The above command gives the correct IP address on both the nodes

# nslookup
# nslookup

## The above commands resolves to the correct hostname on both the nodes

[jeevarajkn]

Hi All

This is my cmclnodelist entry in both nodes.

uaedxbpdctakp02>more /etc/cmcluster/cmclnodelist
uaedxbpdctakp01 root
uaedxbpdctakp02 root
uaedxbpdctakp01 uxgsmc
uaedxbpdctakp02 uxgsmc

But in my other cluster nodes this user can able to run cmviewcl with out this entry in cmclnodlist.

[Duncan Edmonstone]

So you're going to ignore my repsonse are you? It seems from what you are saying that you already have a running cluster. As I stated in my previous post, cmclnodelist is completely ignored once a cluster is created (i.e. the binary file /etc/cmcluster/cmclconfig exists).

From this point on you need to make sure you have the required entries for cluster or package admin, or just for monitoring in your cluster/package configurations. As described in the manual I pointed you at.

HTH

Duncan

[jeevarajkn]

Duncan,

Can you plesae confirm in which file I want to give the entry.

In my /etc/cmcluster/cmclconfig i didn't find any option but same time i found in /etc/cmcluster/pkg1/pkg1.conf file where my package name is pkg1.

I given the below entry in /etc/cmcluster/pkg1/pkg1.conf of both nodes.

USER_NAME ANY_USER
USER_HOST CLUSTER_MEMBER_NODE
USER_ROLE package_admin

But it didn't solve my issue...

[Duncan Edmonstone]

So you put the entries in the package configuration file, but did you check/apply the configuration using cmcheckconf -P ... and cmapplyconf -P ...

HTH

Duncan

[jeevarajkn]

duncan,

Yes i didn't check/apply the configuration file.

Let us know wheteher I can do it in online because server workingis in production and running.

[jeevarajkn]

Dear Guru's

Can anyone help me for the below query.

[sujit kumar singh]

Hi,


But just a note of precaution, it is always good that to do a cmapplyconf that with at least that packages down.
Hopefully for the packages u have a reliable failover and failback testing done.


In the same Document that has been suggested by Duncan u can refer to the Note that has been written over there.






NOTE: You do not have to halt the cluster or package to configure or modify access control policies.










though this is regarding the modification of user admin of the package u can try by doing that with the package up and running i mean both the parts as u have identical changes regarding the same.


However a cmcheckconf should always take place before the cmapplyconf.

U can easily do a cmcheckconf with the running cluster and packages considering that is the only change that u have made to the package conf file.

Regarding cmapplyconf it is already mentioned as a note that u do not need to stop the package or cluster, so grammatically u can go ahead.

But just a note of precaution, it is always good that to do a cmapplyconf that with at least that package down.


Also go thru the note that u should not define the conflicting policies.


So this is up to u â ¦. But I would have tried to do that with at least that package down â ¦ with the surety that the package failover and failback testing has been previously done

Regards
Sujit

[jeevarajkn]

Hi All

I am closing this thread.

[Abd-El-Kerim]

Changin items in cmclnodelist will not do anything since the cluster is already defined :(

For ordinary users recompile cluster file and set proper values for user permission related configuration settings (in the cluster config file)
To resolve root account permisison issues, stop "cm" related activities
#/etc/init.d/cmcluster.init stop

And Recompile cluster file right after that operation...
#cmapplyconf -C $SGCONF/cluster_file

[Abd-El-Kerim]

Changing items in cmclnodelist will not do anything since the cluster is already defined :(

For ordinary users recompile cluster file and set proper values for user permission related configuration settings (in the cluster config file)
To resolve root account permission issues, stop "cm" related activities
#/etc/init.d/cmcluster.init stop

And Recompile cluster file right after that operation...
#cmapplyconf -C $SGCONF/cluster_file