>From Corosync 2.4.1 Release Notes:
This release contains fix for one regression and few more smaller fixes.
"""
During 2.3.6 development the bug which is causing pacemaker to not work after
corosync configuration file is reloaded happened. Solution is ether to use this
fixed version (recommend
** Also affects: pacemaker (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: pacemaker (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: pacemaker (Ubuntu)
Status: Confirmed => Fix Released
** Also affects: pacemaker (Ubuntu Bionic)
I
** No longer affects: lxc (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1439649
Title:
Pacemaker unable to communicate with corosync on restart under lxc
To manage notificati
Serge,
I did double check that the pacemaker processes were running under
hacluster/haclient uid/gid. I will double check for my own sanity (I may
have seen one running as root). However, according to the pacemaker docs
that I referenced above, root and hacluster users should always have
full acce
Hi Billy,
So can you confirm that pacemaker *is* running under haclient/hacluster
uid/gid?
Note, the comments above don't seem correct to me. The 'INSTALL' file
shipped with corosync says:
> Before running any of the test programs
> ---
> The corosync executi
** Attachment added: "syslog"
https://bugs.launchpad.net/ubuntu/+source/pacemaker/+bug/1439649/+attachment/4457039/+files/syslog
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1439649
Looking at logs from bug 1491228, it would appear that the first time
that pacemaker goes to talk to the corosync daemon it gets denied. Per
upstream docs [0], if the enable-acl property isn't explicitly enabled,
then any user in the haclient group should have access. Since the
hacluster charm does
** Tags added: landscpae
** Tags removed: landscpae
** Tags added: landscape
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1439649
Title:
Pacemaker unable to communicate with corosync
FYI to re-check workaround (then possible actual fix), kicked corosync+pacemaker
on cinder, glance services deployed with juju:
$ juju run --service=cinder,glance "service corosync restart; service
pacemaker restart"
, which broke pacemaker start on all of them, with same "Invalid IPC
credentia
After trying several corosync/pacemaker restarts without luck,
I was able to workaround this by adding an 'uidgid'
entry for hacluster:haclient:
* from /var/log/syslog:
Aug 31 18:33:18 juju-machine-3-lxc-3 corosync[901082]: [MAIN ] Denied
connection attempt from 108:113
$ getent passwd 108
hacl
I can reproduce with corosync 2.3.3. Using corosync 2.3.4 from
ppa:mariosplivalo/corosync on trusty I've not been able to reproduce on
2 tries.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/b
A restart of pacemaker and corosync (down pacemaker on all units, down
corosync on all units, start corosync, verify all is good, start
pacemaker) should resolve the issue.
@Jill: are you able to reproduce the issue? I'm assuming you're running
trusty - can you try reproducing using corosync and r
We've run into this problem after an extended maas/dhcp outage with
expiring leases on metals and units. All hacluster-deployed lxc's
(openstack-ha services) lost corosync-pacemaker connectivity with
"corosync Invalid IPC credentials", resolving with lxc reboots. This is
a staging cloud so we cou
@jamespage,
i assume the answer to comment #5 was no, test package didn't fix it?
Was this in the end due to the mtu issue?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1439649
Title:
** Tags added: sts
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1439649
Title:
Pacemaker unable to communicate with corosync on restart under lxc
To manage notifications about this b
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lxc (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1439649
T
I'm seeing this problem in another environment, similar deployment (3
lxc containers)
Apr 20 16:39:26 juju-machine-3-lxc-4 crm_verify[31774]: notice: crm_log_args:
Invoked: crm_verify -V -p
Apr 20 16:39:27 juju-machine-3-lxc-4 cibadmin[31786]: notice: crm_log_args:
Invoked: cibadmin -p -P
Hi, guys.
I am also actively testing to reproduce similar issue (that our customer
complained about) - I'm deploying three unit percona-cluster (each unit
in a separate LXC on separate physical machine) with three unit keystone
(both services have hacluster subodinated), but failed to reproduce it
I've being trying to reproduce this under KVM and on hardware (no LXC)
but I'm unable to reproduce the problem, so this appears isolated to
LXC.
The pacemaker <-> corosync communication occurs over IPC implemented
using shared memory. I'm wondering whether this is managing to get into
an inconsis
19 matches
Mail list logo
