*** This bug is a duplicate of bug 1580045 ***
https://bugs.launchpad.net/bugs/1580045
This bug uncovers more issues than just the IP binding issue (which is
easy to work-around). There's also the issue of /var/lib/pcsd/tokens not
being written into and the way that pcs cluster setup hangs.
*** This bug is a duplicate of bug 1580045 ***
https://bugs.launchpad.net/bugs/1580045
I've just looked at the other bugs that Rafael is working on and they
cover the other issues in this bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
@Mariusz - it sounds like /var/lib/pcsd/tokens still isn't getting
written out by running "pcs cluster auth". Can you confirm that?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584365
Title:
pcs
Unfortunately, I couldn't get a pacemaker cluster to work on Ubuntu (I
instead used ocfs to provide a clustered filesystem) so I'm no longer in
a position to test this.
However, when I was tangling with it, I managed to get pcsd to bind to
IPv4 but there's still the problem with it not writing
Dagnammit - "pcs cluster auth" doesn't write out /var/lib/pcsd/tokens so
anything I try to do with it afterwards just fails.
So, although "pcs cluster auth" returns "authorized", it doesn't
actually do its job.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I got this working after working around two other bugs.
"systemctl pcsd start" fails with ruby errors
(/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
`required`) that can be fixed by running:
gem install orderedhash
After that, there's the problem with Ruby binding to the IPv6
Okay, looks like this isn't necessarily just an Ubuntu bug. I've since
had the same problems with running "pcs cluster auth" on RHEL7. It looks
like my test (see above) was using 127.0.0.1 as the ip address which
does work on both Ubuntu and RHEL7.
After lots of investigation, it looks like
** Package changed: ubuntu => pcs (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1584365
Title:
pcs cluster auth unable to connect
To manage notifications about this bug go to:
Public bug reported:
After installing PCS on (x)Ubuntu 16.04, I'm unable to successfully run "pcs
auth cluster".
I was following the documentation from
http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Clusters_from_Scratch/_enable_pcs_daemon.html
To reproduce:
install Ubuntu 16.04
set
This is still present on Utopic (14.10) and restarting apparmor doesn't
help at all.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/458061
Title:
openntpd no longer installs
I've managed to get it installed by running apt-get purge openntpd
apparmor, performing a reboot and then installing openntp.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/458061
Title:
openntpd no
I just tried the kernel upgrade trick and it seems to have worked!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/772923
Title:
BCM4312 on HP Mini 2133 freezes with Natty
--
ubuntu-bugs mailing
I hit the same problem after an upgrade to Natty and also from a fresh
install of Natty. I suspect it may have something to do with the display
driver as the wireless driver and display seem to be linked on the
hp2133.
--
You received this bug notification because you are a member of Ubuntu
FAYC: you don't need to open synaptic.
Open up a terminal/shell and run the following command (I'll try to
spell it right this time):
sudo dpkg -i --force-overwrite /var/cache/apt/archives/linux-
firmware_1.34.1_all.deb
You may need to check which version of linux-firmware_1.34.1_all.deb
it is
There's a relatively easy workaround - you can run dpkg to install the
package and force it to overwrite the conflict. If I remember, it's
something like this (from a terminal):
sudo dkpg -i --force-overwrite /var/cache/apt/archives/linux-
firmware_1.34.1_all.deb
You might need to change it for
Public bug reported:
Binary package hint: fwknop-server
Reports error when installing
ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage: subprocess post-installation script returned error exit status 1
Package: fwknop-server 1.9.10-1
SourcePackage: fwknop
Title:
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/28467086/Dependencies.txt
** Attachment added: DpkgTerminalLog.gz
http://launchpadlibrarian.net/28467087/DpkgTerminalLog.gz
--
package fwknop-server 1.9.10-1 failed to install/upgrade: subprocess
post-installation
17 matches
Mail list logo
