On 06/06/2013, at 3:45 PM, Vladislav Bogdanov bub...@hoster-ok.com wrote:
06.06.2013 08:14, Andrew Beekhof wrote:
On 06/06/2013, at 2:50 PM, Vladislav Bogdanov bub...@hoster-ok.com wrote:
06.06.2013 07:31, Andrew Beekhof wrote:
On 06/06/2013, at 2:27 PM, Vladislav Bogdanov
Dejan Muhamedagic deja...@fastmail.fm schrieb am 05.06.2013 um 18:37 in
Nachricht 20130605163710.GA4656@squib:
[...]
Sorry for the delay. There were quite a few issues. Can you
please test the attached patches?
[...]
I had a look at the patches, and I wonder:
1) are G_GNUC_PRINTF(2,3) and
Hi Ulrich,
On Thu, Jun 06, 2013 at 08:35:50AM +0200, Ulrich Windl wrote:
Dejan Muhamedagic deja...@fastmail.fm schrieb am 05.06.2013 um 18:37 in
Nachricht 20130605163710.GA4656@squib:
[...]
Sorry for the delay. There were quite a few issues. Can you
please test the attached patches?
06.06.2013 09:02, Andrew Beekhof wrote:
On 06/06/2013, at 3:45 PM, Vladislav Bogdanov bub...@hoster-ok.com wrote:
06.06.2013 08:14, Andrew Beekhof wrote:
On 06/06/2013, at 2:50 PM, Vladislav Bogdanov bub...@hoster-ok.com wrote:
06.06.2013 07:31, Andrew Beekhof wrote:
On 06/06/2013, at
Hello,
I have a two node cluster with cman (v3.1.7) and pacemaker (v1.1.6)
running in ubuntu 12.04 (as recommended in pacemaker documentation).
This cluster has been running without problems for more than a month
(since I isntalled it), but I'm having problems since I rebooted one
node
Hello,
on Debian Wheezy (7.0) I installed pacemaker with heartbeat. When
putting multiple filesystems which depend on multiple drbd promotions,
only the first drbd is promoted and the group never comes up. However
when the promotions are not based on the individual filesystems but on
the group or
group astorage drbd5_fs drbd8_fs nfs-common nfs-kernel-server astorage_ip
order drbd5_fs_after_drbd5 inf: ma-ms-drbd5:promote drbd5_fs:start
order drbd8_fs_after_drbd8 inf: ma-ms-drbd8:promote drbd8_fs:start
should be
group astorage drbd5_fs drbd8_fs nfs-common nfs-kernel-server astorage_ip
Hello,
over the last couple of days, I setup an active passive nfs server and
iSCSI storage using drbd, pacemaker, heartbeat, lio and nfs kernel
server. While testing cluster I was often setting it to unmanaged using:
crm configure property maintenance-mode=true
Sometimes when I did that, both
sorry
it should be
group astorage drbd5_fs drbd8_fs nfs-common nfs-kernel-server astorage_ip
order drbd_fs_after_drbd inf: ma-ms-drbd5:promote ma-ms-drbd8:promote
astorage:start
2013/6/6 emmanuel segura emi2f...@gmail.com
group astorage drbd5_fs drbd8_fs nfs-common nfs-kernel-server
Hello Emmanuel,
* emmanuel segura emi2f...@gmail.com [2013-06-06 11:12]:
order drbd_fs_after_drbd inf: ma-ms-drbd5:promote ma-ms-drbd8:promote
astorage:start
I can see that you promoted multiple drbds in one line. My config where
I promote them individually also works. However my question,
Hello Thomas
Sorry i can't give you any explain, because i don't see any sense in your
config
Sorry
2013/6/6 Thomas Glanzmann tho...@glanzmann.de
Hello,
on Debian Wheezy (7.0) I installed pacemaker with heartbeat. When
putting multiple filesystems which depend on multiple drbd promotions,
Hi all,
just a sidenote: The same trick is done to
solve concurrency problems on a database without locking a
row. E.g. concurrent db updates based on a web form.
Regards
Andreas
-Ursprüngliche Nachricht-
Von: linux-ha-boun...@lists.linux-ha.org
06.06.2013 08:43, Vladislav Bogdanov wrote:
[...]
I recall that LDAP has similar problem, which is easily worked around
with specifying two values, one is original, second is new.
That way you tell LDAP server:
Replace value Y in attribute X to value Z. And if value is not Y at the
moment of
Hi,
On Thu, Jun 06, 2013 at 03:11:16PM +0300, Vladislav Bogdanov wrote:
06.06.2013 08:43, Vladislav Bogdanov wrote:
[...]
I recall that LDAP has similar problem, which is easily worked around
with specifying two values, one is original, second is new.
That way you tell LDAP server:
Hi
I try to build heartbeat system on SUSE linux, and the version is 2.1.3 ;when
reboot my machine, I find these error print in log:
2012-10-05 03:25:59 SPP-2306_1 ipfail: [11267]: ERROR: Cannot chdir to
[/var/lib/heartbeat/cores/hacluster]: Permission denied
So can you please help me :
1.
Hello Shuwen,
What functionality of dir /var/lib/heartbeat/cores/hacluster?
if a component of heartbeat crashed, the core files are kept in this
directory to do post portem analysis of the problem.
How to fix this error print? What is your advice?
Fix the permissions. For me the permissions
Hi Shuwen Xu,
we had this problem too.
To your questions:
1) I assume that the processe(s) want to change into
a well defined directory so that core dumps are written
into that directory in case. But this is only an assumption.
2) Solution: The distribution comes with the following rights
Hi guys,
I don't really understand how status work for custom scripts.
My goal is to check many different status (for now I was just testing a
simple one), so I can make other node to take command when one-node fails.
I never see on the ha-debug logs, any status check (maybe I have to
On 05/06/2013, at 11:22 PM, Ulrich Windl ulrich.wi...@rz.uni-regensburg.de
wrote:
Hi again!
I haven't fully understood the problem, but it looks as if pacemaker likes to
shoot himself in the foot, and then go crazy when it feels the pain:
Shortly after maintenance mode was turned on,
On 06/06/2013, at 7:11 PM, Thomas Glanzmann tho...@glanzmann.de wrote:
Jun 6 10:17:37 astorage1 crmd: [2947]: ERROR: crm_abort:
abort_transition_graph: Triggered assert at te_utils.c:339 : transition_graph
!= NULL
This is the cause of the coredump.
What version of pacemaker is this?
On 07/06/2013, at 10:11 AM, Andrew Beekhof and...@beekhof.net wrote:
[Crazy things go on, until it changes to:]
crmd: [7285]: ERROR: verify_stopped: Resource prm_ping_gw1-v582:1 was active
at shutdown. You may ignore this error if it is unmanaged.
Hey folks!: Why emitting Errors and
21 matches
Mail list logo
