[Bug 1549441] Re: Please sync php-defaults 32 from Debian unstable

[Daniel Holbach]

This bug was fixed in the package php-defaults - 32
Sponsored for Nish Aravamudan (nacc)

---
php-defaults (32) unstable; urgency=medium

  * Bump epoch to 1, so the new version number is higher than the old
one

 -- Ondřej Surý   Tue, 23 Feb 2016 20:47:04 +0100

php-defaults (31) unstable; urgency=medium

  * Generate package version numbers from PHP supported versions and
changelog version
  * Remove php-dbg package
  * Bump standards version to 3.9.7 (no change)

 -- Ondřej Surý   Tue, 23 Feb 2016 20:25:43 +0100

php-defaults (30) unstable; urgency=medium

  * Regenerate d/control

 -- Ondřej Surý   Tue, 23 Feb 2016 18:41:09 +0100

php-defaults (29) unstable; urgency=medium

  * Update modulelist to match the new extension packages

 -- Ondřej Surý   Tue, 23 Feb 2016 10:12:44 +0100

** Changed in: php-defaults (Ubuntu)
   Status: New => Fix Released

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

Title:
  Please sync php-defaults 32 from Debian unstable

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-defaults/+bug/1549441/+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 1318317] Re: openipmi startup script removes kernel modules

[Jeremy Kerr]

Nish: looks good to me:

[jk@hab2 ~]$ sudo service openipmi stop
[jk@hab2 ~]$ sudo modprobe ipmi_devintf
[jk@hab2 ~]$ lsmod | grep ipmi
ipmi_devintf   13227  0 
ipmi_powernv5657  0 
ipmi_msghandler51494  2 ipmi_powernv,ipmi_devintf
[jk@hab2 ~]$ sudo service openipmi start
Job for openipmi.service failed. See "systemctl status openipmi.service" and 
"journalctl -xe" for details.
[jk@hab2 ~]$ lsmod | grep ipmi
ipmi_devintf   13227  0 
ipmi_powernv5657  0 
ipmi_msghandler51494  2 ipmi_powernv,ipmi_devintf
[jk@hab2 ~]$ 

- even though the openipmi service itelf fails, it doesn't take down
everyone else's access to /dev/ipmiX

-- 
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/1318317

Title:
  openipmi startup script removes kernel modules

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openipmi/+bug/1318317/+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 1549388] Re: In some rare cases Postfix connect to a wrong MX server

[Scott Kitterman]

On Thursday, February 25, 2016 08:55:40 AM you wrote:
> Hi,
> 
> Here is the output of "postconf -n | grep relay" :
> 
> relayhost =
> 
> Thank you for your help !

Do you have any relay map files in /etc/postfix/?  If you don't know, please 
provide a list of the files present in that directory.

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

Title:
  In some rare cases Postfix connect to a wrong MX server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1549388/+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

[Serge Hallyn]

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

** Changed in: qemu
   Status: In Progress => Fix Released

-- 
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 1524737] Re: systemd presents hugetblfs at /dev/hugepages

[Serge Hallyn]

** No longer affects: libvirt (Ubuntu Vivid)

-- 
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/1524737

Title:
  systemd presents hugetblfs at /dev/hugepages

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1524737/+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 1549363] Re: Unprivileged LXC will not start after today's updates

[Stéphane Graber]

That's very weird, all my xenial test systems show lxc-container-
default-cgns in the apparmor_status output

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

Title:
  Unprivileged LXC will not start after today's updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+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 1549363] Re: Unprivileged LXC will not start after today's updates

[William Grant]

I grabbed 2.0.0~rc3-0ubuntu2 before I wrote those comments, as I noticed
the cgfs changes. My last reboot was this morning, between upgrading to
-0ubuntu1 and -0ubuntu2, so I think the apparmor stuff is still broken.
The profile doesn't even appear if I explicitly apparmor_parser -r, -a,
-R in any combination, though --debug definitely shows it parsing that
file. It's very, very weird.

This is all with Linux 4.4.0-7, since I hadn't noticed 4.4.0-8 sitting
in -proposed. I might retry with that.

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

Title:
  Unprivileged LXC will not start after today's updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+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 1393842] Re: libvirt does not grant qemu-guest-agent channel perms

[Serge Hallyn]

Confirmed this has regressed in xenial

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

-- 
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/1393842

Title:
  libvirt does not grant qemu-guest-agent channel perms

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1393842/+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 1522422] Re: Update to php 7.0

[Colan Schwartz]

In response to #53, speaking for the Drupal community, I'd like to
report that we have Drupal 8 passing on PHP 7.  See
https://www.drupal.org/node/3060/qa for details.

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

Title:
  Update to php 7.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1522422/+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 1549347] Re: [FFe Requested] Please update nginx to 1.9.12

[Thomas Ward]

** Summary changed:

- Please update nginx to 1.9.12
+ [FFe Requested] Please update nginx to 1.9.12

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

Title:
  [FFe Requested] Please update nginx to 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+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 1549363] Re: Unprivileged LXC will not start after today's updates

[Stéphane Graber]

Hmm, does /etc/init.d/apparmor reload fix the profile not being loaded?

We've not been introducing new profiles very often and those profiles
are loaded through apparmor includes so I can certainly see a standard
dh_apparmor being confused by it and not reloading everything properly
on upgrade.

But forcing an apparmor reload or rebooting the machine sure should fix
that.

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

Title:
  Unprivileged LXC will not start after today's updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+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 1549363] Re: Unprivileged LXC will not start after today's updates

[Stéphane Graber]

As for the cgroups, we've noticed at least one issue in the cgfs logic
of LXC which was fixed earlier today, the package is still going through
QA (currently in proposed), should make it to the release pocket within
a couple of hours.

The fix was specifically to fix unprivileged but root-owned containers
failing to start due to using the wrong cgroup paths. I'm not sure if
that covers this bug's specific case. If it doesn't then we'll have to
look at this more closely.


Note that those regressions are showing up as a result of us removing cgmanager 
and switching to straight cgroupfs, things also got slightly more messy as that 
particular LXC change ended up landing right around the same time as the first 
cgns enabled kernel which also happened to be broken when used in unprivileged 
containers.

So what we know right now is:
 - lxc prior to 2.0.0~rc3-0ubuntu2 will fail to setup cgroups for unprivileged 
containers spawned by the root user, leading to container startup failures
 - linux prior to 4.4.0-8-generic will fail to mount cgroupfs inside 
unprivileged containers, leading to container starting up but pid1 immediately 
failing and no other processes getting spawned.

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

Title:
  Unprivileged LXC will not start after today's updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+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 1549363] Re: Unprivileged LXC will not start after today's updates

[William Grant]

lxc-container-default-cgns doesn't show up in apparmor_status, despite
the other three being there.

If I hack a container's config to use lxc-container-default rather than
lxc-container-default-cgns, hack that profile to allow cgfs, and start
that container, lxc-container-default-cgns shows up and other unmodified
containers can now start. Weird.

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

Title:
  Unprivileged LXC will not start after today's updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+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 1549363] Re: Unprivileged LXC will not start after today's updates

[William Grant]

The cgroup errors go away if I manually create and chown a few parent
cgroups, but then the apparmor error returns.

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

Title:
  Unprivileged LXC will not start after today's updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+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 1549363] Re: Unprivileged LXC will not start after today's updates

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Unprivileged LXC will not start after today's updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+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 1550004] [NEW] Missing Neutron Linux Bridge Cleanup init files (Upstart / SysV / Systemd)

[Thiago Martins]

Public bug reported:

Guys,

 The following files are missing from neutron-linuxbridge-agent package:

 /etc/init/neutron-linuxbridge-cleanup.conf
 /etc/init.d/neutron-linuxbridge-cleanup
 /lib/systemd/system/neutron-linuxbridge-cleanup.service

 I have manually created those files, using neutron-openvswitch-agent
files as an example, then, it worked.

 Otherwise, "service neutron-linuxbridge-agent start" fails.

Cheers!
Thiago

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

** Description changed:

  Guys,
  
-  The following files are missing from neutron-linuxbridge-agent package:
+  The following files are missing from neutron-linuxbridge-agent package:
  
-  /etc/init/neutron-linuxbridge-cleanup.conf
-  /etc/init.d/neutron-linuxbridge-cleanup
-  /lib/systemd/system/neutron-linuxbridge-cleanup.service
+  /etc/init/neutron-linuxbridge-cleanup.conf
+  /etc/init.d/neutron-linuxbridge-cleanup
+  /lib/systemd/system/neutron-linuxbridge-cleanup.service
  
-  I have manually created those files, using neutron-openvswitch-agent
+  I have manually created those files, using neutron-openvswitch-agent
  files as an example, then, it worked.
  
-  Otherwise, "service neutron-linux-agent start" fails.
+  Otherwise, "service neutron-linuxbridge-agent start" fails.
  
  Cheers!
  Thiago

-- 
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/1550004

Title:
  Missing Neutron Linux Bridge Cleanup init files (Upstart / SysV /
  Systemd)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1550004/+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 1549347] Re: Please update nginx to 1.9.12

[Thomas Ward]

** Summary changed:

- New nginx upstream release - 1.9.12
+ Please update nginx to 1.9.12

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

Title:
  Please update nginx to 1.9.12

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nginx/+bug/1549347/+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 1549403] Re: [FFe]: improvements and fixes to cloud-init networking

[Scott Moser]

** Description changed:

  Ubuntu cloud images have network information “hard coded” in
  /etc/network/interfaces (ENI). For cloud images, this configuration has
  always amounted to “dhcp on eth0”.  For MAAS images
  /etc/network/interfaces is a symlink to /run/network/dynamic-interfaces
  which is populated from within the initramfs by the cloud-initramfs-dyn-
  netconf package based on the result of ‘ip=’ parameters on the kernel
  command line.  Both of these networking configurations came from the
  initial use case for the image type.  For cloud-images, this was EC2 and
  for maas-images, the maas ephemeral environment.
  
  The ‘static’ nature of network configuration in these images makes the
  difficult to use for anything other than their original use case.  It
  also makes specific images required simply for networking configuration.
  
  Items to be fixed with in cloud-init are:
-  * remove need for xenial images to have persistent networking disabled
-  * allow easily disabling of cloud-init
-  * Defined and sane behavior on re-writing ENI
-  * Support single and multi-nic network info from  by openstack config-drive
-  * Support dynamic naming of single network device system
-  * MAAS / iscsi root with ip= but no symlink from ENI to 
/run/network/dyn-interfaces
-  * General Cloud-init ‘disable’ kernel command line.
-  * Cloud-localds support for configuring networking
+  * remove need for xenial images to have persistent networking disabled via 
kernel command line
+  * allow easy disabling of cloud-init via kernel command line or file in 
filesystem
+  * Defined and sane behavior on re-writing ENI
+  * Support single and multi-nic network info from  by openstack config-drive
+  * Support dynamic naming of single network device system
+  * MAAS / iscsi root with ip= but no symlink from ENI to 
/run/network/dyn-interfaces
+  * General Cloud-init ‘disable’ kernel command line.
+  * Cloud-localds support for configuring networking

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

Title:
  [FFe]: improvements and fixes to cloud-init networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1549403/+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 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

[Robie Basak]

Now built in xenial-proposed, so you can test from there.

-- 
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/1473691

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1549919] [NEW] neutron-server fails to use configured plugin configuration file

[James Page]

Public bug reported:

The neutron-server init script (also used by systemd units) fails to
source /etc/default/neutron-server before trying to configure the plugin
configuration file.

** Affects: neutron (Ubuntu)
 Importance: Critical
 Assignee: James Page (james-page)
 Status: In Progress

** Changed in: neutron (Ubuntu)
   Importance: Undecided => Critical

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

** Changed in: neutron (Ubuntu)
 Assignee: (unassigned) => James Page (james-page)

-- 
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/1549919

Title:
  neutron-server fails to use configured plugin configuration file

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/neutron/+bug/1549919/+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 1540401] multipath, fdisk, lsblk, sysctl -a output from lpar

[bugproxy]

Default Comment by Bridge

** Attachment added: "multipath, fdisk, lsblk, sysctl -a output from lpar"
   
https://bugs.launchpad.net/bugs/1540401/+attachment/4581048/+files/biglp1_logs.txt

-- 
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/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+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 1540401] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From mauri...@br.ibm.com 2016-02-25 12:18 EDT---
Hi @mathieu-tl,

(In reply to comment #69)
> It's on my list, yes.
>
> The idea however is that I haven't uploaded it because it is so annoying to
> test these patches from a PPA, I uploaded the changes for xenial to the
> archive for further testing since it looked like it worked sufficiently to
> not break too many use cases.

Ok. Thanks for the update.

If that helps, I've been testing that more manually, either installing
the packages at the end of the installation (cd /target/tmp && wget
<...>.deb && chroot /target dpkg -i /target/tmp/*.deb), or by installing
the packages after system is already installed (just manually fixing the
boot problem at initramfs time break=pre-multipath for example).

Regards.

--- Comment From mauri...@br.ibm.com 2016-02-25 12:21 EDT---
Correction:

-packages at the end of the installation (cd /target/tmp && wget <...>.deb &&
-chroot /target dpkg -i /target/tmp/*.deb),

+packages at the end of the installation (cd /target/tmp && wget <...>.deb &&
+chroot /target dpkg -i /tmp/*.deb),

BTW, if you have a chance, it'd be nice to have a Trusty 'affects' row
for tracking purposes. Otherwise it seems this is already resolved
(despite your comment).  Thanks.

-- 
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/1540401

Title:
  ISST-LTE: Ubuntu14.04.4 lpar fails to boot after installation: "The
  disk drive for /boot is not ready yet or not present"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540401/+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 1549436] Re: AppArmor kills StronSwan daemon 'charon'

[Simon Déziel]

On 2016-02-25 10:50 AM, ruslan_ka wrote:
> The server serves only incoming VPN requests, it is for mobile road-
> warriors. And the error does not  occur right after starting a
> strongswan or bringing tunnels up. So it makes no sense to run it with
> auto=add or not.

I somehow assumed it was an initiator (client) and not a responder
(server), sorry.

> Strongswan is serving clients ok. It is working for a long time until a
> first DENIAL. It looks like it is somehow related to reauthentication of
> xauth iOS client, but I can't reproduce it. Sometimes client can reauth
> ok, as I can see at logs, but sometimes  right after successful reauth I
> see this error. There are about 5 active clients right now with 20-30
> connections per/day, and server gives me an error once/twice per day. I
> would not even note it, if it'd not break accounting at radius.

I have no idea what can cause this access to /dev/tty. I never ran into
this problem on my own server which is similar minus the EAP/RADIUS
part, I use xauth-generic only.

> $ sudo cat /etc/ipsec.conf 
> # ipsec.conf - strongSwan IPsec configuration file
> 
> # basic configuration
> 
> config setup
>   strictcrlpolicy=yes
>   # uniqueids = no
> 
> # default options
> 
> conn %default
> ikelifetime=60m
> keylife=20m
> rekeymargin=3m
> keyingtries=1
> inactivity = 60s
> dpdaction = clear
> dpdtimeout = 5s
> dpddelay = 5s

Not related to the problem at hand but you generally don't want
dpdtimeout to be equal to dpddelay. Having them equal means that loosing
a single DPD packet will kill the tunnel and have the client reconnect.

With mobile client, occasional packet loss shouldn’t force the
connection to be re-established. You usually want to redial only after
loosing say 3 DPD packets. This better detects peers going offline or
being affected by more severe connectivity problems.

As such, I'd recommend something like this:

  dpdtimeout=15s
  dpddelay=5s

Also, keep in mind that a low dpddelay drains the clients' battery as it
keeps the radio transmitter active more often.

> # Add connections here.
> 
> conn ikev1-psk-xauth
> leftsubnet=0.0.0.0/0
> leftfirewall=yes
> leftid=@vpn.server.name
> leftauth=psk
> right=%any
> rightsourceip=10.0.0.0/9
> rightauth=psk
> rightauth2=xauth-eap
> auto=add
> 
> conn ikev2-with-eap
> keyexchange=ikev2
> leftsubnet=0.0.0.0/0
> leftfirewall=yes
> leftid="C=US, O=Server.name.co, OU=VPN Dept, CN=vpn.server.name, 
> E=ad...@server.name"
> leftauth=pubkey
> leftcert=vpn.server.name.pem
> right=%any
> rightsourceip=10.0.0.0/16
> rightsendcert=never
> rightauth=eap-radius
> eap_identity=%identity
> auto=add

Again, not related but aren't the 2 rightsourceip= overlapping?

> $ sudo cat /etc/strongswan.conf 
> # strongswan.conf - strongSwan configuration file
> 
> charon {
>   load_modular = yes
>   plugins {
>   include strongswan.d/charon/*.conf
>   }
>   dns1 = 8.8.8.8
> }
> 
> include strongswan.d/*.conf
> 
> 
> $ sudo cat /etc/strongswan.d/charon.conf | grep -v '^[[:space:]]*#'| grep .
> charon {
> crypto_test {
> }
> host_resolver {
> }
> leak_detective {
> }
> processor {
> priority_threads {
> }
> }
> tls {
> }
> x509 {
> }
> }
> 
> 
> $ sudo cat /etc/strongswan.d/charon/xauth-eap.conf  | grep -v 
> '^[[:space:]]*#'| grep .
> xauth-eap {
> backend = radius
> load = yes
> }
> 
> $ sudo cat /etc/strongswan.d/charon/eap-radius.conf   | grep -v 
> '^[[:space:]]*#'| grep .
> eap-radius {
> accounting = yes
> load = yes
> port = 1812
> secret = secret
> server = 127.0.0.1
> sockets = 1000
> dae {
> enable = yes
> listen = 0.0.0.0
> port = 3799
> secret = dae_secret
> }
> forward {
> }
> servers {
> }
> xauth {
> }
> }
> 

I honestly don't know why charon tries to access /dev/tty. Are you able
to see that message on the console or the upstart log when the Apparmor
profile is disabled?

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

Title:
  AppArmor kills StronSwan daemon 'charon'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1549436/+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 1544612] Re: Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

[Launchpad Bug Tracker]

This bug was fixed in the package pm-utils - 1.4.1-13ubuntu0.2

---
pm-utils (1.4.1-13ubuntu0.2) trusty-proposed; urgency=medium

  * 17-fix-wireless-hook.patch: Some drivers actually do have an "enable"
  attribute, so accept both "enable" and "enabled". Also invert the logic
  so that if neither attribute exists the device is considered enabled.
  (Closes: #773647, LP: #1544612)

 -- Martin Pitt   Mon, 15 Feb 2016 10:30:26
+0100

** Changed in: pm-utils (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1544612/+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 1544612] Update Released

[Brian Murray]

The verification of the Stable Release Update for pm-utils has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Missing fix for 1299975 claimed to be in pm-utils (1.4.1-13ubuntu0.1)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1544612/+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 1254085] Re: ssh fails to connect to VPN host - hangs at 'expecting SSH2_MSG_KEX_ECDH_REPLY'

[Rodney Beede]

Might be your PMTU discovery is being blocked by a firewall somewhere.

http://mccltd.net/blog/?p=1577

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

Title:
  ssh fails to connect to VPN host - hangs at 'expecting
  SSH2_MSG_KEX_ECDH_REPLY'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1254085/+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 1503611] Re: systemd: spamassassin not starting after upgrading to 15.04

[Tony Middleton]

I think there might be two separate things here.

I've just had the same problem with a Debian system with spamassassin
not loading at boot time.  My "systemctl status" was similar to the
above ie "disabled".  "systemctl enable" didn't start the service but
changed the status to enabled and gave output as above.  "systemctl
start" started the service OK and it now starts at boot.

The second post above refers to a different problem which looks like it
is covered by the bug mentioned.

-- 
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/1503611

Title:
  systemd: spamassassin not starting after upgrading to 15.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/spamassassin/+bug/1503611/+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 1549403] Re: [FFe]: improvements and fixes to cloud-init networking

[Scott Moser]

** Summary changed:

- FFE: improvements and fixes to cloud-init networking
+ [FFe]: improvements and fixes to cloud-init networking

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

Title:
  [FFe]: improvements and fixes to cloud-init networking

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1549403/+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 1549436] Re: AppArmor kills StronSwan daemon 'charon'

[ruslan_ka]

The server serves only incoming VPN requests, it is for mobile road-
warriors. And the error does not  occur right after starting a
strongswan or bringing tunnels up. So it makes no sense to run it with
auto=add or not.

Strongswan is serving clients ok. It is working for a long time until a
first DENIAL. It looks like it is somehow related to reauthentication of
xauth iOS client, but I can't reproduce it. Sometimes client can reauth
ok, as I can see at logs, but sometimes  right after successful reauth I
see this error. There are about 5 active clients right now with 20-30
connections per/day, and server gives me an error once/twice per day. I
would not even note it, if it'd not break accounting at radius.

If ipsec runs at debug mode at console (--nofork) I don't get this
error.


$ sudo cat /etc/ipsec.secrets 
# This file holds shared secrets or RSA private keys for authentication.

: RSA  vpn.server.name.pem
vpn.server.name: PSK "simpletestpsk"


$ sudo cat /etc/ipsec.conf 
# ipsec.conf - strongSwan IPsec configuration file

# basic configuration

config setup
strictcrlpolicy=yes
# uniqueids = no

# default options

conn %default
ikelifetime=60m
keylife=20m
rekeymargin=3m
keyingtries=1
inactivity = 60s
dpdaction = clear
dpdtimeout = 5s
dpddelay = 5s


# Add connections here.

conn ikev1-psk-xauth
leftsubnet=0.0.0.0/0
leftfirewall=yes
leftid=@vpn.server.name
leftauth=psk
right=%any
rightsourceip=10.0.0.0/9
rightauth=psk
rightauth2=xauth-eap
auto=add

conn ikev2-with-eap
keyexchange=ikev2
leftsubnet=0.0.0.0/0
leftfirewall=yes
leftid="C=US, O=Server.name.co, OU=VPN Dept, CN=vpn.server.name, 
E=ad...@server.name"
leftauth=pubkey
leftcert=vpn.server.name.pem
right=%any
rightsourceip=10.0.0.0/16
rightsendcert=never
rightauth=eap-radius
eap_identity=%identity
auto=add


$ sudo cat /etc/strongswan.conf 
# strongswan.conf - strongSwan configuration file

charon {
load_modular = yes
plugins {
include strongswan.d/charon/*.conf
}
dns1 = 8.8.8.8
}

include strongswan.d/*.conf


$ sudo cat /etc/strongswan.d/charon.conf | grep -v '^[[:space:]]*#'| grep .
charon {
crypto_test {
}
host_resolver {
}
leak_detective {
}
processor {
priority_threads {
}
}
tls {
}
x509 {
}
}


$ sudo cat /etc/strongswan.d/charon/xauth-eap.conf  | grep -v '^[[:space:]]*#'| 
grep .
xauth-eap {
backend = radius
load = yes
}

$ sudo cat /etc/strongswan.d/charon/eap-radius.conf   | grep -v 
'^[[:space:]]*#'| grep .
eap-radius {
accounting = yes
load = yes
port = 1812
secret = secret
server = 127.0.0.1
sockets = 1000
dae {
enable = yes
listen = 0.0.0.0
port = 3799
secret = dae_secret
}
forward {
}
servers {
}
xauth {
}
}

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

Title:
  AppArmor kills StronSwan daemon 'charon'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1549436/+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 1540407] Re: multipathd drops paths of a temporarily lost device

[Ryan Harper]

Hi Thorsten,

Thanks for the update.  I'll attempt to find out if I can force a detach
on the host-side to recreate the issue on x86 while I'm waiting for a Z
system with FCP devices.

Could you attempt to use the Debian package from Sid on top of the
Ubuntu system?  This will help rule out kernel related issues vs.
userspace package bugs.

You can download from here

http://ftp.us.debian.org/debian/pool/main/m/multipath-tools/multipath-
tools_0.5.0+git1.656f8865-4_s390x.deb

And then force install with

sudo dpkg --force all --install multipath-
tools_0.5.0+git1.656f8865-4_s390x.deb

If this is successful, then I can prepare a package with some updated
fixes from upstream; there are a number of changes to path related
discovery in upstream multipath that aren't yet included in the Ubuntu
version.

-- 
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/1540407

Title:
  multipathd drops paths of a temporarily lost device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540407/+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 1549363] Re: Unprivileged LXC will not start after today's updates

[Christopher Townsend]

After the latest lxc updates (2.0.0~rc3-0ubuntu1), a new failure is now
occurring.  See attached debug log.

** Attachment added: "start_lxc.out"
   
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+attachment/4580930/+files/start_lxc.out

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

Title:
  Unprivileged LXC will not start after today's updates

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1549363/+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 1540407] Comment bridged from LTC Bugzilla

[bugproxy]

--- Comment From thorsten.di...@de.ibm.com 2016-02-25 06:05 EDT---
Hi Ryan,

on the most recent repro I already had version: 0.5.0-7ubuntu14 - same symptom.
With
# echo "offline" > /sys/class/block/sdb/device/state
I could not reproduce this symptom on z Systems.

Approved repro is as follows:
z Systems LPAR: chchp -c 0 ;sleep 30;chchp -c 1 
z Systems z/VM guest: vmcp det ;sleep 30;vmcp att  "*"

-- 
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/1540407

Title:
  multipathd drops paths of a temporarily lost device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/multipath-tools/+bug/1540407/+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 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

[Robie Basak]

In the meantime, if others could please test from my PPA above, that
would be helpful to inform us about removing block-proposed and help get
this migrated to the release pocket.

** Changed in: squid3 (Ubuntu)
   Status: In Progress => Fix Committed

-- 
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/1473691

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

[Robie Basak]

Uploaded to xenial-proposed. This will dep-wait on libecap3 NEW though,
and libecap will also FTBFS on 32-bit architectures currently, pending a
symbols file fixup.

-- 
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/1473691

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1549436] Re: AppArmor kills StronSwan daemon 'charon'

[Simon Déziel]

If you re-enable the Apparmor profile and set your connection to not
auto start (use "auto=add") when do you get the access denial on
/dev/tty? Is it after restarting the strongswan service or when you call
"ipsec up $conn"?

Lastly, would you mind providing an obfuscated version of your
ipsec.secrets and ipsec.conf?

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

Title:
  AppArmor kills StronSwan daemon 'charon'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1549436/+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 1330486] Re: strongSwan AppArmor profile doesn't allow smartcard configuration

[Simon Déziel]

@caramba696, smartcard should be improved in Xenial so you might want to
re-test.

The Apparmor profile allows charon to access /run/pcscd/pcscd.comm and
also include other rules related to smartcards.

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

Title:
  strongSwan AppArmor profile doesn't allow smartcard configuration

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/strongswan/+bug/1330486/+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 1171970] Re: Enable tmux bash completion by default

[Mikko Pesari]

Hey, any possibility to get this fixed in Xenial?

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

Title:
  Enable tmux bash completion by default

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tmux/+bug/1171970/+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 1549789] [NEW] Updated walinuxagent to 2.0.16

[Ben Howard]

Public bug reported:

WALinuxAgent has a new up release for 2.0.16.

Github Release: https://github.com/Azure/WALinuxAgent/releases/tag/v2.0.16
Changelog:
Add timeout for http request
Handle http 410 when reporting health
Fix plugin version comparison
Change swap file permission to 0600
Add retry on restarting network interface
Add retry on environment detection
Add log for status report
Copy status files from old plugin dir to new during upgrade
Remove old plugin dir after upgrade

** Affects: walinuxagent (Ubuntu)
 Importance: High
 Assignee: Ben Howard (utlemming)
 Status: In Progress

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

Title:
  Updated walinuxagent to 2.0.16

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1549789/+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 1549788] [NEW] bind9 9.10.3.dfsg.P2-4 crash on exit

[Xu Zhen]

Public bug reported:

systemctl stop bind9.service
journalctl -u bind9 -n 15

Feb 25 20:36:07 ubuntu named[6778]: zone 255.in-addr.arpa/IN: loaded serial 1
Feb 25 20:36:07 ubuntu named[6778]: all zones loaded
Feb 25 20:36:07 ubuntu named[6778]: running
Feb 25 20:36:12 ubuntu systemd[1]: Stopping BIND Domain Name Server...
Feb 25 20:36:12 ubuntu named[6778]: received control channel command 'stop'
Feb 25 20:36:12 ubuntu named[6778]: shutting down: flushing changes
Feb 25 20:36:12 ubuntu named[6778]: stopping command channel on 127.0.0.1#953
Feb 25 20:36:12 ubuntu named[6778]: stopping command channel on ::1#953
Feb 25 20:36:12 ubuntu named[6778]: no longer listening on 127.0.0.1#53
Feb 25 20:36:12 ubuntu named[6778]: exiting
Feb 25 20:36:12 ubuntu named[6778]: ../../../lib/isc/mem.c:1229: 
REQUIRE(ctx->references == 1) failed
Feb 25 20:36:12 ubuntu systemd[1]: bind9.service: Main process exited, 
code=dumped, status=6/ABRT
Feb 25 20:36:12 ubuntu systemd[1]: Stopped BIND Domain Name Server.
Feb 25 20:36:12 ubuntu systemd[1]: bind9.service: Unit entered failed state.
Feb 25 20:36:12 ubuntu systemd[1]: bind9.service: Failed with result 
'core-dump'.

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

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

Title:
  bind9 9.10.3.dfsg.P2-4 crash on exit

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/1549788/+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 1549778] [NEW] ceph 0.94.6

[James Page]

Public bug reported:

This Hammer point release fixes a range of bugs, most notably a fix for
unbounded growth of the monitor’s leveldb store, and a workaround in the
OSD to keep most xattrs small enough to be stored inline in XFS inodes.

We recommend that all hammer v0.94.x users upgrade.

For more detailed information, see the complete changelog:

  http://docs.ceph.com/docs/master/_downloads/v0.94.6.txt

Notable Changes
---

* build/ops: Ceph daemon failed to start, because the service name was already 
used. (#13474, Chuanhong Wang)
* build/ops: LTTng-UST tracing should be dynamically enabled (#13274, Jason 
Dillaman)
* build/ops: ceph upstart script rbdmap.conf incorrectly processes parameters 
(#13214, Sage Weil)
* build/ops: ceph.spec.in License line does not reflect COPYING (#12935, Nathan 
Cutler)
* build/ops: ceph.spec.in libcephfs_jni1 has no %post and %postun  (#12927, 
Owen Synge)
* build/ops: configure.ac: no use to add "+" before ac_ext=c (#14330, Kefu 
Chai, Robin H. Johnson)
* build/ops: deb: strip tracepoint libraries from Wheezy/Precise builds 
(#14801, Jason Dillaman)
* build/ops: init script reload doesn't work on EL7 (#13709, Hervé Rousseau)
* build/ops: init-rbdmap uses distro-specific functions (#12415, Boris Ranto)
* build/ops: logrotate reload error on Ubuntu 14.04 (#11330, Sage Weil)
* build/ops: miscellaneous spec file fixes (#12931, #12994, #12924, #12360, 
Boris Ranto, Nathan Cutler, Owen Synge, Travis Rhoden, Ken Dreyer)
* build/ops: pass tcmalloc env through to ceph-os (#14802, Sage Weil)
* build/ops: rbd-replay-* moved from ceph-test-dbg to ceph-common-dbg as well 
(#13785, Loic Dachary)
* build/ops: unknown argument --quiet in udevadm settle (#13560, Jason Dillaman)
* common: Objecter: pool op callback may hang forever. (#13642, xie xingguo)
* common: Objecter: potential null pointer access when do pool_snap_list. 
(#13639, xie xingguo)
* common: ThreadPool add/remove work queue methods not thread safe (#12662, 
Jason Dillaman)
* common: auth/cephx: large amounts of log are produced by osd (#13610, Qiankun 
Zheng)
* common: client nonce collision due to unshared pid namespaces (#13032, Josh 
Durgin)
* common: common/Thread:pthread_attr_destroy(thread_attr) when done with it 
(#12570, Piotr Dałek)
* common: log: Log.cc: Assign LOG_DEBUG priority to syslog calls (#13993, Brad 
Hubbard)
* common: objecter: cancellation bugs (#13071, Jianpeng Ma)
* common: pure virtual method called (#13636, Jason Dillaman)
* common: small probability sigabrt when setting rados_osd_op_timeout (#13208, 
Ruifeng Yang)
* common: wrong conditional for boolean function KeyServer::get_auth() (#9756, 
#13424, Nathan Cutler)
* crush: crash if we see CRUSH_ITEM_NONE in early rule step (#13477, Sage Weil)
* doc: man: document listwatchers cmd in "rados" manpage (#14556, Kefu Chai)
* doc: regenerate man pages, add orphans commands to radosgw-admin(8) (#14637, 
Ken Dreyer)
* fs: CephFS restriction on removing cache tiers is overly strict (#11504, John 
Spray)
* fs: fsstress.sh fails (#12710, Yan, Zheng)
* librados: LibRadosWatchNotify.WatchNotify2Timeout (#13114, Sage Weil)
* librbd: ImageWatcher shouldn't block the notification thread (#14373, Jason 
Dillaman)
* librbd: diff_iterate needs to handle holes in parent images (#12885, Jason 
Dillaman)
* librbd: fix merge-diff for >2GB diff-files (#14030, Jason Dillaman)
* librbd: invalidate object map on error even w/o holding lock (#13372, Jason 
Dillaman)
* librbd: reads larger than cache size hang (#13164, Lu Shi)
* mds: ceph mds add_data_pool check for EC pool is wrong (#12426, John Spray)
* mon: MonitorDBStore: get_next_key() only if prefix matches (#11786, Joao 
Eduardo Luis)
* mon: OSDMonitor: do not assume a session exists in send_incremental() 
(#14236, Joao Eduardo Luis)
* mon: check for store writeablility before participating in election (#13089, 
Sage Weil)
* mon: compact full epochs also (#14537, Kefu Chai)
* mon: include min_last_epoch_clean as part of PGMap::print_summary and 
PGMap::dump (#13198, Guang Yang)
* mon: map_cache can become inaccurate if osd does not receive the osdmaps 
(#10930, Kefu Chai)
* mon: should not set isvalid = true when cephx_verify_authorizer return false 
(#13525, Ruifeng Yang)
* osd: Ceph Pools' MAX AVAIL is 0 if some OSDs' weight is 0 (#13840, Chengyuan 
Li)
* osd: FileStore calls syncfs(2) even it is not supported (#12512, Kefu Chai)
* osd: FileStore: potential memory leak if getattrs fails. (#13597, xie xingguo)
* osd: IO error on kvm/rbd with an erasure coded pool tier (#12012, Kefu Chai)
* osd: OSD::build_past_intervals_parallel() shall reset primary and up_primary 
when begin a new past_interval. (#13471, xiexingguo)
* osd: ReplicatedBackend: populate recovery_info.size for clone (bug symptom is 
size mismatch on replicated backend on a clone in scrub) (#12828, Samuel Just)
* osd: ReplicatedPG: wrong result code checking logic during sparse_read 
(#14151, xie xingguo)
* osd: 

[Bug 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

[Robie Basak]

11:26  Laney: thank you for responding to bug 1473691. I have notes to 
test against squidguard, squid-deb-proxy and to check upgrade paths more 
throroughly. Would you prefer that I do this before upload?
11:26  bug 1473691 in squid3 (Ubuntu) "[FFe] squid: Update to latest 
upstream release (3.5)" [Wishlist,In progress] 
https://launchpad.net/bugs/1473691
11:26  Apart from that it's ready - no known issues.
11:27  The disadvantage presumably is that nobody else can also test 
until I've uploaded.
11:27  (easily)
11:27  rbasak: You could upload and then block in proposed until you've 
done
11:27  Up to you
11:27  That sounds like a good plan. I'll do that, thanks.


** Tags added: block-proposed

-- 
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/1473691

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1473691] Re: [FFe] squid: Update to latest upstream release (3.5)

[Iain Lane]

On Wed, Feb 24, 2016 at 04:48:38PM -, Robie Basak wrote:
> @Release Team, may I have a review of the FFe request please?
> 
> Proposed merge ready in ppa:racb/experimental, version ~dev5. git tree
> with detailed Ubuntu delta at
> https://git.launchpad.net/~racb/ubuntu/+source/squid3/log/?h=merge
> 
> I will test the upgrade paths again but I believe they're all working
> correctly now.

Are you ready to upload now?

It's still quite early, so go ahead. I think I would be optimally happy
if this were added to manual milestone testing so that QA people (or
whoever) check that squid works/upgrades/etc - but I'll leave that point
to you.

Cheers,

-- 
Iain Lane  [ i...@orangesquash.org.uk ]
Debian Developer   [ la...@debian.org ]
Ubuntu Developer   [ la...@ubuntu.com ]

-- 
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/1473691

Title:
  [FFe] squid: Update to latest upstream release (3.5)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/1473691/+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 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.

[Colin Watson]

Please can you provide as much information as you have?  For example,
"the ctl status is failed 255" is clearly a paraphrase of something that
you're seeing; it would be more useful if you could please copy and
paste the original text of the error messages.

Forum research is probably leading you up entirely the wrong path; that
sounds like information that predates systemd.  The ssh.service unit has
"After=network.target".

"journalctl -u sshd" won't find anything because that's not what the
unit is called.  Try "journalctl -u ssh".

** Changed in: openssh (Ubuntu)
   Status: New => Incomplete

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

Title:
  ssh will not start at boot:  systemctl status ssh -> output is listed
  as failed 255.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+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 1435709] Re: mysql.service fail to start after upgrade to mysql-server.5.6

[ravi sharma]

** Changed in: mysql-5.6 (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  mysql.service fail to start after upgrade to mysql-server.5.6

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1435709/+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 1549388] Re: In some rare cases Postfix connect to a wrong MX server

[Msd]

Hi,

Here is the output of "postconf -n | grep relay" :

relayhost =

Thank you for your help !

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

Title:
  In some rare cases Postfix connect to a wrong MX server

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1549388/+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 1549672] [NEW] Default config files don't match postfix 3

[ChristianEhrhardt]

Public bug reported:

With the recent merge to postfix 3 there were quite some changes to its 
configuration.
Now postfix has a lot to handle those changes in a compatible way so that old 
configurations should transfer to postfix 3 as good as possible.

In case any incompatibilities occur it reports that in the log and
refers to http://www.postfix.org/COMPATIBILITY_README.html to handle
them.

While all that is great for anyone migrating from an old system with any
kind of custom config, there is not much sense in throwing all these
messages out at someone that just freshly installed it.

To Reproduce just:
apt-get remove --purge postfix
apt-get install postfix

in /var/log/mail.log:
Feb 24 11:08:35 lap postfix[25109]: Postfix is running with 
backwards-compatible default settings
Feb 24 11:08:35 lap postfix[25109]: See 
http://www.postfix.org/COMPATIBILITY_README.html for details
Feb 24 11:08:35 lap postfix[25109]: To disable backwards compatibility use 
"postconf compatibility_level=2" and "postfix reload"
Feb 24 11:08:35 lap postfix/master[24994]: reload -- version 3.0.4, 
configuration /etc/postfix
Feb 24 11:08:35 lap postfix/master[24994]: /etc/postfix/master.cf: line 12: 
using backwards-compatible default setting chroot=y
[...] there are more like those

So overall I'd suggest we deliver default configuration files that match
a valid (not only due to backward compatibility) postfix 3
configuration.

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

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

Title:
  Default config files don't match postfix 3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1549672/+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 1522319] Re: package samba-common 2:4.1.17+dfsg-4ubuntu3 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package samba-common 2:4.1.17+dfsg-4ubuntu3 failed to install/upgrade:
  le sous-processus script post-installation installé a retourné une
  erreur de sortie d'état 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1522319/+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 1549136] Re: Move "lxc" dependencies to "lxc1"

[Launchpad Bug Tracker]

This bug was fixed in the package lxc - 2.0.0~rc3-0ubuntu1

---
lxc (2.0.0~rc3-0ubuntu1) xenial; urgency=medium

  * New upstream release (2.0.0~rc3)
- Make the cgfs backend and cgns work without cgmanager
- Manpage updates
- Mark lxc-clone and lxc-start-ephemeral deprecated (still included)
  * Set --enable-deprecated so we still ship lxc-clone and lxc-start-ephemeral

 -- Stéphane Graber   Wed, 24 Feb 2016 21:16:50
-0500

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

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

Title:
  Move "lxc" dependencies to "lxc1"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1549136/+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 1492186] Re: [MIR] dpdk

[Launchpad Bug Tracker]

This bug was fixed in the package openvswitch -
2.5.0~git20160219.522aca6-0ubuntu2

---
openvswitch (2.5.0~git20160219.522aca6-0ubuntu2) xenial; urgency=medium

  * [9c970b06] d/rules,*.manpages,*.install: Prepare for dual build.
  * [f7dff3e7] DPDK enablement (LP: #1492186):
- d/p/system-dpdk.patch: Pick patch from openvswitch-dpdk to
  support use with libdpdk-dev.
- d/control: Add DPDK dependencies for supported archs.
- d/rules: Build DPDK enabled binaries for supported archs.
- d/openvswitch-switch.p*: Install ovs-vswitch-dpdk binary as an
  alternative.
- d/openvswitch-switch.README.Debian: Let users know how to use
  the DPDK binary.

 -- James Page   Wed, 24 Feb 2016 21:44:41 +

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

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

Title:
  [MIR] dpdk

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dpdk/+bug/1492186/+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