Hi
I've came across an odd behavior, which might be considered as
inconsistent. As we know, pacemaker doesn't allow deleting a resource
that's running, but this doesn't produce same behavior every time.
Let's take a VM with a default stop timeout (90 seconds).
First behavior
--
#
On 23.02.2012 23:52, Andrew Beekhof wrote:
On Thu, Feb 23, 2012 at 6:43 PM, Ante Karamatic iv...@ubuntu.com wrote:
Well... Upstart actually does notice if the job failed and respawns it -
depending on job's configuration.
Actually this is /really/ bad as it subverts our recovery policies
On 21.02.2012 17:56, Jake Smith wrote:
Np thanks for adding - I was asking because the exit codes on the
upstart jobs I'm using didn't align (I believe) with the LSB spec and
I wasn't sure if they were supposed to. Haven't really seen the
level of documentation (as LSB resource) for upstart
On 21.02.2012 16:30, Florian Haas wrote:
[1] Why do I need to use a PPA if this release is ostensibly on
long-term support? Don't ask me, ask someone from Canonical. :)
Pacemaker isn't really supported cluster stack in Ubuntu 10.04 (it's in
universe). RHCS is in main and supported. There are
On 22.02.2012 19:45, Vladislav Bogdanov wrote:
I looked at that RAexec very early, just after it was commited, and I
understand that it requires running dbus daemon to operate. I prefer to
simplify operation chains, so that is really not an option for me to
rely on one more service to do
On 23.02.2012 00:10, Andrew Beekhof wrote:
Do you still have LSB scripts on a machine thats using upstart?
Yes, some LSB scripts can't be easily converted to upstart jobs. Or,
let's rephrase that - can't be converted to upstart jobs without losing
some of the functionality.
On fedora they
On 02.12.2011 09:06, Vadim Bulst wrote:
yes , locking_type=3. But clvm needs a place for his socket
(/var/run/lvm) . This directory is not generated automatically.
Correct. It works in Lucid, it doesn't in Oneiric and probably some
other versions too.
Shell I make a bug report to Ubuntu ?
On 30.11.2011 14:16, coredump wrote:
So last night I was supposed to get a cluster running, everything
worked ok on a virtual environment using the same software and by my
experience I only had to install pacemaker and corosync (from the
ubuntu 10.04 ppa) and get it rolling. What really
On 30.11.2011 13:10, Vadim Bulst wrote:
I created now the directory /var/run/lvm . It wasn't there - work for
the package maintainer.
Hm... That directory is used for file based locking. clvmd shouldn't be
using that. Did you set up cluster locking in /etc/lvm/lvm.conf
(locking_type)?
On 23.11.2011 15:30, Vadim Bulst wrote:
clvm resource is not coming up and when I commit some changes on
resources in most cases one node is dying.
Judging by the logs, it looks like clvmd is running already. Make sure
clvmd is not started during the boot:
update-rc.d -f clvm remove
On 23.11.2011 18:47, Vadim Bulst wrote:
these are my active services:
No, that's not all. Ubuntu by default uses upstart (jobs are in
/etc/init) and, by default runlevel is 2 (so /etc/rc2.d), and you've
forgot /etc/rcS.d :)
Just run:
update-rc.d -f clvm remove
as suggested in previous email.
11 matches
Mail list logo
