-----Original Message-----
From: Dejan Muhamedagic [mailto:deja...@fastmail.fm]
Sent: Friday, September 17, 2010 6:01 PM
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] cannot append to /var/log/cluster/corosync.log
permission denied
Hi,
On Fri, Sep 17, 2010 at 12:49:39AM +0800, Alister Wong wrote:
> Hi, all,
>
> I just setup a 2 node clusters in 2 RHEL server(5.5 x86_64).
>
> After I setup and it looked fine. However, I found in
> /var/log/messages I found some logs showed that it failed to append to
> corosync.log. I run the corosync as root.
>
> e.g.
>
> Sep 17 00:39:14 property01-b crmd: [17332]: info: do_state_transition:
State
> transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS
> cause=C_FSA_INTERNAL origin=notify_crmd ]
>
> Sep 17 00:39:14 property01-b crmd: Cannot append to
> /var/log/cluster/corosync.log: Permission denied
>
> Sep 17 00:39:14 property01-b crmd: [17332]: info: do_state_transition:
> Starting PEngine Recheck Timer
>
> Sep 17 00:39:14 property01-b crmd: Cannot append to
> /var/log/cluster/corosync.log: Permission denied
>
>
>
> Below is corosync.conf and crm configure result.
>
> Corosync.conf
>
> # Please read the corosync.conf.5 manual page
>
> compatibility: whitetank
>
>
>
> totem {
>
> version: 2
>
> secauth: off
>
> threads: 0
>
> interface {
>
> ringnumber: 0
>
> bindnetaddr: 192.168.200.15
>
> mcastaddr: 226.94.1.1
>
> mcastport: 5405
>
> }
>
> }
>
>
>
> logging {
>
> fileline: off
>
> to_stderr: no
>
> to_logfile: yes
Change this to:
to_logfile: no
And use just syslog.
Thanks,
Dejan
> to_syslog: yes
>
> logfile: /var/log/cluster/corosync.log
>
> debug: off
>
> timestamp: on
>
> logger_subsys {
>
> subsys: AMF
>
> debug: off
>
> }
>
> }
>
>
>
> amf {
>
> mode: disabled
>
> }
>
> aisexec{
>
> user: root
>
> group: root
>
> }
>
> service{
>
> # Load the Pacemaker Cluster Resource Manager
>
> name: pacemaker
>
> ver: 0
>
> }
>
>
>
> Crm configure:
>
> node property01-a
>
> node property01-b
>
> property $id="cib-bootstrap-options" \
>
> dc-version="1.0.9-89bd754939df5150de7cd76835f98fe90851b677" \
>
> cluster-infrastructure="openais" \
>
> expected-quorum-votes="2"
>
>
>
> Here is the /var/log/corosync/corosync.log permission info:
>
> [r...@property01-b corosync]# ls -l /var/log/cluster/
>
> total 148
>
> -rw-rw---- 1 root root 145285 Sep 17 00:39 corosync.log
>
>
>
> From corosync.log
>
> Pcmk and corosync should able to write the log in corosync.log
>
> Sep 17 00:39:07 corosync [pcmk ] info: pcmk_peer_update: MEMB:
property01-b
> 80259264
>
> Sep 17 00:39:07 corosync [pcmk ] info: send_member_notification: Sending
> membership update 72 to 2 children
>
> Sep 17 00:39:07 corosync [pcmk ] info: update_member: 0x5275c50 Node
> 80259264 ((null)) born on: 72
>
> Sep 17 00:39:07 corosync [TOTEM ] A processor joined or left the
membership
> and a new membership was formed.
>
> Sep 17 00:39:07 corosync [pcmk ] info: update_member: 0x527cec0 Node
> 63482048 (property01-a) born on: 72
>
> Sep 17 00:39:07 corosync [pcmk ] info: update_member: 0x527cec0 Node
> 63482048 now known as property01-a (was: (null))
>
> Sep 17 00:39:07 corosync [pcmk ] info: update_member: Node property01-a
now
> has process list: 00000000000000000000000000013312 (78610)
>
> Sep 17 00:39:08 corosync [pcmk ] info: update_member: Node property01-a
now
> has 1 quorum votes (was 0)
>
> Sep 17 00:39:08 corosync [pcmk ] info: send_member_notification: Sending
> membership update 72 to 2 children
>
> Sep 17 00:39:08 corosync [MAIN ] Completed service synchronization, ready
> to provide service.
>
>
>
> The cluster was just setup and the current configure is so simple, but I
> can't find out what did I do to cause this issue. Can anyone help me to
get
> rid of the permission issue? I have no clue to find out the cause.
>
> Thank you very much.
>
>
>
> Regards,
>
> Alister
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs:
http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
Hi, Dejan,
Thanks. It works. However, I have another cluster was finished setup
about a month ago and they didn't have this problem.
Anyway, thank you.
Regards,
Alister
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs:
http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://developerbugs.linux-foundation.org/enter_bug.cgi?product=Pacemaker
