[Bug 1563027] Re: vsftpd 3.0.3-3ubuntu1 fails to start on installation

[Louis Bouchard]

I have been working on parallel on this one & opened a bug in debian :
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819546

listen_ipv6 was reverted from YES to NO following Debian Bug: #803999 to
allign with the manpage statement.

Either we revert it back & adapt the manpage or we force it in the
systemd unit & document accordingly

** Changed in: vsftpd (Ubuntu)
 Assignee: Chris J Arges (arges) => Louis Bouchard (louis-bouchard)

** Bug watch added: Debian Bug tracker #819546
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819546

** Changed in: vsftpd (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1563027

Title:
  vsftpd 3.0.3-3ubuntu1 fails to start on installation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1563027/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1563089] Re: Memory Leak when new cluster configuration is formed.

[Louis Bouchard]

** Also affects: corosync (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1563089

Title:
  Memory Leak when new cluster configuration is formed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1563089/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1561019] Re: copied cpu flags don't match host cpu

[Louis Bouchard]

** Also affects: libvirt (Ubuntu Wily)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1561019

Title:
  copied cpu flags don't match host cpu

To manage notifications about this bug go to:
https://bugs.launchpad.net/libvirt/+bug/1561019/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1532789] Re: Trusty multipath-tools suffering seg faults

[Louis Bouchard]

** Tags added: sts-sru

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1532789

Title:
  Trusty multipath-tools suffering seg faults

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1532789/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

[Louis Bouchard]

Fixes to the debdiff look ok to me. Sponsored to Trusty

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1530837

Title:
  Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running
  corosync -v

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1288438] Re: Neutron server takes a long time to recover from VIP move

[Louis Bouchard]

** Also affects: neutron (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: neutron (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1288438

Title:
  Neutron server takes a long time to recover from VIP move

To manage notifications about this bug go to:
https://bugs.launchpad.net/fuel/+bug/1288438/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1546445] Re: support vhost user without specifying vhostforce

[Louis Bouchard]

** Changed in: qemu (Ubuntu Vivid)
   Status: New => Won't Fix

** No longer affects: qemu (Ubuntu Trusty)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1546445

Title:
  support vhost user without specifying vhostforce

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-archive/+bug/1546445/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1546445] Re: support vhost user without specifying vhostforce

[Louis Bouchard]

** Also affects: qemu (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: qemu (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: qemu (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu in Ubuntu.
https://bugs.launchpad.net/bugs/1546445

Title:
  support vhost user without specifying vhostforce

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1546445/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1544719] Re: does not start on install / depends on squid which is squid3

[Louis Bouchard]

well, it's not applied backward, it's just that Debian uses squid & not
squid3 as with Xenial. Maybe we should revert this patch

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1544719

Title:
  does not start on install / depends on squid which is squid3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1544719/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1544719] Re: does not start on install / depends on squid which is squid3

[Louis Bouchard]

Either I goofed with bzr or the patch has been applied backward :

# bzr diff -r-2..-1 
=== modified file 'debian/changelog'
--- debian/changelog2015-08-24 09:56:49 +
+++ debian/changelog2016-01-29 16:56:25 +
@@ -1,3 +1,10 @@
+squid-deb-proxy (0.8.14) unstable; urgency=medium
+
+  * depend on squid3 instead of squid, thanks to
+HIGUCHI Daisuke (VDR dai), closes: #813082
+
+ -- Michael Vogt   Fri, 29 Jan 2016 17:55:43 +0100
+
 squid-deb-proxy (0.8.13) unstable; urgency=medium
 
   * add README.md to squid-deb-proxy install, thanks to

=== modified file 'debian/control'
--- debian/control  2013-05-16 18:09:24 +
+++ debian/control  2016-01-29 16:56:25 +
@@ -15,7 +15,7 @@
 Architecture: all
 Depends: ${python:Depends},
  ${misc:Depends},
-squid3
+squid
 Recommends: avahi-utils
 Description: Squid proxy configuration to optimize package downloads
  This package contains a Squid proxy configuration to manage a cache of

=== modified file 'debian/squid-deb-proxy.init'
--- debian/squid-deb-proxy.init 2013-12-19 08:28:46 +
+++ debian/squid-deb-proxy.init 2016-01-29 16:56:25 +
@@ -17,7 +17,7 @@
 
 NAME=squid-deb-proxy
 DESC="Squid Deb HTTP Proxy"
-DAEMON=/usr/sbin/squid3
+DAEMON=/usr/sbin/squid
 PIDFILE=/var/run/$NAME.pid
 CONFIG=/etc/squid-deb-proxy/squid-deb-proxy.conf
 SQUID_ARGS="-YC -f $CONFIG"

=== modified file 'debian/squid-deb-proxy.logrotate'
--- debian/squid-deb-proxy.logrotate2012-04-18 13:58:46 +
+++ debian/squid-deb-proxy.logrotate2016-01-29 16:56:25 +
@@ -12,8 +12,6 @@
  postrotate
   if [ -x /usr/sbin/squid ]; then
   SQUID=/usr/sbin/squid
-  elif  [ -x /usr/sbin/squid3 ]; then
-  SQUID=/usr/sbin/squid3
   else
   echo "No squid binary found"
   exit 1

=== modified file 'debian/squid-deb-proxy.upstart'
--- debian/squid-deb-proxy.upstart  2014-03-19 13:46:32 +
+++ debian/squid-deb-proxy.upstart  2016-01-29 16:56:25 +
@@ -26,8 +26,6 @@
 script
   if [ -x /usr/sbin/squid ]; then
   SQUID=/usr/sbin/squid
-  elif  [ -x /usr/sbin/squid3 ]; then
-  SQUID=/usr/sbin/squid3
   else
   echo "No squid binary found"
   exit 1

=== modified file 'init-common.sh'
--- init-common.sh  2014-12-17 12:27:25 +
+++ init-common.sh  2016-01-29 16:56:25 +
@@ -24,8 +24,6 @@
 pre_start() {
   if [ -x /usr/sbin/squid ]; then
   SQUID=/usr/sbin/squid
-  elif  [ -x /usr/sbin/squid3 ]; then
-  SQUID=/usr/sbin/squid3
   else
   echo "No squid binary found"
   exit 1
@@ -84,7 +82,7 @@
   rm -f $AVAHIFILE
 }
 
-# from the squid3 debian init script
+# from the squid debian init script
 find_cache_dir () {
 w=" " # space tab
 res=`sed -ne '

=== modified file 'squid-deb-proxy.conf'
--- squid-deb-proxy.conf2015-07-14 14:53:01 +
+++ squid-deb-proxy.conf2016-01-29 16:56:25 +
@@ -93,5 +93,5 @@
 # And finally deny all other access to this proxy
 http_access deny all
 
-# we don't want to clash with the squid3 netdb state file
+# we don't want to clash with the squid netdb state file
 netdb_filename stdio:/var/log/squid-deb-proxy/netdb.state

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1544719

Title:
  does not start on install / depends on squid which is squid3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1544719/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1544719] Re: does not start on install / depends on squid which is squid3

[Louis Bouchard]

Bug https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813082 claims to
have fixed the problem

** Bug watch added: Debian Bug tracker #813082
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=813082

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1544719

Title:
  does not start on install / depends on squid which is squid3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1544719/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Louis Bouchard]

Blueprint changed by Louis Bouchard:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: MIR for pps-tools: INPROGRESS
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
  [smoser] openiscsi merge (debian bug 804162): BLOCKED
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (=14days): TODO
  [racb] squid3 merge (=4days): TODO
  [racb] libecap (squid3 dependency): TODO
  [nacc] logwatch cleanup (waiting for release upstream): BLOCKED
  [nacc] Tomcat updates and cleanup (=14days): TODO
  [nacc] Java-related work (=10days): TODO
  [nacc] puppet merge and cleanup: TODO
  [rharper] docker.io 1.9 or greater: INPROGRESS
- [louis-bouchard] clamav merge: INPROGRESS
+ [louis-bouchard] clamav merge: DONE
  [jamespage] crmsh and pacemaker: DONE
  [teward] Update nginx to 1.9.11 (bug 1543624): INPROGRESS
  [kick-d] Amavisd-new update: INPROGRESS
  
  Work items for ubuntu-16.04:
  [paelzer] DPDK MIR: INPROGRESS
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: INPROGRESS
  [serge-hallyn] enable numa in qemu (was actually done in vivid!): DONE
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): TODO
  Consider postfix update: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1540491] Re: Please merge clamav 0.99+dfsg-1 (main) from Debian stable

[Louis Bouchard]

** Changed in: clamav (Ubuntu)
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1540491

Title:
  Please merge clamav 0.99+dfsg-1 (main) from Debian stable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1540491/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Louis Bouchard]

Blueprint changed by Louis Bouchard:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): DONE
  [louis-bouchard] nut merge: DONE
  [nacc] logwatch merge: DONE
  
  Work items for ubuntu-16.02:
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: INPROGRESS
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
  [smoser] openiscsi merge (debian bug 804162): BLOCKED
  [racb] MySQL cleanup (=2days): TODO
  [racb] MySQL flags fix (=5days): TODO
  [lars-tangvald] MySQL move to 5.7 (=14days): TODO
  [racb] squid3 merge (=4days): TODO
  [racb] libecap (squid3 dependency): TODO
  [nacc] logwatch cleanup (waiting for release upstream): BLOCKED
  [nacc] Tomcat updates and cleanup (=14days): TODO
  [nacc] Java-related work (=10days): TODO
  [nacc] puppet merge and cleanup: TODO
  [rharper] docker.io 1.9 or greater: INPROGRESS
- [louis-bouchard] clamav merge: TODO
+ [louis-bouchard] clamav merge: INPROGRESS
  [jamespage] crmsh and pacemaker: DONE
  [teward] Update nginx to 1.9.11 (bug 1543624): TODO
  
  Work items for ubuntu-16.04:
  [paelzer] DPDK MIR: INPROGRESS
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  [paelzer] DPDK upstream work: INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO
  [racb] mail-stack-delivery deprecation plan: TODO
  dovecot merge (doko: done in wily, update to 2.2.2x would be good): TODO
  Consider postfix update: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1534106] Re: rsyslogd crashed with SIGSEGV with juju-local configuration

[Louis Bouchard]

This bug has been fixed by the latest upload of rsyslog :
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1539483. Marking
it fix released

** Changed in: juju-core (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: rsyslog (Ubuntu)
   Status: Triaged => Fix Released

** Changed in: rsyslog (Ubuntu)
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to juju-core in Ubuntu.
https://bugs.launchpad.net/bugs/1534106

Title:
  rsyslogd crashed with SIGSEGV with juju-local configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1534106/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: Please backport haproxy 1.5.14-1ubuntu0.15.10.1 from wily-updates

[Louis Bouchard]

** Summary changed:

- HAProxy 1.5 init script does not terminate processes
+ Please backport haproxy 1.5.14-1ubuntu0.15.10.1 from wily-updates

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  Please backport haproxy 1.5.14-1ubuntu0.15.10.1 from wily-updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: Please backport haproxy 1.5.14-1ubuntu0.15.10.1 from wily-updates

[Louis Bouchard]

Hello,

Here are the following verifications that were made on trusty :
 1) haproxy-1.5.14-1ubuntu0.15.10.1 builds correctly
 2) haproxy-1.5.14-1ubuntu0.15.10.1 installs correctly
 3) when nbproc > 1 is used, all haproxy processes are stopped correctly

I am now positive that 1.5.14 fixes the problem encountered with
1.5.4-1ubuntu2.1~ubuntu14.04.1 and that is also fixed in the latest 1.4
version available in -updates.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  Please backport haproxy 1.5.14-1ubuntu0.15.10.1 from wily-updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521958] Re: rabbit: starvation of connections for reply

[Louis Bouchard]

** Also affects: oslo.messaging (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: oslo.messaging (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1521958

Title:
  rabbit: starvation of connections for reply

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.messaging/+bug/1521958/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1393391] Re: neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-update_fanout..

[Louis Bouchard]

** Also affects: neutron (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: neutron (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1393391

Title:
  neutron-openvswitch-agent stuck on no queue 'q-agent-notifier-port-
  update_fanout..

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1393391/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1521958] Re: rabbit: starvation of connections for reply

[Louis Bouchard]

** Also affects: oslo.messaging (Ubuntu Vivid)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1521958

Title:
  rabbit: starvation of connections for reply

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.messaging/+bug/1521958/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1532789] Re: Trusty multipath-tools suffering seg faults

[Louis Bouchard]

** Changed in: multipath-tools (Ubuntu Trusty)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1532789

Title:
  Trusty multipath-tools suffering seg faults

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1532789/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1540491] [NEW] Please merge clamav 0.99+dfsg-1 (main) from Debian stable

[Louis Bouchard]

Public bug reported:

merge bug

** Affects: clamav (Ubuntu)
 Importance: Wishlist
 Assignee: Louis Bouchard (louis-bouchard)
 Status: Confirmed

** Changed in: clamav (Ubuntu)
   Status: New => Confirmed

** Changed in: clamav (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: clamav (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1540491

Title:
  Please merge clamav 0.99+dfsg-1 (main) from Debian stable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/clamav/+bug/1540491/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

>From what I can gather, the proper version that will fix this issue is
the version which is in wily-updates :

http://archive.ubuntu.com/ubuntu/pool/main/h/haproxy/haproxy_1.5.14-1ubuntu0.15.10.1.dsc

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1248054] Re: [SRU] dlm package installation fails

[Louis Bouchard]

Hello,

I would suggest a few modifications :

1) lockfile="/var/run/$progdir/$NAME.pid"
 Should point to /run as /var/run is a symbolic link

2) Your mount statement should terminate by : || true as in

mount -t configfs none /sys/kernel/config > /dev/null 2>&1 || true

If the mount fails for any reason the fact that the shell runs as -e
will make the complete command fails badly.

3) The upstream has a systemd service ; shouldn't it be used instead of
relying on the obsolete sysinit script ? While I understand that this is
intended to be SRUed, the proper service should be used on Xenial
anyhow.

pitti also commented that the script (if used) should go in /usr/lib
/modules-load.d/ but that would not be required if we go with the
systemd service.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dlm in Ubuntu.
https://bugs.launchpad.net/bugs/1248054

Title:
  [SRU] dlm package installation fails

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dlm/+bug/1248054/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1515278] Re: rabbit queues should expire when unused

[Louis Bouchard]

** Also affects: oslo.messaging (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: oslo.messaging (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: oslo.messaging (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to oslo.messaging in Ubuntu.
https://bugs.launchpad.net/bugs/1515278

Title:
  rabbit queues should expire when unused

To manage notifications about this bug go to:
https://bugs.launchpad.net/oslo.messaging/+bug/1515278/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

[Louis Bouchard]

** Changed in: nut (Ubuntu)
 Assignee: Steve Langasek (vorlon) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1522346

Title:
  Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Louis Bouchard]

Blueprint changed by Louis Bouchard:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: DONE
  [paelzer] NIS merge: DONE
  
  Work items for ubuntu-15.12:
  [raharper] : tgt merge (bug 1524982): DONE
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: DONE
  [kick-d] exim4 merge: DONE
  
  Work items for ubuntu-16.01:
  [stgraber] unbound merge: DONE
  [raharper] strongswan merge and cleanup (=4days ha! bug 1535951): INPROGRESS
  [nacc] logwatch merge and cleanup: INPROGRESS
  [smoser] openiscsi merge: TODO
  [kick-d] amavisd-new merge: DONE
  [vorlon] freeipmi merge and cleanup (=3days): DONE
  [vorlon] freeipmi12 to 16 transition: DONE
  [wesley-wiedenmeier] dovecot merge (doko: done in wily, update to 2.2.2x 
would be good): TODO
  [nacc] Consider php7.0 for Xenial: INPROGRESS
  [kick-d] NTP merge, cleanup and PPS support: INPROGRESS
  [teward] Update nginx to 1.9.10 (disregarding additional Debian changes): DONE
  [teward] Merge nginx 1.9.10 (extra Debian changes not already included): TODO
  
  Work items for ubuntu-16.03:
  [teward] Update nginx to 1.10.x after upstream release: BLOCKED
  
  Work items:
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  puppet merge and cleanup: TODO
  [paelzer] DPDK MIR: INPROGRESS
  [paelzer] DPDK upstream work: TODO
  [racb] MySQL cleanup and move to 5.7 (=14days): TODO
  [rharper] Tomcat updates and cleanup (=14days): TODO
  Java-related work (=10days): TODO
  mail-stack-delivery deprecation plan: TODO
  [racb] squid3 merge (=4days): TODO
- [louis-bouchard] nut merge: INPROGRESS
+ [louis-bouchard] nut merge: DONE
  [arges] libvirt merge (bug 1533003) : INPROGRESS
  [arges] libvirt-python: INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO
  [racb] HTTP/2 related work (=1days): TODO
  Consider postfix update: TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1382079] Re: Project selector not working

[Louis Bouchard]

** Also affects: horizon (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Wily)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: horizon (Ubuntu Vivid)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to horizon in Ubuntu.
https://bugs.launchpad.net/bugs/1382079

Title:
  Project selector not working

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1382079/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

[Louis Bouchard]

** Patch added: "nut_2.7.1-1ubuntu5-2.7.2-4ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+attachment/4556135/+files/nut_2.7.1-1ubuntu5-2.7.2-4ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1522346

Title:
  Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

[Louis Bouchard]

** Patch added: "nut_2.7.1-1ubuntu5-2.7.2-4ubuntu1_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+attachment/4554760/+files/nut_2.7.1-1ubuntu5-2.7.2-4ubuntu1_v2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1522346

Title:
  Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

[Louis Bouchard]

To further add to Mathieu's comment, here is the backtrace of one of the
recent core that we got :

(gdb) bt
#0  0x7f17a122a0d5 in __GI_raise (sig=) at 
../nptl/sysdeps/unix/sysv/linux/raise.c:64
#1  0x7f17a122d83b in __GI_abort () at abort.c:91
#2  0x7f17a126732e in __libc_message (do_abort=2, fmt=0x7f17a13715d8 "*** 
glibc detected *** %s: %s: 0x%s ***\n")
at ../sysdeps/unix/sysv/linux/libc_fatal.c:201
#3  0x7f17a1271b26 in malloc_printerr (action=3, str=0x7f17a13717c8 "double 
free or corruption (fasttop)", 
ptr=) at malloc.c:5051
#4  0x7f17a15c8f27 in free_multipath (mpp=0x7f177c009160, free_paths=0) at 
structs.c:174
#5  0x7f17a15ec09a in _remove_map (mpp=0x7f177c009160, vecs=0xbaea70, 
stop_waiter=1, purge_vec=1) at structs_vec.c:143
#6  0x7f17a15ec0f8 in remove_map_and_stop_waiter (mpp=0x7f177c009160, 
vecs=0xbaea70, purge_vec=1) at structs_vec.c:156
#7  0x004075f5 in mpvec_garbage_collector (vecs=0xbaea70) at main.c:949
#8  0x7f177c007060 in ?? ()
#9  0x00baea70 in ?? ()
#10 0x7f177c009160 in ?? ()
#11 0x00020003 in ?? ()
#12 0x7f17a2274e20 in ?? ()
#13 0x004080f0 in checkerloop (ap=0x7f17a13717c8) at main.c:1162
#14 0x in ?? ()
(gdb) f 4
#4  0x7f17a15c8f27 in free_multipath (mpp=0x7f177c009160, free_paths=0) at 
structs.c:174
warning: Source file is more recent than executable.
174 FREE(mpp->dmi);
(gdb) l
169 FREE(mpp->alias);
170 mpp->alias = NULL;
171 }
172
173 if (mpp->dmi) {
174 FREE(mpp->dmi);
175 mpp->dmi = NULL;
176 }
177
178 /*
(gdb)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1535898

Title:
  Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1535898] Re: Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

[Louis Bouchard]

** Also affects: multipath-tools (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: multipath-tools (Ubuntu Precise)
   Status: New => In Progress

** Changed in: multipath-tools (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: multipath-tools (Ubuntu Precise)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1535898

Title:
  Trusty & Vivid multipath-tools (multipathd) seg-fault core dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1535898/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

[Louis Bouchard]

** Patch removed: "nut_debian_2.7.2-4_to_ubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+attachment/4531908/+files/nut_debian_2.7.2-4_to_ubuntu.debdiff

** Patch removed: "nut_2.7.1-1ubuntu5-2.7.2-4ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+attachment/4531909/+files/nut_2.7.1-1ubuntu5-2.7.2-4ubuntu1.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1522346

Title:
  Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

Re: [Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

[Louis Bouchard]

Hello Robie, Steve,

I will address both of your updates sequentially :

Le 14/01/2016 19:13, Robie Basak a écrit :
> Hi Louis,
> 
> Thank you for working on this merge. Good job identifying some changes that
> could be dropped.
> 
> However I think this work could do with some improvement before I am happy to
> upload it.
> 
> Overall it looks like it might be OK, but I'm concerned that the changelog is
> misleading. There are changes that are being carried forward that are not
> mentioned in your Remaining Changes section, and conversely there are also
> changes that are claimed to have been carried forward but are partially
> missing. Details below:
> 
> udev changes in debian/rules. Was this dropped? In your merge the delta still
> seems to be there, and it still looks relevant. So why does the changelog say
> that this is dropped?

Oh dear! I mistakenly thought that the change was coming from upstream as there
is no mention in grab-merge's REPORT file of any conflict on debian/rules. I
will revert the changelog entry accordingly.

I definitively will stop to use this tool for merges. Not only it makes my life
miserable by having to systematically revert to pristine source packages for
comparaison, but it seems to silently changes files without any indication.

So far, grab-merge has been a source of problems for me. I had to restart the
rsyslog merge twice because of mismatch and build problems.

I may need your help to get my head around it, but I will give a second look at
your git workflow that I bookmarked earlier.
> 
> Some but not all changes made in 2.7.1-1ubuntu5 seem to have disappeared. Are
> they still needed? Why is this part of the delta not mentioned in the
> changelog?
>

Indeed, the .ubuntu5 modification that you uploaded got dropped. I was mislead
to believe that it was an upstream change added and not dropped from our part. I
will reintroduce it.

I also added a mention of dropped changes in debian/tests/test-nut.py that are
now superseded upstream but had no mention in the previous changelog.

> What about these parts of the previous delta, for which I don't see any
> information in your merge changelog about whether these were carried forward 
> or
> dropped?
> 
>   * Disable systemd unit; it does not check nut.conf whether nut is
> configured, and thus fails to start (and the package install). The 
> init.d
> script works well enough for the time being. (LP: #1313231)
> 
>   * debian/tests/test-nut.py: in the CVE_2012_2944 test, give nut at most 
> 5
> seconds to shut down, instead of expecting it to be shut down 
> immediately
> after sending the killall. (LP: #1291378)
> 
>   * debian/patches/0006-ups-conf-reorder.patch: Move maxretry setting
> above Examples section, closer to the "outside of a driver definition"
> comment. (LP: #1405822)
> 

My changelog mention the following :

* Ubuntu bugs fixed upstream:

  LP: #1405822, #1291378, #1313231


Those are the three bugs that you mention above.  I do agree that I should have
carried forward the previous changelog description and state that the bug had
been fixed upstream. I'll carry that change in a new debdiff.

> Please could you address these questions above? In particular I'd like
> the changelog to be accurate in explaining what is being carried
> forward, what is being dropped and any additional changes made (I think
> there are none in this case). Otherwise it's tough both to review now
> and for a future merge.
> 
> Minor: I'd put the extra Ubuntu delta lines for debian/patches/series after 
> all
> the Debian ones, unless there's a good reason to insert them into the middle.
> 

Regarding Steve's update now :

>  - nut-{cgi,server}.postinst: the existing delta with Debian is bad form,
> adduser is designed to be called unconditionally. Not strictly speaking part
> of the merge, but something I spotted along the way that I think it's
> important to fix. Along the way, I fixed up the changelog explanation for why
> this is still needed (since we no longer do upgrades from hardy, if that were
> the only reason we could drop the delta).
>

Fixed in the new merge.

>  - debian/patches/backport-fix-lp753661.patch has been a pointless diff for
> several upstream releases. The patch still applies, but upstream fixed the
> issue differently (using rtrim() ).

Fixed in the new merge.

>  - as Robie noted, you say the udev delta is dropped, but the delta to
> debian/rules still exists. I've dropped the delta, with more explanation in
> the changelog to why it can be dropped.

Fixed in the new merge with your drop of the previous delta.

>  - the changes from 2.7.7-1ubuntu5 are restored, as still required.

Yes, already noted in Robie's comment

Regarding 

[Bug 1532789] Re: Trusty multipath-tools suffering seg faults

[Louis Bouchard]

** Also affects: multipath-tools (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1532789

Title:
  Trusty multipath-tools suffering seg faults

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1532789/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1530837] Re: Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running corosync -v

[Louis Bouchard]

** Also affects: corosync (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to corosync in Ubuntu.
https://bugs.launchpad.net/bugs/1530837

Title:
  Logsys file leaks in /dev/shm after sigabrt, sigsegv and when running
  corosync -v

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1530837/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1520192] Re: multipath-tools from Precise should have been fixed together with Trusty fixes

[Louis Bouchard]

** Also affects: multipath-tools (Ubuntu Precise)
   Importance: Undecided
   Status: New

** Changed in: multipath-tools (Ubuntu Precise)
   Status: New => In Progress

** Changed in: multipath-tools (Ubuntu Precise)
   Importance: Undecided => High

** Changed in: multipath-tools (Ubuntu Precise)
 Assignee: (unassigned) => Rafael David Tinoco (inaddy)

** Changed in: multipath-tools (Ubuntu)
   Status: In Progress => Invalid

** Changed in: multipath-tools (Ubuntu)
 Assignee: Rafael David Tinoco (inaddy) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to multipath-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1520192

Title:
  multipath-tools from Precise should have been fixed together with
  Trusty fixes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1520192/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

[Louis Bouchard]

debian upstream to merged 2.7.2-4ubuntu1 debdiff

** Patch added: "nut_debian_2.7.2-4_to_ubuntu.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+attachment/4531908/+files/nut_debian_2.7.2-4_to_ubuntu.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1522346

Title:
  Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

[Louis Bouchard]

ubuntu wily to Xenial debdiff

** Patch added: "nut_2.7.1-1ubuntu5-2.7.2-4ubuntu1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+attachment/4531909/+files/nut_2.7.1-1ubuntu5-2.7.2-4ubuntu1.debdiff

** Changed in: nut (Ubuntu)
   Status: In Progress => Confirmed

** Changed in: nut (Ubuntu)
     Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1522346

Title:
  Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

[Louis Bouchard]

ok, I'm on the vivid SRU

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1481737

Title:
  HAProxy init script does not work correctly with nbproc configuration
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

[Louis Bouchard]

** Tags removed: verification-needed
** Tags added: verification-done

** Changed in: haproxy (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1481737

Title:
  HAProxy init script does not work correctly with nbproc configuration
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

[Louis Bouchard]

debdiff for vivid SRU

** Patch added: "lp1481737_vivid.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+attachment/4531521/+files/lp1481737_vivid.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1481737

Title:
  HAProxy init script does not work correctly with nbproc configuration
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Blueprint servercloud-x-server-core] General server work for Xenial

[Louis Bouchard]

Blueprint changed by Louis Bouchard:

Work items changed:
  Work items for ubuntu-15.11:
  [serge-hallyn] etckeeper: TODO
  [paelzer] NIS merge: INPROGRESS
  
  Work items:
  [racb] nagios-plugins/monitoring-plugins merge and cleanup: INPROGRESS
  strongswan merge and cleanup: TODO
  [smoser] systemd-boot tag ~ubuntu-server package review and fixes: TODO
  puppet merge and cleanup: TODO
  [paelzer] DPDK MIR: INPROGRESS
  DPDK upstream work: TODO
  [racb] MySQL cleanup and move to 5.7: TODO
  NTP merge, cleanup and PPS support: TODO
  freeipmi merge and cleanup: TODO
  logwatch merge and cleanup: TODO
  Tomcat updates and cleanup: TODO
  mail-stack-delivery deprecation plan: TODO
  [tdaitx] squid3 merge: INPROGRESS
  dovecot merge: TODO
- nut merge: TODO
+ [louis-bouchard] nut merge: INPROGRESS
  amavisd-new merge: TODO
  [arges] libvirt merge (bug 1519433) : INPROGRESS
  [serge-hallyn] enable numa in qemu (=2days): TODO

-- 
General server work for Xenial
https://blueprints.launchpad.net/ubuntu/+spec/servercloud-x-server-core

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] Re: Please merge nut 2.7.2-4 (main) from debian (unstable)

[Louis Bouchard]

** Changed in: nut (Ubuntu)
   Status: New => In Progress

** Changed in: nut (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: nut (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1522346

Title:
  Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1522346] [NEW] Please merge nut 2.7.2-4 (main) from debian (unstable)

[Louis Bouchard]

Public bug reported:

merge bug

** Affects: nut (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nut in Ubuntu.
https://bugs.launchpad.net/bugs/1522346

Title:
  Please merge nut 2.7.2-4 (main) from debian (unstable)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1522346/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

** Changed in: trusty-backports
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1461429] Re: ceph-osd early start interferes with kdump-tools during kernel dump

[Louis Bouchard]

** Changed in: ceph (Ubuntu Trusty)
   Status: Confirmed => Fix Released

** Changed in: ceph (Ubuntu Trusty)
 Assignee: Louis Bouchard (louis-bouchard) => (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1461429

Title:
  ceph-osd early start interferes with kdump-tools during kernel dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1461429/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

[Louis Bouchard]

** Also affects: haproxy (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Changed in: haproxy (Ubuntu Vivid)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: haproxy (Ubuntu Vivid)
   Importance: Undecided => Medium

** Changed in: haproxy (Ubuntu Vivid)
   Status: New => In Progress

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1481737

Title:
  HAProxy init script does not work correctly with nbproc configuration
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

Vincent Bernat (vbernat) is the Debian maintainer for haproxy. His PPA
assumes a version of dpkg that is newer than 1.17.7. I'll try to open a
Debian bug on that.

The problem lies in the use of start-stop-daemon's new --pid option that
is only available after wily.

If 1.6 is backported to any version earlier than wily, this bug will
exist and the fix for it will need to be applied.

I just got the fix for 1.4 uploaded so I should be able to fix the 1.5
backport in the near future.

..Louis

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

Greg, 1.6.2 is not packaged for Trusty. I don't know where it comes
from.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

Claudio, it is only partly fixed by Jorge's patch.

I have proposed the same fix than for this bug in LP: #1481737.
Unfortunately, not being a core dev, it needs to be sponsored to be
accepted.  Then I can backport the fix here in 1.5

Sorry for the delay, I'll chase a sponsor.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

[Louis Bouchard]

** Patch removed: "lp1494141_fix_stop_failure.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+attachment/4473139/+files/lp1494141_fix_stop_failure.debdiff

** Patch added: "lp1481737_stop_multipid.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+attachment/4492590/+files/lp1481737_stop_multipid.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1481737

Title:
  HAProxy init script does not work correctly with nbproc configuration
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

[Louis Bouchard]

** Description changed:

+ [SRU justification]
+ The sysVinit script does not completely stop processes when nbproc > 1
+ 
+ [Impact]
+ Stopping haproxy without this fix leaves all but one process running
+ 
+ [Fix]
+ Use temporary pidfile in a loop containing one single PID as the --pid option 
is not available for start-stop-daemon.
+ 
+ [Test Case]
+ Set nbproc > 4 in /etc/haproxy/haproxy.cfg
+ resart haproxy & verify that there is more than one haproxy process
+ Run :
+ $ ps aux | grep haproxy | grep -v grep | wc -l
+ 4
+ $ service haproxy stop
+ $ ps aux | grep haproxy | grep -v grep | wc -l
+ 
+ Without the patch, the result of the last command will be 3. With the
+ fix, it will be 0
+ 
+ [Regression]
+ The regression risk is in the use of a temporary file instead of the 
start-stop-daemon option.
+ 
+ It has been tested with TMPDIR="/tmp/My Dir" to check for spaces in
+ directory names.
+ 
+ [Original description of the problem]
  In case you have more than one process enabled in the haproxy config, the 
init script fails to stop all of those processes.
  So to clarify you need to have this in your haproxy.cfg:
  
  """
  ...
  global
- maxconn 32000
- ulimit-n65536
- userhaproxy
- group   haproxy
- nbproc  2
+ maxconn 32000
+ ulimit-n65536
+ userhaproxy
+ group   haproxy
+ nbproc  2
  
  ...
  """
  
  the problem is more visible if you set the nbproc to higher number.
  
  service haproxy stop --> will only stop on of the haproxy processes.
  
  The problem is so that start-stop-daemon can't handle pid files with multiple 
lines. Only stopping the first one. HAProxy does write all the pids started by 
itself into the pid file, so the problem is not in HAProxy, but in the 
start-stop-daemon or more likely in the init scrip of haproxy.
  One solution or workaround is to remove pidfile option of start-stop-daemon 
in the init script, than it wil work as killall and will stop the haproxy 
processes properly.
  
  To proof you can try this sequence:
  
  service haproxy start #if its not running
  ps ax | grep haproxy | grep -v grep | wc -l #this should report 2
  service haproxy restart
  ps ax | grep haproxy | grep -v grep | wc -l #this will report 3
  
  The workaround as a diff:
- root@ubi1:/opt# diff /etc/init.d/haproxy /etc/init.d/haproxy.orig 
+ root@ubi1:/opt# diff /etc/init.d/haproxy /etc/init.d/haproxy.orig
  62c62
  <   --retry 5 --exec $HAPROXY || ret=$?
  ---
  >   --retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
  
  extra infos:
  root@ubi1:/opt# lsb_release -rd
  Description:Ubuntu 14.04.3 LTS
  Release:14.04
  
  root@ubi1:/opt# apt-cache policy haproxy
  haproxy:
-   Installed: 1.4.24-2ubuntu0.2
-   Candidate: 1.4.24-2ubuntu0.2
-   Version table:
-  1.5.3-1~ubuntu14.04.1 0
- 100 http://us.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 
Packages
-  *** 1.4.24-2ubuntu0.2 0
- 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
- 100 /var/lib/dpkg/status
-  1.4.24-2 0
- 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
+   Installed: 1.4.24-2ubuntu0.2
+   Candidate: 1.4.24-2ubuntu0.2
+   Version table:
+  1.5.3-1~ubuntu14.04.1 0
+ 100 http://us.archive.ubuntu.com/ubuntu/ trusty-backports/main amd64 
Packages
+  *** 1.4.24-2ubuntu0.2 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 
Packages
+ 100 /var/lib/dpkg/status
+  1.4.24-2 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages

** Patch added: "lp1494141_fix_stop_failure.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+attachment/4473139/+files/lp1494141_fix_stop_failure.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1481737

Title:
  HAProxy init script does not work correctly with nbproc configuration
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

[Louis Bouchard]

** Also affects: haproxy (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: haproxy (Ubuntu Trusty)
   Importance: Undecided => Medium

** Changed in: haproxy (Ubuntu Trusty)
   Status: New => In Progress

** Changed in: haproxy (Ubuntu Trusty)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

** Changed in: haproxy (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1481737

Title:
  HAProxy init script does not work correctly with nbproc configuration
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

Hello,

Unfortunately Jorge's patch is incomplete. The reason for the looping on
pid is that, if nproc > 1, the pidfile will contain more than one PID
and using --pidfile will only kill the first one.

The proposed patch here will fix both situation, i.e. the fact that
--pid is silently ignored and that if nproc > 1, all processes will be
killed.

I think we need to create new bug for Trusty as, if nproc > 1, only the
first PID will be killed.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

FYI, I will rebase the debdiff on the new version currently in backport
& repost.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1481737] Re: HAProxy init script does not work correctly with nbproc configuration option

[Louis Bouchard]

Peter, you will not be able to reproduce on Debian unless you test
versions prior to Stable.

The reason why the stop script does not stop at all processes is because
it relied on the --pidfile option and this one only kills the first PID.
When nproc > 1, the PIDFILE contains all PIDs. This is why debian
introduced the use of --pid in a loop for all haproxy PIDs.

Now, the --pid option that is introduced in dpkg version 1.17.6 as
outlined in the man page of start-stop-daemon :

   [--pid] pid
  Check for a process with the specified pid (since version 
1.17.6). The pid must be a number greater than 0.

This version is available in all Debian releases since Stable but only
available in Ubuntu Wily.  A fix for this situation is available for
haproxy 1.5 which is in trusty-backport (see LP: #1494141).  I will
backport that fix for the stable release and ask for an SRU on this one.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1481737

Title:
  HAProxy init script does not work correctly with nbproc configuration
  option

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1481737/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

Good catch Claudio.  The bug is present in Trusty and Trusty-backports.

Prior to LP: #1477198, the stop script did not stop at all because it
relied on the --pid option that is introduced in dpkg version 1.17.6 as
outlined in the man page of start-stop-daemon :

   [--pid] pid
  Check  for a process with the specified pid (since version 
1.17.6). The pid must be a number greater than 0.

Now with the fix introduced by LP: #1477198, it will work as expected
unless nproc > 1. Otherwise, we will see the behavior described in LP:
#1481737 whereas processes other than the first PID appearing in the
pidfile will remain active.

The patch included here solves both situation as it loops through all
the PIDs in the pidfile & terminates them using a temporary pidfile.

I will carry on this explanation in the other bug so the version in
-updates is fixed as well.

This bug remains valid as we still see only the first PID being  killed
with the recent patch.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

Marking task Trusty as invalid, since haproxy 1.4 uses --pidfile and is
unaffected.

Marking task Wily as fix released as the --pid option is available in
Wily so haproxy 1.5 is unaffected

** Also affects: haproxy (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: haproxy (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: haproxy (Ubuntu)
   Status: New => Fix Released

** Changed in: haproxy (Ubuntu Trusty)
   Status: New => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

Patch for the fix to the backport package

** Patch added: "lp1494141_fix_stop_failure.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1494141/+attachment/4466700/+files/lp1494141_fix_stop_failure.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

Bonjour Claudio,

No, I have just submitted the fix for inclusion in the backported
package.  Once the backport team has taken care of it, it will be
indicated as  such in the bug.

Kind regards,

..Louis

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1434684] Re: Pacemaker is not started and stopped automatically with Corosync

[Louis Bouchard]

** Also affects: corosync (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: corosync (Ubuntu Trusty)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1434684

Title:
  Pacemaker is not started and stopped automatically with Corosync

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1434684/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1434684] Re: Pacemaker is not started and stopped automatically with Corosync

[Louis Bouchard]

** Changed in: corosync (Ubuntu Trusty)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1434684

Title:
  Pacemaker is not started and stopped automatically with Corosync

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1434684/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1434684] Re: Pacemaker is not started and stopped automatically with Corosync

[Louis Bouchard]

Hello,

Well, elbandi have found the answer to your question : pacemaker now
needs to be started as a separate service. To quote the document :

"Pacemaker used to obtain membership and quorum from a custom Corosync plugin. 
This plugin also had the capability to start Pacemaker automatically when 
Corosync was started.
Neither behavior is possible with Corosync 2.0 and beyond as support for 
plugins was removed. Instead, Pacemaker must be started as a separate service."

Looks like the services are correctly setup as pacemaker starts normally
at boot time.  If you want to manually stop your cluster, you will have
to issue :

$ service corosync stop
$ service pacemaker stop


** Changed in: corosync (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: corosync (Ubuntu Trusty)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1434684

Title:
  Pacemaker is not started and stopped automatically with Corosync

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1434684/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

** Package changed: haproxy (Ubuntu) => trusty-backports

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

Micah, got the bug number ? Maybe we should make this one  a duplicate
then ?

..Louis

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

** Patch removed: "lp1494141_fix_stop_failure.debdiff"
   
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+attachment/4466700/+files/lp1494141_fix_stop_failure.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/trusty-backports/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

** Changed in: haproxy (Ubuntu)
   Status: New => In Progress

** Changed in: haproxy (Ubuntu)
   Importance: Undecided => Medium

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

Hi,

haproxy 1.5.4 introduces the following change :

ret=0
-   start-stop-daemon --quiet --oknodo --stop \
-   --retry 5 --pidfile $PIDFILE --exec $HAPROXY || ret=$?
+   for pid in $(cat $PIDFILE); do
+   start-stop-daemon --quiet --oknodo --stop \
+   --retry 5 --pid $pid --exec $HAPROXY || ret=$?
+   done

start-stop-daemon --pidfile is replaced by --pid but this option is only
available in dpkg 1.17.6 and onward :

$ man start-stop-daemon (on Wily) :
   [--pid] pid
  Check for a process with the specified pid (since version 
1.17.6). The pid must be a number greater than 0.

This is not available on trusty, which explains why the process does not
stop.  I must admit that silently ignoring a false option is not an
appropriate behavior though

The reason for that change is that, if nbproc > 1 in the haproxy config
file, all the PIDs will be in one single /var/run/haproxy.pid file so in
order to kill each process, we must loop through the pid list.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1434684] Re: Pacemaker is not started and stopped automatically with Corosync

[Louis Bouchard]

** Changed in: corosync (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1434684

Title:
  Pacemaker is not started and stopped automatically with Corosync

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1434684/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1494141] Re: HAProxy 1.5 init script does not terminate processes

[Louis Bouchard]

** Changed in: haproxy (Ubuntu)
 Assignee: (unassigned) => Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1494141

Title:
  HAProxy 1.5 init script does not terminate processes

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/haproxy/+bug/1494141/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1386869] Re: -host in auto.master not mounting nfs exports

[Louis Bouchard]

** Also affects: autofs (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1386869

Title:
  -host in auto.master not mounting nfs exports

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1346935] Re: Failing to create simplestreams bucket on ceph-radosgw

[Louis Bouchard]

** Also affects: simplestreams (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: simplestreams (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to simplestreams in Ubuntu.
https://bugs.launchpad.net/bugs/1346935

Title:
  Failing to create simplestreams bucket on ceph-radosgw

To manage notifications about this bug go to:
https://bugs.launchpad.net/simplestreams/+bug/1346935/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1349888] Re: Attempting to attach the same volume multiple times can cause bdm record for existing attachment to be deleted.

[Louis Bouchard]

** Also affects: nova (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nova (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1349888

Title:
  Attempting to attach the same volume multiple times can cause bdm
  record for existing attachment to be deleted.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1349888/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1327218] Re: Volume detach failure because of invalid bdm.connection_info

[Louis Bouchard]

** Also affects: nova (Ubuntu)
   Importance: Undecided
   Status: New

** Also affects: nova (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1327218

Title:
  Volume detach failure because of invalid bdm.connection_info

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1327218/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1474667] Re: log dir permissions are incorrect

[Louis Bouchard]

** Also affects: ceilometer (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: ceilometer (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: ceilometer (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: ceilometer (Ubuntu Wily)
   Importance: Undecided
   Status: Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceilometer in Ubuntu.
https://bugs.launchpad.net/bugs/1474667

Title:
  log dir permissions are incorrect

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1474667/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1459046] Re: [SRU] nova-* services do not start if rsyslog is not yet started

[Louis Bouchard]

** Also affects: nova (Ubuntu Utopic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1459046

Title:
  [SRU] nova-* services do not start if rsyslog is not yet started

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1459046/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1470687] Re: Not working properly with compile options -symbolic-functions

[Louis Bouchard]

** Also affects: autofs (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Also affects: autofs (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: autofs (Ubuntu Utopic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1470687

Title:
  Not working properly with compile options -symbolic-functions

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1470687/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1471022] Re: [SRU] race between nova-compute and neutron-ovs-cleanup

[Louis Bouchard]

** Also affects: neutron (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: neutron (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: neutron (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to neutron in Ubuntu.
https://bugs.launchpad.net/bugs/1471022

Title:
  [SRU] race between nova-compute and neutron-ovs-cleanup

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1471022/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1466013] [NEW] kdump-tools does not have an upstart job

[Louis Bouchard]

Public bug reported:

kdump-tools relies on a sysVinit script to  capture the kernel dump.  It
sometimes gets interference from other jobs starting at runlevels 2 to
5.

An upstart job starting before RUNLEVEL is emitted would alleviate that.

** Affects: makedumpfile (Ubuntu)
 Importance: Undecided
 Status: Invalid

** Affects: makedumpfile (Ubuntu Trusty)
 Importance: Medium
 Assignee: Louis Bouchard (louis-bouchard)
 Status: Confirmed

** Also affects: ceph (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: ceph (Ubuntu Trusty)
   Status: New = Confirmed

** Changed in: ceph (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: ceph (Ubuntu Trusty)
 Assignee: (unassigned) = Louis Bouchard (louis-bouchard)

** Package changed: ceph (Ubuntu) = makedumpfile (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1466013

Title:
  kdump-tools does not have an upstart job

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1466013/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1464175] Re: libvirt-daemon: virObjectUnref(): libvirtd killed by SIGSEGV

[Louis Bouchard]

** Also affects: libvirt (Ubuntu Vivid)
   Importance: Undecided
   Status: New

** Also affects: libvirt (Ubuntu Utopic)
   Importance: Undecided
   Status: New

** Also affects: libvirt (Ubuntu Trusty)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/1464175

Title:
  virObjectUnref(): libvirtd killed by SIGSEGV

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1464175/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1456662] Re: squid-deb-proxy fails to resolve dns entry : needs to be restarted

[Louis Bouchard]

** Tags removed: verification-needed
** Tags added: verification-done

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1456662

Title:
  squid-deb-proxy fails to resolve dns entry : needs to be restarted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1461429] Re: ceph-osd early start intefere with kdump-tools during kernel dump

[Louis Bouchard]

** Changed in: ceph (Ubuntu)
   Status: New = Confirmed

** Changed in: ceph (Ubuntu)
   Importance: Undecided = Medium

** Changed in: ceph (Ubuntu)
 Assignee: (unassigned) = Louis Bouchard (louis-bouchard)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1461429

Title:
  ceph-osd early start intefere with kdump-tools during kernel dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1461429/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1461429] [NEW] ceph-osd early start intefere with kdump-tools during kernel dump

[Louis Bouchard]

Public bug reported:

When a kernel crash dump occurs on a system with kdump-tools configured
and enabled, kexec triggers a reboot of the server which will start
kdump-tools to capture the kernel dump.

On systems running CEPH osd's, the configured osds will start even if
kdump-tools is setup to start very early in the boot phase.  Even
replacing the kdump-tools sysVinit script by an upstart job that runs
before the runlevel signal is not sufficient.

The /etc/init/ceph-osd.conf job still runs while kdump is capturing the
dums, triggering the OOM killer.

** Affects: ceph (Ubuntu)
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1461429

Title:
  ceph-osd early start intefere with kdump-tools during kernel dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1461429/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1461429] Re: ceph-osd early start intefere with kdump-tools during kernel dump

[Louis Bouchard]

Marking the development release as Invalid since Wily uses systemd

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1461429

Title:
  ceph-osd early start intefere with kdump-tools during kernel dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1461429/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1461429] Re: ceph-osd early start intefere with kdump-tools during kernel dump

[Louis Bouchard]

Here is an example of a captured session :

[  399.597207] SysRq : Trigger a crash
[  399.599050] BUG: unable to handle kernel NULL pointer dereference at 
  (null)
[  399.600421] IP: [81457fc6] sysrq_handle_crash+0x16/0x20
[  399.600745] PGD 3758e067 PUD 3d616067 PMD 0
[  399.600745] Oops: 0002 [#1] SMP
...
 * Starting enable remaining boot-time encrypted block devices[74G[ OK ]
Cloud-init v. 0.7.5 running 'init' at Wed, 03 Jun 2015 07:33:31 +. Up 8.83 
seconds.
ci-info: Net device info
ci-info: ++--+---+-+---+
ci-info: | Device |  Up  |  Address  | Mask| Hw-Address|
ci-info: ++--+---+-+---+
ci-info: |   lo   | True | 127.0.0.1 |  255.0.0.0  | . |
ci-info: |  eth0  | True | 10.5.1.39 | 255.255.0.0 | fa:16:3e:09:27:0b |
ci-info: ++--+---+-+---+
ci-info: +Route info+
ci-info: +---+-+--+-+---+---+
ci-info: | Route | Destination | Gateway  |   Genmask   | Interface | Flags |
ci-info: +---+-+--+-+---+---+
ci-info: |   0   |   0.0.0.0   | 10.5.0.1 |   0.0.0.0   |eth0   |   UG  |
ci-info: |   1   |   10.5.0.0  | 0.0.0.0  | 255.255.0.0 |eth0   |   U   |
ci-info: +---+-+--+-+---+---+
 * Starting Ceph OSD[74G[ OK ]  
   
 * Starting Signal sysvinit that local filesystems are mounted[74G[ OK ]
 * Starting configure network device security[74G[ OK ]
 * Starting flush early job output to logs[74G[ OK ]
...
 * Starting Ceph OSD (start all instances)[74G[ OK ]
 * Starting regular background program processing daemon[74G[ OK ]
 * Starting deferred execution scheduler[74G[ OK ]
Starting kdump-tools:  * Starting Ceph MON (start all instances)[74G[ OK ]
 * Stopping save kernel messages[74G[ OK ]
 * Starting Ceph MON[74G[ OK ]
 * Starting automatic crash report generation[74G[ OK ]
 * Stopping CPU interrupts balancing daemon[74G[ OK ]
 * running makedumpfile -c -d 31 /proc/vmcore 
/var/crash/201506030733/dump-incomplete
 * Stopping Ceph MON (start all instances)[74G[ OK ]
 * Starting Ceph monitor (all instances)[74G[ OK ]
The kernel version is not supported.
The created dumpfile may be incomplete.
cyclic buffer size has been changed: 32767 = 32640
Excluding unnecessary pages: [  0.0 %] / 
* Starting Create Ceph client.admin key when possible[74G[ OK ]
Excluding unnecessary pages: [100.0 %] |
Excluding unnecessary pages: [100.0 %] \
Excluding unnecessary pages: [100.0 %] -
Excluding unnecessary pages: [100.0 %] /
Excluding unnecessary pages: [100.0 %] |
 * Starting OpenSSH server[74G[ OK ]
Copying data   : [  9.4 %] \
Copying data   : [ 25.1 %] -
Copying data   : [ 47.2 %] /
Copying data   : [ 59.8 %] |
Copying data   : [ 70.5 %] \
Copying data   : [ 93.6 %] - 
* Stopping Read required files in advance (for other mountpoints)[74G[ OK ]
Excluding unnecessary pages: [100.0 %] /
Copying data   : [100.0 %] |

The dumpfile is saved to /var/crash/201506030733/dump-incomplete.

makedumpfile Completed.
 * kdump-tools: saved vmcore in /var/crash/201506030733
 * running makedumpfile --dump-dmesg /proc/vmcore 
/var/crash/201506030733/dmesg.201506030733
The kernel version is not supported.
The created dumpfile may be incomplete.

The dmesg log is saved to /var/crash/201506030733/dmesg.201506030733.

makedumpfile Completed.
 * kdump-tools: saved dmesg content in /var/crash/201506030733
Wed, 03 Jun 2015 07:33:49 +


We can clearly see the Ceph OSD start messages during the kernel dump

** Also affects: ceph (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: ceph (Ubuntu Trusty)
   Status: New = Confirmed

** Changed in: ceph (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: ceph (Ubuntu Trusty)
 Assignee: (unassigned) = Louis Bouchard (louis-bouchard)

** Changed in: ceph (Ubuntu)
 Assignee: Louis Bouchard (louis-bouchard) = (unassigned)

** Changed in: ceph (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1461429

Title:
  ceph-osd early start intefere with kdump-tools during kernel dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1461429/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe

[Bug 1461429] Re: ceph-osd early start interferes with kdump-tools during kernel dump

[Louis Bouchard]

This is caused by the fact that Ceph OSDs are started by the following
udev rule : /lib/udev/rules.d/95-ceph-osd.rules. This rules emits the
ceph-osd signal that triggers the job to start.

The problem is not with ceph but with how kdump-tools relies on sysVinit
script ordering to run early.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to ceph in Ubuntu.
https://bugs.launchpad.net/bugs/1461429

Title:
  ceph-osd early start interferes with kdump-tools during kernel dump

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ceph/+bug/1461429/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1456662] Re: squid-deb-proxy fails to resolve dns entry : needs to be restarted

[Louis Bouchard]

debdiff from the fix in Wily

** Patch added: lp1456662_sru_upstart.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456662/+attachment/4408486/+files/lp1456662_sru_upstart.debdiff

** Description changed:

+ [SRU justification]
+ In some race situation, squid-deb-proxy is unable to operate and needs to be 
restarted.
+ 
+ [Impact]
+ Requires manual intervention from system administrator to function correctly.
+ 
+ [Fix]
+ Change the start on upstart statement to match the one used by squid3
+ 
+ [Test Case]
+ See Original description.
+ 
+ [Regression]
+ None expected as the same statement is already in use in the squid3 package 
and in the upstream debian package.
+ 
+ [ORiginal description of the problem]
+ 
  In some specific context that I currently cannot identify (i.e. happens
  everytime on my server but never in VMs), after a reboot, squid-deb-
  proxy fails to resolve DNS entries for URL that it needs to service. The
  problem seems systematic on the hardware that I have.
  
  Release : Trusty (squid-deb-proxy_0.8.6)
  
  Test :
  1) Reboot squid-deb-proxy server
  2) From some client, issue :
  $ telnet {squid-deb-proxy-server} 8000
  GET http://fr.archive.ubuntu.com/ubuntu/dists/wily/InRelease
  Trying 192.168.1.11...
  Connected to avogadro.
  Escape character is '^]'.
  HTTP/1.1 503 Service Unavailable
  Server: squid/3.3.8
  Mime-Version: 1.0
  Date: Tue, 19 May 2015 14:21:51 GMT
  Content-Type: text/html
  Content-Length: 3287
  X-Squid-Error: ERR_DNS_FAIL 0
  Vary: Accept-Language
  Content-Language: en
  X-Cache: MISS from squid-deb-proxy
  X-Cache-Lookup: MISS from squid-deb-proxy:8000
  Via: 1.1 squid-deb-proxy (squid/3.3.8)
  Connection: close
  !DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01//EN 
http://www.w3.org/TR/html4/strict.dtd;
  htmlhead
  meta http-equiv=Content-Type content=text/html; charset=utf-8
  titleERROR: The requested URL could not be retrieved/title
  style type=text/css!--
   /*
   Stylesheet for Squid Error pages
   Adapted from design by Free CSS Templates
   http://www.freecsstemplates.org
   Released for free under a Creative Commons Attribution 2.5 License
  */
  ...
  div id=content
  pThe following error was encountered while trying to retrieve the URL: a 
href=http://fr.archive.ubuntu.com/ubuntu/dists/wily/InRelease;http://fr.archive.ubuntu.com/ubuntu/dists/wily/InRelease/a/p
  
  blockquote id=error
  pbUnable to determine IP address from host name 
qfr.archive.ubuntu.com/q/b/p
  /blockquote
  
  pThe DNS server returned:/p
  blockquote id=data
  preNo DNS records/pre
  /blockquote
  
  pThis means that the cache was not able to resolve the hostname
  presented in the URL. Check if the address is correct./p
  
  pYour cache administrator is a 
href=mailto:webmaster?subject=CacheErrorInfo%20-%20ERR_DNS_FAILamp;body=CacheHost%3A%20squid-deb-proxy%0D%0AErrPage%3A%20ERR_DNS_FAIL%0D%0AErr%3A%20%5Bnone%5D%0D%0ADNS%20ErrMsg%3A%20No%20DNS%20records%0D%0ATimeStamp%3A%20Tue,%2019%20May%202015%2014%3A21%3A51%20GMT%0D%0A%0D%0AClientIP%3A%20192.168.1.10%0D%0A%0D%0AHTTP%20Request%3A%0D%0AGET%20%2Fubuntu%2Fdists%2Fwily%2FInRelease%20HTTP%2F0.9%0A%0D%0A%0D%0A;webmaster/a./p
  br
  
  Restarting the squid-deb-proxy service fixes the problem

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1456662

Title:
  squid-deb-proxy fails to resolve dns entry : needs to be restarted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1456662] Re: squid-deb-proxy fails to resolve dns entry : needs to be restarted

[Louis Bouchard]

debdiff for the trusty fix

** Patch added: squid-deb-proxy-lp1456662_dns_race_fix.debdiff
   
https://bugs.launchpad.net/ubuntu/trusty/+source/squid-deb-proxy/+bug/1456662/+attachment/4405343/+files/squid-deb-proxy-lp1456662_dns_race_fix.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1456662

Title:
  squid-deb-proxy fails to resolve dns entry : needs to be restarted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1456662] Re: squid-deb-proxy fails to resolve dns entry : needs to be restarted

[Louis Bouchard]

As it turns out, mvo has just uploaded the fix along with some other bug
fix for this bug : http://bugs.debian.org/780083 to Debian this morning.
So I will pick up his changes from Wily and SRU it when it becomes
available

** Patch removed: squid-deb-proxy-lp1456662_dns_race_fix.debdiff
   
https://bugs.launchpad.net/ubuntu/trusty/+source/squid-deb-proxy/+bug/1456662/+attachment/4405343/+files/squid-deb-proxy-lp1456662_dns_race_fix.debdiff

** Bug watch added: Debian Bug tracker #780083
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=780083

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1456662

Title:
  squid-deb-proxy fails to resolve dns entry : needs to be restarted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1456662] [NEW] squid-deb-proxy fails to resolve dns entry : needs to be restarted

[Louis Bouchard]

Public bug reported:

In some specific context that I currently cannot identify (i.e. happens
everytime on my server but never in VMs), after a reboot, squid-deb-
proxy fails to resolve DNS entries for URL that it needs to service. The
problem seems systematic on the hardware that I have.

Release : Trusty (squid-deb-proxy_0.8.6)

Test :
1) Reboot squid-deb-proxy server
2) From some client, issue :
$ telnet {squid-deb-proxy-server} 8000
GET http://fr.archive.ubuntu.com/ubuntu/dists/wily/InRelease
Trying 192.168.1.11...
Connected to avogadro.
Escape character is '^]'.
HTTP/1.1 503 Service Unavailable
Server: squid/3.3.8
Mime-Version: 1.0
Date: Tue, 19 May 2015 14:21:51 GMT
Content-Type: text/html
Content-Length: 3287
X-Squid-Error: ERR_DNS_FAIL 0
Vary: Accept-Language
Content-Language: en
X-Cache: MISS from squid-deb-proxy
X-Cache-Lookup: MISS from squid-deb-proxy:8000
Via: 1.1 squid-deb-proxy (squid/3.3.8)
Connection: close
!DOCTYPE html PUBLIC -//W3C//DTD HTML 4.01//EN 
http://www.w3.org/TR/html4/strict.dtd;
htmlhead
meta http-equiv=Content-Type content=text/html; charset=utf-8
titleERROR: The requested URL could not be retrieved/title
style type=text/css!--
 /*
 Stylesheet for Squid Error pages
 Adapted from design by Free CSS Templates
 http://www.freecsstemplates.org
 Released for free under a Creative Commons Attribution 2.5 License
*/
...
div id=content
pThe following error was encountered while trying to retrieve the URL: a 
href=http://fr.archive.ubuntu.com/ubuntu/dists/wily/InRelease;http://fr.archive.ubuntu.com/ubuntu/dists/wily/InRelease/a/p

blockquote id=error
pbUnable to determine IP address from host name 
qfr.archive.ubuntu.com/q/b/p
/blockquote

pThe DNS server returned:/p
blockquote id=data
preNo DNS records/pre
/blockquote

pThis means that the cache was not able to resolve the hostname
presented in the URL. Check if the address is correct./p

pYour cache administrator is a 
href=mailto:webmaster?subject=CacheErrorInfo%20-%20ERR_DNS_FAILamp;body=CacheHost%3A%20squid-deb-proxy%0D%0AErrPage%3A%20ERR_DNS_FAIL%0D%0AErr%3A%20%5Bnone%5D%0D%0ADNS%20ErrMsg%3A%20No%20DNS%20records%0D%0ATimeStamp%3A%20Tue,%2019%20May%202015%2014%3A21%3A51%20GMT%0D%0A%0D%0AClientIP%3A%20192.168.1.10%0D%0A%0D%0AHTTP%20Request%3A%0D%0AGET%20%2Fubuntu%2Fdists%2Fwily%2FInRelease%20HTTP%2F0.9%0A%0D%0A%0D%0A;webmaster/a./p
br

Restarting the squid-deb-proxy service fixes the problem

** Affects: squid-deb-proxy (Ubuntu)
 Importance: Medium
 Status: Confirmed

** Affects: squid-deb-proxy (Ubuntu Trusty)
 Importance: Medium
 Assignee: Louis Bouchard (louis-bouchard)
 Status: In Progress


** Tags: sts

** Changed in: squid-deb-proxy (Ubuntu)
   Status: New = Confirmed

** Changed in: squid-deb-proxy (Ubuntu)
   Importance: Undecided = Medium

** Also affects: squid-deb-proxy (Ubuntu Trusty)
   Importance: Undecided
   Status: New

** Changed in: squid-deb-proxy (Ubuntu Trusty)
   Status: New = In Progress

** Changed in: squid-deb-proxy (Ubuntu Trusty)
   Importance: Undecided = Medium

** Changed in: squid-deb-proxy (Ubuntu Trusty)
 Assignee: (unassigned) = Louis Bouchard (louis-bouchard)

** Description changed:

  In some specific context that I currently cannot identify (i.e. happens
  everytime on my server but never in VMs), after a reboot, squid-deb-
  proxy fails to resolve DNS entries for URL that it needs to service. The
  problem seems systematic on the hardware that I have.
  
  Release : Trusty (squid-deb-proxy_0.8.6)
  
  Test :
  1) Reboot squid-deb-proxy server
  2) From some client, issue :
  $ telnet {squid-deb-proxy-server} 8000
  GET http://fr.archive.ubuntu.com/ubuntu/dists/wily/InRelease
- Trying 192.168.1.11...
   
- Connected to avogadro.
   
- Escape character is '^]'. 
   
- HTTP/1.1 503 Service Unavailable  
   
- Server: squid/3.3.8   
   
- Mime-Version: 1.0 
   
- Date: Tue, 19 May 2015 14:21:51 GMT   
   
- Content-Type: text/html   
   
- Content-Length: 3287  
   
- X-Squid-Error: ERR_DNS_FAIL 0 
   
- Vary: Accept-Language 
   
- Content-Language: en  
   
- X-Cache: MISS from squid-deb-proxy
   
- X-Cache-Lookup: MISS from squid-deb-proxy:8000
   
- Via: 1.1 squid-deb-proxy (squid/3.3.8)
   
- Connection: close

[Bug 1456662] Re: squid-deb-proxy fails to resolve dns entry : needs to be restarted

[Louis Bouchard]

Using the same start on  clause than for the squid3 job fixes the
problem (start on runlevel ...)  :

 # squid-deb-proxy - a proxy for deb packages
 #
 
 description squid-deb-proxy
 start on runlevel [2345]
 stop on runlevel [!2345]

I am going to prepare a debdiff with that modification

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1456662

Title:
  squid-deb-proxy fails to resolve dns entry : needs to be restarted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1456662] Re: squid-deb-proxy fails to resolve dns entry : needs to be restarted

[Louis Bouchard]

debdiff for Trusty

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid-deb-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1456662

Title:
  squid-deb-proxy fails to resolve dns entry : needs to be restarted

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid-deb-proxy/+bug/1456662/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1386869] Re: -host in auto.master not mounting nfs exports

[Louis Bouchard]

** Also affects: autofs (Ubuntu Utopic)
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs in Ubuntu.
https://bugs.launchpad.net/bugs/1386869

Title:
  -host in auto.master not mounting nfs exports

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autofs/+bug/1386869/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1387594] Re: init: symbol lookup error: /lib/powerpc64le-linux-gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock

[Louis Bouchard]

looks like I forgot to attach the trusty debdiff

** Patch added: lp1387594_glibc_trusty.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1387594/+attachment/4299974/+files/lp1387594_glibc_trusty.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1387594

Title:
  init: symbol lookup error: /lib/powerpc64le-linux-
  gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1387594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1346703] Re: /var/log/maas/rsyslog has incorrect permission

[Louis Bouchard]

New debdiff against most recent version in trusty-updates

** Patch removed: lp1346703_maas_rsyslog.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346703/+attachment/4235378/+files/lp1346703_maas_rsyslog.debdiff

** Patch added: lp1346703_maas_rsyslog_v2.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346703/+attachment/4276923/+files/lp1346703_maas_rsyslog_v2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1346703

Title:
  /var/log/maas/rsyslog has incorrect permission

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1346703/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1387594] Re: init: symbol lookup error: /lib/powerpc64le-linux-gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock

[Louis Bouchard]

The version in Precise is unaffected. Marking the task invalid

** Changed in: libnss-ldap (Ubuntu Precise)
   Status: New = Invalid

** Changed in: libnss-ldap (Ubuntu Trusty)
   Status: Confirmed = In Progress

** Changed in: libnss-ldap (Ubuntu Utopic)
   Status: Confirmed = In Progress

** Changed in: libnss-ldap (Ubuntu)
 Assignee: Louis Bouchard (louis-bouchard) = (unassigned)

** Tags added: cts

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1387594

Title:
  init: symbol lookup error: /lib/powerpc64le-linux-
  gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1387594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1387594] Re: init: symbol lookup error: /lib/powerpc64le-linux-gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock

[Louis Bouchard]

debdiff for the SRU on Trusty

** Description changed:

- This bug is specific to the PPC64EL architecture. More details in the
- analysis.
+ [SRU justification]
+ The version of the library in the archive for Utopic and Trusty has been 
built prior to a change in glibc that removes an expected symbol. Rebuild of 
the libnss-ldap library with the current source package will render the library 
unusable and may cause systems to become unbootable.
+ 
+ [Impact]
+ Without this fix, a rebuild of the libnss-ldap package will cause grave 
impact where usage of the libnss-ldap will segfault. Such a segfault during the 
boot process will cause the system to become unbootable.
+ 
+ [Fix]
+ Backport the glibc-2.16.patch that is now merged in Vivid into Utopic and 
Trusty. The version of the library in Precise already uses the correct glibc 
symbol.
+ 
+ [Test Case]
+ $ sudo apt-get download libnss-ldap
+ $ mkdir tmp
+ $ dpkg -x libnss-ldap_264-2.2ubuntu4_amd64.deb tmp
+ $ nm -D tmp/lib/x86_64-linux-gnu/libnss_ldap-2.15.so |grep lock$
+  w __pthread_mutex_lock
+  w __pthread_mutex_unlock
+ #Rebuild the library
+ $ pull-lp-source libnss-ldap trusty
+ $ sbuild -A -d trusty libnss-ldap_264-2.2ubuntu4.dsc
+ $ rm -Rf tmp/*
+ $ dpkg -x libnss-ldap_264-2.2ubuntu4_amd64.deb tmp
+ $ nm -D tmp/lib/x86_64-linux-gnu/libnss_ldap-2.19.so | grep lock$
+  U __libc_lock_lock
+  U __libc_lock_unlock
+ 
+ Notice that the libnss-ldap version change (2.15 - 2.19). With the
+ newly built version, the expected _pthread_mutex_lock|unlock is no
+ longer present.
+ 
+ [Regression]
+ None expected. This is already present and in use in the upstream version of 
the library.
+ 
+ [Original Description of the problem]
+ 
+ Unlike previously thought, this bug is _NOT_ specific to the PPC64EL
+ architecture. More details in the analysis.
  
  Many commands that require the use of libnss-ldap will fail with
  Segmentation Fault. The boot procedure itself can be blocked with the
  following message.
  
  One potential workaround is to remove the use of ldap from the
  /etc/nsswitch.conf file to at least provide a bootable system.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1387594

Title:
  init: symbol lookup error: /lib/powerpc64le-linux-
  gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1387594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1387594] Re: init: symbol lookup error: /lib/powerpc64le-linux-gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock

[Louis Bouchard]

debdiff for SRU on Utopic

** Patch added: lp1387594_glibc_utopic.debdiff
   
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1387594/+attachment/4276986/+files/lp1387594_glibc_utopic.debdiff

** Changed in: libnss-ldap (Ubuntu Precise)
 Assignee: Louis Bouchard (louis-bouchard) = (unassigned)

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1387594

Title:
  init: symbol lookup error: /lib/powerpc64le-linux-
  gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1387594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs

[Bug 1387594] Re: init: symbol lookup error: /lib/powerpc64le-linux-gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock

[Louis Bouchard]

** Description changed:

  [SRU justification]
  The version of the library in the archive for Utopic and Trusty has been 
built prior to a change in glibc that removes an expected symbol. Rebuild of 
the libnss-ldap library with the current source package will render the library 
unusable and may cause systems to become unbootable.
  
  [Impact]
  Without this fix, a rebuild of the libnss-ldap package will cause grave 
impact where usage of the libnss-ldap will segfault. Such a segfault during the 
boot process will cause the system to become unbootable.
  
  [Fix]
  Backport the glibc-2.16.patch that is now merged in Vivid into Utopic and 
Trusty. The version of the library in Precise already uses the correct glibc 
symbol.
  
  [Test Case]
+ On a server properly configured for ldap authentication :
+ 
+ root@trusty-ldapclient:~# getent passwd john
+ john:x:1:5000:John Doe:/home/john:/bin/bash
+ 
+ The same test on arm64 or ppc64el platform where the libnss-ldap have
+ been rebuilt recently you will get :
+ 
+ root@trusty-ldapclient:~# getent passwd john
+ Segmentation fault (core dumped)
+ 
  $ sudo apt-get download libnss-ldap
  $ mkdir tmp
  $ dpkg -x libnss-ldap_264-2.2ubuntu4_amd64.deb tmp
  $ nm -D tmp/lib/x86_64-linux-gnu/libnss_ldap-2.15.so |grep lock$
-  w __pthread_mutex_lock
-  w __pthread_mutex_unlock
+  w __pthread_mutex_lock
+  w __pthread_mutex_unlock
  #Rebuild the library
  $ pull-lp-source libnss-ldap trusty
  $ sbuild -A -d trusty libnss-ldap_264-2.2ubuntu4.dsc
  $ rm -Rf tmp/*
  $ dpkg -x libnss-ldap_264-2.2ubuntu4_amd64.deb tmp
  $ nm -D tmp/lib/x86_64-linux-gnu/libnss_ldap-2.19.so | grep lock$
-  U __libc_lock_lock
-  U __libc_lock_unlock
+  U __libc_lock_lock
+  U __libc_lock_unlock
  
  Notice that the libnss-ldap version change (2.15 - 2.19). With the
  newly built version, the expected _pthread_mutex_lock|unlock is no
  longer present.
  
  [Regression]
  None expected. This is already present and in use in the upstream version of 
the library.
  
  [Original Description of the problem]
  
  Unlike previously thought, this bug is _NOT_ specific to the PPC64EL
  architecture. More details in the analysis.
  
  Many commands that require the use of libnss-ldap will fail with
  Segmentation Fault. The boot procedure itself can be blocked with the
  following message.
  
  One potential workaround is to remove the use of ldap from the
  /etc/nsswitch.conf file to at least provide a bootable system.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnss-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/1387594

Title:
  init: symbol lookup error: /lib/powerpc64le-linux-
  gnu/libnss_ldap.so.2: undefined symbol: __libc_lock_lock

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnss-ldap/+bug/1387594/+subscriptions

-- 
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs