[Ubuntu-ha] [Bug 689734] Re: HAProxy fails to start at boot time
[Expired for haproxy (Ubuntu) because there has been no activity for 60 days.] ** Changed in: haproxy (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/689734 Title: HAProxy fails to start at boot time Status in “haproxy” package in Ubuntu: Expired Bug description: Binary package hint: haproxy I've got haproxy installed and configured on one of my servers. In the first 'listen' section of the config file, it binds to a number of aliased IP addresses. While I can start the service fine from the login prompt, it would not start at boot time, instead it showed the following in /var/log/boot.log * Starting haproxy haproxy [ALERT] 346/160552 (927) : Starting proxy haproxy: cannot bind socket [ALERT] 346/160552 (927) : Starting proxy haproxy: cannot bind socket [ALERT] 346/160552 (927) : Starting proxy haproxy: cannot bind socket [ALERT] 346/160552 (927) : Starting proxy haproxy: cannot bind socket [ALERT] 346/160552 (927) : Starting proxy haproxy: cannot bind socket [ALERT] 346/160552 (927) : Starting proxy haproxy: cannot bind socket [ALERT] 346/160552 (927) : Starting proxy haproxy: cannot bind socket [fail] On inspection the problem seems to come down to the lack of and specified start/stop numbers in the sysV init scripts, so it defaults to S20/K20 for everything. While the correct solution is to write an upstart script for haproxy, in the mean time, it should be set, so that the start number is higher than 35 (which seems to be the number /etc/init.d/networking uses)/ Changing the startup number to 35 seems to fix it, but I think 36 would be safer (the old number for networking was 35, so best make it start after that). This fixed the problem, on my server:- update-rc.d -f haproxy remove update-rc.d haproxy start 36 2 3 4 5 . stop 20 0 1 6 . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/689734/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 876648] Re: Unable to mount local glusterfs volume at boot
This bug was fixed in the package glusterfs - 3.2.5-1ubuntu1 --- glusterfs (3.2.5-1ubuntu1) precise; urgency=low * Added Ubuntu upstart jobs providing support for local glusterfs mounts (LP: #876648) -- Louis Zuckerman m...@louiszuckerman.com Sat, 28 Jan 2012 15:32:55 -0500 ** Changed in: glusterfs (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to glusterfs in Ubuntu. https://bugs.launchpad.net/bugs/876648 Title: Unable to mount local glusterfs volume at boot Status in “glusterfs” package in Ubuntu: Fix Released Bug description: Mounting glusterfs volumes from localhost in fstab does not work because the mounts are started before the glusterfs-server daemon. The problem is that upstart runs mountall before it runs the /etc/rc2.d/S20glusterfs-server initscript, so when the mount is tried it fails because there is not yet any glusterfs-server running on localhost. To reproduce (as root): apt-get install glusterfs-server glusterfs-client gluster volume create test eth0-IP:/var/tmp gluster volume start test mkdir /media/test echo localhost:test /media/test glusterfs defaults 0 0 /etc/fstab shutdown -r now After rebooting, the new volume will not be mounted. However, once the system has started and glusterfs-server daemon is running, doing a 'mount -a' will work to mount the volume (confirming that the volume fstab config are correct.) Solution: The solution is to replace the glusterfs-server initscript with a proper upstart job which will start the glusterfs-server daemon before the glusterfs mounts are tried by mountall. I have contributed the necessary upstart job upstream to the glusterfs project and it is included in the development source tree under extras/Ubuntu/glusterd.conf. https://github.com/gluster/glusterfs/blob/master/extras/Ubuntu/glusterd.conf To include this file in the glusterfs-server binary package, remove the debian/glusterfs-server.init file from the source package and add that upstart job to it as debian/glusterfs-server.upstart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/876648/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 876648] Re: Unable to mount local glusterfs volume at boot
** Branch linked: lp:~semiosis/ubuntu/precise/glusterfs/fix-for-876648 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to glusterfs in Ubuntu. https://bugs.launchpad.net/bugs/876648 Title: Unable to mount local glusterfs volume at boot Status in “glusterfs” package in Ubuntu: New Bug description: Mounting glusterfs volumes from localhost in fstab does not work because the mounts are started before the glusterfs-server daemon. The problem is that upstart runs mountall before it runs the /etc/rc2.d/S20glusterfs-server initscript, so when the mount is tried it fails because there is not yet any glusterfs-server running on localhost. To reproduce (as root): apt-get install glusterfs-server glusterfs-client gluster volume create test eth0-IP:/var/tmp gluster volume start test mkdir /media/test echo localhost:test /media/test glusterfs defaults 0 0 /etc/fstab shutdown -r now After rebooting, the new volume will not be mounted. However, once the system has started and glusterfs-server daemon is running, doing a 'mount -a' will work to mount the volume (confirming that the volume fstab config are correct.) Solution: The solution is to replace the glusterfs-server initscript with a proper upstart job which will start the glusterfs-server daemon before the glusterfs mounts are tried by mountall. I have contributed the necessary upstart job upstream to the glusterfs project and it is included in the development source tree under extras/Ubuntu/glusterd.conf. https://github.com/gluster/glusterfs/blob/master/extras/Ubuntu/glusterd.conf To include this file in the glusterfs-server binary package, remove the debian/glusterfs-server.init file from the source package and add that upstart job to it as debian/glusterfs-server.upstart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/876648/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 876648] Re: Unable to mount local glusterfs volume at boot
** Branch linked: lp:~semiosis/ubuntu/precise/glusterfs/fix-for-876648 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to glusterfs in Ubuntu. https://bugs.launchpad.net/bugs/876648 Title: Unable to mount local glusterfs volume at boot Status in “glusterfs” package in Ubuntu: New Bug description: Mounting glusterfs volumes from localhost in fstab does not work because the mounts are started before the glusterfs-server daemon. The problem is that upstart runs mountall before it runs the /etc/rc2.d/S20glusterfs-server initscript, so when the mount is tried it fails because there is not yet any glusterfs-server running on localhost. To reproduce (as root): apt-get install glusterfs-server glusterfs-client gluster volume create test eth0-IP:/var/tmp gluster volume start test mkdir /media/test echo localhost:test /media/test glusterfs defaults 0 0 /etc/fstab shutdown -r now After rebooting, the new volume will not be mounted. However, once the system has started and glusterfs-server daemon is running, doing a 'mount -a' will work to mount the volume (confirming that the volume fstab config are correct.) Solution: The solution is to replace the glusterfs-server initscript with a proper upstart job which will start the glusterfs-server daemon before the glusterfs mounts are tried by mountall. I have contributed the necessary upstart job upstream to the glusterfs project and it is included in the development source tree under extras/Ubuntu/glusterd.conf. https://github.com/gluster/glusterfs/blob/master/extras/Ubuntu/glusterd.conf To include this file in the glusterfs-server binary package, remove the debian/glusterfs-server.init file from the source package and add that upstart job to it as debian/glusterfs-server.upstart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/876648/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 876648] Re: Unable to mount local glusterfs volume at boot
** Branch linked: lp:~semiosis/ubuntu/precise/glusterfs/fix-for-876648 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to glusterfs in Ubuntu. https://bugs.launchpad.net/bugs/876648 Title: Unable to mount local glusterfs volume at boot Status in “glusterfs” package in Ubuntu: New Bug description: Mounting glusterfs volumes from localhost in fstab does not work because the mounts are started before the glusterfs-server daemon. The problem is that upstart runs mountall before it runs the /etc/rc2.d/S20glusterfs-server initscript, so when the mount is tried it fails because there is not yet any glusterfs-server running on localhost. To reproduce (as root): apt-get install glusterfs-server glusterfs-client gluster volume create test eth0-IP:/var/tmp gluster volume start test mkdir /media/test echo localhost:test /media/test glusterfs defaults 0 0 /etc/fstab shutdown -r now After rebooting, the new volume will not be mounted. However, once the system has started and glusterfs-server daemon is running, doing a 'mount -a' will work to mount the volume (confirming that the volume fstab config are correct.) Solution: The solution is to replace the glusterfs-server initscript with a proper upstart job which will start the glusterfs-server daemon before the glusterfs mounts are tried by mountall. I have contributed the necessary upstart job upstream to the glusterfs project and it is included in the development source tree under extras/Ubuntu/glusterd.conf. https://github.com/gluster/glusterfs/blob/master/extras/Ubuntu/glusterd.conf To include this file in the glusterfs-server binary package, remove the debian/glusterfs-server.init file from the source package and add that upstart job to it as debian/glusterfs-server.upstart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/876648/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 876648] Re: Unable to mount local glusterfs volume at boot
** Branch linked: lp:~semiosis/ubuntu/precise/glusterfs/fix-for-876648 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to glusterfs in Ubuntu. https://bugs.launchpad.net/bugs/876648 Title: Unable to mount local glusterfs volume at boot Status in “glusterfs” package in Ubuntu: New Bug description: Mounting glusterfs volumes from localhost in fstab does not work because the mounts are started before the glusterfs-server daemon. The problem is that upstart runs mountall before it runs the /etc/rc2.d/S20glusterfs-server initscript, so when the mount is tried it fails because there is not yet any glusterfs-server running on localhost. To reproduce (as root): apt-get install glusterfs-server glusterfs-client gluster volume create test eth0-IP:/var/tmp gluster volume start test mkdir /media/test echo localhost:test /media/test glusterfs defaults 0 0 /etc/fstab shutdown -r now After rebooting, the new volume will not be mounted. However, once the system has started and glusterfs-server daemon is running, doing a 'mount -a' will work to mount the volume (confirming that the volume fstab config are correct.) Solution: The solution is to replace the glusterfs-server initscript with a proper upstart job which will start the glusterfs-server daemon before the glusterfs mounts are tried by mountall. I have contributed the necessary upstart job upstream to the glusterfs project and it is included in the development source tree under extras/Ubuntu/glusterd.conf. https://github.com/gluster/glusterfs/blob/master/extras/Ubuntu/glusterd.conf To include this file in the glusterfs-server binary package, remove the debian/glusterfs-server.init file from the source package and add that upstart job to it as debian/glusterfs-server.upstart. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/876648/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 893352] Re: mysql ocf script broken in 1:1.0.3-2ubuntu1 (lucid)
** Branch linked: lp:ubuntu/lucid-proposed/cluster-agents -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to cluster-agents in Ubuntu. https://bugs.launchpad.net/bugs/893352 Title: mysql ocf script broken in 1:1.0.3-2ubuntu1 (lucid) Status in “cluster-agents” package in Ubuntu: Fix Released Status in “cluster-agents” source package in Lucid: Fix Committed Status in “cluster-agents” source package in Natty: Fix Released Status in “cluster-agents” source package in Precise: Fix Released Status in “cluster-agents” source package in Hardy: Invalid Bug description: Due to ubuntu putting /var/run on a tempory fs the /var/run/mysqld directory is removed upon a reboot. Mysql will fail to start via the crm after next boot as it cannot access or find the the needed /var/run/mysqld directory. This directory is created in the OCF script in the mysql_start() function , but for some reason not until after the script checks for the directory and write permissions, logs an error, and exits. (Line 345) I have fixed it by merely moving the if statement which test -w the pid_dir to after the if statements which create the pid_dir (line 350) SRU Justification: [Impact] /var/run/mysqld directory is typically created by pre-start in the mysql upstart job prior to starting the service every boot, as /var/run is tempfs and its contents ephemeral. Users of the Linux HA stack typically hand over control of specific services to the cluster managed by OCF scripts. The OCF script to manage mysql should take the same steps the required directories are present. A bug exists in the version of the mysql OCF script shipped in 1:1.0.3-2ubuntu1 which prevents the required directories from being created if they do not exist. If the clustered service is configured to use /var/run/mysqld (the ubuntu default for certain files), the cluster will fail to start mysql after a reboot. As most users of the cluster agent anticipate a *highly* available service, graceful system reboots should not result in an unavailable service. [Development Fix] As Florian Hass pointed out, this has been fixed upstream over a year ago and is not present in the current development release (precise, package renamed resource agents 1:3.9.2-5ubuntu1) [Stable Fix] A trivial fix at https://github.com/ClusterLabs/resource-agents/commit/a1801207e0602d9b975f336569b562c195a6eb8a solves the issue and is easily backported. [Test Case] See http://paste.ubuntu.com/746339/ for a minimal test case which involves configuration of a 1-node heartbeat/pacemaker cluster. [Regression Potential] Minimal chance of regression. Change simply ensures mysql directories exist before they are checked for write permissions. The change only affects the mysql OCF agent, all others are untouched. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cluster-agents/+bug/893352/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 821732] Re: Drop raexecupstart.patch and fix_lrmd_leak.patch to not cause socket leak in lrmd.
This bug was fixed in the package cluster-glue - 1.0.8-2ubuntu2 --- cluster-glue (1.0.8-2ubuntu2) precise; urgency=low * debian/patches/fix_lrmd_leak.patch: Drop as the issue was in glib and it is now fixed. (LP: #821732) -- Andres Rodriguez andres...@ubuntu.com Thu, 10 Nov 2011 13:22:47 -0500 ** Changed in: cluster-glue (Ubuntu Precise) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to cluster-glue in Ubuntu. https://bugs.launchpad.net/bugs/821732 Title: Drop raexecupstart.patch and fix_lrmd_leak.patch to not cause socket leak in lrmd. Status in “cluster-glue” package in Ubuntu: Fix Released Status in “cluster-glue” source package in Oneiric: Confirmed Status in “cluster-glue” source package in Precise: Fix Released Bug description: ii cluster-glue 1.0.7-3ubuntu2 The reusable cluster components for Linux HA The comamnds `crm ra classes` and `cr ra list` cause a socket leak in the lrmd daemon. When approx. 1024 sockets are allocated, the lrmd becomes unresponsive and must be killed. The syslog then shows repeated entries: Aug 3 10:25:08 server lrmd: [1941]: ERROR: socket_accept_connection: accept(sock=6): Too many open files While I only use these commands during development, it is still a nuisance. The leak does not appear for other commands, e.g. `crm resource list`, but I have not tested exhaustively. I originally reported this bug to http://developerbugs.linux- foundation.org/show_bug.cgi?id=2626. There I was informed that the behavior most likely stems from an unsupported patch (raexecupstart.patch) in the Ubuntu package. When I remove that patch, the socket leaks does indeed go away. Although I did not have any deadlock situations with the original code, I replaced it with the attached patch which should prevent any possible recursive calls of the `on_remove_client' function. *** After further investigation it was determined that the problem was in glib itself and the patch was not needed in the latest's releases of Ubuntu, but rather, this patches were creating the socket leak. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cluster-glue/+bug/821732/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 883781] Re: cman package no longer includes /usr/sbin/fenced
** Branch linked: lp:ubuntu/oneiric-proposed/redhat-cluster -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to redhat-cluster in Ubuntu. https://bugs.launchpad.net/bugs/883781 Title: cman package no longer includes /usr/sbin/fenced Status in “redhat-cluster” package in Ubuntu: Fix Released Status in “redhat-cluster” source package in Oneiric: Fix Committed Status in “redhat-cluster” source package in Precise: Fix Released Bug description: Hi, I noticed that in oneiric 11.10 the program /usr/sbin/fenced is absent from package cman 3.0.12-2ubuntu5 when I try to set up a cman cluster it looks for fenced and doesn't find it: Starting cluster: Checking Network Manager... [ OK ] Global setup... [ OK ] Loading kernel modules... [ OK ] Mounting configfs... [ OK ] Starting cman... [ OK ] Waiting for quorum... [ OK ] Starting fenced... Unable to find fenced in PATH [FAILED] == SRU Justification == [Impact] During the separation of files from the redhat-cluster source in preparation for newer releases, the fenced bin was left out from installation. [Development Fix] This bug was addressed in Precise by simply installing the missing file and its manpage. [Test Case] To reproduce the bug simply install cman and try to initialize it. It won't be able to find fenced. [Regression Potential] None, as it is just the installation of a file that used to be installed before removing the installation of other files that are now on its own package (fence-agents, resource-agents). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/redhat-cluster/+bug/883781/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 799711] Re: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up
[Expired for ocfs2-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ocfs2-tools (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/799711 Title: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up Status in “ocfs2-tools” package in Ubuntu: Expired Bug description: Binary package hint: ocfs2-tools The system is an asymmetric-opt-in cluster. Following this HowTo: https://wiki.ubuntu.com/ClusterStack/LucidTesting#Pacemaker.2C_drbd8_and_OCFS2_or_GFS2 I'm able to start the DRBD resource and the DLM but when trying to start the resource cloneO2CB the following is logged in syslog: o2cb[11796]: ERROR: ocfs2_controld.pcmk did not come up ocfs2_controld[12870]: Unable to connect to CKPT: Object does not exist The same thing happens when trying to test the o2cb script manually using: /usr/sbin/ocf-tester -n oc2b /usr/lib/ocf/resource.d/pacemaker/o2cb Found the following document while trying to gain more information about the error: http://www.drbd.org/users-guide/s-ocfs2-enable.html After creating the configuration file mentioned in that document and executing dpkg-reconfigure ocfs2-tools the following is logged on the console Loading stack plugin o2cb: OK Setting cluster stack o2cb: OK Starting O2CB cluster ocfs2: OK Leaving the file /etc/ocfs2/cluster.conf mentioned in the LinBit document in place or deleting it does not help starting the o2cb resource as Pacemaker resource. Any help would be greatly appreciated. So long Henning Malzahn ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: ocfs2-tools (not installed) ProcVersionSignature: Ubuntu 2.6.32-32.62-generic 2.6.32.38+drm33.16 Uname: Linux 2.6.32-32-generic x86_64 NonfreeKernelModules: vmnet vsock vmci vmmon nvidia Architecture: amd64 Date: Mon Jun 20 14:42:09 2011 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) ProcEnviron: PATH=(custom, user) LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: ocfs2-tools To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/799711/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 802770] Re: can't use ocfs2 with cman clustering
[Expired for ocfs2-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ocfs2-tools (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/802770 Title: can't use ocfs2 with cman clustering Status in “ocfs2-tools” package in Ubuntu: Expired Bug description: operating system: linux ubuntu server 11.04 64-bit kernetl 2.6.38-8-server relevant installed packages: 1. ocfs2-tools 1.6.3-1ubuntu2 2. ocfs2-tools-cman 1.6.3-1ubuntu2 3. cman 3.0.12-2ubuntu3 i've configure ocfs2 cluster and cman cluster service in a 2 node setup cman runs and both nodes communicate if o2cd service is not running ocfs2 service will not start. Starting Oracle Cluster File System (OCFS2) mount.ocfs2: Unable to access cluster service while trying initialize cluster Failed i need to use cman for fcntl locks that oc2b does not provide config file: /etc/ocfs2/cluster.conf cluster: node_count = 2 name = smbhaclus node: ip_port = 7901 ip_address = 10.0.0.23 number = 7 name = sambaha.n1 cluster = smbhaclus node: ip_port = 7901 ip_address = 10.0.0.24 number = 87 name = sambaha.n2 cluster = smbhaclus the config file shouldn't be a problem as the cluster will function if o2cb is started. have tried to update stack using tunefs.ocfs2 --update-cluster-stack DEVICE no success creating a new ocfs2 file system is also unsuccessful further information: mkfs.ocfs2 approach yields a formatted fs still using o2cb stack: sudo mkfs.ocfs2 -F -b 4KB -N 3 -T mail --fs-feature-level=max-features /dev/drbd1 mkfs.ocfs2 1.6.3 Cluster stack: classic o2cb Filesystem Type of mail Label: ocfs2smbha sudo service o2cb status Driver for configfs: Loaded Filesystem configfs: Mounted Driver for ocfs2_dlmfs: Not loaded Checking O2CB cluster ocfs2: Offline --- sudo cman_tool status Version: 6.2.0 Config Version: 2 Cluster Name: smbhaclus Cluster Id: 56117 Cluster Member: Yes Cluster Generation: 48 Membership state: Cluster-Member Nodes: 2 Expected votes: 1 Total votes: 2 Node votes: 1 Quorum: 1 Active subsystems: 7 Flags: 2node Ports Bound: 0 Node name: sambaha.n1 Node ID: 1 Multicast addresses: 239.192.219.17 Node addresses: 10.0.0.23 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ocfs2-tools/+bug/802770/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 744293] Re: Infinite loop in helper LVM script for DRBD 8 in Lucid
** Branch linked: lp:ubuntu/lucid-proposed/drbd8 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in Ubuntu. https://bugs.launchpad.net/bugs/744293 Title: Infinite loop in helper LVM script for DRBD 8 in Lucid Status in “drbd8” package in Ubuntu: Fix Released Status in “drbd8” source package in Lucid: Fix Committed Bug description: The script /usr/lib/drbd/snapshot-resync-target-lvm.sh shipped with drbd v8.3.7 in Lucid fails to read its command line options and falls into an infinite loop. This bug is not in present in natty, but I humbly request an SRU to Lucid. This script can be called by DRBD to create an LVM snapshot of a resource before it starts resyncing (thus becoming inconsistent). This script is present (though commented out) in the default drbd configuration file /etc/drbd.d/global_common.conf . This bug can result in drbd silently failing to resync an outdated resource. Thus, any newer data will be lost if the cluster fails over to the outdated node. This is a known problem upstream and it was fixed in later versions of DRBD. The following patch was committed upstream to address this bug : http://git.drbd.org/?p=drbd-8.3.git;a=commitdiff;h=1fd3ad953663615e946167191e1d9885af81450a Steps to reproduce: On a cluster composed of node A and node B: - on both nodes, uncomment the line before-resync-target /usr/lib/drbd/snapshot-resync-target-lvm.sh -p 15 -- -c 16k; - on both nodes, configure a drbd resource called test - make the initial synchronization - on B, do drbdadm disconnect test - nn A, make test primary and write to it - on B, do drbdadm connect test = the script will kick in and fall in an endless loop - top will show it using 100% CPU. lsb_release -rd Description: Ubuntu 10.04.2 LTS Release: 10.04 apt-cache policy drbd8-utils drbd8-utils: Installé : 2:8.3.7-1ubuntu2.1 Candidat : 2:8.3.7-1ubuntu2.1 Table de version : *** 2:8.3.7-1ubuntu2.1 0 500 http://fr.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 2:8.3.7-1ubuntu2 0 500 http://fr.archive.ubuntu.com/ubuntu/ lucid/main Packages Lionel Sausin. === SRU Justification IMPACT: Using the --percent option, the script entered in an endless loop. This can result on having DRBD failing to resync an outdated resource when using LVM. REPRODUCE (as specified above): On a cluster composed of node A and node B: - on both nodes, uncomment the line before-resync-target /usr/lib/drbd/snapshot-resync-target-lvm.sh -p 15 -- -c 16k; - on both nodes, configure a drbd resource called test - make the initial synchronization - on B, do drbdadm disconnect test - nn A, make test primary and write to it - on B, do drbdadm connect test = the script will kick in and fall in an endless loop - top will show it using 100% CPU. HOW FIXED: The fix was taken from upstream. It basically consists on sourcing the default file first, then shifting correctly the option, and finally and use drbdadm sh-minor to obtain the minor version instead of guessing it, which all together can cause the script to enter in infinite loop and fail to resync as specified above. PATCH: Attached. Uploaded to lucid-proposed for review. REGRESSION POTENTIAL: Minimal. This has been tested thoroughly. === To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/drbd8/+bug/744293/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 770743] Re: pacemaker-mgmt version 2.0.0+hg1141-2ubuntu1 failed to build on amd64 with GCC-4.6/oneiric
** Branch linked: lp:ubuntu/heartbeat -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to heartbeat in Ubuntu. https://bugs.launchpad.net/bugs/770743 Title: pacemaker-mgmt version 2.0.0+hg1141-2ubuntu1 failed to build on amd64 with GCC-4.6/oneiric Status in Heartbeat - Subsystem for High-Availability Linux: Confirmed Status in “heartbeat” package in Ubuntu: Fix Released Status in “pacemaker-mgmt” package in Ubuntu: Fix Released Status in “heartbeat” source package in Oneiric: Fix Released Status in “pacemaker-mgmt” source package in Oneiric: Fix Released Bug description: pacemaker-mgmt version 2.0.0+hg1141-2ubuntu1 failed to build on amd64 with GCC-4.6/oneiric Link to failed build: https://launchpad.net/ubuntu/+archive/test-rebuild-20110413/+buildjob/2464315 Details about the rebuild: https://lists.ubuntu.com/archives/ubuntu-devel/2011-April/033042.html Direct link to the build log: https://launchpad.net/ubuntu/+archive /test-rebuild-20110413/+buildjob/2464315/+files/buildlog_ubuntu-natty- amd64.pacemaker-mgmt_2.0.0%2Bhg1141-2ubuntu1_FAILEDTOBUILD.txt.gz This log snippet might be of interest, since it triggered the matcher 'Purging chroot-autobuild'. Excerpt 1640 lines into the build log: libtool: link: gcc -std=gnu99 -Wall -g -O2 -I/usr/include/heartbeat -I/usr/include/pacemaker -fgnu89-inline -Wall -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wdeclaration-after-statement -Wpointer-arith -Wwrite-strings -Wcast-qual -Wcast-align -Wbad-function-cast -Winline -Wmissing-format-attribute -Wformat=2 -Wformat-security -Wformat-nonliteral -Wno-long-long -Wno-strict-aliasing -ansi -D_GNU_SOURCE -DANSI_ONLY -ggdb3 -funsigned-char -Wall -g -O2 -I/usr/include/heartbeat -I/usr/include/pacemaker -fgnu89-inline -Wall -Wmissing-prototypes -Wmissing-declarations -Wstrict-prototypes -Wdeclaration-after-statement -Wpointer-arith -Wwrite-strings -Wcast-qual -Wcast-align -Wbad-function-cast -Winline -Wmissing-format-attribute -Wformat=2 -Wformat-security -Wformat-nonliteral -Wno-long-long -Wno-strict-aliasing -ansi -D_GNU_SOURCE -DANSI_ONLY -ggdb3 -funsigned-char -Wl,-Bsymbolic-functions -Wl,-E -Wl,-Bsymbolic-functions -o hbagent hbagent.o hbagentv2.o LHANodeTable.o LHAClusterInfo.o LHAIFStatusTable.o LHAMembershipTable.o LHAHeartbeatConfigInfo.o LHAResourceGroupTable.o LHAResourceTable.o LHAResourceStatusUpdate.o -L/usr/lib /usr/lib/libnetsnmpagent.so /usr/lib/libnetsnmphelpers.so /usr/lib/libnetsnmpmibs.so /usr/lib/libnetsnmp.so -lwrap /usr/lib/libcrmcommon.so /usr/lib/libcib.so /usr/lib/libpe_status.so /usr/lib/libhbclient.so /usr/lib/libccmclient.so /usr/lib/libclm.so -lncurses -L/usr/lib/x86_64-linux-gnu /usr/lib/x86_64-linux-gnu/libglib-2.0.so /usr/lib/x86_64-linux-gnu/libgnutls.so -lbz2 /usr/lib/libplumb.so /usr/lib/libpils.so /usr/lib/libxml2.so -lc -lpam -lrt -ldl /usr/lib/libltdl.so /usr/lib/libclm.so: undefined reference to `oc_ev_activate' /usr/lib/libclm.so: undefined reference to `oc_ev_set_callback' /usr/lib/libclm.so: undefined reference to `oc_ev_callback_done' /usr/lib/libclm.so: undefined reference to `oc_ev_special' /usr/lib/libclm.so: undefined reference to `oc_ev_handle_event' /usr/lib/libclm.so: undefined reference to `oc_ev_unregister' /usr/lib/libclm.so: undefined reference to `oc_ev_register' collect2: ld returned 1 exit status make[2]: *** [hbagent] Error 1 make[2]: Leaving directory `/build/buildd/pacemaker-mgmt-2.0.0+hg1141/snmp_subagent' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/build/buildd/pacemaker-mgmt-2.0.0+hg1141' make: *** [build-stamp] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 ** Build finished at 20110425-0910 FAILED [dpkg-buildpackage died] Purging chroot-autobuild/build/buildd/pacemaker-mgmt-2.0.0+hg1141 To manage notifications about this bug go to: https://bugs.launchpad.net/heartbeat/+bug/770743/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 763467] Re: SIOCGMIIREG errors on e1000e interface
[Expired for keepalived (Ubuntu) because there has been no activity for 60 days.] ** Changed in: keepalived (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/763467 Title: SIOCGMIIREG errors on e1000e interface Status in “keepalived” package in Ubuntu: Expired Bug description: Binary package hint: keepalived Running keepalived on 10.04 LTS (running fully updated) throws SIOCGMIIREG errors, it seems to be related to the e1000e driver. I compiled the latest keepalived version (1.2.2) from source and this resolves the problem. # dpkg -l | grep keepalived ii keepalived 1.1.17-2ubuntu1 Failover and monitoring daemon for LVS clust Errors: - Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error Keepalived_healthcheckers: SIOCGMIIREG on eth4.4010 failed: Input/output error Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error Keepalived_healthcheckers: SIOCGMIIREG on eth4.4010 failed: Input/output error Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error Keepalived_healthcheckers: SIOCGMIIREG on eth4.4010 failed: Input/output error Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error Keepalived_healthcheckers: SIOCGMIIREG on eth4.4010 failed: Input/output error Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error Keepalived_healthcheckers: SIOCGMIIREG on eth4.4010 failed: Input/output error Keepalived_vrrp: SIOCGMIIREG on eth3.4005 failed: Input/output error Keepalived_healthcheckers: SIOCGMIIREG on eth4.4010 failed: Input/output error lspci of the nic: (intel quad gig copper nic) - 06:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) (rev 06) Subsystem: Intel Corporation 82571EB Gigabit Ethernet Controller (Copper) Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast TAbort- TAbort- MAbort- SERR- PERR- INTx- Latency: 0, Cache Line Size: 64 bytes Interrupt: pin A routed to IRQ 33 Region 0: Memory at fe3a (32-bit, non-prefetchable) [size=128K] Region 1: Memory at fe38 (32-bit, non-prefetchable) [size=128K] Region 2: I/O ports at ccc0 [size=32] Expansion ROM at e010 [disabled] [size=128K] Capabilities: [c8] Power Management version 2 Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold-) Status: D0 PME-Enable- DSel=0 DScale=1 PME- Capabilities: [d0] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0 Enable+ Address: fee0300c Data: 41d1 Capabilities: [e0] Express (v1) Endpoint, MSI 00 DevCap: MaxPayload 256 bytes, PhantFunc 0, Latency L0s 512ns, L1 64us ExtTag- AttnBtn- AttnInd- PwrInd- RBE- FLReset- DevCtl: Report errors: Correctable+ Non-Fatal+ Fatal+ Unsupported+ RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+ MaxPayload 128 bytes, MaxReadReq 512 bytes DevSta: CorrErr- UncorrErr+ FatalErr- UnsuppReq+ AuxPwr- TransPend- LnkCap: Port #4, Speed 2.5GT/s, Width x4, ASPM L0s, Latency L0 4us, L1 64us ClockPM- Suprise- LLActRep- BwNot- LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- Retrain- CommClk- ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt- LnkSta: Speed 2.5GT/s, Width x4, TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt- Capabilities: [100] Advanced Error Reporting ? Capabilities: [140] Device Serial Number 1e-bb-f6-ff-ff-17-15-00 Kernel driver in use: e1000e Kernel modules: e1000e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/763467/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 787062] Re: Please resync corosync 1.3.0-3 (main) from debian unstable (main)
This bug was fixed in the package corosync - 1.3.0-3ubuntu1 --- corosync (1.3.0-3ubuntu1) oneiric; urgency=low * Resync from debian unstable (LP: #787062). * debian/corosync.init: Ensure that '/var/run/resource-agents' is created; otherwise cluster operations will fail as RA's expect it (LP: #751344). corosync (1.3.0-3) unstable; urgency=low * [b763c6a] New patch 0001-Define-semun-on-KFreeBSD.patch Thanks to Martin G. Loschwitz (Closes: #621889) * [0e2ebb8] Switch to 3.0 (quilt) format corosync (1.3.0-2) unstable; urgency=low * Upload to unstable * [f1907f8] Move corosync start out of rcS since we want to be able to log to syslog and rsyslog isn't started in rcS. Fix cherry-picked from squeeze. (Closes: #608269) corosync (1.3.0-1) experimental; urgency=low * [986d8ed] Make sure we start before and stop after $syslog. Thanks to Frank Schmidt for tracking down the start issues (Closes: #596694) * [12e6e88] Fix default consensus timeout (Closes: #573030) * [0d7cc00] Don't timeout during daemon shut down since this might leave pacemaker resources running. See: http://developerbugs.linux-foundation.org/show_bug.cgi?id=2217 (Closes: #556533) * [583fe40] Add copytruncate to logrotate snippet (Closes: #584582) * [0082261] No need for quilt anymore * [d64862c] Bump standards version * [5cbb2cc] New upstream version 1.3.0 * [61a8159] Upstream renamed CHANGELOG to ChangeLog * [836c0ef] Don't ignore make clean errors * [3c3b0c0] Include BSD license instead of referencing it corosync (1.2.7-1) experimental; urgency=low * [1c157d6] New upstream version 1.2.7 * [a2453fb] Add status to corosync init script (Closes: #582104) - thanks to Raoul Bhatia for the patch -- Andres Rodriguez andres...@ubuntu.com Thu, 26 May 2011 21:02:54 +0200 ** Changed in: corosync (Ubuntu) Status: Confirmed = Fix Released ** Bug watch added: developerbugs.linux-foundation.org/ #2217 http://developerbugs.linux-foundation.org/show_bug.cgi?id=2217 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to corosync in Ubuntu. https://bugs.launchpad.net/bugs/787062 Title: Please resync corosync 1.3.0-3 (main) from debian unstable (main) Status in “corosync” package in Ubuntu: Fix Released Bug description: Binary package hint: corosync corosync (1.3.0-3ubuntu1) oneiric; urgency=low . * Resync from debian unstable. * debian/corosync.init: Ensure that '/var/run/resource-agents' is created; otherwise cluster operations will fail as RA's expect it (LP: #751344). . -- Andres Rodriguez andres...@ubuntu.com Mon, 23 May 2011 11:49:46 -0400 . corosync (1.3.0-3) unstable; urgency=low . * [b763c6a] New patch 0001-Define-semun-on-KFreeBSD.patch Thanks to Martin G. Loschwitz (Closes: #621889) * [0e2ebb8] Switch to 3.0 (quilt) format . corosync (1.3.0-2) unstable; urgency=low . * Upload to unstable * [f1907f8] Move corosync start out of rcS since we want to be able to log to syslog and rsyslog isn't started in rcS. Fix cherry-picked from squeeze. (Closes: #608269) . corosync (1.3.0-1) experimental; urgency=low . * [986d8ed] Make sure we start before and stop after $syslog. Thanks to Frank Schmidt for tracking down the start issues (Closes: #596694) * [12e6e88] Fix default consensus timeout (Closes: #573030) * [0d7cc00] Don't timeout during daemon shut down since this might leave pacemaker resources running. See: http://developerbugs.linux-foundation.org/show_bug.cgi?id=2217 (Closes: #556533) * [583fe40] Add copytruncate to logrotate snippet (Closes: #584582) * [0082261] No need for quilt anymore * [d64862c] Bump standards version * [5cbb2cc] New upstream version 1.3.0 * [61a8159] Upstream renamed CHANGELOG to ChangeLog * [836c0ef] Don't ignore make clean errors * [3c3b0c0] Include BSD license instead of referencing it . corosync (1.2.7-1) experimental; urgency=low . * [1c157d6] New upstream version 1.2.7 * [a2453fb] Add status to corosync init script (Closes: #582104) - thanks to Raoul Bhatia for the patch ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 583309] Re: fsck.ocfs2 not supporting -a option, causing os boot to stall
[Expired for ocfs2-tools (Ubuntu) because there has been no activity for 60 days.] ** Changed in: ocfs2-tools (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to ocfs2-tools in Ubuntu. https://bugs.launchpad.net/bugs/583309 Title: fsck.ocfs2 not supporting -a option, causing os boot to stall Status in “ocfs2-tools” package in Ubuntu: Expired Bug description: Binary package hint: ocfs2-tools 1.3.9-0ubuntu1 If the ocfs file system is configured to be mounted at boot time with 8.04 it will stop and ask for a root password or control-d to continue because fsck.ocfs2 does not support the -a option, it make no sense to try to do a fsck on a shared storage file system. I need a patch for the boot scripts or an updated fsck.ocfs2 to support the -a as a noop. Thanks Mike ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 751344] Re: Cluster resource agents fail to run because of missing /var/run/resource-agents directory
This bug was fixed in the package corosync - 1.2.1-4ubuntu1 --- corosync (1.2.1-4ubuntu1) natty; urgency=low * debian/corosync.init: Ensure that '/var/run/resource-agents' is created; otherwise cluster operations will fail as RA's expect it (LP: #751344). -- Andres Rodriguez andres...@ubuntu.com Fri, 15 Apr 2011 13:21:30 -0700 ** Changed in: corosync (Ubuntu) Status: Fix Committed = Fix Released ** Changed in: heartbeat (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to heartbeat in Ubuntu. https://bugs.launchpad.net/bugs/751344 Title: Cluster resource agents fail to run because of missing /var/run /resource-agents directory Status in “cluster-agents” package in Ubuntu: Invalid Status in “corosync” package in Ubuntu: Fix Released Status in “heartbeat” package in Ubuntu: Fix Released Bug description: Binary package hint: cluster-agents ## Issue * Cluster IP resource cannot be started * Error messages in /var/log/syslog: Apr 5 13:38:32 natty2 lrmd: [1199]: info: RA output: (virtual-ip:start:stderr) touch: Apr 5 13:38:32 natty2 lrmd: [1199]: info: RA output: (virtual-ip:start:stderr) cannot touch `/var/run/resource-agents/IPaddr-eth0' Apr 5 13:38:32 natty2 lrmd: [1199]: info: RA output: (virtual-ip:start:stderr) : No such file or directory Apr 5 13:38:32 natty2 lrmd: [1199]: info: RA output: (virtual-ip:start:stderr) ## Environment * Natty Narwhale 11.04 (all architectures) ## Resolution * (Workaround) Create /var/run/resource-agents manually ## Root Cause Package does not create directory under /var/run. Some resource agents check it, and will create it if necessary. ## Diagnostic Steps # grep lrmd /var/log/syslog: Apr 5 13:38:25 natty1 lrmd: [1534]: info: RA output: (virtual-ip:start:stderr) touch: Apr 5 13:38:25 natty1 lrmd: [1534]: info: RA output: (virtual-ip:start:stderr) cannot touch `/var/run/resource-agents/IPaddr-eth0' Apr 5 13:38:25 natty1 lrmd: [1534]: info: RA output: (virtual-ip:start:stderr) : No such file or directory Apr 5 13:38:25 natty1 lrmd: [1534]: info: RA output: (virtual-ip:start:stderr) Apr 5 13:38:30 natty1 lrmd: [1534]: info: rsc:virtual-ip:8: stop # crm status [...] Failed actions: virtual-ip_start_0 (node=natty1, call=18, rc=1, status=complete): unknown error # mkdir /var/run/resource-agents/ # (all nodes) # crm cleanup web-1 # crm status Resource Group: web-1 apache (ocf::heartbeat:apache):Started natty1 virtual-ip (ocf::heartbeat:IPaddr):Started natty1 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cluster-agents 1:1.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 Date: Tue Apr 5 13:46:35 2011 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cluster-agents UpgradeStatus: No upgrade log present (probably fresh install) ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 751344] Re: Cluster resource agents fail to run because of missing /var/run/resource-agents directory
This bug was fixed in the package heartbeat - 1:3.0.4-1ubuntu3 --- heartbeat (1:3.0.4-1ubuntu3) natty; urgency=low * debian/patches/create_ra_rundir.patch: Ensure that init script creates '/var/run/resource-agents'; otherwise cluster operations will fail as RA's expect it (LP: #751344). -- Andres Rodriguez andres...@ubuntu.com Fri, 15 Apr 2011 13:26:23 -0700 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to heartbeat in Ubuntu. https://bugs.launchpad.net/bugs/751344 Title: Cluster resource agents fail to run because of missing /var/run /resource-agents directory Status in “cluster-agents” package in Ubuntu: Invalid Status in “corosync” package in Ubuntu: Fix Released Status in “heartbeat” package in Ubuntu: Fix Released Bug description: Binary package hint: cluster-agents ## Issue * Cluster IP resource cannot be started * Error messages in /var/log/syslog: Apr 5 13:38:32 natty2 lrmd: [1199]: info: RA output: (virtual-ip:start:stderr) touch: Apr 5 13:38:32 natty2 lrmd: [1199]: info: RA output: (virtual-ip:start:stderr) cannot touch `/var/run/resource-agents/IPaddr-eth0' Apr 5 13:38:32 natty2 lrmd: [1199]: info: RA output: (virtual-ip:start:stderr) : No such file or directory Apr 5 13:38:32 natty2 lrmd: [1199]: info: RA output: (virtual-ip:start:stderr) ## Environment * Natty Narwhale 11.04 (all architectures) ## Resolution * (Workaround) Create /var/run/resource-agents manually ## Root Cause Package does not create directory under /var/run. Some resource agents check it, and will create it if necessary. ## Diagnostic Steps # grep lrmd /var/log/syslog: Apr 5 13:38:25 natty1 lrmd: [1534]: info: RA output: (virtual-ip:start:stderr) touch: Apr 5 13:38:25 natty1 lrmd: [1534]: info: RA output: (virtual-ip:start:stderr) cannot touch `/var/run/resource-agents/IPaddr-eth0' Apr 5 13:38:25 natty1 lrmd: [1534]: info: RA output: (virtual-ip:start:stderr) : No such file or directory Apr 5 13:38:25 natty1 lrmd: [1534]: info: RA output: (virtual-ip:start:stderr) Apr 5 13:38:30 natty1 lrmd: [1534]: info: rsc:virtual-ip:8: stop # crm status [...] Failed actions: virtual-ip_start_0 (node=natty1, call=18, rc=1, status=complete): unknown error # mkdir /var/run/resource-agents/ # (all nodes) # crm cleanup web-1 # crm status Resource Group: web-1 apache (ocf::heartbeat:apache):Started natty1 virtual-ip (ocf::heartbeat:IPaddr):Started natty1 ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: cluster-agents 1:1.0.4-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38 Uname: Linux 2.6.38-7-generic x86_64 Architecture: amd64 Date: Tue Apr 5 13:46:35 2011 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cluster-agents UpgradeStatus: No upgrade log present (probably fresh install) ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 619712] Re: keepalived vrrp race condition and fix (versions 1.1.17 and 1.2.0 but perhaps all?)
** Branch linked: lp:~andreserl/ubuntu/natty/keepalived/lp619712 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to keepalived in Ubuntu. https://bugs.launchpad.net/bugs/619712 Title: keepalived vrrp race condition and fix (versions 1.1.17 and 1.2.0 but perhaps all?) Status in Release Notes for Ubuntu: Invalid Status in “keepalived” package in Ubuntu: Fix Committed Status in “keepalived” source package in Maverick: Won't Fix Bug description: Binary package hint: keepalived Hello, About a keepalived vrrp race condition and fix (versions 1.1.17 and 1.2.0) and probably all other versions. Impact: possible complete/partial datacenter disruptions due to gratious arp/multicast floods The situation to reproduce the race condition The race condition got triggered in our situation with 1 cluster of 4 machines, sharing 3 (vlan) interfaces. Reason for doing doing so, not really importand, using vrrp and redundant cluster (2x2) for changing the default gateway, in case of a lease line failure. The most basic setup, and easyest way to trigger is a subset of above -3 machines, with keepalived -2 interfaces/machine, defined in keepalived as vrrp_instance -1 vrrp_sync_group, with those interfaces included some key settings: machine1: initial state: state BACKUP int 1, prio 250 int 2, prio 250 machine2: initial state: state BACKUP int 1, prio 200 int 2, prio 200 machine3: initial state: state MASTER int 1, prio 150 int 2, prio 150 Machine3 is set to master, just to trigger the race condition, but in initial state BACKUP, a connection failure (without a link down) will do the same, which is the situation we encountered. WARNING: below may/will cause network disruption, so be prepared. The way to trigger, is having started keepalived on machine 1 2, where machine 1 gently becomes a master as meant/configured. Now, start machine3, and here it happens, as soon machine sends a single vrrp message (as it want's to be master), machine 1 2 get's crazy(haywire), and come in a race condition which will never stop, until you stop one of machine 1 or 2. Stopping machine 3 will definitly NOT stop the race. A sample of the relevant logging of the race: machine 1: Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV610) Received lower prio advert, forcing new election Aug 16 13:22:27 saaplsprd01 Keepalived_vrrp: VRRP_Instance(AMV910) Received
[Ubuntu-ha] [Bug 719333] [NEW] CLVM not locking LV's properly even when set to exclusive
You have been subscribed to a public bug by Tom Ellis (tellis): Binary package hint: lvm2 Hello, i got Ubuntu Lucid Server + openais + lvm + clvm running on a central storage. Metadata updates are distributed properly: root@xen1:~# vgs VG #PV #LV #SN Attr VSize VFree vgsas11 5 0 wz--nc 1.36t 1.33t root@xen1:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-diskvgsas1 -wi-a- 4.00g root@xen2:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-disk vgsas1 -wi-a- 4.00g root@xen1:~# lvchange -an vgsas1/play1.xxx.net-disk root@xen1:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-diskvgsas1 -wi--- 4.00g NOW: Metadata obviously distributed correctly the xen2 root@xen2:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-disk vgsas1 -wi--- 4.00g root@xen1:~# lvchange -aey vgsas1/play1.xxx.net-disk root@xen1:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-diskvgsas1 -wi-a- 4.00g NOW: LV still shown as inactive on the second node. root@xen2:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-disk vgsas1 -wi--- 4.00g NOW: even better, i can activate it exclusive on the second node: root@xen2:~# lvchange -aey vgsas1/play1.xxx.net-disk root@xen2:~# lvs LV VG Attr LSize Origin Snap% Move Log Copy% Convert play1.xxx.net-disk vgsas1 -wi-a- 4.00g I can even mount it from both nodes: root@xen2:~# mount /dev/vgsas1/play1.xxx.net-disk /mnt/ root@xen2:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/cciss/c0d0p1 57672700 9810272 44932816 18% / none525972 268525704 1% /dev none525972 9512516460 2% /dev/shm none52597272525900 1% /var/run none525972 0525972 0% /var/lock none525972 0525972 0% /lib/init/rw /dev/mapper/vgsas1-play1.xxx.net--disk 4128448754656 3164080 20% /mnt AND ON: root@xen1:~# !mou mount /dev/vgsas1/play1.xxx.net-disk /mnt/ root@xen1:~# df Filesystem 1K-blocks Used Available Use% Mounted on /dev/cciss/c0d0p1 24030076 14832148 7977272 66% / none525972 280525692 1% /dev none525972 9392516580 2% /dev/shm none52597284525888 1% /var/run none525972 0525972 0% /var/lock none525972 0525972 0% /lib/init/rw /dev/mapper/vgsas1-play1.xxx.net--disk 4128448754656 3164080 20% /mnt If that was no test setting but 2 vm's accessing one ext3 fs simultaneously, I would be in serious trouble now! btw, the Clvm was recompiled against openais to get rid of cman. root@xen1:~# dpkg --list|grep lvm ii clvm2.02.54-1ubuntu4.2 Cluster LVM Daemon for lvm2 ii lvm22.02.54-1ubuntu4.1 The Linux Logical Volume Manager root@xen1:~# crm status Last updated: Tue Feb 15 14:16:39 2011 Stack: openais Current DC: xen2 - partition with quorum Version: 1.0.8-042548a451fce8400660f6031f4da6f0223dd5dd 2 Nodes configured, 2 expected votes 0 Resources configured. Online: [ xen1 xen2 ] What's wrong there? so long, Bastian ** Affects: lvm2 Importance: Unknown Status: Unknown ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: Confirmed -- CLVM not locking LV's properly even when set to exclusive https://bugs.launchpad.net/bugs/719333 You received this bug notification because you are a member of Ubuntu High Availability Team, which is a direct subscriber. ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 680825] Re: package drbd8-source 2:8.3.7-1ubuntu2.1 failed to install/upgrade: drbd8 kernel module failed to build
[Expired for drbd8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: drbd8 (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. https://bugs.launchpad.net/bugs/680825 Title: package drbd8-source 2:8.3.7-1ubuntu2.1 failed to install/upgrade: drbd8 kernel module failed to build Status in “drbd8” package in Ubuntu: Expired Bug description: package drbd8-source 2:8.3.7-1ubuntu2.1 failed to install/upgrade: drbd8 kernel module failed to build ProblemType: Package DistroRelease: Ubuntu 10.04 Package: drbd8-source 2:8.3.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.31-14.48-generic-pae Uname: Linux 2.6.31-14-generic-pae i686 Architecture: i386 Date: Tue Nov 23 02:12:52 2010 ErrorMessage: drbd8 kernel module failed to build PackageArchitecture: all PackageVersion: 2:8.3.7-1ubuntu2.1 SourcePackage: drbd8 Title: package drbd8-source 2:8.3.7-1ubuntu2.1 failed to install/upgrade: drbd8 kernel module failed to build ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 697601] [NEW] Keepalived version bump to 1.2.1
You have been subscribed to a public bug: Keepalived 1.2.x (1.2.1 is the last version) introduces support for IPv6. I'd say that this is very important to have now. ** Affects: keepalived (Ubuntu) Importance: Undecided Status: New -- Keepalived version bump to 1.2.1 https://bugs.launchpad.net/bugs/697601 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to keepalived in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 663564] Re: Don't report persistentconns as activeconns
** Branch linked: lp:ubuntu/lucid-proposed/ipvsadm -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to ipvsadm in ubuntu. https://bugs.launchpad.net/bugs/663564 Title: Don't report persistentconns as activeconns Status in “ipvsadm” package in Ubuntu: Fix Released Status in “ipvsadm” source package in Lucid: Fix Released Status in “ipvsadm” package in Debian: New Bug description: Binary package hint: ipvsadm Description:Ubuntu 10.04.1 LTS Release:10.04 ipvsadm: Installed: 1:1.25.clean-1 Candidate: 1:1.25.clean-1 Version table: *** 1:1.25.clean-1 0 500 http://apt-mirror1.us.archive.org/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status there is what appears to be a typo in the netlink client code whereby the activeconns is read as activeconns and then overwritten by persistentconns. The result is that the active connection count reported by ipvsadm -L is wrong if the code is compiled to use the netlink interface. (description taken from http://archive.linuxvirtualserver.org/html/lvs- devel/2010-02/msg6.html) the attached patch is taken from https://bugzilla.redhat.com/show_bug.cgi?id=573921 (the same patch as from the lvs-devel link but with unmangled whitespace) == SRU REPORT == === IMPACT === This patch is extremely straight forward and only affects the reporting code, so risk of crash/security problems are low. If somebody has built a workaround for the lack of active connection reporting, or if they have been assuming that the number was lower/0, the update reporting accurate numbers may cause some confusion, but that should be easy to correlate with the system updates. === DEV FIX === The code was patched and uploaded to natty in version 1:1.25.clean- 1ubuntu1 === PATCH === See merge proposal. === TEST CASE: === From redhat bug report: Steps to Reproduce: 1. Create an IPVS virtual service, something along these lines: ipvsadm -A -t this.host.ip:80 ipvsadm -a -t this.host.ip:80 -r other.host.ip:80 -m (and set up the HTTP server on other.host.ip). 2. from different host run telnet this.host.ip 80 3. run /sbin/ipvsadm -L Actual results: The ActiveConn column is zero even though there is an open connection. Expected results: The ActiveConn column should be greater than zero. === REGRESSION POTENTIAL === Very low. See IMPACT. ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 655548] Re: ocfs2console fails with python errors
** Branch linked: lp:~davewalker/ubuntu/natty/ocfs2-tools/bug_363877 -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to ocfs2-tools in ubuntu. https://bugs.launchpad.net/bugs/655548 Title: ocfs2console fails with python errors Status in “ocfs2-tools” package in Ubuntu: Triaged Bug description: Binary package hint: ocfs2-tools ocfs2console fails with deprecation warnings. Commenting warnings.filterwarnings(error) from /usr/sbin/ocfs2console is a workaround. /usr/bin/python -W ignore::DeprecationWarning will not help. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ocfs2console 1.4.3-2 [modified: usr/sbin/ocfs2console] ProcVersionSignature: Ubuntu 2.6.35-22.33-virtual 2.6.35.4 Uname: Linux 2.6.35-22-virtual i686 Architecture: i386 Date: Wed Oct 6 10:25:29 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release Candidate i386 (20100928.1) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: ocfs2-tools ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 697605] [NEW] HAProxy 1.3.23 version bump
You have been subscribed to a public bug: The last version avaiable in Lucid is 1.3.22. But 1.3.23 has loads of bugfixes, especially in regard to cookie parsing. This shouldn't be too hard as it's not a major version change. (upgrading to maverick or HAProxy 1.4.x is not an option, and most people will want to stick with the LTS release anyway). ** Affects: haproxy (Ubuntu) Importance: Undecided Status: New ** Tags: upgrade -- HAProxy 1.3.23 version bump https://bugs.launchpad.net/bugs/697605 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to haproxy in ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 655548] Re: ocfs2console fails with python errors
This bug was fixed in the package ocfs2-tools - 1.6.3-1ubuntu2 --- ocfs2-tools (1.6.3-1ubuntu2) natty; urgency=low * debian/patches/popen2-ignore-depreciation-warn.patch: Ignore the depreciation warning that importing popen2 raises, which caused the application to exit. (LP: #655548) -- Dave Walker (Daviey) davewal...@ubuntu.com Wed, 19 Jan 2011 19:23:53 + ** Changed in: ocfs2-tools (Ubuntu) Status: Triaged = Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to ocfs2-tools in ubuntu. https://bugs.launchpad.net/bugs/655548 Title: ocfs2console fails with python errors Status in “ocfs2-tools” package in Ubuntu: Fix Released Bug description: Binary package hint: ocfs2-tools ocfs2console fails with deprecation warnings. Commenting warnings.filterwarnings(error) from /usr/sbin/ocfs2console is a workaround. /usr/bin/python -W ignore::DeprecationWarning will not help. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: ocfs2console 1.4.3-2 [modified: usr/sbin/ocfs2console] ProcVersionSignature: Ubuntu 2.6.35-22.33-virtual 2.6.35.4 Uname: Linux 2.6.35-22-virtual i686 Architecture: i386 Date: Wed Oct 6 10:25:29 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release Candidate i386 (20100928.1) ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 SourcePackage: ocfs2-tools ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 671431] Re: package drbd8-source 2:8.3.7-1ubuntu2.1 failed to install/upgrade: drbd8 kernel module failed to build
[Expired for drbd8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: drbd8 (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. https://bugs.launchpad.net/bugs/671431 Title: package drbd8-source 2:8.3.7-1ubuntu2.1 failed to install/upgrade: drbd8 kernel module failed to build Status in “drbd8” package in Ubuntu: Expired Bug description: I don't know ProblemType: Package DistroRelease: Ubuntu 10.04 Package: drbd8-source 2:8.3.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Fri Nov 5 14:09:41 2010 ErrorMessage: drbd8 kernel module failed to build InstallationMedia: Ubuntu 10.04.1 LTS Lucid Lynx - Release amd64 (20100816.1) PackageArchitecture: all PackageVersion: 2:8.3.7-1ubuntu2.1 SourcePackage: drbd8 Title: package drbd8-source 2:8.3.7-1ubuntu2.1 failed to install/upgrade: drbd8 kernel module failed to build ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 702013] Re: Enable Pacemaker Support
This bug was fixed in the package redhat-cluster - 3.0.12-2ubuntu3 --- redhat-cluster (3.0.12-2ubuntu3) natty; urgency=low * Enable pacemaker support. (LP: #702013) * debian/control: Add Build-Depends on cluster-glue-dev to prevent FTBFS. -- Andres Rodriguez andres...@ubuntu.com Wed, 12 Jan 2011 11:52:45 -0600 ** Changed in: redhat-cluster (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to redhat-cluster in ubuntu. https://bugs.launchpad.net/bugs/702013 Title: Enable Pacemaker Support Status in “redhat-cluster” package in Ubuntu: Fix Released Bug description: Re=Enable pacemaker support in RHCS ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 700161] Re: Please merge cluster-glue 1.0.7-3 (main) from debian unstable (main)
This bug was fixed in the package cluster-glue - 1.0.7-3ubuntu1 --- cluster-glue (1.0.7-3ubuntu1) natty; urgency=low * Merge from debian unstable (LP: #700161). Remaining changes: - debian/control: Tighten Replaces/Conflicts to Ubuntu version. - debian/rules: Add -V argument to dh_makeshlibs. - Enable Upstart RA: + debian/cluster-glue.install: Install upstart RA. + debian/control: Build-depends on libdbus-glib-1-dev and libdbus-1-dev. + debian/patches/raexecupstart.patch: Fix deadlock -- Andres Rodriguez andres...@ubuntu.com Fri, 07 Jan 2011 18:45:39 -0500 ** Changed in: cluster-glue (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to cluster-glue in ubuntu. https://bugs.launchpad.net/bugs/700161 Title: Please merge cluster-glue 1.0.7-3 (main) from debian unstable (main) Status in “cluster-glue” package in Ubuntu: Fix Released Bug description: Binary package hint: cluster-glue cluster-glue (1.0.7-3ubuntu1) natty; urgency=low * Merge from debian unstable. Remaining changes: - debian/control: Tighten Replaces/Conflicts to Ubuntu version. - debian/rules: Add -V argument to dh_makeshlibs. - Enable Upstart RA: + debian/cluster-glue.install: Install upstart RA. + debian/control: Build-depends on libdbus-glib-1-dev and libdbus-1-dev. + debian/patches/raexecupstart.patch: Fix deadlock ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 701233] Re: Please merge pacemaker 1.0.10-4 (main) from debian unstable (main)
This bug was fixed in the package pacemaker - 1.0.10-4ubuntu1 --- pacemaker (1.0.10-4ubuntu1) natty; urgency=low * Merge from debian unstable (LP: #701233). Remaining changes: - debian/patches: + lib_license_headers_update.patch: Update the License Headers to correctly reflect the use of LGPL-2.1+. + other_license_headers_update.patch: Update the License Headers of files that show GPL version 2.1, to correctly show version 2+. + raexecupstart.patch: Utilize new upstart LRM plugin. + fix_ftbfs_linker_as_needed.patch: Prevent FTBFS due to linker changes. + fix_return_o2cb_ra.patch: Fix a return variale error in the o2cb RA. - debian/pacemaker.postinst: Fix permissions on /var/lib/pengine. * debian/control: - Bump cluster-glue dependencies to Ubuntu specific. - pacemaker-dev binary: Update dependencies to correct ones: (libpe-status2-dev,libpe-rules2-dev) - libcrmcommon2-dev: Drop Depends on cluster-glue-dev. -- Andres Rodriguez andres...@ubuntu.com Wed, 12 Jan 2011 10:12:46 -0600 ** Changed in: pacemaker (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in ubuntu. https://bugs.launchpad.net/bugs/701233 Title: Please merge pacemaker 1.0.10-4 (main) from debian unstable (main) Status in “pacemaker” package in Ubuntu: Fix Released Bug description: Binary package hint: pacemaker pacemaker (1.0.10-4ubuntu1) natty; urgency=low . * Merge from debian unstable (LP: #701233). Remaining changes: - debian/patches: + lib_license_headers_update.patch: Update the License Headers to correctly reflect the use of LGPL-2.1+. + other_license_headers_update.patch: Update the License Headers of files that show GPL version 2.1, to correctly show version 2+. + raexecupstart.patch: Utilize new upstart LRM plugin. + fix_ftbfs_linker_as_needed.patch: Prevent FTBFS due to linker changes. + fix_return_o2cb_ra.patch: Fix a return variale error in the o2cb RA. - debian/pacemaker.postinst: Fix permissions on /var/lib/pengine. * debian/control: - Bump cluster-glue dependencies to Ubuntu specific. - pacemaker-dev binary: Update dependencies to correct ones: (libpe-status2-dev,libpe-rules2-dev) ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 644562] Re: package drbd8-source 2:8.3.7-1ubuntu2.1 failed to install/upgrade: drbd8 kernel module failed to build
[Expired for drbd8 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: drbd8 (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. https://bugs.launchpad.net/bugs/644562 Title: package drbd8-source 2:8.3.7-1ubuntu2.1 failed to install/upgrade: drbd8 kernel module failed to build Status in “drbd8” package in Ubuntu: Expired Bug description: i dont know ProblemType: Package DistroRelease: Ubuntu 10.04 Package: drbd8-source 2:8.3.7-1ubuntu2.1 ProcVersionSignature: Ubuntu 2.6.32-25.44-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic x86_64 Architecture: amd64 Date: Mon Sep 20 21:55:25 2010 ErrorMessage: drbd8 kernel module failed to build InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release amd64 (20100429) PackageArchitecture: all PackageVersion: 2:8.3.7-1ubuntu2.1 SourcePackage: drbd8 Title: package drbd8-source 2:8.3.7-1ubuntu2.1 failed to install/upgrade: drbd8 kernel module failed to build ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 687975] Re: [FTBFS] package 'heartbeat' (1:3.0.3-2) failed to build on natty
This bug was fixed in the package heartbeat - 1:3.0.3-2ubuntu1 --- heartbeat (1:3.0.3-2ubuntu1) natty; urgency=low * debian/patches/ftbfs_no_as_needed.patch: Fix FTBFS (LP: #687975). -- Andres Rodriguez andres...@ubuntu.com Thu, 09 Dec 2010 14:09:59 -0500 ** Changed in: heartbeat (Ubuntu) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to heartbeat in ubuntu. https://bugs.launchpad.net/bugs/687975 Title: [FTBFS] package 'heartbeat' (1:3.0.3-2) failed to build on natty Status in “heartbeat” package in Ubuntu: Fix Released Bug description: When attempting to rebuild the source package of 'heartbeat' version '1:3.0.3-2' it failed to produce the expected binaries ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 663564] Re: Don't report persistentconns as activeconns
** Branch linked: lp:~clint-fewbar/ubuntu/lucid/ipvsadm/fix-activeconns- report -- Don't report persistentconns as activeconns https://bugs.launchpad.net/bugs/663564 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to ipvsadm in ubuntu. Status in “ipvsadm” package in Ubuntu: Fix Released Status in “ipvsadm” source package in Lucid: Triaged Status in “ipvsadm” package in Debian: New Bug description: Binary package hint: ipvsadm Description:Ubuntu 10.04.1 LTS Release:10.04 ipvsadm: Installed: 1:1.25.clean-1 Candidate: 1:1.25.clean-1 Version table: *** 1:1.25.clean-1 0 500 http://apt-mirror1.us.archive.org/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status there is what appears to be a typo in the netlink client code whereby the activeconns is read as activeconns and then overwritten by persistentconns. The result is that the active connection count reported by ipvsadm -L is wrong if the code is compiled to use the netlink interface. (description taken from http://archive.linuxvirtualserver.org/html/lvs-devel/2010-02/msg6.html) the attached patch is taken from https://bugzilla.redhat.com/show_bug.cgi?id=573921 (the same patch as from the lvs-devel link but with unmangled whitespace) ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 663564] Re: Don't report persistentconns as activeconns
This bug was fixed in the package ipvsadm - 1:1.25.clean-1ubuntu1 --- ipvsadm (1:1.25.clean-1ubuntu1) natty; urgency=low * libipvs/libipvs.c: upstream patch (r64) to fix incorrect activeconns, (Debian bug 574587), (LP: #663564) -- Clint Byrum cl...@ubuntu.com Tue, 16 Nov 2010 15:25:39 -0800 ** Branch linked: lp:ubuntu/ipvsadm ** Changed in: ipvsadm (Ubuntu) Status: In Progress = Fix Released -- Don't report persistentconns as activeconns https://bugs.launchpad.net/bugs/663564 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to ipvsadm in ubuntu. Status in “ipvsadm” package in Ubuntu: Fix Released Status in “ipvsadm” source package in Lucid: Triaged Status in “ipvsadm” package in Debian: New Bug description: Binary package hint: ipvsadm Description:Ubuntu 10.04.1 LTS Release:10.04 ipvsadm: Installed: 1:1.25.clean-1 Candidate: 1:1.25.clean-1 Version table: *** 1:1.25.clean-1 0 500 http://apt-mirror1.us.archive.org/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status there is what appears to be a typo in the netlink client code whereby the activeconns is read as activeconns and then overwritten by persistentconns. The result is that the active connection count reported by ipvsadm -L is wrong if the code is compiled to use the netlink interface. (description taken from http://archive.linuxvirtualserver.org/html/lvs-devel/2010-02/msg6.html) the attached patch is taken from https://bugzilla.redhat.com/show_bug.cgi?id=573921 (the same patch as from the lvs-devel link but with unmangled whitespace) ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 663564] Re: Don't report persistentconns as activeconns
** Branch linked: lp:~clint-fewbar/ubuntu/natty/ipvsadm/fix-activeconns- report -- Don't report persistentconns as activeconns https://bugs.launchpad.net/bugs/663564 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to ipvsadm in ubuntu. Status in “ipvsadm” package in Ubuntu: Triaged Status in “ipvsadm” source package in Lucid: Triaged Status in “ipvsadm” package in Debian: Unknown Bug description: Binary package hint: ipvsadm Description:Ubuntu 10.04.1 LTS Release:10.04 ipvsadm: Installed: 1:1.25.clean-1 Candidate: 1:1.25.clean-1 Version table: *** 1:1.25.clean-1 0 500 http://apt-mirror1.us.archive.org/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status there is what appears to be a typo in the netlink client code whereby the activeconns is read as activeconns and then overwritten by persistentconns. The result is that the active connection count reported by ipvsadm -L is wrong if the code is compiled to use the netlink interface. (description taken from http://archive.linuxvirtualserver.org/html/lvs-devel/2010-02/msg6.html) the attached patch is taken from https://bugzilla.redhat.com/show_bug.cgi?id=573921 (the same patch as from the lvs-devel link but with unmangled whitespace) ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 666494] Re: Data Corruption bug in GlusterFS 3.0.2
** Branch linked: lp:ubuntu/lucid-proposed/glusterfs -- Data Corruption bug in GlusterFS 3.0.2 https://bugs.launchpad.net/bugs/666494 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to glusterfs in ubuntu. Status in Gluster: Fix Released Status in “glusterfs” package in Ubuntu: Fix Released Status in “glusterfs” source package in Lucid: Fix Committed Bug description: Impact: data corruption when using GlusterFS with certain options set. Patch: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/666494/+attachment/1711751/+files/glusterfs_3.0.2-1ubuntu1.debdiff Reproducing: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=639 Regression potential: none known As an interim fix I did a backport of GlusterFS 3.0.4 from Maverick to Lucid https://launchpad.net/~nutznboltz/+archive/glusterfs3 so my systems are safe. This is the upstream Changelog message: commit c55134fc0c5ebe952de12757d5c53d463a9c21b5 Author: Anand Avati av...@gluster.com Date: Thu Feb 18 10:28:06 2010 + server_writev: add proper iobuf into iobref this typo results in corruption when write-behind is loaded on server side Signed-off-by: Anand V. Avati av...@blackhole.gluster.com Signed-off-by: Anand V. Avati av...@dev.gluster.com BUG: 639 (Data corruption with write-behind on server side) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=639 ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: glusterfs-server (not installed) ProcVersionSignature: Ubuntu 2.6.32-25.45-generic 2.6.32.21+drm33.7 Uname: Linux 2.6.32-25-generic i686 Architecture: i386 Date: Mon Oct 25 16:24:24 2010 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100427.1) ProcEnviron: LANG=en_US.utf8 SHELL=/bin/bash SourcePackage: glusterfs ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 627174] Re: SRU: package drbd8-utils (not installed) failed to install/upgrade: trying to overwrite '/usr/share/cluster/drbd.sh', which is also in package rgmanager 0:3.0.2-2ubuntu3
This bug was fixed in the package redhat-cluster - 3.0.2-2ubuntu3.1 --- redhat-cluster (3.0.2-2ubuntu3.1) lucid-proposed; urgency=low * SRUs: - debian/liblogthread-dev: Install missing pkg-config file (LP: #627291) - debian/rules: Remove drbd.sh and drbd.metadata because DRBD already ships them. (LP: #627174) -- Andres Rodriguez andres...@ubuntu.com Wed, 20 Oct 2010 12:44:43 -0400 ** Changed in: redhat-cluster (Ubuntu Lucid) Status: Fix Committed = Fix Released -- SRU: package drbd8-utils (not installed) failed to install/upgrade: trying to overwrite '/usr/share/cluster/drbd.sh', which is also in package rgmanager 0:3.0.2-2ubuntu3 https://bugs.launchpad.net/bugs/627174 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. Status in “drbd8” package in Ubuntu: Invalid Status in “redhat-cluster” package in Ubuntu: Fix Released Status in “drbd8” source package in Lucid: Invalid Status in “redhat-cluster” source package in Lucid: Fix Released Bug description: drbd8-utils fails to install when rgmanager is installed. rgmanager is shipping two shell scripts that are also shipped with drbd8. The fix is to not install such scripts with rgmanager in redhat-cluster source package. The error is detailed bellow: ProblemType: Package DistroRelease: Ubuntu 10.04 Package: drbd8-utils (not installed) ProcVersionSignature: Ubuntu 2.6.32-24.42-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-24-generic i686 Architecture: i386 Date: Tue Aug 31 10:14:06 2010 ErrorMessage: trying to overwrite '/usr/share/cluster/drbd.sh', which is also in package rgmanager 0:3.0.2-2ubuntu3 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) SourcePackage: drbd8 Title: package drbd8-utils (not installed) failed to install/upgrade: trying to overwrite '/usr/share/cluster/drbd.sh', which is also in package rgmanager 0:3.0.2-2ubuntu3 TEST CASE: - Install rgmanager. - Install drbd8-utils. - You will see how drbd8-utils will fail to install as detailed above. Once the proposed fix is applied, drbd8-utils will install correctly. ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 668818] Re: Please merge keepalived 1:1.1.20-1 (main) from debian unstable (main)
This bug was fixed in the package keepalived - 1:1.1.20-1ubuntu1 --- keepalived (1:1.1.20-1ubuntu1) natty; urgency=low * Merge from debian unstable (LP: #668818), remaining changes: - debian/rules: DEB_UPDATE_RCD_PARAMS := expicit init start/stop parameters (don't stop at 0 and 6) - debian/init.d: init script header adapted to stop rule - debian/keepalived.postinst: Remove shutdown and reboot links keepalived (1:1.1.20-1) unstable; urgency=low * Go back to 1.1.20 since 1.2.0 is not ready for release * Bump standards version (no changes) keepalived (1.2.0-1) unstable; urgency=low * New upstream release (Closes: #580607) * Bump standards version (no changes) keepalived (1.1.20-1) unstable; urgency=low * New upstream release (Closes: #580607) * Bump standards version (no changes) * Raise debhelper dep to v5 * Refresh 95_use_linux_ip_vs_h.patch * Fix typo in description * Declare debsource v1.0 * Fix restart if daemon doesn't run (Closes: #561357) keepalived (1.1.19-1) unstable; urgency=low * New upstream version (Closes: #557814, #548254) - Fix gigabit status interface support (Closes: #555634) * Fix error reporting and manpage of genhash (Closes: #575399) -- Lorenzo De Liso bla...@ubuntu.com Sat, 30 Oct 2010 20:01:07 +0200 ** Changed in: keepalived (Ubuntu) Status: New = Fix Released -- Please merge keepalived 1:1.1.20-1 (main) from debian unstable (main) https://bugs.launchpad.net/bugs/668818 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to keepalived in ubuntu. Status in “keepalived” package in Ubuntu: Fix Released Bug description: Binary package hint: keepalived keepalived (1:1.1.20-1) unstable; urgency=low * Go back to 1.1.20 since 1.2.0 is not ready for release * Bump standards version (no changes) -- Alexander Wirt formo...@debian.org Sat, 14 Aug 2010 10:17:10 +0200 keepalived (1.2.0-1) unstable; urgency=low * New upstream release (Closes: #580607) * Bump standards version (no changes) -- Alexander Wirt formo...@debian.org Sun, 04 Jul 2010 11:02:13 +0200 keepalived (1.1.20-1) unstable; urgency=low * New upstream release (Closes: #580607) * Bump standards version (no changes) * Raise debhelper dep to v5 * Refresh 95_use_linux_ip_vs_h.patch * Fix typo in description * Declare debsource v1.0 * Fix restart if daemon doesn't run (Closes: #561357) -- Alexander Wirt formo...@debian.org Sat, 08 May 2010 20:56:58 +0200 keepalived (1.1.19-1) unstable; urgency=low * New upstream version (Closes: #557814, #548254) - Fix gigabit status interface support (Closes: #555634) * Fix error reporting and manpage of genhash (Closes: #575399) -- Alexander Wirt formo...@debian.org Fri, 23 Apr 2010 13:17:53 +0200 ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 627291] Re: liblogthread-dev is missing pkg-config file
** Branch linked: lp:ubuntu/lucid-proposed/redhat-cluster -- liblogthread-dev is missing pkg-config file https://bugs.launchpad.net/bugs/627291 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to redhat-cluster in ubuntu. Status in “redhat-cluster” package in Ubuntu: Fix Released Status in “redhat-cluster” source package in Lucid: Fix Committed Bug description: liblogthread-dev should contain a pkg-config description, /usr/lib/pkgconfig/liblogthread.pc. The upstream Debian package, version 3.0.12-2 has this file. It is absent from the current Ubuntu version, 3.0.2-2ubuntu3. This breaks the build process for any packages using liblogthread functionality in conjunction with pkg-config. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: liblogthread-dev 3.0.2-2ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-23.37-generic 2.6.32.15+drm33.5 Uname: Linux 2.6.32-23-generic x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue Aug 31 10:57:36 2010 SourcePackage: redhat-cluster ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 659510] Re: Upstart Resource Agent Plugin is not installed
** Branch linked: lp:ubuntu/maverick-proposed/cluster-glue -- Upstart Resource Agent Plugin is not installed https://bugs.launchpad.net/bugs/659510 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to cluster-glue in ubuntu. Status in “cluster-glue” package in Ubuntu: Confirmed Status in “cluster-glue” source package in Maverick: Fix Committed Bug description: Binary package hint: cluster-glue Cluster Glue's Upstart Resource Agent is being built in the package, however, it is not being installed causing Pacemaker not to recognize resources configured to use this resource agent. This is currently affecting the Cluster Stack in Maverick, which is breaking the possibility of managing resources that use upstart scripts. TEST CASE: - Install an Standalone cluster at as specified at [1]. - Once installed, try to configure a resource using the Upstart Resource Agent: sudo crm configure primitive mysql upstart:mysql And you will see the following error: crm(live)configure# primitive mysql upstart:mysql ERROR: upstart:mysql: could not parse meta-data: ERROR: upstart:mysql: no such resource agent [1]: https://wiki.ubuntu.com/ClusterStack/LucidTesting#Pacemaker, standalone Once the proposed fix is applied, Pacemaker will recognize the Upstart RA and the configuration will be successful. I have personally tested this fix and everything works as expected. Build logs can be found at: https://launchpad.net/~andreserl/+archive/ha/+build/1995468/+files/buildlog_ubuntu-maverick-i386.cluster-glue_1.0.6-1ubuntu1.1_BUILDING.txt.gz ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 585468] Re: /usr/lib/stonith/plugins/external/sbd works uses wrong shell commands
** Branch linked: lp:ubuntu/lucid-proposed/cluster-glue -- /usr/lib/stonith/plugins/external/sbd works uses wrong shell commands https://bugs.launchpad.net/bugs/585468 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to cluster-glue in ubuntu. Status in “cluster-glue” package in Ubuntu: Fix Released Status in “cluster-glue” source package in Lucid: Fix Committed Bug description: Binary package hint: cluster-glue /usr/lib/stonith/plugins/external/sbd uses ha_log as shell command which is now ha_logger also the nodes=$( if is_heartbeat; then crm_node -H -p else crm_node -p fi) lines are nor working. fix is: if is_heartbeat; then nodes=$(crm_node -H -p) else nodes=$(crm_node -p) fi source: http://www.gossamer-threads.com/lists/linuxha/pacemaker/63969 patch: 28c28 ha_log err sbd could not list nodes from $sbd_device --- ha_logger err sbd could not list nodes from $sbd_device 31d30 nodes=$( 33c32 crm_node -H -p --- nodes=$(crm_node -H -p) 35,36c34,36 crm_node -p fi) --- nodes=$(crm_node -p) fi 39c39 ha_log warn no active nodes reported by the CRM --- ha_logger warn no active nodes reported by the CRM 44c44 ha_log err node $N not accessible through $sbd_device --- ha_logger err node $N not accessible through $sbd_device PLEASE TEST SRU IN lucid-proposed The Stable Release update meant to fix this bug ha been uploaded to the lucid-proposed repository. Please test the latest version of this package (1.0.5-1ubuntu0.1) in the proposed repository, using the instructions described on this page: https://wiki.ubuntu.com/Testing/EnableProposed After testing, please comment on this bug if the package fixes the bug well and if it causes any regressions or not. ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 607835] Re: New Upstream Release DRBD 8.3.8.1
This bug was fixed in the package drbd8 - 2:8.3.8.1-0ubuntu1 --- drbd8 (2:8.3.8.1-0ubuntu1) maverick; urgency=low * New upstream release (LP: #607835) * DRBD Kernel Module is now in mainline Kernel. Related changes: - debian/control: + Comment out drbd8-source package. + Drop Depends on drbd8-source for drbd8-utils package. - debian/rules: Comment rules related to -source package installation. * debian/patches/01_ubuntu_cn_idx.dpatch: Update CN_IDX to 0x8. -- Andres Rodriguez andres...@ubuntu.com Tue, 20 Jul 2010 12:01:03 -0400 ** Changed in: drbd8 (Ubuntu) Status: In Progress = Fix Released -- New Upstream Release DRBD 8.3.8.1 https://bugs.launchpad.net/bugs/607835 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. Status in “drbd8” package in Ubuntu: Fix Released Bug description: The DRBD Kernel module has been included to mainline starting from kernel 2.6.33. Related changes: rbd8 (2:8.3.8.1-0ubuntu1) maverick; urgency=low * New upstream release * DRBD Kernel Module is now in mainline Kernel. Related changes: - debian/control: + Comment out drbd8-source package. + Drop Depends on drbd8-source for drbd8-utils package. - debian/rules: Comment rules related to -source package installation. * debian/patches/01_ubuntu_cn_idx.dpatch: Update CN_IDX to 0x8. The Module included in the Maverick kernel (2.6.35) is DRBD 8.3.8. The new upstream changes are detailed as follows: 8.3.8.1 (api:88/proto:86-94) * Revert delay probes, they could potentially lead to stalled resync. Feature is being re-implemented differently * DRBD ocf resource agent now treats hostnames case insensitive 8.3.8 (api:88/proto:86-94) * Do not expose failed local READs to upper layers, regression introduced in 8.3.3 * Fixed support for devices with 4k hard sector size (again) * Fixed a potential Oops in the disconnect code * Fixed a race condition that could cause DRBD to consider the peers disk as Inconstent after resync instead of UpToDate (Bugz 271) * Fixed a reace condition that could cause DRBD to consider the peers disk as Outdated instead of Inconsistent during resync (Bugz 277) * Disallow to start a resync with invalidate / invalidate-remote when the source disk is not UpToDate * Forcing primary works now also for Consistent, not only for Outdated and Inconsistent (Bugz 266) * Improved robustness against corrupt or malicous sector addresses when receiving data * Added the initial-split-brain, it gets called also if the split-brain gets automatically resolved * Added the --assume-clean option for the resize command, it causes drbd to not resync the new storage after an online grow operation * drbdadm: Do not segfault if stacked-on-top-of refers to an undefined res * drbdadm: Do not consider configs with invalid after statements as invalid * drbdadm: Do not segfault if the peer's proxy section is missing * drbdadm: Allow nullglob in include statement * drbdadm: Fixed the use of waitpid * init script: fix insserv headers (Debian 576901) * Gave the receiving code the ability to use multiple BIOs for writing a single data packet; now DRBD works with BIOs up to 32kByte also on LVM devices; from now on the use_bmbv config option does nothing * New command check-resize, that allows DRBD to detect offline resizing and to move internal meta-data accordingly * Added a control loop, that allows DRBD to find auto tune the resync speed, on connections with large queues (drbd-proxy) * --dry-run option for connect; disconnects after sync handshake * --overwrite-data-of-peer got an alias named --force * Improvements to crm-fence-peer * Fixed option parsing and stacking in snapshot-resync-target-lvm.sh * Compiles on 2.6.33 and 2.6.34 I've personally tested the new package and it works as expected. Build logs can be found here: amd64: http://launchpadlibrarian.net/52140584/buildlog_ubuntu-maverick-amd64.drbd8_2:8.3.8.1-0ubuntu1~ppa1_FULLYBUILT.txt.gz i386: http://launchpadlibrarian.net/52130223/buildlog_ubuntu-maverick-i386.drbd8_2:8.3.8.1-0ubuntu1~ppa1_FULLYBUILT.txt.gz ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 604413] Re: Merge pacemaker 1.0.9.1 (universe) from debian unstable (main)
This bug was fixed in the package pacemaker - 1.0.9.1-1ubuntu1 --- pacemaker (1.0.9.1-1ubuntu1) maverick; urgency=low * Merge from debian unstable (LP: #604413). Remaining changes: - debian/control: Drop unnecessary Build-Depends on python-dev. - debian/pacemaker.postinst: fix permissions on /var/lib/pengine. pacemaker (1.0.9.1-1) unstable; urgency=low * New Upstream -- Andres Rodriguez andres...@ubuntu.com Sun, 11 Jul 2010 20:11:42 -0400 ** Changed in: pacemaker (Ubuntu) Status: In Progress = Fix Released -- Merge pacemaker 1.0.9.1 (universe) from debian unstable (main) https://bugs.launchpad.net/bugs/604413 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in ubuntu. Status in “pacemaker” package in Ubuntu: Fix Released Bug description: Binary package hint: pacemaker pacemaker (1.0.9.1-1) unstable; urgency=low . * New Upstream ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 591006] Re: [MIR] haproxy
** Branch linked: lp:~clint-fewbar/ubuntu-seeds/add-haproxy -- [MIR] haproxy https://bugs.launchpad.net/bugs/591006 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to haproxy in ubuntu. Status in “haproxy” package in Ubuntu: In Progress Bug description: Binary package hint: haproxy Availability: Package has been in universe since Hardy. Rationale: * HAProxy is considered to be one of the best app level load balancers available. * MIR is marked as a requirement for maverick alpha2 in https://blueprints.launchpad.net/ubuntu/+spec/server-maverick-uds-cloud-loadbalancing Security: * No CVE's or vulnerabilities listed in the usual place. Further searches turn up no previous security problems. * Disabled by default, must be enabled by editing /etc/default/haproxy. * The ports opened in the default configuration are 10001 thru 10005, and 8443. On connecting to those ports, these attempt to connect to non-routable IP's of backend servers that may or may not exist, so this config file may need to be moved to an examples directory. Quality assurance: * There are no important bug reports against haproxy in Debian or Ubuntu * The debian package has been well maintained and has stayed quite close to upstream. UI standards: (generally only for user-facing applications) N/A Dependencies: * All are in main. Standards compliance: * Packaging is very straight forward and package appears to comply with policy upon cursory examination. Maintenance: * Package produces a single binary package, that includes a single binary, a daemon that uses a single config file. Background information: HAProxy is quite mature, as is its debian package. ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 600900] Re: Please merge corosync 1.2.1-1 (main) from debian unstable (main)
This bug was fixed in the package corosync - 1.2.1-1ubuntu1
---
corosync (1.2.1-1ubuntu1) maverick; urgency=low
* Merge from debian unstable (LP: #600900). Remaining changes:
- Raised consensus time out to 5000ms
- debian/control, debian/rules: Removing now-unnecessary quilt build-dep
corosync (1.2.1-1) unstable; urgency=low
* [c254474] Bump standards version
* [d4bd86b] Add ${misc:Depends} dependencies
* [cef00bb] Upstream changed the login - fix watch file
* [6e03508] Imported Upstream version 1.2.1
corosync (1.2.0-3) unstable; urgency=low
* [3c2ff0a] Use passive ftp for uscan
* [fb2678a] Fix typo in dependencies that breaks the autobuild (Closes:
#573676)
* [81e5a81] corosync-dbg: dependency on corosync or libcorosync4 so the
library can be debugged without corosync installed.
corosync (1.2.0-2) unstable; urgency=low
* [e6d54e6] Make sure /var/log/corosync/ is nonempty otherwise removing
corosync also removes this dir which makes logrotate choke. A purge
cleans up the log files anyway.
corosync (1.2.0-1) unstable; urgency=low
* [0538e91] Imported Upstream version 1.2.0
-- Andres Rodriguez andres...@ubuntu.com Fri, 02 Jul 2010 01:24:53 -0400
** Changed in: corosync (Ubuntu)
Status: Confirmed = Fix Released
--
Please merge corosync 1.2.1-1 (main) from debian unstable (main)
https://bugs.launchpad.net/bugs/600900
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to corosync in ubuntu.
Status in “corosync” package in Ubuntu: Fix Released
Bug description:
Binary package hint: corosync
corosync (1.2.1-1) unstable; urgency=low
.
* [c254474] Bump standards version
* [d4bd86b] Add ${misc:Depends} dependencies
* [cef00bb] Upstream changed the login - fix watch file
* [6e03508] Imported Upstream version 1.2.1
.
corosync (1.2.0-3) unstable; urgency=low
.
* [3c2ff0a] Use passive ftp for uscan
* [fb2678a] Fix typo in dependencies that breaks the autobuild (Closes:
#573676)
* [81e5a81] corosync-dbg: dependency on corosync or libcorosync4 so the
library can be debugged without corosync installed.
.
corosync (1.2.0-2) unstable; urgency=low
.
* [e6d54e6] Make sure /var/log/corosync/ is nonempty otherwise removing
corosync also removes this dir which makes logrotate choke. A purge
cleans up the log files anyway.
.
corosync (1.2.0-1) unstable; urgency=low
.
* [0538e91] Imported Upstream version 1.2.0
___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 562832] Re: [SRU] module drbd8 update kernel from 2.6.32-16 to 2.6.32-20
This bug was fixed in the package drbd8 - 2:8.3.7-1ubuntu2.1 --- drbd8 (2:8.3.7-1ubuntu2.1) lucid-proposed; urgency=low * Use KDIR instead of KERNELDIR variable for headers path - thanks Gaëtan Ferez for debugging - (LP: #562832) -- Ante Karamatic iv...@ubuntu.com Mon, 19 May 2010 09:22:17 +0200 ** Changed in: drbd8 (Ubuntu Lucid) Status: Fix Committed = Fix Released -- [SRU] module drbd8 update kernel from 2.6.32-16 to 2.6.32-20 https://bugs.launchpad.net/bugs/562832 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. Status in “dkms” package in Ubuntu: Confirmed Status in “drbd8” package in Ubuntu: Fix Released Status in “dkms” source package in Lucid: Won't Fix Status in “drbd8” source package in Lucid: Fix Released Bug description: I have installed drbd8-utils on Ubuntu Lucid 10.04 beta 1. After updating the kernel to 2.6.32-20-generic, the module drbd can't be loaded. I have an error during the load : FATAL: Error inserting drbd (/lib/modules/2.6.32-20-generic/updates/dkms/drbd.ko): Invalid module format Dmesg : [ 190.376039] drbd: disagrees about version of symbol module_layout When i update the kernel, i can just see in the log : ubuntu-laptop dkms_autoinstaller: drbd8 (8.3.7): Installing module on kernel 2.6.32-20-generic. I think that the problem results from dkms program ProblemType: Bug Architecture: i386 Date: Wed Apr 14 09:47:41 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318) Package: drbd8-utils 2:8.3.7-1ubuntu1 ProcEnviron: LANG=fr_FR.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2 SourcePackage: drbd8 Uname: Linux 2.6.32-20-generic i686 ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 562832] Re: [SRU] module drbd8 update kernel from 2.6.32-16 to 2.6.32-20
** Branch linked: lp:ubuntu/lucid-proposed/drbd8 -- [SRU] module drbd8 update kernel from 2.6.32-16 to 2.6.32-20 https://bugs.launchpad.net/bugs/562832 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. Status in “dkms” package in Ubuntu: Confirmed Status in “drbd8” package in Ubuntu: In Progress Status in “dkms” source package in Lucid: Won't Fix Status in “drbd8” source package in Lucid: Fix Committed Bug description: I have installed drbd8-utils on Ubuntu Lucid 10.04 beta 1. After updating the kernel to 2.6.32-20-generic, the module drbd can't be loaded. I have an error during the load : FATAL: Error inserting drbd (/lib/modules/2.6.32-20-generic/updates/dkms/drbd.ko): Invalid module format Dmesg : [ 190.376039] drbd: disagrees about version of symbol module_layout When i update the kernel, i can just see in the log : ubuntu-laptop dkms_autoinstaller: drbd8 (8.3.7): Installing module on kernel 2.6.32-20-generic. I think that the problem results from dkms program ProblemType: Bug Architecture: i386 Date: Wed Apr 14 09:47:41 2010 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 Lucid Lynx - Beta i386 (20100318) Package: drbd8-utils 2:8.3.7-1ubuntu1 ProcEnviron: LANG=fr_FR.utf8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-20.30-generic 2.6.32.11+drm33.2 SourcePackage: drbd8 Uname: Linux 2.6.32-20-generic i686 ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 530945] Re: [SRU] keepalived in karmic
This bug was fixed in the package keepalived - 1.1.17-1ubuntu1.1 --- keepalived (1.1.17-1ubuntu1.1) karmic-proposed; urgency=low * SRU: Add 95_use_linux_ip_vs_h.patch to fix missing IPVS support. (LP: #496932, LP: #530945) -- Andres Rodriguez andres...@ubuntu.com Wed, 03 Mar 2010 11:38:02 -0500 ** Changed in: keepalived (Ubuntu Karmic) Status: Fix Committed = Fix Released -- [SRU] keepalived in karmic https://bugs.launchpad.net/bugs/530945 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to keepalived in ubuntu. Status in “keepalived” package in Ubuntu: Fix Released Status in “keepalived” source package in Karmic: Fix Released Bug description: Binary package hint: keepalived 1. The reason behind this is because keepalived 1.1.17-1 in karmic does not have IPVS support, which is a regression from Jaunty. So this SRU is needed to re-enable IPVS support in karmic. See [1] 2. The related bug and [1], have been already fixed in both Debian and Ubuntu Lucid by applying the same patch. 3. To reproduce please follow [1]. I've personally tested the before and after the fix and can confirm that this fix works as expected. [1]: https://bugs.launchpad.net/ubuntu/+source/keepalived/+bug/496932 Build logs can be found: http://launchpadlibrarian.net/40094086/buildlog_ubuntu-karmic-amd64.keepalived_1.1.17-1ubuntu1.1_FULLYBUILT.txt.gz http://launchpadlibrarian.net/40094175/buildlog_ubuntu-karmic-i386.keepalived_1.1.17-1ubuntu1.1_BUILDING.txt.gz http://launchpadlibrarian.net/40094654/buildlog_ubuntu-karmic-lpia.keepalived_1.1.17-1ubuntu1.1_BUILDING.txt.gz ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 562709] Re: [FFe] Please sync cluster-glue 1.0.3+hg2366-5 (universe) from debian (unstable)
This bug was fixed in the package cluster-glue - 1.0.3+hg2366-5ubuntu1
---
cluster-glue (1.0.3+hg2366-5ubuntu1) lucid; urgency=low
* Sync from debian unstable (LP: #562709).
* debian/control: Remove depends on hard coded perl modules
for cluster-glue.
-- Andres Rodriguez andres...@ubuntu.com Wed, 14 Apr 2010 00:08:56 -0400
** Changed in: cluster-glue (Ubuntu)
Status: New = Fix Released
--
[FFe] Please sync cluster-glue 1.0.3+hg2366-5 (universe) from debian (unstable)
https://bugs.launchpad.net/bugs/562709
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to cluster-glue in ubuntu.
Status in “cluster-glue” package in Ubuntu: Fix Released
Bug description:
Binary package hint: cluster-glue
Please sync cluster-glue from debian unstable:
cluster-glue (1.0.3+hg2366-5) unstable; urgency=low
* Rebuild and do NOT include the .orig.tar.gz in the .changes-file.
Wasn't this default until some time ago?!
-- Martin Loschwitz madk...@debian.org Tue, 06 Apr 2010 15:20:30 +
cluster-glue (1.0.3+hg2366-4) unstable; urgency=low
* Disable fatal warnings to make cluster-glue compile on numerous
architectures other than x86(_64)
-- Martin Loschwitz madk...@debian.org Tue, 06 Apr 2010 13:08:01 +
cluster-glue (1.0.3+hg2366-3) unstable; urgency=low
* Added files to cluster-glue.install that were added upstream
-- Martin Loschwitz madk...@debian.org Tue, 30 Mar 2010 11:03:34 +
cluster-glue (1.0.3+hg2366-2) unstable; urgency=low
* Include patch by Simon Hormann to Replaces/Conflicts
-- Martin Loschwitz madk...@debian.org Tue, 30 Mar 2010 07:04:53 +
cluster-glue (1.0.3+hg2366-1) unstable; urgency=low
* New upstream checkout.
* Updated debian/copyright to reflect the current situation
* Remove useless STYLESHEET_PREFIX patch from debian/patches
-- Martin Loschwitz madk...@debian.org Tue, 30 Mar 2010 06:28:50 +
cluster-glue (1.0.3+hg2365-1) unstable; urgency=low
* New upstream checkout.
* Move lintian overides from cluster-glue to libcluster-glue.
-- Frederik Schüler f...@debian.org Fri, 12 Mar 2010 12:36:56 +0100
cluster-glue (1.0.3+hg2337-2) unstable; urgency=low
* Add libcluster-glue{-dev}.install files, and actually install libraries.
-- Frederik Schüler f...@debian.org Tue, 09 Mar 2010 13:12:04 +0100
cluster-glue (1.0.3+hg2337-1) unstable; urgency=low
[ Martin G. Loschwitz ]
* Replaced the copyright-file with the one updated by Ante Karamatic
* Split cluster-glue into libcluster-glue{-dev} and cluster-glue{-dev}
-- Martin Loschwitz madk...@debian.org Wed, 02 Mar 2010 13:02:00 +0100
cluster-glue (1.0.3-2) UNRELEASED; urgency=low
[ Simon Horman ]
* Do not do a binary-indep build as there is nothing to do.
* Build-Depend on libsensors4-dev | libsensors-dev.
[ Frederik Schüler ]
* Bump standards to version 3.8.4, no changes needed.
* Switch to source version 3.0 quilt.
* Switch to debian compatibility level 7.
* Drop dpatch.
* Add misc-depends to cluster-glue-dev.
* Add linian overrides.
* Remove rpath from ipmilan.so.
-- Frederik Schüler f...@debian.org Fri, 26 Feb 2010 19:39:13 +0100
cluster-glue (1.0.3-1) unstable; urgency=low
* New upstream release.
-- Martin Loschwitz madk...@debian.org Wed, 03 Feb 2010 08:05:00 +0100
The Ubuntu Cluster Stack [1] packages have been updated with the latest
versions. This new packages contain various fixes in both upstream and
packaging that we need in Ubuntu. These packages contain some of the Ubuntu
changes already, however, some others have not yet reached the packages but are
in the debian-ha mercurial repositories.
Build logs can be found in:
http://launchpadlibrarian.net/44107565/buildlog_ubuntu-lucid-amd64.cluster-glue_1.0.3%2Bhg2366-5ubuntu1_FULLYBUILT.txt.gz
http://launchpadlibrarian.net/44104633/buildlog_ubuntu-lucid-i386.cluster-glue_1.0.3%2Bhg2366-5ubuntu1_FULLYBUILT.txt.gz
[1]: https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-cluster-stack
___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 562711] Re: [FFe] Please sync heartbeat 1:3.0.2+hg12555-2 (universe) from debian (unstable)
This bug was fixed in the package heartbeat - 1:3.0.2+hg12555-2ubuntu1
---
heartbeat (1:3.0.2+hg12555-2ubuntu1) lucid; urgency=low
* Sync from debian unstable (LP: #562711).
* debian/control: Remove duplicated uuid-dev Build-Depends.
* debian/rules: Add '--disable-fatal-warnings' to configure.
-- Andres Rodriguez andres...@ubuntu.com Wed, 14 Apr 2010 00:21:06 -0400
** Changed in: heartbeat (Ubuntu)
Status: New = Fix Released
--
[FFe] Please sync heartbeat 1:3.0.2+hg12555-2 (universe) from debian (unstable)
https://bugs.launchpad.net/bugs/562711
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to heartbeat in ubuntu.
Status in “heartbeat” package in Ubuntu: Fix Released
Bug description:
Binary package hint: heartbeat
Please sync heartbeat from debian unstable:
heartbeat (1:3.0.2+hg12555-2) unstable; urgency=low
* Removed 01_docbook_path.dpatch from debian/patches as it's useless
-- Martin Loschwitz madk...@debian.org Tue, 30 Mar 2010 11:08:39 +
heartbeat (1:3.0.2+hg12555-1) unstable; urgency=low
* New Mercurial checkout
* Adopt patch by Florian Haas to delete libnet build dependency
-- Martin Loschwitz madk...@debian.org Tue, 30 Mar 2010 07:40:29 +
heartbeat (1:3.0.2+hg12547-2) unstable; urgency=low
[ Martin Loschwitz ]
* Re-add dh_installinit but delete heartbeat.init
* Deleted some ancient files from debian-subdirectory
-- Martin Loschwitz madk...@debian.org Wed, 03 Mar 2010 08:49:00 +0100
heartbeat (1:3.0.2+hg12547-1) unstable; urgency=low
[ Martin Loschwitz ]
* Update to latest HG version
* New copyright-file by Ante Karamatic
* Use heartbeat standard init script instead of the old one
-- Martin Loschwitz madk...@debian.org Tue, 02 Mar 2010 17:11:00 +0100
heartbeat (1:3.0.2-2) UNRELEASED; urgency=low
[ Simon Horman ]
* Build-depend on libsensors4-dev | libsensors-dev.
* remove ldconfig from heartbeat.{postrm,postinst}.
[ Frederik Schüler ]
* Add myself to uploaders.
* Drop duplicate priority and section fields from debian/control.
* Bump standards version to 3.8.4, no changes needed.
* Switch to debhelper 7.
* Switch to source version 3.0 quilt, drop dpatch dependency.
* Use dh_prep instead of dh_clean -k.
* Depend on cluster-agents.
-- Frederik Schüler f...@debian.org Fri, 26 Feb 2010 19:20:44 +0100
heartbeat (1:3.0.2-1) unstable; urgency=low
* New upstream release.
-- Martin Loschwitz madk...@debian.org Wed, 03 Feb 2010 08:05:00 +0100
The Ubuntu Cluster Stack [1] packages have been updated with the latest
versions. This new packages contain various fixes in both upstream and
packaging that we need in Ubuntu. These packages contain some of the Ubuntu
changes already, however, some others have not yet reached the packages but are
in the debian-ha mercurial repositories.
Build logs:
http://launchpadlibrarian.net/44109664/buildlog_ubuntu-lucid-amd64.heartbeat_1:3.0.2%2Bhg12555-2ubuntu1_FULLYBUILT.txt.gz
http://launchpadlibrarian.net/44109672/buildlog_ubuntu-lucid-i386.heartbeat_1:3.0.2%2Bhg12555-2ubuntu1_FULLYBUILT.txt.gz
[1]: https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-cluster-stack
___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 562710] Re: [FFe] Please sync cluster-agents 1:1.0.2+hg1712-1 (universe) from debian (unstable)
This bug was fixed in the package cluster-agents - 1:1.0.2+hg1712-1ubuntu1 --- cluster-agents (1:1.0.2+hg1712-1ubuntu1) lucid; urgency=low * Sync from debian unstable (LP: #562710). * Remove hard coded perl modules: - debian/control: Remove depends on perl modules for cluster-agents. - debian/rules: Add dh_perl to binary-common. * debian/ldirectord.init: Change from '/var/lock/subsys/ldirectord' to '/var/lock/subsys' * debian/rules: Add XSLTPROC_OPTIONS. -- Andres Rodriguez andres...@ubuntu.com Wed, 14 Apr 2010 16:09:45 -0400 ** Changed in: cluster-agents (Ubuntu) Status: New = Fix Released -- [FFe] Please sync cluster-agents 1:1.0.2+hg1712-1 (universe) from debian (unstable) https://bugs.launchpad.net/bugs/562710 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to cluster-agents in ubuntu. Status in “cluster-agents” package in Ubuntu: Fix Released Bug description: Binary package hint: cluster-agents Please sync cluster-agents from debian unstable cluster-agents (1:1.0.2+hg1712-1) unstable; urgency=low * New upstream Mercurial checkout * Prepare for unstable upload and actually do it * Include files added by upstream in cluster-agents -- Martin Loschwitz madk...@debian.org Tue, 30 Mar 2010 06:57:42 + cluster-agents (1:1.0.2+hg1702-1) unstable; urgency=low * New package revision prepared for upload to unstable. * Update debian/copyright: list LGPL and GPL version 2 components. * ldirectord: check for a config file in initscript, and do nothing if it is not present. -- Frederik Schüler f...@debian.org Fri, 26 Mar 2010 12:23:40 +0100 cluster-agents (1:1.0.2+hg1686-1) unstable; urgency=low * New package revision prepared for upload to unstable. * Install ldirector.8 manpage. * Drop unused lintian overrides. -- Frederik Schüler f...@debian.org Fri, 12 Mar 2010 12:01:30 +0100 cluster-agents (1:1.0.2+hg1657-2) unstable; urgency=low [ Martin Loschwitz ] * Update the copyright-file to be more appropriate and up to date. -- Martin Loschwitz madk...@debian.org Wed, 03 Mar 2010 08:40:00 +0100 cluster-agents (1:1.0.2+hg1657-1) unstable; urgency=low [ Martin Loschwitz ] * New package revision prepared for upload to unstable. -- Martin Loschwitz madk...@debian.org Wed, 02 Mar 2010 14:21:00 +0100 cluster-agents (1:1.0.2-2) UNRELEASED; urgency=low [ Simon Horman ] * Add build dependency on xsltproc. * Use dh_installinit to install the debian ldirectord init script. * Do not pass --sourcedir to dh_install. [ Frederik Schüler ] * Use source version 3.0 instead of dpatch, drop dependency accordingly. * Bump standards version to 3.8.4, no changes needed. * Install lintian override file. * Install manpages. * Really clean up in clean target. * debian/control: drop duplicate Section: field. -- Frederik Schüler f...@debian.org Fri, 26 Feb 2010 19:33:36 +0100 cluster-agents (1:1.0.2-1) unstable; urgency=low * New upstream release. -- Martin Loschwitz madk...@debian.org Wed, 03 Feb 2010 08:05:00 +0100 The Ubuntu Cluster Stack [1] packages have been updated with the latest versions. This new packages contain various fixes in both upstream and packaging that we need in Ubuntu. These packages contain some of the Ubuntu changes already, however, some others have not yet reached the packages but are in the debian-ha mercurial repositories. Build logs: http://launchpadlibrarian.net/44108879/buildlog_ubuntu-lucid-amd64.cluster-agents_1:1.0.2%2Bhg1712-1ubuntu1_FULLYBUILT.txt.gz http://launchpadlibrarian.net/44108148/buildlog_ubuntu-lucid-i386.cluster-agents_1:1.0.2%2Bhg1712-1ubuntu1_FULLYBUILT.txt.gz [1]: https://blueprints.launchpad.net/ubuntu/+spec/server-lucid-cluster-stack ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 519940] Re: Please merge keepalived 1.1.17-2 from debian testing
** Branch linked: lp:~andreserl/ubuntu/lucid/keepalived/merge-from- squeeze-lp519940 -- Please merge keepalived 1.1.17-2 from debian testing https://bugs.launchpad.net/bugs/519940 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to keepalived in ubuntu. Status in “keepalived” package in Ubuntu: Confirmed Bug description: Binary package hint: keepalived keepalived (1.1.17-2) unstable; urgency=low . * Reenable ipvs support thanks to Vincent Bernat for the hint ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 519940] Re: Please merge keepalived 1.1.17-2 from debian testing
This bug was fixed in the package keepalived - 1.1.17-2ubuntu1 --- keepalived (1.1.17-2ubuntu1) lucid; urgency=low * Merge from debian testing (LP: #519940), remaining changes: - debian/rules: DEB_UPDATE_RCD_PARAMS := expicit init start/stop parameters (don't stop at 0 and 6) - debian/init.d: init script header adapted to stop rule - debian/keepalived.postinst: Remove shutdown and reboot links -- Andres Rodriguez andres...@ubuntu.com Wed, 10 Feb 2010 13:35:16 -0500 ** Changed in: keepalived (Ubuntu) Status: Confirmed = Fix Released -- Please merge keepalived 1.1.17-2 from debian testing https://bugs.launchpad.net/bugs/519940 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to keepalived in ubuntu. Status in “keepalived” package in Ubuntu: Fix Released Bug description: Binary package hint: keepalived keepalived (1.1.17-2) unstable; urgency=low . * Reenable ipvs support thanks to Vincent Bernat for the hint ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst
This bug was fixed in the package batmand - 0.3.2-5
---
batmand (0.3.2-5) unstable; urgency=low
* Remove shlibs:Depends for binary packages without shared libs dependencies
* Add missing ${misc:Depends} debhelper for batmand-gateway-source
* Use dkms postinst script for batmand-gateway-dkms (Closes LP: #497149)
* Correct spelling errors found by lintian
-- Ubuntu Archive Auto-Sync arch...@ubuntu.com Mon, 01 Feb 2010 23:57:15
+
** Changed in: batmand (Ubuntu)
Status: Incomplete = Fix Released
--
Packages using DKMS should make use of /usr/lib/dkms/common.postinst
https://bugs.launchpad.net/bugs/497149
You received this bug notification because you are a member of Ubuntu
High Availability Team, which is subscribed to drbd8 in ubuntu.
Status in “batman-adv-kernelland” package in Ubuntu: Fix Released
Status in “batmand” package in Ubuntu: Fix Released
Status in “bcmwl” package in Ubuntu: New
Status in “dahdi-linux” package in Ubuntu: Fix Released
Status in “dkms” package in Ubuntu: Fix Released
Status in “drbd8” package in Ubuntu: Confirmed
Status in “fglrx-installer” package in Ubuntu: New
Status in “kqemu” package in Ubuntu: New
Status in “lirc” package in Ubuntu: Fix Released
Status in “nouveau-kernel-source” package in Ubuntu: New
Status in “nvidia-graphics-drivers-173” package in Ubuntu: Fix Committed
Status in “nvidia-graphics-drivers-180” package in Ubuntu: Fix Released
Status in “nvidia-graphics-drivers-96” package in Ubuntu: Fix Committed
Status in “openafs” package in Ubuntu: New
Status in “sl-modem” package in Ubuntu: New
Status in “virtualbox-ose” package in Ubuntu: Fix Released
Bug description:
Packages in Debian Ubuntu that are using their own postinstall script should
remove the logic from there and instead use /usr/lib/dkms/common.postinst .
This script contains sufficient logic to figure out the correct kernels to
build for and accounts for allowing builds on a buildd (if a package is ever
included in a live media build).
The following sample template is sufficient to use instead:
http://linux.dell.com/git/?p=dkms.git;a=blob;f=template-dkms-mkdeb/debian/postinst;hb=HEAD
___
Mailing list: https://launchpad.net/~ubuntu-ha
Post to : ubuntu-ha@lists.launchpad.net
Unsubscribe : https://launchpad.net/~ubuntu-ha
More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst
This bug was fixed in the package dkms - 2.1.1.1-0ubuntu1 --- dkms (2.1.1.1-0ubuntu1) lucid; urgency=low [ Mario Limonciello ] * dkms_common.postinst: Add some missing quotes around strings used in comparisons to make sure that this is safe on more shells. * Makefile, debian/rules: Only copy the init script in for redhat targets. * kernel_postinst.d: Make sure that dkms_autoinstaller is executable (LP: #480055) * Move the architecture mapping logic out of the DKMS template and into common.postinst for Ubuntu only. (LP: #497149) * template-dkms-mkdeb/debian/control: Build-depends on dkms (LP: #506959) [ Thomas Chenault ] * Fix parsing in find_external_dependencies(). The existing code behaves improperly when a driver disk module has more than two dependencies. -- Mario Limonciello mario_limoncie...@dell.com Mon, 25 Jan 2010 17:42:40 -0600 ** Changed in: dkms (Ubuntu) Status: Fix Committed = Fix Released -- Packages using DKMS should make use of /usr/lib/dkms/common.postinst https://bugs.launchpad.net/bugs/497149 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. Status in “batman-adv-kernelland” package in Ubuntu: Fix Released Status in “batmand” package in Ubuntu: Incomplete Status in “bcmwl” package in Ubuntu: New Status in “dahdi-linux” package in Ubuntu: Fix Released Status in “dkms” package in Ubuntu: Fix Released Status in “drbd8” package in Ubuntu: Confirmed Status in “fglrx-installer” package in Ubuntu: New Status in “kqemu” package in Ubuntu: New Status in “lirc” package in Ubuntu: Fix Released Status in “nouveau-kernel-source” package in Ubuntu: New Status in “nvidia-graphics-drivers-173” package in Ubuntu: Fix Committed Status in “nvidia-graphics-drivers-180” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-96” package in Ubuntu: Fix Committed Status in “openafs” package in Ubuntu: New Status in “sl-modem” package in Ubuntu: New Status in “virtualbox-ose” package in Ubuntu: Fix Released Bug description: Packages in Debian Ubuntu that are using their own postinstall script should remove the logic from there and instead use /usr/lib/dkms/common.postinst . This script contains sufficient logic to figure out the correct kernels to build for and accounts for allowing builds on a buildd (if a package is ever included in a live media build). The following sample template is sufficient to use instead: http://linux.dell.com/git/?p=dkms.git;a=blob;f=template-dkms-mkdeb/debian/postinst;hb=HEAD ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst
** Branch linked: lp:ubuntu/dkms -- Packages using DKMS should make use of /usr/lib/dkms/common.postinst https://bugs.launchpad.net/bugs/497149 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. Status in “batman-adv-kernelland” package in Ubuntu: Fix Released Status in “batmand” package in Ubuntu: Incomplete Status in “bcmwl” package in Ubuntu: New Status in “dahdi-linux” package in Ubuntu: Fix Released Status in “dkms” package in Ubuntu: Fix Released Status in “drbd8” package in Ubuntu: Confirmed Status in “fglrx-installer” package in Ubuntu: New Status in “kqemu” package in Ubuntu: New Status in “lirc” package in Ubuntu: Fix Released Status in “nouveau-kernel-source” package in Ubuntu: New Status in “nvidia-graphics-drivers-173” package in Ubuntu: Fix Committed Status in “nvidia-graphics-drivers-180” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-96” package in Ubuntu: Fix Committed Status in “openafs” package in Ubuntu: New Status in “sl-modem” package in Ubuntu: New Status in “virtualbox-ose” package in Ubuntu: Fix Released Bug description: Packages in Debian Ubuntu that are using their own postinstall script should remove the logic from there and instead use /usr/lib/dkms/common.postinst . This script contains sufficient logic to figure out the correct kernels to build for and accounts for allowing builds on a buildd (if a package is ever included in a live media build). The following sample template is sufficient to use instead: http://linux.dell.com/git/?p=dkms.git;a=blob;f=template-dkms-mkdeb/debian/postinst;hb=HEAD ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst
This bug was fixed in the package batman-adv-kernelland - 0.2-5 --- batman-adv-kernelland (0.2-5) unstable; urgency=low * Correct spelling errors found by lintian * Use dkms postinst script for batman-adv-dkms (Closes LP: #497149) -- Ubuntu Archive Auto-Sync arch...@ubuntu.com Mon, 25 Jan 2010 03:42:13 + ** Changed in: batman-adv-kernelland (Ubuntu) Status: Incomplete = Fix Released -- Packages using DKMS should make use of /usr/lib/dkms/common.postinst https://bugs.launchpad.net/bugs/497149 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. Status in “batman-adv-kernelland” package in Ubuntu: Fix Released Status in “batmand” package in Ubuntu: Incomplete Status in “bcmwl” package in Ubuntu: New Status in “dahdi-linux” package in Ubuntu: Fix Released Status in “dkms” package in Ubuntu: Fix Committed Status in “drbd8” package in Ubuntu: Confirmed Status in “fglrx-installer” package in Ubuntu: New Status in “kqemu” package in Ubuntu: New Status in “lirc” package in Ubuntu: Fix Released Status in “nouveau-kernel-source” package in Ubuntu: New Status in “nvidia-graphics-drivers-173” package in Ubuntu: Fix Committed Status in “nvidia-graphics-drivers-180” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-96” package in Ubuntu: Fix Committed Status in “openafs” package in Ubuntu: New Status in “sl-modem” package in Ubuntu: New Status in “virtualbox-ose” package in Ubuntu: Fix Released Bug description: Packages in Debian Ubuntu that are using their own postinstall script should remove the logic from there and instead use /usr/lib/dkms/common.postinst . This script contains sufficient logic to figure out the correct kernels to build for and accounts for allowing builds on a buildd (if a package is ever included in a live media build). The following sample template is sufficient to use instead: http://linux.dell.com/git/?p=dkms.git;a=blob;f=template-dkms-mkdeb/debian/postinst;hb=HEAD ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 509588] Re: latest heartbeat for lucid and karmic FTBFS
This bug was fixed in the package heartbeat - 2.99.2+sles11r9-5ubuntu2 --- heartbeat (2.99.2+sles11r9-5ubuntu2) lucid; urgency=low * debian/control: + added libdbd-mysql-perl to ldirectord package Depends (LP: #509567) + added libsocket6-perl to ldirectord package Depends (LP: #487508) * resources/OCF/Makefile.am: + removed duplicate drbd resource script (LP: #509588) -- Stephan Hermann s...@sourcecode.de Tue, 19 Jan 2010 11:32:17 + ** Changed in: heartbeat (Ubuntu) Status: In Progress = Fix Released -- latest heartbeat for lucid and karmic FTBFS https://bugs.launchpad.net/bugs/509588 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to heartbeat in ubuntu. Status in “heartbeat” package in Ubuntu: Fix Released Bug description: Binary package hint: heartbeat Dear Colleagues, the actual package of heartbeat FTBFS in lucid and karmic (with latest security and update pockets). The problem is that latest autotools doesn't like to install twice the same file. In $sourceroot/resources/OCF/Makefile.am the resulting Makefile tries to install the DRBD resource script two times. Removing the duplicate one, will result in no FTBFS anymore :) Regards, \sh ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 509567] Re: ldirectord is missing a dependency on libdbd-mysql-perl
This bug was fixed in the package heartbeat - 2.99.2+sles11r9-5ubuntu2 --- heartbeat (2.99.2+sles11r9-5ubuntu2) lucid; urgency=low * debian/control: + added libdbd-mysql-perl to ldirectord package Depends (LP: #509567) + added libsocket6-perl to ldirectord package Depends (LP: #487508) * resources/OCF/Makefile.am: + removed duplicate drbd resource script (LP: #509588) -- Stephan Hermann s...@sourcecode.de Tue, 19 Jan 2010 11:32:17 + ** Changed in: heartbeat (Ubuntu Lucid) Status: In Progress = Fix Released -- ldirectord is missing a dependency on libdbd-mysql-perl https://bugs.launchpad.net/bugs/509567 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to heartbeat in ubuntu. Status in “heartbeat” package in Ubuntu: Fix Released Status in “heartbeat” source package in Lucid: Fix Released Status in “heartbeat” source package in Jaunty: New Status in “heartbeat” source package in Karmic: New Bug description: Binary package hint: heartbeat Dear Colleagues, when using ldirectord + heartbeat + mysql loadbalancing, you need the the libdbd-mysql-perl package to make ldirectord do the checks against a mysql database. this is missing in jaunty, eventually in karmic and lucid. Please fix ;) Regards, \sh ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 509567] Re: ldirectord is missing a dependency on libdbd-mysql-perl
** Branch linked: lp:ubuntu/heartbeat -- ldirectord is missing a dependency on libdbd-mysql-perl https://bugs.launchpad.net/bugs/509567 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to heartbeat in ubuntu. Status in “heartbeat” package in Ubuntu: Fix Released Status in “heartbeat” source package in Lucid: Fix Released Status in “heartbeat” source package in Jaunty: New Status in “heartbeat” source package in Karmic: New Bug description: Binary package hint: heartbeat Dear Colleagues, when using ldirectord + heartbeat + mysql loadbalancing, you need the the libdbd-mysql-perl package to make ldirectord do the checks against a mysql database. this is missing in jaunty, eventually in karmic and lucid. Please fix ;) Regards, \sh ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 497149] Re: Packages using DKMS should make use of /usr/lib/dkms/common.postinst
** Branch linked: lp:debian/sid/batman-adv-kernelland ** Branch linked: lp:debian/sid/batmand -- Packages using DKMS should make use of /usr/lib/dkms/common.postinst https://bugs.launchpad.net/bugs/497149 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to drbd8 in ubuntu. Status in “batman-adv-kernelland” package in Ubuntu: Incomplete Status in “batmand” package in Ubuntu: Incomplete Status in “bcmwl” package in Ubuntu: New Status in “dahdi-linux” package in Ubuntu: Fix Released Status in “dkms” package in Ubuntu: Fix Committed Status in “drbd8” package in Ubuntu: Confirmed Status in “fglrx-installer” package in Ubuntu: New Status in “kqemu” package in Ubuntu: New Status in “lirc” package in Ubuntu: Fix Released Status in “nouveau-kernel-source” package in Ubuntu: New Status in “nvidia-graphics-drivers-173” package in Ubuntu: Fix Committed Status in “nvidia-graphics-drivers-180” package in Ubuntu: Fix Released Status in “nvidia-graphics-drivers-96” package in Ubuntu: Fix Committed Status in “openafs” package in Ubuntu: New Status in “sl-modem” package in Ubuntu: New Status in “virtualbox-ose” package in Ubuntu: Fix Released Bug description: Packages in Debian Ubuntu that are using their own postinstall script should remove the logic from there and instead use /usr/lib/dkms/common.postinst . This script contains sufficient logic to figure out the correct kernels to build for and accounts for allowing builds on a buildd (if a package is ever included in a live media build). The following sample template is sufficient to use instead: http://linux.dell.com/git/?p=dkms.git;a=blob;f=template-dkms-mkdeb/debian/postinst;hb=HEAD ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 442952] Re: pacemaker-openais causes high cpu load
This bug was fixed in the package pacemaker - 1.0.5+hg20090813-0ubuntu4 --- pacemaker (1.0.5+hg20090813-0ubuntu4) karmic; urgency=low * Remove old and obsolete patches and patching system * Add quilt to build-depends * debian/patches/001-excessive-load.patch: - Avoid excessive load by checking for dead children every 1s (instead of 100ms) (LP: #442952) -- Ante Karamatic iv...@ubuntu.com Thu, 15 Oct 2009 01:41:43 +0200 ** Changed in: pacemaker (Ubuntu) Status: Confirmed = Fix Released -- pacemaker-openais causes high cpu load https://bugs.launchpad.net/bugs/442952 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to pacemaker in ubuntu. Status in “pacemaker” package in Ubuntu: Fix Released Bug description: Binary package hint: pacemaker-openais hi, there is a bug in pacemaker-openais. When you start corosync you will see that corosync shows a high cpu load. this was fixed in the upstream packages in Aug 17th. See: http://hg.clusterlabs.org/pacemaker/stable-1.0/rev/33da369d36e3 beekhof changed the 100ms to 1 second. Then the load drops down. Greetings, misch. ProblemType: Bug Architecture: i386 Date: Mon Oct 5 11:20:30 2009 DistroRelease: Ubuntu 9.10 Package: pacemaker-openais 1.0.5+hg20090813-0ubuntu3 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-11.36-generic SourcePackage: pacemaker Uname: Linux 2.6.31-11-generic i686 ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
[Ubuntu-ha] [Bug 254257] Re: Still uses multiuser argument to dh_installinit
** Branch linked: lp:ubuntu/karmic/keepalived -- Still uses multiuser argument to dh_installinit https://bugs.launchpad.net/bugs/254257 You received this bug notification because you are a member of Ubuntu High Availability Team, which is subscribed to keepalived in ubuntu. Status in “keepalived” package in Ubuntu: Fix Released Status in “keepalived” package in Debian: New Bug description: Binary package hint: keepalived Hi, keepalived still uses the multiuser argument to dh_installinit, but this is now deprecated. For how to change the package to no longer use this please see https://lists.ubuntu.com/archives/ubuntu-devel-announce/2008-June/000430.html Please forward the new patch to Debian when you do this, as multiuser isn't applicable to Debian, but the new scheme is. Thanks, James ___ Mailing list: https://launchpad.net/~ubuntu-ha Post to : ubuntu-ha@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-ha More help : https://help.launchpad.net/ListHelp
