Well, did not think I should spam the list right away with
the whole lot.
Should I show anything specific? Like I said, usual places, eg.:
-> $ pcs status --full
show nothing unusual, all the resources enabled are a ok,
usual warnings:
-> $ pcs status --full | __grepColorIt
'(error|fail|clone|pgsql)'
Cluster name: MINE
WARNINGS:
Following resources have been moved and their move
constraints are still in place: 'box1.proxmox',
'box2.proxmox', 'box3.proxmox', 'box4.proxmox',
'box5.proxmox', 'box6.proxmox', 'esx1.vmware',
'esx2.vmware', 'esx3.vmware', 'ocp0node', 'ocp1node',
'ocp2node', 'podnode1', 'podnode2', 'podnode3', 'podster1',
'podster2', 'podster3', 'ubusrv1', 'ubusrv2', 'ubusrv3'
Run 'pcs constraint location' or 'pcs resource clear
<resource id>' to view or remove the constraints, respectively
Cluster Summary:
* Stack: corosync (Pacemaker is running)
* Current DC: whale (2) (version 3.0.1-5.el10-2cbee04) -
partition with quorum
* Last updated: Thu Mar 12 15:04:39 2026 on dzien
* Last change: Tue Mar 10 21:47:22 2026 by root via root
on dzien
* 3 nodes configured
* 85 resource instances configured (39 DISABLED)
...
...
...
Migration Summary:
Tickets:
PCSD Status:
dzien: Online
swir: Online
whale: Online
Daemon Status:
corosync: active/enabled
pacemaker: active/enabled
pcsd: active/enabled
Perhaps from from _pacemaker.log_ which I think might be
"unusual" ?
...
15:07:17.065 swir.mine.priv pacemaker-based [3362]
(pcmk__ipc_send_iov) notice: Response 2 (part 1) to pid
1593095 failed: Resource temporarily unavailable |
bytes=131072 rc=-11 ipcs=0x5642e633beb0
15:07:17.066 swir.mine.priv pacemaker-based [3362]
(pcmk__ipc_send_iov) notice: Response 2 (final part 2)
to pid 1593095 failed: Resource temporarily unavailable |
bytes=9370 rc=-11 ipcs=0x5642e633beb0
15:07:17.066 swir.mine.priv pacemaker-based [3362]
(pcmk__ipc_send_iov) notice: Response 2 (final part 2)
to pid 1593095 failed: Resource temporarily unavailable |
bytes=9370 rc=-11 ipcs=0x5642e633beb0
15:07:17.066 swir.mine.priv pacemaker-based [3362]
(pcmk__ipc_send_iov) notice: Response 2 (final part 2)
to pid 1593095 failed: Resource temporarily unavailable |
bytes=9370 rc=-11 ipcs=0x5642e633beb0
15:07:17.137 swir.mine.priv pacemaker-based [3362]
(pcmk__ipc_send_iov) notice: Response 2 (part 1) to pid
1593101 failed: Resource temporarily unavailable |
bytes=131072 rc=-11 ipcs=0x5642e633beb0
15:07:17.138 swir.mine.priv pacemaker-based [3362]
(pcmk__ipc_send_iov) notice: Response 2 (final part 2)
to pid 1593101 failed: Resource temporarily unavailable |
bytes=9370 rc=-11 ipcs=0x5642e633beb0
15:07:17.209 swir.mine.priv pacemaker-based [3362]
(pcmk__ipc_send_iov) notice: Response 2 (part 1) to pid
1593107 failed: Resource temporarily unavailable |
bytes=131072 rc=-11 ipcs=0x5642e633beb0
15:07:17.209 swir.mine.priv pacemaker-based [3362]
(pcmk__ipc_send_iov) notice: Response 2 (final part 2)
to pid 1593107 failed: Resource temporarily unavailable |
bytes=9370 rc=-11 ipcs=0x5642e633beb0
15:07:17.209 swir.mine.priv pacemaker-based [3362]
(pcmk__ipc_send_iov) notice: Response 2 (final part 2)
to pid 1593107 failed: Resource temporarily unavailable |
bytes=9370 rc=-11 ipcs=0x5642e633beb0
15:07:17.209 swir.mine.priv pacemaker-based [3362]
(pcmk__ipc_send_iov) notice: Response 2 (final part 2)
to pid 1593107 failed: Resource temporarily unavailable |
bytes=9370 rc=-11 ipcs=0x5642e633beb0
...
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users
ClusterLabs home: https://www.clusterlabs.org/
