Re: [ClusterLabs] Location not working [FIXED]

2023-04-12 Thread Klaus Wenninger 
On Wed, Apr 12, 2023 at 9:27 AM Andrei Borzenkov 
wrote:

> On Tue, Apr 11, 2023 at 6:27 PM Ken Gaillot  wrote:
> >
> > On Tue, 2023-04-11 at 17:31 +0300, Miro Igov wrote:
> > > I fixed the issue by changing location definition from:
> > >
> > > location intranet-ip_on_any_nginx intranet-ip \
> > > rule -inf: opa-nginx_1_active eq 0 \
> > > rule -inf: opa-nginx_2_active eq 0
> > >
> > > To:
> > >
> > > location intranet-ip_on_any_nginx intranet-ip \
> > > rule opa-nginx_1_active eq 1 \
> > >rule opa-nginx_2_active eq 1
> > >
> > > Now it works fine and shows the constraint with: crm res constraint
> > > intranet-ip
> >
> > Ah, I suspect the issue was that the original constraint compared only
> > against 0, when initially (before the resources ever start) the
> > attribute is undefined.
> >
>
> This does not really explain the original question. Apparently the
> attribute *was* defined but somehow ignored.
>
> Apr 10 12:11:02 intranet-test2 pacemaker-attrd[1511]:  notice: Setting
> opa-nginx_1_active[intranet-test1]: 1 -> 0
> ...
>   * intranet-ip (ocf::heartbeat:IPaddr2):Started intranet-test1
>

But that log is from a different node that sets the node-attribute for
another node and some time has gone by till the IP was detected
to be running unwantedly (a failure of the nfs-service recorded 14min
later - so at least that much). A lot can have happened in between like
rejoins - not saying what happened (like merging the CIBs) did
happen as it should have - but the log-line isn't necessarily a proof
that the attribute was still at 0. Searching the logs for changes
in the cluster-topology in the time in between may give some insights.

Klaus

> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/
>
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Location not working [FIXED]

2023-04-12 Thread Andrei Borzenkov 
On Tue, Apr 11, 2023 at 6:27 PM Ken Gaillot  wrote:
>
> On Tue, 2023-04-11 at 17:31 +0300, Miro Igov wrote:
> > I fixed the issue by changing location definition from:
> >
> > location intranet-ip_on_any_nginx intranet-ip \
> > rule -inf: opa-nginx_1_active eq 0 \
> > rule -inf: opa-nginx_2_active eq 0
> >
> > To:
> >
> > location intranet-ip_on_any_nginx intranet-ip \
> > rule opa-nginx_1_active eq 1 \
> >rule opa-nginx_2_active eq 1
> >
> > Now it works fine and shows the constraint with: crm res constraint
> > intranet-ip
>
> Ah, I suspect the issue was that the original constraint compared only
> against 0, when initially (before the resources ever start) the
> attribute is undefined.
>

This does not really explain the original question. Apparently the
attribute *was* defined but somehow ignored.

Apr 10 12:11:02 intranet-test2 pacemaker-attrd[1511]:  notice: Setting
opa-nginx_1_active[intranet-test1]: 1 -> 0
...
  * intranet-ip (ocf::heartbeat:IPaddr2):Started intranet-test1
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Location not working [FIXED]

2023-04-11 Thread Miro Igov 
This is a multipart message in MIME format.

Rq39EWBVFo_related
Content-Type: text/html;
charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Type: multipart/related;
boundary="--Rq39EWBVFo_related" charset="utf-8"

It does not matter if ip resource starts on n=
ode without nginx_active. It is equal situation as if the ip is stopped.The public ip forwards to the virtual ip and if there =
is no nginix on the node running it will be same as if virtual ip is not ru=
nning.From: Users  on behalf of Ken Gaillot Sent: Tuesday, April 11, 2023, 18:27To: C=
luster Labs - All topics related to open-source clustering welcomed Subject: Re: [ClusterLabs] Locat=
ion not working [FIXED]On Tue, 2023-04-11 at 17:31 +0300, Mir=
o Igov wrote:> I fixed the issue by changing location definition fro=
m:>  > location intranet-ip_on_any_nginx intranet-ip \>=
; rule -inf: opa-nginx_1_active eq 0 \> rule -inf: o=
pa-nginx_2_active eq 0>  > To:>  > location int=
ranet-ip_on_any_nginx intranet-ip \> rule opa-nginx_1_active=
 eq 1 \>rule opa-nginx_2_active eq 1>  > N=
ow it works fine and shows the constraint with: crm res constraint> =
intranet-ipAh, I suspect the issue was that the original constraint=
 compared onlyagainst 0, when initially (before the resources ever star=
t) theattribute is undefined.Note that your new constraint says=
 that the IP *prefers* to run wherethe attribute is 1, but if there are=
 no nodes with the attribute set to1, it can still start somewhere. On =
the other hand, bans are mandatory,so you may want to go back to that a=
nd just specify it as "ne 1".>  >  >  > Fro=
m: Users  On Behalf Of Miro Igov&g=
t; Sent: 10 April 2023 14:19> To: users@clusterlabs.org> Subj=
ect: [ClusterLabs] Location not working>  > Hello,> I =
have a resource with location constraint set to:>  > location=
 intranet-ip_on_any_nginx intranet-ip \> rule -inf: opa-ngin=
x_1_active eq 0 \> rule -inf: opa-nginx_2_active eq 0>=
;  > In syslog I see the attribute transition:> Apr 10 12:11:=
02 intranet-test2 pacemaker-attrd[1511]:  notice:> Setting opa-nginx=
_1_active[intranet-test1]: 1 -> 0>  > Current cluster stat=
us is :>  > Node List:>   * Online: [ intranet-test1 i=
ntranet-test2 nas-sync-test1 nas-sync-> test2 ]>  > * =
stonith-sbd (stonith:external/sbd):  Started intranet-test2>   * adm=
in-ip(ocf::heartbeat:IPaddr2):Started nas-sync-> test2>   * cron_symlink(ocf::heartbeat:symlink):Started=
> intranet-test1>   * intranet-ip (ocf::heartbeat:IPaddr2):  =
  Started intranet-> test1>   * mysql_1 (systemd:mariadb@=
intranet-test1):Started> intranet-test1>   * mysql_2 =
(systemd:mariadb@intranet-test2):Started> intranet-test2=
>   * nginx_1 (systemd:nginx@intranet-test1):  Stopped>  =
 * nginx_1_active  (ocf::pacemaker:attribute):  Stopped>   *=
 nginx_2 (systemd:nginx@intranet-test2):  Started intranet-> tes=
t2>   * nginx_2_active  (ocf::pacemaker:attribute):  Started=
> intranet-test2>   * php_1   (systemd:php5.6-fpm@intrane=
t-test1): Started> intranet-test1>   * php_2   (syste=
md:php5.6-fpm@intranet-test2): Started> intranet-test2>  =
 * data_1  (ocf::heartbeat:Filesystem): Stopped>   * data_2 =
 (ocf::heartbeat:Filesystem): Started intranet-> test2&g=
t;   * nfs_export_1(ocf::heartbeat:exportfs):   Stopped>=
   * nfs_export_2(ocf::heartbeat:exportfs):   Started nas-&=
gt; sync-test2>   * nfs_server_1(systemd:nfs-server@nas-sync=
-test1):> Stopped>   * nfs_server_2(systemd:nfs-s=
erver@nas-sync-test2):> Started nas-sync-test2>  >=
 Failed Resource Actions:>   * nfs_server_1_start_0 on nas-sync-test=
1 'error' (1): call=3D95,> status=3D'complete', exitreason=3D'', las=
t-rc-change=3D'2023-04-10 12:35:12> +02:00', queued=3D0ms, exec=3D20=
9ms>  >  > Why intranet-ip is located on intranet-test=
1 while nginx_1_active is> 0 ?>  > # crm res constrain=
t intranet-ip>> cron_symlink =
> (score=3DINFINITY, id=3Dc_cron=
_symlink_on_intranet-ip)> * intranet-ip>   : Node nas-sync-> test2 &g=
t; (score=3D-INFINITY, id=3Dintranet-ip_loc-rule)>   : Node nas-sync=
-> test1 > (score=3D-INFINITY, id=3Dintranet-ip_loc-rule)>  > Why =
no constraint entry for intranet-ip_on_any_nginx location ?>  &g=
t;  >  > >  This message has been sent as a part of di=
scussion between PHARMYA> and the addressee whose name is specified =
above. Should you receive> this message by mistake, we would be most=
 grateful if you informed us> that the message has been sent to you.=
 In this case, we also ask that> you delete this message

Re: [ClusterLabs] Location not working [FIXED]

2023-04-11 Thread Ken Gaillot 
On Tue, 2023-04-11 at 17:31 +0300, Miro Igov wrote:
> I fixed the issue by changing location definition from:
>  
> location intranet-ip_on_any_nginx intranet-ip \
> rule -inf: opa-nginx_1_active eq 0 \
> rule -inf: opa-nginx_2_active eq 0
>  
> To:
>  
> location intranet-ip_on_any_nginx intranet-ip \
> rule opa-nginx_1_active eq 1 \
>rule opa-nginx_2_active eq 1
>  
> Now it works fine and shows the constraint with: crm res constraint
> intranet-ip

Ah, I suspect the issue was that the original constraint compared only
against 0, when initially (before the resources ever start) the
attribute is undefined.

Note that your new constraint says that the IP *prefers* to run where
the attribute is 1, but if there are no nodes with the attribute set to
1, it can still start somewhere. On the other hand, bans are mandatory,
so you may want to go back to that and just specify it as "ne 1".

>  
>  
>  
> From: Users  On Behalf Of Miro Igov
> Sent: 10 April 2023 14:19
> To: users@clusterlabs.org
> Subject: [ClusterLabs] Location not working
>  
> Hello,
> I have a resource with location constraint set to:
>  
> location intranet-ip_on_any_nginx intranet-ip \
> rule -inf: opa-nginx_1_active eq 0 \
> rule -inf: opa-nginx_2_active eq 0
>  
> In syslog I see the attribute transition:
> Apr 10 12:11:02 intranet-test2 pacemaker-attrd[1511]:  notice:
> Setting opa-nginx_1_active[intranet-test1]: 1 -> 0
>  
> Current cluster status is :
>  
> Node List:
>   * Online: [ intranet-test1 intranet-test2 nas-sync-test1 nas-sync-
> test2 ]
>  
> * stonith-sbd (stonith:external/sbd):  Started intranet-test2
>   * admin-ip(ocf::heartbeat:IPaddr2):Started nas-sync-
> test2
>   * cron_symlink(ocf::heartbeat:symlink):Started
> intranet-test1
>   * intranet-ip (ocf::heartbeat:IPaddr2):Started intranet-
> test1
>   * mysql_1 (systemd:mariadb@intranet-test1):Started
> intranet-test1
>   * mysql_2 (systemd:mariadb@intranet-test2):Started
> intranet-test2
>   * nginx_1 (systemd:nginx@intranet-test1):  Stopped
>   * nginx_1_active  (ocf::pacemaker:attribute):  Stopped
>   * nginx_2 (systemd:nginx@intranet-test2):  Started intranet-
> test2
>   * nginx_2_active  (ocf::pacemaker:attribute):  Started
> intranet-test2
>   * php_1   (systemd:php5.6-fpm@intranet-test1): Started
> intranet-test1
>   * php_2   (systemd:php5.6-fpm@intranet-test2): Started
> intranet-test2
>   * data_1  (ocf::heartbeat:Filesystem): Stopped
>   * data_2  (ocf::heartbeat:Filesystem): Started intranet-
> test2
>   * nfs_export_1(ocf::heartbeat:exportfs):   Stopped
>   * nfs_export_2(ocf::heartbeat:exportfs):   Started nas-
> sync-test2
>   * nfs_server_1(systemd:nfs-server@nas-sync-test1):
> Stopped
>   * nfs_server_2(systemd:nfs-server@nas-sync-test2):
> Started nas-sync-test2
>  
> Failed Resource Actions:
>   * nfs_server_1_start_0 on nas-sync-test1 'error' (1): call=95,
> status='complete', exitreason='', last-rc-change='2023-04-10 12:35:12
> +02:00', queued=0ms, exec=209ms
>  
>  
> Why intranet-ip is located on intranet-test1 while nginx_1_active is
> 0 ?
>  
> # crm res constraint intranet-ip
>
> cron_symlink 
> (score=INFINITY, id=c_cron_symlink_on_intranet-ip)
> * intranet-ip
>   : Node nas-sync-
> test2 
> (score=-INFINITY, id=intranet-ip_loc-rule)
>   : Node nas-sync-
> test1 
> (score=-INFINITY, id=intranet-ip_loc-rule)
>  
> Why no constraint entry for intranet-ip_on_any_nginx location ?
>  
>  
>  
> 
>  This message has been sent as a part of discussion between PHARMYA
> and the addressee whose name is specified above. Should you receive
> this message by mistake, we would be most grateful if you informed us
> that the message has been sent to you. In this case, we also ask that
> you delete this message from your mailbox, and do not forward it or
> any part of it to anyone else.
> Thank you for your cooperation and understanding. 
> 
> ___
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
> 
> ClusterLabs home: https://www.clusterlabs.org/
-- 
Ken Gaillot 

___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Re: [ClusterLabs] Location not working [FIXED]

2023-04-11 Thread Miro Igov 
I fixed the issue by changing location definition from:

 

location intranet-ip_on_any_nginx intranet-ip \

rule -inf: opa-nginx_1_active eq 0 \

rule -inf: opa-nginx_2_active eq 0

 

To:

 

location intranet-ip_on_any_nginx intranet-ip \

rule opa-nginx_1_active eq 1 \

   rule opa-nginx_2_active eq 1

 

Now it works fine and shows the constraint with: crm res constraint
intranet-ip

 

 

 

From: Users  On Behalf Of Miro Igov
Sent: 10 April 2023 14:19
To: users@clusterlabs.org
Subject: [ClusterLabs] Location not working

 

Hello,

I have a resource with location constraint set to:

 

location intranet-ip_on_any_nginx intranet-ip \

rule -inf: opa-nginx_1_active eq 0 \

rule -inf: opa-nginx_2_active eq 0

 

In syslog I see the attribute transition:

Apr 10 12:11:02 intranet-test2 pacemaker-attrd[1511]:  notice: Setting
opa-nginx_1_active[intranet-test1]: 1 -> 0

 

Current cluster status is :

 

Node List:

  * Online: [ intranet-test1 intranet-test2 nas-sync-test1 nas-sync-test2 ]

 

* stonith-sbd (stonith:external/sbd):  Started intranet-test2

  * admin-ip(ocf::heartbeat:IPaddr2):Started nas-sync-test2

  * cron_symlink(ocf::heartbeat:symlink):Started
intranet-test1

  * intranet-ip (ocf::heartbeat:IPaddr2):Started intranet-test1

  * mysql_1 (systemd:mariadb@intranet-test1):Started
intranet-test1

  * mysql_2 (systemd:mariadb@intranet-test2):Started
intranet-test2

  * nginx_1 (systemd:nginx@intranet-test1):  Stopped

  * nginx_1_active  (ocf::pacemaker:attribute):  Stopped

  * nginx_2 (systemd:nginx@intranet-test2):  Started intranet-test2

  * nginx_2_active  (ocf::pacemaker:attribute):  Started
intranet-test2

  * php_1   (systemd:php5.6-fpm@intranet-test1): Started
intranet-test1

  * php_2   (systemd:php5.6-fpm@intranet-test2): Started
intranet-test2

  * data_1  (ocf::heartbeat:Filesystem): Stopped

  * data_2  (ocf::heartbeat:Filesystem): Started intranet-test2

  * nfs_export_1(ocf::heartbeat:exportfs):   Stopped

  * nfs_export_2(ocf::heartbeat:exportfs):   Started
nas-sync-test2

  * nfs_server_1(systemd:nfs-server@nas-sync-test1): Stopped

  * nfs_server_2(systemd:nfs-server@nas-sync-test2): Started
nas-sync-test2

 

Failed Resource Actions:

  * nfs_server_1_start_0 on nas-sync-test1 'error' (1): call=95,
status='complete', exitreason='', last-rc-change='2023-04-10 12:35:12
+02:00', queued=0ms, exec=209ms

 

 

Why intranet-ip is located on intranet-test1 while nginx_1_active is 0 ?

 

# crm res constraint intranet-ip

cron_symlink
(score=INFINITY, id=c_cron_symlink_on_intranet-ip)

* intranet-ip

  : Node nas-sync-test2
(score=-INFINITY, id=intranet-ip_loc-rule)

  : Node nas-sync-test1
(score=-INFINITY, id=intranet-ip_loc-rule)

 

Why no constraint entry for intranet-ip_on_any_nginx location ?

 

 






 


-- 
This message has been sent as a part of discussion between PHARMYA and the
addressee whose name is specified above. Should you receive this message by
mistake, we would be most grateful if you informed us that the message has
been sent to you. In this case, we also ask that you delete this message
from your mailbox, and do not forward it or any part of it to anyone else.
Thank you for your cooperation and understanding.
___
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/