Re: [ClusterLabs] Cannot ping a secondary address apart from the server which it is assigned to (on Azure)

2021-10-31 Thread Andrei Borzenkov
On 01.11.2021 01:56, Paul Warwicker wrote: > On 28/10/2021 14:30, Andrei Borzenkov wrote: >> For virtual IP you can (should?) use Azure >> load balancers - basically,  you create a pool of one address, Azure >> probes each node and detects which node has IP active. >> >> See as example this RH

Re: [ClusterLabs] Cannot ping a secondary address apart from the server which it is assigned to (on Azure)

2021-10-31 Thread Paul Warwicker
On 28/10/2021 14:30, Andrei Borzenkov wrote: For virtual IP you can (should?) use Azure load balancers - basically, you create a pool of one address, Azure probes each node and detects which node has IP active. See as example this RH documentation:

Re: [ClusterLabs] How to globally enable trace log level in pacemaker?

2021-10-31 Thread Andrei Borzenkov
On 31.10.2021 19:37, Strahil Nikolov wrote: > At least it's worth trying (/etc/sysconfig/pacemaker):PCMK_trace_files=* commit 85040eb19b9405464b01a7e67eb6769d2a03c611 Author: Ken Gaillot Date: Fri Jun 19 17:49:22 2020 -0500 Doc: sysconfig: remove outdated reference to wildcards in

Re: [ClusterLabs] How to globally enable trace log level in pacemaker?

2021-10-31 Thread Strahil Nikolov via Users
At least it's worth trying (/etc/sysconfig/pacemaker):PCMK_trace_files=* Best Regards,Strahil Nikolov On Sun, Oct 31, 2021 at 18:10, Vladislav Bogdanov wrote: ___ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users

Re: [ClusterLabs] How to globally enable trace log level in pacemaker?

2021-10-31 Thread Vladislav Bogdanov
Hi You may want to look at blackbox fuctionality, controlled by signals, if you won't find a way to get traces by env vars. It provides traces. Best regards On October 31, 2021 11:20:16 AM Andrei Borzenkov wrote: I think it worked in the past by passing a lot of -VVV when starting

Re: [ClusterLabs] How to globally enable trace log level in pacemaker?

2021-10-31 Thread Andrei Borzenkov
On 31.10.2021 16:48, Strahil Nikolov via Users wrote: > Have you checked the options in /etc/sysconfig/pacemaker as recommended in  > https://documentation.suse.com/sle-ha/15-SP3/html/SLE-HA-all/app-ha-troubleshooting.html#sec-ha-troubleshooting-log > ? > And where exactly it explains how to

Re: [ClusterLabs] How to globally enable trace log level in pacemaker?

2021-10-31 Thread Strahil Nikolov via Users
Have you checked the options in /etc/sysconfig/pacemaker as recommended in  https://documentation.suse.com/sle-ha/15-SP3/html/SLE-HA-all/app-ha-troubleshooting.html#sec-ha-troubleshooting-log ? Best Regards, Strahil Nikolov В неделя, 31 октомври 2021 г., 13:33:43 ч. Гринуич+2, Andrei

Re: [ClusterLabs] How to globally enable trace log level in pacemaker?

2021-10-31 Thread Andrei Borzenkov
On 31.10.2021 13:30, Jehan-Guillaume de Rorthais wrote: > Hi, > > Under EL and Debian, there's a PCMK_debug variable (iirc) in > "/etc/sysconfig/pacemaker" or "/etc/default/pacemaker". > > Comments in there explain how to set debug mode for part or all of the > pacemaker processes. > > This

Re: [ClusterLabs] How to globally enable trace log level in pacemaker?

2021-10-31 Thread Jehan-Guillaume de Rorthais
Hi, Under EL and Debian, there's a PCMK_debug variable (iirc) in "/etc/sysconfig/pacemaker" or "/etc/default/pacemaker". Comments in there explain how to set debug mode for part or all of the pacemaker processes. This might be the environment variable you are looking for ? Regards, Le 31

[ClusterLabs] How to globally enable trace log level in pacemaker?

2021-10-31 Thread Andrei Borzenkov
I think it worked in the past by passing a lot of -VVV when starting pacemaker. It does not seem to work now. I can call /usr/sbin/pacemakerd -..., but it does pass options further to children it starts. So every other daemon is started without any option and with default log