Hello,
I have a similar problem when I try to set up a Postgresql 11 cluster with PAF
on Debian 10. Would you tell me what's wrong with my command line?
# pcs resource create pgsqld ocf:heartbeat:pgsqlms \
pgdata="/etc/postgresql/11/main" \
bindir="/usr/lib/postgresql/11/bin" \
datadir="/var/lib
On Wed, 2022-06-22 at 17:16 +0530, Priyanka Balotra wrote:
> Hi All,
>
> We are seeing an issue where we performed cluster shutdown followed
> by cluster boot operation. All the nodes joined the cluster excet one
> (the first node). Here are some pacemaker logs around that
> timestamp:
>
> 2022
Hi Klaus,
The config is as follows:
There are 2 nodes in the setup and some resources configured (stonith, IP,
systemd services related).
Sorry, I can share only high level details for this.
- pacemaker version
# rpm -qa pacemaker
pacemaker-2.0.3+20200511.2b248d828-1.10.x86_64
# rpm -qa coro
On Wed, Jun 22, 2022 at 1:46 PM Priyanka Balotra
wrote:
>
> Hi All,
>
> We are seeing an issue where we performed cluster shutdown followed by
> cluster boot operation. All the nodes joined the cluster excet one (the first
> node). Here are some pacemaker logs around that timestamp:
>
> 2022-06-
Hi All,
We are seeing an issue where we performed cluster shutdown followed by
cluster boot operation. All the nodes joined the cluster excet one (the
first node). Here are some pacemaker logs around that timestamp:
2022-06-19T07:02:08.690213+00:00 FILE-1 pacemaker-fenced[11637]: notice:
Operati
On 22/06/2022 07:12, Andrei Borzenkov wrote:
On 22.06.2022 02:27, Antony Stone wrote:
On Friday 17 June 2022 at 11:39:14, Mario Freytag wrote:
I’d like to ask about the security of corosync. We’re using a Proxmox HA
setup in our testing environment and need to confirm it’s compliance with
PCI