Re: [ClusterLabs] pacemaker-fenced /dev/shm errors

2023-03-27 Thread d tbsky
Ken Gaillot > I'm glad it's resolved, but for future reference, that does indicate a > serious problem. It means the fencer is not accepting any requests, so > any fencing attempts or even attempts to monitor a fencing device from > that node will fail. > That sounds like pacemaker-fenced

Re: [ClusterLabs] pacemaker-fenced /dev/shm errors

2023-03-27 Thread d tbsky
Christine caulfield > It sounds like you're running an old version of libqb, upgrading to > libqb 2.0.6 (in RHEL 9.1) should fix those messages Thanks a lot for the quick response! I will arrange the upgrade. Regards, tbskyd ___ Manage your

[ClusterLabs] pacemaker-fenced /dev/shm errors

2023-03-27 Thread d tbsky
Hi: the cluster is running under RHEL 9.0 elements. today I saw log report strange errors like below: Mar 27 13:07:06.287 example.com pacemaker-fenced[2405] (qb_sys_mmap_file_open) error: couldn't allocate file /dev/shm/qb-2405-2403-12-A9UUaJ/qb-request-stonith-ng-data: Interrupted

[ClusterLabs] cibadmin response unexpected

2023-01-17 Thread d tbsky
Hi: I am using RHEL 9.1 with pacemaker-cli-2.1.4-5. I tried command below: > cibadmin -Q -o xxx I expect the result tell me that "xxx" scope is not exist, but the command return the whole configuration. is this the normal behavior? thanks a lot for help. Regards, tbskyd

Re: [ClusterLabs] best practice for scripting

2021-04-13 Thread d tbsky
Ken Gaillot > FYI, the old and new status XML are nearly identical. The old XML's > outermost element is > > >... > > > while the new XML has > > >... > > > > As long as you're not looking at those particular elements, parsing the > XML output is the same. > > The format is

Re: [ClusterLabs] best practice for scripting

2021-04-13 Thread d tbsky
Tomas Jelinek > As we are aware of the difficulties of using pcs in scripts, we indeed > have a long term goal to provide machine readable output from pcs. Since > pcs started with a focus on producing human readable output, it's a lot > of work to do. Quite a big part of pcs code base cannot be

Re: [ClusterLabs] Antw: [EXT] best practice for scripting

2021-04-13 Thread d tbsky
Strahil Nikolov > > By the way , how do you monitor your pacemaker clusters ? > We are using Nagios and I found only 'check_crm' but it looks like it was > made for crmsh and most probably won't work with pcs without modifications. > > Best Regards, > Strahil Nikolov we use zabbix so we wrote

Re: [ClusterLabs] Antw: [EXT] best practice for scripting

2021-04-13 Thread d tbsky
Ulrich Windl > "Coming from SUSE" I'm using crm shell for most tasks, and I think the syntax > is quite good. good for SUSE! unfortunately RHEL didn't include the utility... ___ Manage your subscription:

[ClusterLabs] best practice for scripting

2021-04-13 Thread d tbsky
Hi: I have some scripts which use 'pcs' and 'crm_mon'. I prefer pcs since it is an all-in-one tool. but besides 'pcs cluster cib' it has no stable text output. reading document of pacemaker 2.1 I found it says: "In addition to crm_mon and stonith_admin, the crmadmin, crm_resource,

Re: [ClusterLabs] how to setup single node cluster

2021-04-08 Thread d tbsky
Reid Wahl > Disaster recovery is the main use case we had in mind. See the RHEL 8.2 > release notes: > - > https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/8.2_release_notes/rhel-8-2-0-release#enhancement_high-availability-and-clusters > > I thought I also

Re: [ClusterLabs] how to setup single node cluster

2021-04-08 Thread d tbsky
Reid Wahl > I don't think we do require fencing for single-node clusters. (Anyone at Red > Hat, feel free to comment.) I vaguely recall an internal mailing list or IRC > conversation where we discussed this months ago, but I can't find it now. > I've also checked our support policies

Re: [ClusterLabs] Antw: [EXT] how to setup single node cluster

2021-04-08 Thread d tbsky
Ulrich Windl > > >>> d tbsky schrieb am 08.04.2021 um 05:52 in Nachricht > : > > Hi: > > I found RHEL 8.2 support single node cluster now. but I didn't > > find further document to explain the concept. RHEL 8.2 also support > > "disaster re

[ClusterLabs] how to setup single node cluster

2021-04-07 Thread d tbsky
Hi: I found RHEL 8.2 support single node cluster now. but I didn't find further document to explain the concept. RHEL 8.2 also support "disaster recovery cluster". so I think maybe a single node disaster recovery cluster is not bad. I think corosync is still necessary under single node

Re: [ClusterLabs] staggered resource start/stop

2021-04-06 Thread d tbsky
Klaus Wenninger > Guess that heavily depends on what you are running inside your VMs. > If the services inside don't need each other or anything provided by > the other cluster-resources (or other way round) or everything is > synchronizing independently from the cluster ... > What you could

Re: [ClusterLabs] staggered resource start/stop

2021-03-31 Thread d tbsky
Klaus Wenninger > In this case it might be useful not to wait some defined time > hoping startup of the VM would have gone far enough that > the IO load has already decayed enough. > What about a resource that checks for something running > inside the VM that indicates that startup has completed?

Re: [ClusterLabs] staggered resource start/stop

2021-03-29 Thread d tbsky
Reid Wahl > > An order constraint set with kind=Serialize (which is mentioned in the first > reply to the thread you linked) seems like the most logical option to me. You > could serialize a set of resource sets, where each inner set contains a > VirtualDomain resource and an

[ClusterLabs] staggered resource start/stop

2021-03-28 Thread d tbsky
Hi: since the vm start/stop at once will consume disk IO, I want to start/stop the vm one-by-one with delay. search the email-list I found the discussion https://oss.clusterlabs.org/pipermail/pacemaker/2013-August/043128.html now I am testing rhel8 with pacemaker 2.0.4. I wonder if