On Fri, Sep 17, 2010 at 1:37 PM, Michele Pellegrini
wrote:
> Change log owner and group to:
>
> -rw-rw 1 hacluster haclient 111231 17 set 13:01
> /var/log/corosync/corosync.log
>
> and check logrotate config (if you use it).
>
> Even if in corosync.conf you have specified "user: root" the crmd
Change log owner and group to:
-rw-rw 1 hacluster haclient 111231 17 set 13:01
/var/log/corosync/corosync.log
and check logrotate config (if you use it).
Even if in corosync.conf you have specified "user: root" the crmd daemon
is executed as hacluster and not as root. I think this change has
-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
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
> coros
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
