I don’t have an “aisexec” section at all. I simply copied the sample file,
which did not have one.
I did figure out why it wasn’t logging. It was set to AMF mode and ‘mode’ was
‘disabled’ in the AMF configuration section. After changing that to ‘enabled’,
I now have logging. That allowed me to
On Fri, Jun 18, 2010 at 5:25 PM, Eliot Gable wrote:
> I am trying to set up Corosync + Pacemaker on a new CentOS 5.5 x86_64
> install, but when I try to start corosync, it just says [FAILED] and does
> not provide any further information. I created the authkey using
> corosync-keygen and created
I am trying to set up Corosync + Pacemaker on a new CentOS 5.5 x86_64 install,
but when I try to start corosync, it just says [FAILED] and does not provide
any further information. I created the authkey using corosync-keygen and
created a corosync.conf file. The log file remains empty and no err
On Fri, Jun 18, 2010 at 12:18 PM, Maros Timko wrote:
>> Despite your clocks being a bit out, "dampen" looks to be doing what
>> its supposed to...
>
> OK, vsp7 is more than 1 second ahead, still not that bad
> [r...@vsp7 ~]# date +%H:%M:%S.%N; ssh 135.64.30.29 date +%H:%M:%S.%N
> 10:07:15.09394300
> Despite your clocks being a bit out, "dampen" looks to be doing what
> its supposed to...
OK, vsp7 is more than 1 second ahead, still not that bad
[r...@vsp7 ~]# date +%H:%M:%S.%N; ssh 135.64.30.29 date +%H:%M:%S.%N
10:07:15.093943000
10:07:13.924642000
>
> Jun 17 15:13:27 vsp7 attrd_updater: [3
