Urgent !!

[Kenn Chen]

Any idea about the below error log in syslog.log ? Thanks.
=====================================
Aug 18 11:54:01 sin_unix cmclconfd[15973]: Permission denied for user root on node samasia.sdsoscc.co.kr (2)
Aug 18 11:58:21 sin_unix LVM[17147]: /sbin/lvlnboot -v vg00
Aug 18 11:58:21 sin_unix LVM[17150]: /sbin/lvlnboot -v vg00

[Sridhar Bhaskarla]

on samaisa, edit $HOME/.rhosts entry and place
sin_unix root and
samaisa.sdso..kr root

Do the same on sin_unix also

$HOME is the home directory of the root account by default it is /.

You can also use cmnodelist in /etc/cmcluster directory.

-Sri

[eran maor]

Hi

Both running lvlnboot -v from command line and using Sam will log repeated lvlnboot -v commands to the syslog.
SAM--> Disks and Filesystems --> Disk Devices

Check the samlog

SAM--> Options --> View SAM Log
to see if the access date/times correspond to the entries in syslog.

These messages are informational only.

[linuxfan]

Hi,


The above situation arises because of two reasons

1. samasia and sin_unix are two nodes in the cluster and you haven't updated the /.rhosts or the /etc/cmcluster/cmclnodelist to be to talk to each other.

2. You have the set up correctly but you have multiple clusters in the same subnet. For eg: sin_unix and nodeA are in a cluster and you are forming a new cluster with samasia and nodeB, since samasia does not permissions to talk to sin_unix you would be seeing this errors.

what you should do to avoid this?
1. If indeed samasia and sin_unix belong to the same cluster then update the .rhosts or cmclnodelist
2. When you are setting up new clusters run cmquerycl -n samasia -n nodeB to limit the query to just those two hosts.

-HTH
I am RU

[Tim D Fulford]

Idris

Further to Sri's point (which will work for the 1st mesage).

You do not seem to have root equivalence between two of your ServiceGuard Clustered nodes. This would normally be checked when the cluster was generated so someone has edited the equivalences!!! I'm assuming this was due to security issues. You can do this by having a /etc/cmcluster/cmnodelist with the appropriate users & machines eg
machine1 root
machine2 root
machine3 ...

Tim