Re: [ClusterLabs] Order set troubles

On 24.03.2021 20:56, Ken Gaillot wrote: > On Wed, 2021-03-24 at 09:27 +, Strahil Nikolov wrote: >> Hello All, >> >> I have a trouble creating an order set . >> The end goal is to create a 2 node cluster where nodeA will mount >> nfsA , while nodeB will mount nfsB.On top of that a depended

Re: [ClusterLabs] Order set troubles

On Wed, 2021-03-24 at 09:27 +, Strahil Nikolov wrote: > Hello All, > > I have a trouble creating an order set . > The end goal is to create a 2 node cluster where nodeA will mount > nfsA , while nodeB will mount nfsB.On top of that a depended cloned > resource should start on the node only

Re: [ClusterLabs] WebSite_start_0 on node2 'error' (1): call=6, status='complete', exitreason='Failed to access httpd status page.'

On Wed, 2021-03-24 at 10:50 +, Jason Long wrote: > Thank you. > Form node1 and node2, I can ping the floating IP address > (192.168.56.9). > I stopped node1: > > # pcs cluster stop node1 > node1: Stopping Cluster (pacemaker)... > node1: Stopping Cluster (corosync)... > > And from both

Re: [ClusterLabs] WebSite_start_0 on node2 'error' (1): call=6, status='complete', exitreason='Failed to access httpd status page.'

Thank you. Form node1 and node2, I can ping the floating IP address (192.168.56.9). I stopped node1: # pcs cluster stop node1 node1: Stopping Cluster (pacemaker)... node1: Stopping Cluster (corosync)... And from both machines, I can ping the floating IP address: [root@node1 ~]# ping

[ClusterLabs] Order set troubles

Hello All,   I have a trouble creating an order set . The end goal is to create a 2 node cluster where nodeA will mount nfsA , while nodeB will mount nfsB.On top of that a depended cloned resource should start on the node only if nfsA or nfsB has started locally.   A prototype code would

[ClusterLabs] resource-agents v4.8.0

ClusterLabs is happy to announce resource-agents v4.8.0. Source code is available at: https://github.com/ClusterLabs/resource-agents/releases/tag/v4.8.0 The most significant enhancements in this release are: - bugfixes and enhancements: - awsvip: dont partially match similar IPs during

Re: [ClusterLabs] Q: Is there any plan for pcs to support corosync-notifyd?

On Thu, Mar 18, 2021 at 6:31 PM Jehan-Guillaume de Rorthais wrote: > > On Thu, 18 Mar 2021 17:29:59 +0900 > 井上和徳 wrote: > > > On Tue, Mar 16, 2021 at 10:23 PM Jehan-Guillaume de Rorthais > > wrote: > > > > > > > On Tue, 16 Mar 2021, 09:58 井上和徳, wrote: > > > > > > > > > Hi! > > > > > > > > > >

[ClusterLabs] Antw: Re: Antw: [EXT] Re: WebSite_start_0 on node2 'error' (1): call=6, status='complete', exitreason='Failed to access httpd status page.'

Hi! I'm beginning to get the impression that you are quite ignorant to the advice people give to you: Either you have to use pacemaker the way it is intended to be used, or you have to look for another product. So if you want any HA network service managed by pacemaker, the service has to use an