Re: [ClusterLabs] Resource-agents log is not output to /var/log/pacemaker/pacemaker.log on RHEL8

2019-05-29 Thread
or the written log may disappear? I have never actually had a problem, but I'm interested in how this might happen. Regards, Yusuke 2019年5月28日(火) 23:56 Jan Pokorný : > On 28/05/19 09:29 -0500, Ken Gaillot wrote: > > On Mon, 2019-05-27 at 14:12 +0900, 飯田雄介 wrote: > >> By the way, when

[ClusterLabs] Resource-agents log is not output to /var/log/pacemaker/pacemaker.log on RHEL8

2019-05-26 Thread
Hi, I am verifying the operation of the cluster with RHEL8. In the verification, I noticed that resource-agents log was not output to /var/log/pacemaker/pacemaker.log. "/etc/sysconfig/pacemaker" is used by default. I know that resource-agents logs are output when passing the HA_logfile

Re: [ClusterLabs] How can I prevent multiple start of IPaddr 2 in an environment using fence_mpath?

2018-04-17 Thread
using fence_mpath? > > On Fri, 2018-04-06 at 04:30 +, 飯田 雄介 wrote: > > Hi, all > > I am testing the environment using fence_mpath with the following > > settings. > > > > === > >   Stack: corosync > >   Current DC: x3650f (version 1.1.17-1.el

Re: [ClusterLabs] How can I prevent multiple start of IPaddr 2 in an environment using fence_mpath?

2018-04-17 Thread
ent using fence_mpath? > > 06.04.2018 07:30, 飯田 雄介 пишет: > > Hi, all > > I am testing the environment using fence_mpath with the following settings. > > > > === > > Stack: corosync > > Current DC: x3650f (version 1.1.17-1.el7-b36b869) - partition with

[ClusterLabs] How can I prevent multiple start of IPaddr 2 in an environment using fence_mpath?

2018-04-05 Thread
Hi, all I am testing the environment using fence_mpath with the following settings. === Stack: corosync Current DC: x3650f (version 1.1.17-1.el7-b36b869) - partition with quorum Last updated: Fri Apr 6 13:16:20 2018 Last change: Thu Mar 1 18:38:02 2018 by root via cibadmin on x3650e

Re: [ClusterLabs] IPaddr2, interval between unsolicited ARP packets

2016-10-05 Thread
Hi, Hamaguchi-san send_arp exists in two versions depending on the environment. https://github.com/ClusterLabs/resource-agents/blob/master/tools/send_arp.libnet.c https://github.com/ClusterLabs/resource-agents/blob/master/tools/send_arp.linux.c Those that contain in your environment, it seems

Re: [ClusterLabs] "After = syslog.service" it is not working?

2016-01-28 Thread
29, 2016 12:16 AM > To: users@clusterlabs.org > Subject: Re: [ClusterLabs] "After = syslog.service" it is not working? > > On 01/28/2016 12:48 AM, 飯田 雄介 wrote: > > Hi, All > > > > I am building a cluster in the following environments. > > RHEL7.2 > > Pacemake

[ClusterLabs] "After = syslog.service" it is not working?

2016-01-27 Thread
Hi, All I am building a cluster in the following environments. RHEL7.2 Pacemaker-1.1.14 The OS while it is running the Pacemaker was allowed to shutdown. Logs at this time Pacemaker in the stop was not output to the syslog. This "After = syslog.service" does not work is set to start-up script,