similar to: Winbind ADS feature request

Hi, We are using the heartbeat and drbd packages from latest centos (4.3) extras repository. Upon installation of both packages I noticed that if you "chkconfig heartbeat off" that will cause drbd to chkconfig'ed on. And visa versa. After doing some trouble shooting it turns out the "BEGIN INIT INFO" sections appear to be the cause. drbd has: ### BEGIN INIT INFO #

I have an OCFS2 filesystem on a coraid AOE device. It mounts fine, but with heavy I/O the server self fences claiming a write timeout: (16,2):o2hb_write_timeout:164 ERROR: Heartbeat write timeout to device etherd/e0.1p1 after 12000 milliseconds (16,2):o2hb_stop_all_regions:1789 ERROR: stopping heartbeat on all active regions. Kernel panic - not syncing: ocfs2 is very sorry to be fencing this

This patch fixes state changes in dbomatic so that there is no intermediate 'stopped' state after being unreachable or on startup of dbomatic etc. Also fixes a number of smaller bugs around host associations, state changes, etc. Signed-off-by: Ian Main <imain at redhat.com> --- src/db-omatic/db_omatic.rb | 85 +++++++++++++++++++++++++++++++------------- 1 files changed, 60

This patch updates dbomatic, taskomatic and host-register to use the new C++ wrapped ruby QMF bindings. It also fixes a couple of bugs along the way including the 0 cpu bug for host-register. This is a compilation of work done by myself and Arjun Roy. Signed-off-by: Ian Main <imain at redhat.com> --- src/db-omatic/db_omatic.rb | 111 ++++++-------

The new version of heartbeat (http://linux-ha.org/GettingStartedV2) supports up to 16nodes. I was wondering if anyone has tried it with Asterisk. The biggest hurdle would be to configure multiple instances of Asterisk on the same box. Anyone configure more than one copy of asterisk on the same machine? Each instance would need their own set of configuration files. This would be a VOIP only

Dear Developers, I've released a patch against openssh-2.5.2p2. The patch adds heartbeat (keepalive) function to ssh(1), and watchdog timeout function to sshd(8). The watchdog timeout is intended to terminate user's processes as soon as possible after the link has been lost. http://www.ecip.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html The combination of the heartbeat and the

I've been using OCFS2 on a 3 way Centos 5.2 Xen cluster for a while now using it to share the VM disk images. In this way I can have live and transparent VM migration. I'd been having intermittent (every 2-3 weeks) incidents where a server would self fence. After configuring netconsole I managed to see that the fencing was due to a heartbeat threshold timeout so I have now increased

Hello list, Working on migrating my existing High-Availability setups from CentOS 5.3 to 6.0, both x86_64. I generally setup a fairly simple 2 node active/passive cluster using DRBD , Heartbeat, and Pacemaker. Use these clusters to run our proprietary Medical software plus a few key services ( openvpn , Digi PortServer Daemon, etc.). I had a procedure in place for doing all of this under 5.3

Also includes a couple minor model changes to support better error reporting. This method was added so that a client could submit multiple vms to the service layer in one call and get back appropriate messages showing any failures without those failures also causing the entire call to fail, or forcing the client to implement handling (begin/rescue blocks) of these errors to continue through the

Hoping someone can help me understand what is happening here; we start asterisk as a service at boot (actually, with heartbeat) on CentOS using the asterisk init script installed with "make config" upon reboot of the server (when the asterisk service is first started by heartbeat) we get color in the console when we connect to it using asterisk -r after the execution of

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

Hi, I ran the strace command while upssched was 100% CPU hungry. This is what I got: 1686633611.702798 read(7, "", 1) = 0 <0.000004> 1686633611.702816 read(7, "", 1) = 0 <0.000004> 1686633611.702834 pselect6(11, [7 10], NULL, NULL, {tv_sec=1, tv_nsec=0}, NULL) = 1 (in [7], left {tv_sec=0, tv_nsec=999998800}) <0.000006> 1686633611.702862 read(7,

I am sorry for the long *involved* post, however we are at wits end and advice would be greatly appreciated. Background: We have three servers in this example. Two of the servers (we will call Server A & B) each have a 2.7T raid 5 array that is mirrored with DRBD and monitored for failover with Heartbeat. NFS is running and exporting the array on Heartbeats virtual IP. "Server C"

Hello OCFS2 team, I'm currently looking at the OCFS2 code in linux-2.6.17.11, and i wander why OCFS2 performs its heartbeat on a disk region unlike on the network like many clustered services stack do. What is the requirement for a disk heartbeat ? Is there any way to tune this behaviour and change it into a network heartbeat ? -- Mathieu

Hello, Hideaki Goto has written a patch for OpenSSH that adds heartbeat and watchdog functions to OpenSSH: http://www.sc.isc.tohoku.ac.jp/~hgot/sources/openssh-watchdog.html The heartbeat function sends an SSH_MSG_IGNORE packet every <n> seconds to the server, and the watchdog function checks incoming packets only to see if the connection has been interrupted. Where I work, all Internet

Hi! Winbind is rather suboptimally reacts to networking changes. I use my notebook in at least 3 different network settings, in one of them I have very probabilistic access to DCs (cisco vpn client is a crap). An nss lookup sometimes takes very looong, sometimes even returns failure. Sometimes I have to login as root and restart winbind to get to my X session past the screensaver. This is far

This patch separates o2net and o2quo from knowing about one another as much as possible. This is the first in a series of patches that will allow userspace cluster interaction. Quorum is separated out first, and will ultimately only be associated with the disk heartbeat as a separate module. To do so, this patch performs the following changes: * o2hb_notify() is added to handle injection of

The fact that '-o ServerAliveInterval=50' makes no difference suggests that there is a bug in the OpenSSH client. It either fails to sent heartbeats, or it gets stuck in some Windows system call and this makes it to fail to send heartbeats. Yuri

On Thu, 24 Aug 2017 12:26:11 +0000 "A. James Lewis" <james at fsck.co.uk> wrote: > Well, network connectivity to the other DC would probably also be > required... and I don't have that currently... so there's the first > hurdle... but thanks for confirming that there's no other > configuration required. > > I'm slightly surprised that the

A new intel-gpu-tools quarterly release is available with the following changes: Library changes: - Changed debugfs handlers to open files for the DRM device in use, for setups with more than one DRM device. (Tomeu Vizoso) - Added support for 4K and audio HDMI EDID injection. (Abdiel Janulgue, Marius Vlad) - Added support for AMDGPU devices. (Chris Wilson) Tools changes: -