[Bug 2039342] Re: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Brian Candler]

Additional info: in my case, the cause of the file going missing is
something to do with incus image publishing. Details:

https://discuss.linuxcontainers.org/t/file-goes-missing-during-image-
publish-usr-lib-x86-64-linux-gnu-dhcpcd-dev-udev-so/19969

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039342

Title:
  package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 2039342] Re: package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Brian Candler]

I am getting the same error with Ubuntu 24.04, but a different file from
dhcpcd-base was missing.

With set -x in /usr/share/initramfs-tools/hooks/dhcpcd:

...
+ grep ^dhcpcd: /etc/passwd
+ ldd /usr/sbin/dhcpcd
+ sed -En s;^.*/lib(/lib[^/]*prof)?/([^/]+)/libc\.so\..*$;\2;p
+ multiarch_dir=x86_64-linux-gnu
+ copy_exec /usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so
+ local src target x nonoptlib ret
+ src=/usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so
+ target=/usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so
+ copy_file binary /usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so 
/usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so
+ local type src target link_target
+ type=binary
+ src=/usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so
+ target=/usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so
+ [ -f /usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so ]
+ return 2
+ return 1
E: /usr/share/initramfs-tools/hooks/dhcpcd failed with return 1.
update-initramfs: failed for /boot/initrd.img-6.8.0-31-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

Checking:

# ls /usr/lib/x86_64-linux-gnu/dhcpcd/dev
# dpkg-query -S /usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so
dhcpcd-base: /usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so
# dpkg -V dhcpcd-base
missing /usr/lib/x86_64-linux-gnu/dhcpcd/dev/udev.so
#

And as before,

apt install --reinstall dhcpcd-base

fixes the problem. But I don't know why or how this file got deleted in
the first place.

Workaround for a scripted install:

if dpkg -V dhcpcd-base | grep missing; then
  apt install --yes --reinstall dhcpcd-base
fi

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2039342

Title:
  package linux-image-6.5.0-1005-raspi 6.5.0-1005.7 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1693361] Re: cloud-init sometimes fails on dpkg lock due to concurrent apt-daily.service execution

[Brian Candler]

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1693361

Title:
  cloud-init sometimes fails on dpkg lock due to concurrent apt-
  daily.service execution

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805625] Re: wpasupplicant package does not include eapol_test

[Brian Candler]

Should have said: available in Ubuntu since 21.04

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805625

Title:
  wpasupplicant package does not include eapol_test

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805625] Re: wpasupplicant package does not include eapol_test

[Brian Candler]

Update: it looks like Debian made a separate package "eapoltest" and
this has been available in Ubuntu since 20.10.

Unfortunately it did not arrive in time for 20.04, and the hirsute package 
requires a newer libc so can't be installed on focal - you still have to build 
yourself.
https://unix.stackexchange.com/questions/684349/how-to-install-eapol-test-in-ubuntu

Still, this problem should be closed once 22.04 is out.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805625

Title:
  wpasupplicant package does not include eapol_test

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 849416]

[Brian Candler]

> thanks for the explanations, I would have never thought that the small
black triangle was something clickable.

Me neither.  Bug 1742101 is now dealing with this usability issue.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/849416

Title:
  text/calendar attachments are not shown at all

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 849416]

[Brian Candler]

It's at the top of the body of the mail, just below the screenshot you
showed:

|> (Person Name) has invited you to (Meeting Name)

There is a small black triangle next to "Person Name".  The usability
bug is that it shouldn't be necessary to point this out :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/849416

Title:
  text/calendar attachments are not shown at all

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 849416]

[Brian Candler]

I didn't realise until now that the event details were folded away, and
became visible if the arrow is clicked.  Thank you, this is awesome!  It
would be more awesome if it was open by default - but I don't know if
this is Thunderbird's rendering of an ics file, or something controlled
by Microsoft's HTML/CSS.

Getting invites from Office365: "View Message Body > All Body Parts"
didn't show the event details, and "View Message Source" just showed a
bunch of base64-encoded junk.  So I wasn't able to see the event details
at all, until I learned the click-to-expand trick.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/849416

Title:
  text/calendar attachments are not shown at all

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936407] Re: socat bug with SSL "file transfers"

[Brian Candler]

** Summary changed:

- socat bug with SSL "filte transfers"
+ socat bug with SSL "file transfers"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936407

Title:
  socat bug with SSL "file transfers"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1936407] Re: socat bug with SSL "filte transfers"

[Brian Candler]

In the socat git repository, if you diff tag 1.7.4.0 to 1.7.4.1, you see
this:

+Corrections:
+   Socat 1.7.4.0 failed to compile especially on 32 bit systems.
+   Thanks to Wang Mingyu and others for sending a patch or reporting this
+   issue.
+
+   Under certain conditions OpenSSL stream connections, in particular bulk
+   data transfer in unidirectional mode, failed during transfer or near
+   its with Connection reset by peer on receiver side.
+   This happened with Socat versions 1.7.3.3 to 1.7.4.0. Reasons were
+   lazy SSL shutdown handling on the sender side in combination with
+   SSL_MODE_AUTO_RETRY turned off.
+   Fix: After SSH_shutdown but before socket shutdown call SSL_read()
+   Test: OPENSSL_STREAM_TO_SERVER
+   Fixes Red Hat issue 1870279.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1936407

Title:
  socat bug with SSL "filte transfers"

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


-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1875475] Re: Unison from Ubuntu 20.04 is incompatible with Unison from Ubuntu 18.04, Windows or Mac OS X

[Brian Candler]

The snap package isn't compatible with the version from macOS homebrew
either.

In the end, I just went with the binary tarballs available from
https://github.com/bcpierce00/unison/releases

The reason for these incompatibilities is described here:
https://github.com/bcpierce00/unison/#getting-unison

"Beware that Unison uses OCaml's built-in data marshalling, and that
this facility is unstable across versions of "ocaml" (the standard
implementation of the OCaml language). Additionally, Unison has
incompatible changes across minor releases (e.g. 2.48 vs 2.51, but
2.51.2 and 2.51.3 are compatible). Therefore, you must use the same
Unison minor version built with the same ocaml version on all systems."

To make compatible packages for 16.04/18.04/20.04 would require either a
newer OCaml to build the 16.04/18.04 packages, or an older OCaml to
build the 18.04/20.04 packages.

I do think that the incompatible versions should be reflected in the
package naming, e.g. "unison" is a meta-package and
"unison-2.51.3-4.12.0" is the actual package. Then potentially multiple
versions could be installed and /etc/alternatives/unison could point to
the chosen one.  But unless someone actually builds these different
versions, it doesn't really matter.

There are other more modern filesystem synchronization tools available,
like Syncthing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875475

Title:
  Unison from Ubuntu 20.04 is incompatible with Unison from Ubuntu
  18.04, Windows or Mac OS X

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1922070] [NEW] mdraid: /dev/md directory no longer exists

[Brian Candler]

Public bug reported:

In Ubuntu 20.04 (kernel 5.4.0), the /dev/md directory which contains
/dev/md/ links apparently no longer exists.

# ls -l /dev/md*
brw-rw 1 root disk 9, 127 Mar 31 08:46 /dev/md127
# 

Compare to an 18.04 system:

$ ls -l /dev/md*
brw-rw 1 root disk 9, 0 Mar 26 08:01 /dev/md0
brw-rw 1 root disk 9, 1 Mar 26 08:01 /dev/md1

/dev/md:
total 0
lrwxrwxrwx 1 root root 6 Mar 26 08:01 0 -> ../md0
lrwxrwxrwx 1 root root 6 Mar 26 08:01 1 -> ../md1

I've confirmed this is also the case with Debian 10 (also 5.4.0), so it
appears to have been an upstream change.  It might be in udev/devtmpfs
or the kernel itself, I don't know which.

However the md(4) manpage still says that it exists:

SYNOPSIS
   /dev/mdn
   /dev/md/n
   /dev/md/name

There are scripts which depend on the /dev/md/n or /dev/md/name link,
e.g. https://github.com/prometheus-community/node-exporter-textfile-
collector-scripts/issues/92, so arguably this is a regression.  I'm OK
with it going, but I think the manpage should be updated to reflect this
change.

WORKAROUND: switch to using /dev/disk/by-id/md-name-.

# find /dev -lname '*md*'
/dev/log
/dev/disk/by-uuid/f36588df-7e7f-446a-9be4-c0c6d092dcf4
/dev/disk/by-id/md-name-CORE-ELASTIC-VM1:127
/dev/disk/by-id/md-uuid-f6641f8b:65b425e9:298e0ac2:b6c3c83e
/dev/block/9:127
# find /dev -lname '*md*' | xargs ls -l
lrwxrwxrwx 1 root root  8 Mar 31 08:46 /dev/block/9:127 -> ../md127
lrwxrwxrwx 1 root root 11 Mar 31 08:46 
/dev/disk/by-id/md-name-CORE-ELASTIC-VM1:127 -> ../../md127
lrwxrwxrwx 1 root root 11 Mar 31 08:46 
/dev/disk/by-id/md-uuid-f6641f8b:65b425e9:298e0ac2:b6c3c83e -> ../../md127
lrwxrwxrwx 1 root root 11 Mar 31 08:46 
/dev/disk/by-uuid/f36588df-7e7f-446a-9be4-c0c6d092dcf4 -> ../../md127
lrwxrwxrwx 1 root root 28 Mar 31 08:46 /dev/log -> /run/systemd/journal/dev-log


Note that the  is typically :, and even on older 
systems which have /dev/md/ the  may be different to /dev/md/.

** Affects: ubuntu
 Importance: Undecided
 Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922070

Title:
  mdraid: /dev/md directory no longer exists

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587204] Re: Spams motd with "proxy ... looks invalid"

[Brian Candler]

Correction: the "Failed to connect..." message appears on stdout anyway,
so it *does* persist.

So as a second change, I suggest that /usr/lib/ubuntu-release-upgrader
/release-upgrade-motd should capture the stderr as well, by adding
"2>&1" before "&"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587204

Title:
  Spams motd with "proxy ... looks invalid"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1587204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1587204] Re: Spams motd with "proxy ... looks invalid"

[Brian Candler]

I am also getting this with 18.04.5 LTS.  In /etc/apt/apt.conf.d/99proxy
I have:

Acquire::http::Proxy "http://127.0.0.1:3142/;;
Acquire::https::Proxy "DIRECT";

and sometimes the the motd displays

proxy 'DIRECT' looks invalid

I have discovered why it's intermittent: that text is the *stderr*
output from /usr/lib/ubuntu-release-upgrader/check-new-release -q

This means it doesn't get stored in /var/lib/ubuntu-release-upgrader
/release-upgrade-available, because only the *stdout* is redirected
there.

Therefore, it only gets displayed at login time when /usr/lib/ubuntu-
release-upgrader/release-upgrade-motd is run, and this only performs the
check if its previous output is more than 1 day old.

I also note that the script runs "check-new-release -q" in the
background (with &), which means that its stderr output could in
principle appear later on and be mixed up with other output. Perhaps
this is intentional, so that messages like "Failed to connect to
https://changelogs.ubuntu.com/meta-release-lts. Check your Internet
connection or proxy settings" don't persist in the motd.

But in any case, "DIRECT" is a documented and valid form for proxy, so
it should not generate any warning.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587204

Title:
  Spams motd with "proxy ... looks invalid"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/1587204/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM

[Brian Candler]

Seeing this on bare metal (Dell R740xd) with Ubuntu 18.04 and linux-
image-generic-hwe-18.04 (5.3.0-62-generic)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820063

Title:
  [Hyper-V] KVP daemon fails to start on first boot of disco VM

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1779401] Re: Cacti 1.1.38 fails to display graphs and acts erratically

[Brian Candler]

SNMP data collection is also broken in the Ubuntu 18.04 cacti package

https://github.com/Cacti/cacti/issues/1634
https://github.com/Cacti/cacti/commit/32f1538a4a382b7b27e2340705e9b034f335ae6e
https://github.com/Cacti/cacti/commit/afa01553f574554f782bbed3d2f1efaa355df2d0
https://github.com/Cacti/cacti/commit/9311987e8a22e9c838bc879ff8eceae7abfbeb65

diff to /usr/share/cacti/site:

--- a/lib/snmp.php
+++ b/lib/snmp.php
@@ -74,6 +74,7 @@ function cacti_snmp_session($hostname, $community, $version, 
$auth_user, $auth_p
$session->valueretrieval = SNMP_VALUE_LIBRARY;
}

+   $session->quick_print = false;
$session->max_oids = $max_oids;

if (read_config_option('oid_increasing_check_disable') == 'on') {
--- a/cmd.php   2020-06-13 08:45:09.660470210 +
+++ b/cmd.php   2020-06-13 08:59:50.586094241 +
@@ -504,8 +504,7 @@


if 
(isset($sessions[$host_id . '_' . $item['snmp_version'] . '_' . 
$item['snmp_port']])) {
-   
$sessions[$host_id . '_' . $item['snmp_version'] . '_' . 
$item['snmp_port']]->quick_print = true;
-   $output = 
cacti_snmp_session_get($sessions[$host_id . '_' . $item['snmp_version'] . '_' . 
$item['snmp_port']], $index_item['arg1'], true);
+   $output = 
cacti_snmp_session_get($sessions[$host_id . '_' . $item['snmp_version'] . '_' . 
$item['snmp_port']], $index_item['arg1']);
} else {
$output = 'U';
}



** Bug watch added: github.com/Cacti/cacti/issues #1634
   https://github.com/Cacti/cacti/issues/1634

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1779401

Title:
  Cacti 1.1.38 fails to display graphs and acts erratically

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1866573] [NEW] rsyslog does not contain pmciscoios module

[Brian Candler]

Public bug reported:

rsyslog has a parser module for Cisco IOS formatted syslog messages:
https://www.rsyslog.com/doc/master/configuration/modules/pmciscoios.html
https://github.com/rsyslog/rsyslog/tree/master/plugins/pmciscoios

It has been in rsyslog since early days (8.3.4); Bionic has 8.16.0.

However, the Ubuntu Bionic package of rsyslog neither compiles
pmciscoios into the binary, nor includes it as a loadable module.

To replicate, try these lines in /etc/rsyslog.conf:

module(load="pmciscoios")
$RulesetParser rsyslog.ciscoios

and restart rsyslog; you get these errors

Mar  8 21:54:39 noc rsyslogd-2066: could not load module 
'/usr/lib/rsyslog/pmciscoios.so', dlopen: /usr/lib/rsyslog/pmciscoios.so: 
cannot open shared object file: No such file or directory  [v8.16.0 try 
http://www.rsyslog.com/e/2066 ]
Mar  8 21:54:39 noc rsyslogd-2159: error: parser 'rsyslog.ciscoios' unknown at 
this time (maybe defined too late in rsyslog.conf?) [v8.16.0 try 
http://www.rsyslog.com/e/2159 ]

There is "pmcisconames.so", but that is something else:
https://github.com/rsyslog/rsyslog/blob/master/contrib/pmcisconames/pmcisconames.c

# dpkg-query -L rsyslog | grep pm.*so
/usr/lib/rsyslog/pmaixforwardedfrom.so
/usr/lib/rsyslog/pmlastmsg.so
/usr/lib/rsyslog/pmsnare.so
/usr/lib/rsyslog/pmcisconames.so

There doesn't appear to be a separate package with the module:

# apt-cache search rsyslog
...

Upstream Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=929608

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: rsyslog 8.16.0-1ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-166.195-generic 4.4.194
Uname: Linux 4.4.0-166-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Sun Mar  8 21:53:43 2020
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SourcePackage: rsyslog
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.rsyslog.conf: 2020-03-08T21:53:39.943611

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


** Tags: amd64 apport-bug third-party-packages uec-images xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1866573

Title:
  rsyslog does not contain pmciscoios module

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1667016] Re: tcpdump in lxd container: apparmor blocks writing to stdout/stderr

[Brian Candler]

*** This bug is a duplicate of bug 1641236 ***
https://bugs.launchpad.net/bugs/1641236

I believe this bug has been wrongly marked as a duplicate of #1641236.
I described in the second paragraph of the bug report why this is *not*
a duplicate.

#1641236 is when lxc exec passes an open pty from the host to the
container.

This bug (#1667016) is specifically when the pty is opened within the
container, by connecting to sshd inside the container.

See also: https://github.com/lxc/lxd/issues/2930

** Bug watch added: LXD bug tracker #2930
   https://github.com/lxc/lxd/issues/2930

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1667016

Title:
  tcpdump in lxd container: apparmor blocks writing to stdout/stderr

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1805625] [NEW] wpasupplicant package does not include eapol_test

[Brian Candler]

Public bug reported:

wpasupplicant comes with an auxiliary program, eapol_test, but it is not
included in the Ubuntu wpasupplicant package.  I'd like to request that
it be added.

It's very useful for testing wifi RADIUS servers: e.g. you can call it
from a Nagios check script where you want to test the entire EAP/PEAP
authentication cycle.

WORKAROUND: build from source.

* download and untar the wpasuppliant source
* cd wpa_supplicant-2.6/wpa_supplicant
* create/edit the .config file
* make eapol_test && strip eapol_test
* sudo cp eapol_test /usr/local/bin/

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1805625

Title:
  wpasupplicant package does not include eapol_test

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802906] Re: libvirt inside lxd container cannot start virbr0 (Unable to set bridge virbr0 forward_delay: Permission denied)

[Brian Candler]

Yes, it worked - as soon as the new packages were installed.  Thank you!

root@bionic:~# ls
libvirt-bin_4.0.0-1ubuntu8.7~ppa2_amd64.deb
libvirt-clients_4.0.0-1ubuntu8.7~ppa2_amd64.deb
libvirt-daemon-driver-storage-rbd_4.0.0-1ubuntu8.7~ppa2_amd64.deb
libvirt-daemon-system_4.0.0-1ubuntu8.7~ppa2_amd64.deb
libvirt-daemon_4.0.0-1ubuntu8.7~ppa2_amd64.deb
libvirt0_4.0.0-1ubuntu8.7~ppa2_amd64.deb
root@bionic:~# dpkg -i *.deb
(Reading database ... 30717 files and directories currently installed.)
...
root@bionic:~# ifconfig virbr0
virbr0: flags=4099  mtu 1500
inet 192.168.122.1  netmask 255.255.255.0  broadcast 192.168.122.255
ether 52:54:00:11:cc:e6  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

root@bionic:~# virsh net-destroy default
Network default destroyed

root@bionic:~# virsh net-start default
Network default started

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802906

Title:
  libvirt inside lxd container cannot start virbr0 (Unable to set bridge
  virbr0 forward_delay: Permission denied)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802906] Re: libvirt inside lxd container cannot start virbr0 (Unable to set bridge virbr0 forward_delay: Permission denied)

[Brian Candler]

Sorry, but I still think it's a bug.

The reason is that "brctl setfd ..." works fine in an unprivileged
container, but libvirt-daemon fails.  In other words: brctl shows that
it *is* possible to create and manage bridges in an unprivileged
container, but libvirt-daemon isn't doing it correctly.

I am currently only using libvirt to create virbr0 (for GNS3) - I'm not
running kvm.

It's quite possible that anyone who wants to run kvm would require
privileged mode for other reasons, but that would be a separate point.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1802906

Title:
  libvirt inside lxd container cannot start virbr0 (Unable to set bridge
  virbr0 forward_delay: Permission denied)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1802906] [NEW] libvirt inside lxd container cannot start virbr0 (Unable to set bridge virbr0 forward_delay: Permission denied)

[Brian Candler]

Public bug reported:

Ubuntu 18.04 lxd container, running on Ubuntu 18.04 host (kernel
4.15.0-38-generic)

Inside the container, I installed libvirt-bin.  However it fails to
start the predefined 'default' network:

root@bionic:/etc# virsh net-start default
error: Failed to start network default
error: Unable to set bridge virbr0 forward_delay: Permission denied

root@bionic:/etc# echo $?
1

root@bionic:/etc# virsh net-list
 Name State  Autostart Persistent
--

root@bionic:/etc# virsh net-list --all
 Name State  Autostart Persistent
--
 default  inactive   yes   yes


Here is the config:

root@bionic:/etc# cat /etc/libvirt/qemu/networks/default.xml



  default
  0c431cb9-7348-48df-b692-8eece268b0a0
  
  
  
  

  

  


Using "virsh net-edit default" to remove "delay='0'" does not make a
difference; it gets reinserted and the same error occurs.

/var/log/syslog shows:

Nov 12 11:59:11 bionic networkd-dispatcher[212]: WARNING:Unknown index 4 seen, 
reloading interface list
Nov 12 11:59:11 bionic systemd-networkd[178]: virbr0-nic: Gained carrier
Nov 12 11:59:11 bionic libvirtd[225]: 2018-11-12 11:59:11.257+: 251: error 
: virNetDevBridgeSet:140 : Unable to set bridge virbr0 forward_delay: 
Permission denied
Nov 12 11:59:11 bionic systemd-networkd[178]: virbr0-nic: Lost carrier
Nov 12 11:59:11 bionic networkd-dispatcher[212]: WARNING:Unknown index 5 seen, 
reloading interface list
Nov 12 11:59:11 bionic networkd-dispatcher[212]: ERROR:Unknown interface index 
5 seen even after reload
Nov 12 11:59:11 bionic networkd-dispatcher[212]: WARNING:Unknown index 5 seen, 
reloading interface list
Nov 12 11:59:11 bionic networkd-dispatcher[212]: ERROR:Unknown interface index 
5 seen even after reload
Nov 12 11:59:11 bionic networkd-dispatcher[212]: WARNING:Unknown index 5 seen, 
reloading interface list
Nov 12 11:59:11 bionic networkd-dispatcher[212]: ERROR:Unknown interface index 
5 seen even after reload
Nov 12 11:59:11 bionic networkd-dispatcher[212]: WARNING:Unknown index 5 seen, 
reloading interface list
Nov 12 11:59:11 bionic networkd-dispatcher[212]: ERROR:Unknown interface index 
5 seen even after reload


Attaching strace to libvirtd, this is what I see:

...
[pid   225] <... recvmsg resumed> {msg_name={sa_family=AF_NETLINK, nl_pid=0, 
nl_groups=0x01}, msg_namelen=12, 
msg_iov=[{iov_base="add@/devices/virtual/net/virbr0-nic/queues/tx-0\0ACTION=add\0DEVPATH=/devices/virtual/net/virbr0-nic/queues/tx-0\0SUBSYSTEM=queues\0"...,
 iov_len=16384}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 
MSG_PEEK|MSG_TRUNC) = 141
[pid   250] ioctl(23, SIOCGIFINDEX, {ifr_name="virbr0-nic" 
[pid   225] recvmsg(13,  
[pid   250] <... ioctl resumed> , })= 0
[pid   225] <... recvmsg resumed> {msg_name={sa_family=AF_NETLINK, nl_pid=0, 
nl_groups=0x01}, msg_namelen=12, 
msg_iov=[{iov_base="add@/devices/virtual/net/virbr0-nic/queues/tx-0\0ACTION=add\0DEVPATH=/devices/virtual/net/virbr0-nic/queues/tx-0\0SUBSYSTEM=queues\0"...,
 iov_len=16384}], msg_iovlen=1, msg_controllen=0, msg_flags=0}, 0) = 141
[pid   250] close(23 
[pid   225] poll([{fd=4, events=POLLIN}, {fd=6, events=POLLIN}, {fd=9, 
events=POLLIN}, {fd=10, events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, 
events=POLLIN}, {fd=13, events=POLLIN}, {fd=14, events=POLLIN}, {fd=17, 
events=POLLIN}, {fd=18, events=POLLIN}, {fd=20, events=POLLIN}], 11, 4996 

[pid   250] <... close resumed> )   = 0
[pid   250] ioctl(22, SIOCBRADDIF)  = 0
[pid   250] close(22)   = 0
[pid   250] socket(AF_UNIX, SOCK_DGRAM, 0) = 22
[pid   250] fcntl(22, F_GETFD)  = 0
[pid   250] fcntl(22, F_SETFD, FD_CLOEXEC) = 0
[pid   250] ioctl(22, SIOCGIFFLAGS, {ifr_name="virbr0-nic", 
ifr_flags=IFF_BROADCAST|IFF_MULTICAST}) = 0
[pid   250] ioctl(22, SIOCSIFFLAGS, {ifr_name="virbr0-nic", 
ifr_flags=IFF_UP|IFF_BROADCAST|IFF_MULTICAST}) = 0
[pid   250] close(22)   = 0
[pid   250] access("/var/lib/libvirt/dnsmasq/virbr0.macs", F_OK) = -1 ENOENT 
(No such file or directory)
[pid   250] socket(AF_UNIX, SOCK_DGRAM, 0) = 22
[pid   250] fcntl(22, F_GETFD)  = 0
[pid   250] fcntl(22, F_SETFD, FD_CLOEXEC) = 0
[pid   250] access("/sys/class/net/virbr0/bridge/forward_delay", F_OK) = 0
[pid   250] openat(AT_FDCWD, "/sys/class/net/virbr0/bridge/forward_delay", 
O_WRONLY|O_TRUNC) = -1 EACCES (Permission denied)
[pid   250] gettid()= 250
[pid   250] write(2, "2018-11-12 12:02:07.815+: 250: error : 
virNetDevBridgeSet:140 : Unable to set bridge virbr0 forward_delay: Permission 
denied"..., 129) = 129
...


WORKAROUND: "lxc config set bionic security.privileged yes && lxc restart 
bionic"

However, I don't think that privileged mode should be necessary.  If I
turn off privileged mode, I can still create and edit bridges by hand,
including setting the 

[Bug 1736975] Re: netplan does not bring up anonymous bridge on boot

[Brian Candler]

> How can I make this bridge come up at boot without assigning an IP
address?

See the link earlier in this thread:
http://djanotes.blogspot.com/2018/04/anonymous-bridges-in-netplan.html

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1736975

Title:
  netplan does not bring up anonymous bridge on boot

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1793976] Re: kvm kernel missing nbd module

[Brian Candler]

Excellent, thank you.  FYI, the actual application I'm using which
requires nbd is snf-image-creator.

I agree it makes sense to remove most modules relating to physical
hardware from the kvm kernel, but loopback and networking modules are
useful.

I did a quick diff. "rbd" might be another one to add; also veth and
vxlan.

(Aside: I was surprised to find many virtio modules missing, but since
they still work, I imagine they have been compiled directly in)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793976

Title:
  kvm kernel missing nbd module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1793976/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1793976] [NEW] kvm kernel missing nbd module

[Brian Candler]

Public bug reported:

The "nbd" module is missing from linux-modules-XXX-kvm in bionic

root@ubuntu:~# /sbin/modprobe nbd max_part=16
modprobe: FATAL: Module nbd not found in directory /lib/modules/4.15.0-1021-kvm
root@ubuntu:~# uname -a
Linux ubuntu 4.15.0-1021-kvm #21-Ubuntu SMP Tue Aug 28 09:57:01 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

root@ubuntu:~# dpkg-query -l | grep linux-modules
ii  linux-modules-4.15.0-1019-kvm 4.15.0-1019.19
 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii  linux-modules-4.15.0-1021-kvm 4.15.0-1021.21
 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii  linux-modules-4.15.0-34-generic   4.15.0-34.37  
 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP
ii  linux-modules-extra-4.15.0-34-generic 4.15.0-34.37  
 amd64Linux kernel extra modules for version 4.15.0 on 64 bit x86 SMP

nbd exists for the generic kernel, but not kvm.

root@ubuntu:~# find /lib/modules -name '*nbd*'
/lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko
root@ubuntu:~# dpkg-query -S 
/lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko
linux-modules-4.15.0-34-generic: 
/lib/modules/4.15.0-34-generic/kernel/drivers/block/nbd.ko

In fact, there are many more modules in the generic kernel:

root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-1021-kvm | wc -l
514
root@ubuntu:~# dpkg-query -L linux-modules-4.15.0-34-generic | wc -l
1285

I checked if there is a linux-modules-extra for kvm and this kernel
version, but there is not - only for azure.

root@ubuntu:~# apt-cache search linux-modules-extra-4.15.0-1021
linux-modules-extra-4.15.0-1021-azure - Linux kernel extra modules for version 
4.15.0 on 64 bit x86 SMP
root@ubuntu:~#

There is a "linux-image-extra-virtual" package, but it's empty:

root@ubuntu:~# dpkg-query -L linux-image-extra-virtual
/.
/usr
/usr/share
/usr/share/doc
/usr/share/doc/linux-image-extra-virtual
/usr/share/doc/linux-image-extra-virtual/copyright
/usr/share/doc/linux-image-extra-virtual/changelog.gz

As a workaround, I expect I can use the generic kernel - but this won't
be optimised for kvm.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-modules-4.15.0-1021-kvm 4.15.0-1021.21
ProcVersionSignature: Ubuntu 4.15.0-1021.21-kvm 4.15.18
Uname: Linux 4.15.0-1021-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
Date: Sun Sep 23 19:43:56 2018
Dependencies:
 
InstallationDate: Installed on 2018-06-15 (100 days ago)
InstallationMedia: Ubuntu-Server 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
ProcEnviron:
 LANG=en_GB.UTF-8
 TERM=xterm-256color
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: linux-kvm (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1793976

Title:
  kvm kernel missing nbd module

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1793976/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1405424] Re: mod_xml2enc not available

[Brian Candler]

Thank you.  It looks like it was fixed in 16.04:

# dpkg-query -L apache2-bin | grep mod_xml
/usr/lib/apache2/modules/mod_xml2enc.so

The dependency isn't automatic in 16.04:

# a2enmod proxy_html
Considering dependency proxy for proxy_html:
Enabling module proxy.
Enabling module proxy_html.
To activate the new configuration, you need to run:
  service apache2 restart

But you can enable it manually:

# a2enmod xml2enc
Enabling module xml2enc.
To activate the new configuration, you need to run:
  service apache2 restart

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1405424

Title:
  mod_xml2enc not available

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[Brian Candler]

Awesome, thanks again!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630946

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[Brian Candler]

> no matter if we succeed/fail there one can at least later remove open-
iscsid if he wants without taking out the ubuntu-server meta.

That's perfect - thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630946

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630946] Re: ubuntu-server depends on open-iscsi and runs iscsid

[Brian Candler]

Workaround:

systemctl stop iscsid
systemctl disable iscsid

... but I still object to not being able to remove it without also
removing ubuntu-server.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630946

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool

[Brian Candler]

> So I wonder is this "just" a conflict between how libvirt expects
pools to be set up (and as it does by itself) vs the manual set up one?

(1) If libvirt is only supposed to work with a top-level pool, then it
should have refused to allow me to create a libvirt pool with a slash in
the zfs pool name.

But that's not a great solution.  Given that everything apart from zpool
usage stats works fine, it would be much better to allow use of a parent
dataset, which can be done by fixing the zpool command invocation.

This is much more flexible: it allows the zpool to be shared with other
applications, and have separate quotas and usage reporting for libvirt
versus those other applications.  I definitely wouldn't want to dedicate
an entire zpool to libvirt.

(2) In any case, if an error occurs when libvirt is refreshing a storage
pool and shelling out to zfs subcommands, the failure should be reported
and propagated.  Ideally it wouldn't discard the previous volume info
either.

Any system error which can happen, will sooner or later happen :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767997

Title:
  virt-manager destroys all volumes in libvirt zfs pool

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool

[Brian Candler]

I checked libvirt HEAD and the code's the same there:
src/storage/storage_backend_zfs.c

cmd = virCommandNewArgList(ZPOOL,
   "get", "-Hp",
   "health,size,free,allocated",
   def->source.name,
   NULL);

I guess this needs to go upstream.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767997

Title:
  virt-manager destroys all volumes in libvirt zfs pool

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool

[Brian Candler]

> if that worked for you before or not

Did this work in ubuntu 16.04 you mean?  No it didn't; I was able to
create the the libvirt zfs pool via virsh, and virt-manager would show
that the pool existed, but not any volumes within it.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767997

Title:
  virt-manager destroys all volumes in libvirt zfs pool

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool

[Brian Candler]

I looked in both 4.0.0 and HEAD source, and the call to zpool uses
def->source.name.  I think it would work fine if it stripped out
everything from the first slash.

(Aside: if the zpool command fails, virStorageBackendZFSRefreshPool()
just goes straight to cleanup and returns zero, as if nothing bad had
happened)

It then goes on to call zfs list, which would do the following:

root@beaver:~# zfs list -Hp -t volume -r -o name,volsize,refreservation 
zfs/images
zfs/images/vol1 1073741824  1109393408

That looks perfectly OK to me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767997

Title:
  virt-manager destroys all volumes in libvirt zfs pool

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1767997/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool

[Brian Candler]

And using strace on libvirtd, I see it's running this:

[pid  5806] execve("/sbin/zpool", ["/sbin/zpool", "get", "-Hp",
"health,size,free,allocated", "zfs/images"], 0x7fffedc8b6c8 /* 6 vars
*/) = 0

Which is not a valid command:

root@beaver:~# /sbin/zpool get -Hp health,size,free,allocated zfs/images
cannot open 'zfs/images': invalid character '/' in pool name

Right.  It seems that this part of libvirt thinks that it has full reign
over a zfs *pool*, whereas everything else is happy to create child
datasets of an existing *dataset*

Furthermore: when the zpool command fails, libvirt is still happy to zap
all the existing defined libvirt volumes (or it has already done so).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767997

Title:
  virt-manager destroys all volumes in libvirt zfs pool

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1767997/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767997] Re: virt-manager destroys all volumes in libvirt zfs pool

[Brian Candler]

Aha, good thinking about reproducing with virsh.  To find out what virt-
manager is doing, I did:

LIBVIRT_DEBUG=1 virt-manager --no-fork

Clicking the refresh button shows me it's doing "virStoragePoolRefresh", which 
takes me to
ftp://libvirt.org/libvirt/virshcmdref/html/sect-pool-refresh.html

And yes, I can reproduce using just virsh pool-refresh:

root@beaver:~# virsh vol-create-as --pool zfs --name vol1 --capacity 1G
Vol vol1 created

root@beaver:~# virsh vol-list --pool zfs
 Name Path
--
 vol1 /dev/zvol/zfs/images/vol1

root@beaver:~# virsh pool-refresh zfs
Pool zfs refreshed

root@beaver:~# virsh vol-list --pool zfs
 Name Path
--

root@beaver:~#

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767997

Title:
  virt-manager destroys all volumes in libvirt zfs pool

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1767997/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767997] [NEW] virt-manager destroys all volumes in libvirt zfs pool

[Brian Candler]

Public bug reported:

How to replicate:

1. Install libvirt, libvirt-daemon-driver-storage-zfs and virt-manager

2. Create a zfs pool

# zpool create -oashift=12 zfs /dev/sdb
# zfs set compression=lz4 zfs
# zfs create zfs/images
# virsh pool-define-as --name zfs --source-name zfs/images --type zfs

3. Create a volume in that pool

root@beaver:~# virsh vol-create-as --pool zfs --name vol1 --capacity 1G
Vol vol1 created

root@beaver:~# virsh vol-list --pool zfs
 Name Path
--
 vol1 /dev/zvol/zfs/images/vol1


4. Start virt-manager (even as a non-root user)

5. Immediately re-list the volumes from virsh:

root@beaver:~# virsh vol-list --pool zfs
 Name Path
--

root@beaver:~#

All zfs volumes have been forgotten!!  Fortunately they still exist in
zfs:

root@beaver:~# zfs list
NAME  USED  AVAIL  REFER  MOUNTPOINT
zfs  1.03G  8.59G96K  /zfs
zfs/images   1.03G  8.59G96K  /zfs/images
zfs/images/vol1  1.03G  9.63G56K  -


I think virt-manager is supposed to play nicely with zfs:

* You can create a zfs pool successfully in the GUI
* You can click to create a zfs volume.  It actually creates the underlying 
zvol (as shown by "zfs list")
* But every time you do any action in virt-manager, even just clicking the 
Refresh button on the list of volumes, all volumes disappear from libvirt.

root@beaver:~# virsh vol-list --pool zfs
 Name Path
--
 vol1 /dev/zvol/zfs/images/vol1

root@beaver:~#

<<< click the Refresh button >>>

root@beaver:~# virsh vol-list --pool zfs
 Name Path
--

root@beaver:~#

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: virt-manager 1:1.5.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Mon Apr 30 10:24:19 2018
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: virt-manager
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: virt-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767997

Title:
  virt-manager destroys all volumes in libvirt zfs pool

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/virt-manager/+bug/1767997/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767973] Re: libvirt no longer has support for zfs pools (18.04 regression)

[Brian Candler]

Ah right: I had not installed libvirt-daemon-driver-storage-zfs.  Doing
so has added the ability to virsh and virt-manager to create zfs pools
and volumes. Thank you!

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767973

Title:
  libvirt no longer has support for zfs pools (18.04 regression)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1767973] [NEW] libvirt no longer has support for zfs pools (18.04 regression)

[Brian Candler]

Public bug reported:

In Ubuntu 16.04 it was possible to create zfs pools in libvirt.  But
this no longer works in 18.04:

# zpool create -oashift=12 zfs /dev/sdb
# zfs set compression=lz4 zfs
# zfs create zfs/images
# virsh pool-define-as --name zfs --source-name zfs/images --type zfs
error: Failed to define pool zfs
error: internal error: missing backend for pool type 11 (zfs)

Relates to #1561553 where this was fixed in 16.04.  I expect libvirt is
no longer being built with the right flags.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libvirt0 4.0.0-1ubuntu8
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
Date: Mon Apr 30 09:03:59 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic uec-images

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1767973

Title:
  libvirt no longer has support for zfs pools (18.04 regression)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1405424] Re: mod_xml2enc not available

[Brian Candler]

Having to build the module yourself from source is not a proper
solution.  This module should be pre-built and included with apache2 (or
in a separate package).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1405424

Title:
  mod_xml2enc not available

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1705766] Re: Invalid DNSSEC signatures on empty responses to mixed-case queries

[Brian Candler]

P.S. Changelogs for 4.0.0 alpha3, beta1, rc2 and release are here:
https://doc.powerdns.com/authoritative/changelog/4.0.html#powerdns-authoritative-server-4-0-0

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705766

Title:
  Invalid DNSSEC signatures on empty responses to mixed-case queries

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1705766] Re: Invalid DNSSEC signatures on empty responses to mixed-case queries

[Brian Candler]

PDNS 4.0.0-alpha2 in Xenial is horribly broken(*) so IMO it seems a bit
of a waste of effort backporting this specific fix, without also
backporting the critical fixes from 4.0.0 alpha 3 and later, which in
turn would be best done by going straight to 4.0.0 release (or 4.0.4+)

PDNS is a fine piece of software, and it's a shame that for many people
their first experience will be using the Xenial package, which may put
them off forever - it nearly did for me.

(*) at least with a SQL backend:
https://mailman.powerdns.com/pipermail/pdns-users/2016-May/024192.html

At the moment, it seems the only safe way to run pdns-server on Xenial
is to use the packages from the origin repository:
https://repo.powerdns.com/

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1705766

Title:
  Invalid DNSSEC signatures on empty responses to mixed-case queries

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 591823] Re: "File descriptor \d+ (\S+) leaked on lvs invocation."

[Brian Candler]

Just doing an "apt-get dist-upgrade" on a 16.04 VM:

...
Setting up grub-common (2.02~beta2-36ubuntu3.11) ...
Installing new version of config file /etc/grub.d/10_linux ...
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
Setting up grub-pc-bin (2.02~beta2-36ubuntu3.11) ...
Setting up grub2-common (2.02~beta2-36ubuntu3.11) ...
Setting up grub-pc (2.02~beta2-36ubuntu3.11) ...
Installing for i386-pc platform.
File descriptor 3 (pipe:[136263]) leaked on vgs invocation. Parent PID 18940: 
grub-install
File descriptor 3 (pipe:[136263]) leaked on vgs invocation. Parent PID 18940: 
grub-install
File descriptor 3 (pipe:[136263]) leaked on vgs invocation. Parent PID 18940: 
grub-install
Installation finished. No error reported.
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.4.0-83-generic
Found initrd image: /boot/initrd.img-4.4.0-83-generic
Found linux image: /boot/vmlinuz-4.4.0-21-generic
Found initrd image: /boot/initrd.img-4.4.0-21-generic
done
...
Setting up initramfs-tools-core (0.122ubuntu8.8) ...
Setting up initramfs-tools (0.122ubuntu8.8) ...
update-initramfs: deferring update (trigger activated)
Setting up mdadm (3.3-2ubuntu7.2) ...
update-initramfs: deferring update (trigger activated)
Generating grub configuration file ...
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19859: 
grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19859: 
grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19899: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19899: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19909: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19909: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19919: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19919: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19929: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19929: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19979: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 19979: 
/usr/sbin/grub-probe
Found linux image: /boot/vmlinuz-4.4.0-83-generic
Found initrd image: /boot/initrd.img-4.4.0-83-generic
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 20061: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 20061: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 20072: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 20072: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 20082: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 20082: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 20092: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 20092: 
/usr/sbin/grub-probe
Found linux image: /boot/vmlinuz-4.4.0-21-generic
Found initrd image: /boot/initrd.img-4.4.0-21-generic
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 20335: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on vgs invocation. Parent PID 20335: 
/usr/sbin/grub-probe
File descriptor 3 (pipe:[140340]) leaked on lvs invocation. Parent PID 20417: 
/bin/sh
done
update-rc.d: warning: start and stop actions are no longer supported; falling 
back to defaults
...

It updated 119 packages, but lvm2 was not one of them.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/591823

Title:
  "File descriptor \d+ (\S+) leaked on lvs invocation."

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1562333] Re: iptstate assert failure: *** Error in `iptstate': munmap_chunk(): invalid pointer: 0x000000000193c990 ***

[Brian Candler]

2.2.5 in xenial crashes for me.  Building 2.2.6 from source on xenial,
it works.

+1 for backport; the package is currently not usable.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1562333

Title:
  iptstate assert failure: *** Error in `iptstate': munmap_chunk():
  invalid pointer: 0x0193c990 ***

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1654310] Re: lxcfs: update the 'btime' field in /proc/stat to reflect guest boot time not host

[Brian Candler]

After upgrading to lxcfs/xenial-proposed (2.0.7-0ubuntu1~16.04.2), the
problem is fixed for me

Inside a container:

root@apt-cacher:~# ps auxwww | grep apt
apt-cac+   309  0.0  0.7 653476  7128 ?Ssl  Jul08   1:02 
/usr/sbin/apt-cacher-ng SocketPath=/run/apt-cacher-ng/socket -c 
/etc/apt-cacher-ng ForeGround=1
root  1922  0.0  0.1  14620  1016 ?S+   08:04   0:00 grep 
--color=auto apt
root@apt-cacher:~# date
Tue Jul 11 08:04:09 UTC 2017

- start time of apt-cacher-ng is correct (in the past)
- start time of 'grep' process is correct (current time)

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

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1654310

Title:
  lxcfs: update the 'btime' field in /proc/stat to reflect guest boot
  time not host

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1691763] [NEW] mdadm segfaults in lxd container

[Brian Candler]

Public bug reported:

Inside a 16.04 lxd container (running in default unprivileged mode),
inside a 16.04 host:

# /etc/cron.daily/mdadm
Segmentation fault (core dumped)

# strace -f /sbin/mdadm --monitor --scan --oneshot
...
brk(0x1ba1000)  = 0x1ba1000
mknod("/dev/.tmp.md1", S_IFBLK|0600, makedev(9, 1)) = -1 EPERM (Operation not 
permitted)
--- SIGSEGV {si_signo=SIGSEGV, si_code=SEGV_MAPERR, si_addr=0} ---
+++ killed by SIGSEGV (core dumped) +++
Segmentation fault (core dumped)

This is troublesome because (a) mdadm is installed by default, (b) mdadm
runs under a daily cron job, (c) cron sends out errors via E-mail.  So
you get spammed from each container.

As others have observed[^1], the workaround is to remove mdadm from
inside lxd containers.

[^1] https://blog.sleeplessbeastie.eu/2017/05/04/how-to-fix-mdadm-
segfault-inside-lxc-container/

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: mdadm 3.3-2ubuntu7.2
ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-52-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Thu May 18 13:48:22 2017
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 413c:a001 Dell Computer Corp. Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. PowerEdge R230
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-52-generic 
root=/dev/mapper/ix--mon2-root ro console=tty1 console=ttyS0,115200
SourcePackage: mdadm
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/12/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.0.8
dmi.board.name: 0DWX9P
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr2.0.8:bd01/12/2017:svnDellInc.:pnPowerEdgeR230:pvr:rvnDellInc.:rn0DWX9P:rvrA00:cvnDellInc.:ct23:cvr:
dmi.product.name: PowerEdge R230
dmi.sys.vendor: Dell Inc.
etc.blkid.tab: Error: [Errno 2] No such file or directory: '/etc/blkid.tab'
initrd.files: Error: [Errno 2] No such file or directory: 
'/boot/initrd.img-4.8.0-52-generic'

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


** Tags: amd64 apport-bug uec-images xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1691763

Title:
  mdadm segfaults in lxd container

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1688034] Re: 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

[Brian Candler]

I guess this also makes 1.8.16-0ubuntu1.3 a "security" update, since
sudo+sssd now enforces policy which it should have done before, but
didn't.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688034

Title:
  1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1688034] Re: 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

[Brian Candler]

I found out how to enable debugging for sudoers:

Debug sudo /var/log/sudo-debug all@info
Debug sudoers.so /var/log/sudoers-debug all@info

With the *new* sudo I get the following logged matching 'sssd':

May  5 12:40:06 sudo[17912] sssd/ldap sudoHost 'ALL' ... MATCH!
May  5 12:40:06 sudo[17912] sssd/ldap sudoUser '%system_administrators' ... not 
(brian.candler)
May  5 12:40:06 sudo[17912] sssd/ldap sudoUser '%security_administrators' ... 
not (brian.candler)

But with the *old* sudo I get:

May  5 12:41:48 sudo[18384] sssd/ldap sudoHost 'ALL' ... MATCH!
May  5 12:41:48 sudo[18384] sssd/ldap sudoRunAsUser 'ALL' ... MATCH!
May  5 12:41:48 sudo[18384] sssd/ldap sudoCommand 'ALL' ... MATCH!

It seems to be a behaviour change with group checking.

The 'brian.candler' user *is* a member of one of those groups in IPA;
but those groups are not posix groups so they are not visible using
(e.g.) "id"

I was able to solve the problem by adding

objectClass: posixgroup
gidNumber: 

to those group objects.  After this, the sudoers log shows:

May  5 13:11:50 sudo[19545] sssd/ldap sudoHost 'ALL' ... MATCH!
May  5 13:11:50 sudo[19545] sssd/ldap sudoUser '%system_administrators' ... not 
(brian.candler)
May  5 13:11:50 sudo[19545] sssd/ldap sudoUser '%security_administrators' ... 
MATCH! (brian.candler)
May  5 13:11:50 sudo[19545] sssd/ldap sudoRunAsUser 'ALL' ... MATCH!
May  5 13:11:50 sudo[19545] sssd/ldap sudoCommand 'ALL' ... MATCH!

So: arguably this is not a bug, but a bug fix.  Still, it would be nice
if the release notes explained the potential for regression.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688034

Title:
  1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1688034] Re: 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

[Brian Candler]

Now trying with @debug instead of @info

Slight munging of output to make it diffable, then diff -u:

--- v1.debug.trim   2017-05-03 20:28:07.78400 +
+++ v2.debug.trim   2017-05-03 20:28:14.03200 +
@@ -38,87 +38,6 @@
 -> parse_args @ /build/sudo-XX/sudo-1.8.16/src/parse_args.c:172
 -> get_net_ifs @ /build/sudo-XX/sudo-1.8.16/src/net_ifs.c:120
 <- get_net_ifs @ /build/sudo-XX/sudo-1.8.16/src/net_ifs.c:205 := 3
-<- parse_args @ /build/sudo-XX/sudo-1.8.16/src/parse_args.c:512 := 8
-sudo_mode 8
--> sudo_load_plugins @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:283
--> sudo_load_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:160
--> sudo_check_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:112
--> sudo_stat_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:46
-<- sudo_stat_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:104 := 0
-<- sudo_check_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:137 
:= true
--> sudo_conf_debug_files_v1 @ 
/build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:509
-<- sudo_conf_debug_files_v1 @ 
/build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:535 := (nil)
-<- sudo_load_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:255 := 
true
--> sudo_load_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:160
--> sudo_check_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:112
--> sudo_stat_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:46
-<- sudo_stat_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:104 := 0
-<- sudo_check_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:137 
:= true
--> sudo_conf_debug_files_v1 @ 
/build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:509
-<- sudo_conf_debug_files_v1 @ 
/build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:535 := (nil)
-<- sudo_load_plugin @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:255 := 
true
-<- sudo_load_plugins @ /build/sudo-XX/sudo-1.8.16/src/load_plugins.c:352 
:= true
--> policy_open @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1231
--> format_plugin_settings @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1175
--> sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:44
-<- sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:56 
:= plugin_path=/usr/lib/sudo/sudoers.so
-settings: progname=sudo
--> sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:44
-<- sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:56 
:= progname=sudo
-settings: network_addrs=10.0.0.230/255.255.255.0 
:::::230/::::::: 
fe80::1:::/:::::
--> sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:44
-<- sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:56 
:= network_addrs=10.0.0.230/255.255.255.0 
:::::230/::::::: 
fe80::1:::/:::::
-settings: plugin_dir=/usr/lib/sudo/
--> sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:44
-<- sudo_new_key_val_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/key_val.c:56 
:= plugin_dir=/usr/lib/sudo/
-<- format_plugin_settings @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1217 := 
0x
-<- policy_open @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1261 := 1
--> init_signals @ /build/sudo-XX/sudo-1.8.16/src/signal.c:121
--> pipe_nonblock @ /build/sudo-XX/sudo-1.8.16/src/exec.c:975
-<- pipe_nonblock @ /build/sudo-XX/sudo-1.8.16/src/exec.c:993 := 0
-<- init_signals @ /build/sudo-XX/sudo-1.8.16/src/signal.c:154
--> policy_invalidate @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1350
-<- policy_invalidate @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:1358
--> sudo_check_suid @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:828
-<- sudo_check_suid @ /build/sudo-XX/sudo-1.8.16/src/sudo.c:872
--> save_signals @ /build/sudo-XX/sudo-1.8.16/src/signal.c:64
-<- save_signals @ /build/sudo-XX/sudo-1.8.16/src/signal.c:71
--> sudo_conf_read_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:562
--> sudo_secure_path @ /build/sudo-XX/sudo-1.8.16/lib/util/secure_path.c:43
-<- sudo_secure_path @ /build/sudo-XX/sudo-1.8.16/lib/util/secure_path.c:62 
:= 0
--> sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:55
-<- sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:118 := 
40
--> sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:55
-<- sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:118 := 
46
--> sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:55
-<- sudo_parseln_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/parseln.c:117 := 
-1
-<- sudo_conf_read_v1 @ /build/sudo-XX/sudo-1.8.16/lib/util/sudo_conf.c:651 
:= 1
--> get_user_info @ 

[Bug 1688034] Re: 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

[Brian Candler]

Some additional info.

I enabled sudo debugging by creating /etc/sudo.conf containing:

Debug sudo /var/log/sudo-debug all@info
Debug sudoers /var/log/sudoers-debug all@info

With the newer (non-functioning) sudo, /var/log/sudo-debug contains:

May  3 18:55:50 sudo[8003] comparing dev 34817 to /dev/pts/1: match! @ 
sudo_ttyname_dev() /build/sudo-40pSZP/sudo-1.8.16/src/ttyname.c:336
May  3 18:55:50 sudo[8003] settings: run_shell=true
May  3 18:55:50 sudo[8003] settings: progname=sudo
May  3 18:55:50 sudo[8003] settings: network_addrs=10.0.0.230/255.255.255.0 
:::::230/::::::: 
fe80::1:::/:::::
May  3 18:55:50 sudo[8003] settings: plugin_dir=/usr/lib/sudo/
May  3 18:55:51 sudo[8003] policy plugin returns 0

With the older (working) sudo, /var/log/sudo-debug contains:

May  3 19:00:19 sudo[8746] comparing dev 34817 to /dev/pts/1: match! @ 
sudo_ttyname_dev() /build/sudo-g3ghsu/sudo-1.8.16/src/ttyname.c:336
May  3 19:00:19 sudo[8746] settings: run_shell=true
May  3 19:00:19 sudo[8746] settings: progname=sudo
May  3 19:00:19 sudo[8746] settings: network_addrs=10.0.0.230/255.255.255.0 
:::::230/::::::: 
fe80::1:::/:::::
May  3 19:00:19 sudo[8746] settings: plugin_dir=/usr/lib/sudo/
May  3 19:00:22 sudo[8746] policy plugin returns 1
May  3 19:00:22 sudo[8746] settings: run_shell=true
May  3 19:00:22 sudo[8746] settings: progname=sudo
May  3 19:00:22 sudo[8746] settings: network_addrs=10.0.0.230/255.255.255.0 
:::::230/::::::: 
fe80::1:::/:::::
May  3 19:00:22 sudo[8746] settings: plugin_dir=/usr/lib/sudo/
May  3 19:00:22 sudo[8746] command info from plugin:
May  3 19:00:22 sudo[8746] 0: command=/bin/bash
May  3 19:00:22 sudo[8746] 1: runas_uid=0
May  3 19:00:22 sudo[8746] 2: runas_gid=0
May  3 19:00:22 sudo[8746] 3: runas_groups=0
May  3 19:00:22 sudo[8746] 4: closefrom=3
May  3 19:00:22 sudo[8746] 5: set_utmp=true
May  3 19:00:22 sudo[8746] 6: umask=022
May  3 19:00:22 sudo[8746] executed /bin/bash, pid 8754
May  3 19:00:22 sudo[8746] sudo_ev_add_v1: adding event 0x55e83b06c630 to base 
0x55e83b07ea40
May  3 19:00:22 sudo[8746] sudo_ev_add_v1: adding event 0x55e83b078180 to base 
0x55e83b07ea40
May  3 19:00:22 sudo[8746] signal pipe fd 10
May  3 19:00:22 sudo[8746] backchannel fd 5
May  3 19:00:22 sudo[8754] exec /bin/bash [/bin/bash]
May  3 19:00:22 sudo[8746] sudo_ev_scan_impl: 1 fds ready
May  3 19:00:22 sudo[8746] failed to read child status: EOF
May  3 19:00:22 sudo[8746] sudo_ev_del_v1: removing event 0x55e83b078180 from 
base 0x55e83b07ea40

(/var/log/sudoers-debug is not created in either case)

Note "policy plugin returns 0" in the first case.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688034

Title:
  1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1688034] [NEW] 1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

[Brian Candler]

Public bug reported:

ubuntu 16.04, enrolled with freeipa-client to FreeIPA 4.4.0 (under
CentOS 7)

With sudo 1.8.16-0ubuntu1, everything is fine:

brian.candler@api-dev:~$ sudo -s
[sudo] password for brian.candler:
root@api-dev:~#

After update to 1.8.16-0ubuntu1.3, it no longer works:

brian.candler@api-dev:~$ sudo -k
brian.candler@api-dev:~$ sudo -s
[sudo] password for brian.candler:
brian.candler is not allowed to run sudo on api-dev.int.example.com.  This 
incident will be reported.

This is repeatable: downgrade sudo and it works again.

Seems very likely related to change made as part of #1607666, which
changes how sudo policies are matched, but has unexpected regression.

--- Additional info ---

The sudo policy in IPA is extremely simple. It has a single rule, which
says:

- applies to users in groups "system_administrators" and 
"security_administrators"
- applies to any host
- applies to any command

In LDAP under ou=sudoers tree, the groups are flattened out:

# system administrators on all hosts, sudoers, ipa.example.com
dn: cn=system administrators on all hosts,ou=sudoers,dc=ipa,dc=example,dc=com
sudoRunAsGroup: ALL
objectClass: sudoRole
objectClass: top
sudoUser: brian.candler
sudoUser: ...
sudoUser: ... list more users
sudoUser: ...
sudoRunAsUser: ALL
sudoCommand: ALL
sudoHost: ALL
cn: system administrators on all hosts

Under cn=sudorules,cn=sudo it refers to the groups rather than the
individuals:

# 59ffb10a-9c61-11e6-b5b8-00163efd5284, sudorules, sudo, ipa.example.com
dn: 
ipaUniqueID=59ffb10a-9c61-11e6-b5b8-00163efd5284,cn=sudorules,cn=sudo,dc=ipa,dc=example,dc=com
ipaSudoRunAsUserCategory: all
ipaSudoRunAsGroupCategory: all
description: admins have full sudo access on any host they can ssh into
cmdCategory: all
hostCategory: all
memberUser: 
cn=system_administrators,cn=groups,cn=accounts,dc=ipa,dc=example,dc=com
memberUser: 
cn=security_administrators,cn=groups,cn=accounts,dc=ipa,dc=example,dc=com
objectClass: ipasudorule
objectClass: ipaassociation
ipaEnabledFlag: TRUE
cn: system administrators on all hosts
ipaUniqueID: 59ffb10a-9c61-11e6-b5b8-00163efd5284

I have no workaround other than downgrade.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: sudo 1.8.16-0ubuntu1.3
ProcVersionSignature: Ubuntu 4.4.0-1016.25-aws 4.4.59
Uname: Linux 4.4.0-1016-aws x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Wed May  3 16:01:23 2017
Ec2AMI: ami-a8d2d7ce
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1a
Ec2InstanceType: t2.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: sudo
UpgradeStatus: No upgrade log present (probably fresh install)
VisudoCheck:
 /etc/sudoers: parsed OK
 /etc/sudoers.d/90-cloud-init-users: parsed OK
 /etc/sudoers.d/README: parsed OK

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


** Tags: amd64 apport-bug ec2-images xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1688034

Title:
  1.8.16-0ubuntu1.3 update breaks sudo with freeipa-client / sssd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670303] Re: dhcpd does not respect ip_local_port _range or ip_local_reserved_ports

[Brian Candler]

WORKAROUND: if the other application which needs to bind to a UDP port
can be configured to bind to a specific interface, then you can make
isc-dhcp-server bind to a different interface in dhcpd.conf. e.g.

ddns-local-address4 127.0.0.1;
ddns-local-address6 ::1;

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670303

Title:
  dhcpd does not respect ip_local_port _range or ip_local_reserved_ports

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1670303/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670303] Re: dhcpd does not respect ip_local_port _range or ip_local_reserved_ports

[Brian Candler]

strace shows that dhcpd is binding to explicit ports which it has chosen
itself:

setsockopt(20, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
setsockopt(20, SOL_IP, IP_MTU_DISCOVER, [0], 4) = 0
getsockopt(20, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
setsockopt(20, SOL_IP, IP_RECVTOS, [1], 4) = 0
bind(20, {sa_family=AF_INET, sin_port=htons(15101), 
sin_addr=inet_addr("0.0.0.0")}, 16) = 0
socket(PF_INET6, SOCK_DGRAM, IPPROTO_UDP) = 5
fcntl(5, F_DUPFD, 20)   = 21
close(5)= 0
fcntl(21, F_GETFL)  = 0x2 (flags O_RDWR)
fcntl(21, F_SETFL, O_RDWR|O_NONBLOCK)   = 0
setsockopt(21, SOL_IPV6, IPV6_MTU, [1280], 4) = 0
setsockopt(21, SOL_SOCKET, SO_TIMESTAMP, [1], 4) = 0
setsockopt(21, SOL_IPV6, IPV6_RECVPKTINFO, [1], 4) = 0
setsockopt(21, SOL_IPV6, IPV6_MTU_DISCOVER, [0], 4) = 0
getsockopt(21, SOL_SOCKET, SO_RCVBUF, [212992], [4]) = 0
setsockopt(21, SOL_IPV6, IPV6_RECVTCLASS, [1], 4) = 0
setsockopt(21, SOL_IPV6, IPV6_V6ONLY, [1], 4) = 0
bind(21, {sa_family=AF_INET6, sin6_port=htons(11709), inet_pton(AF_INET6, "::", 
_addr), sin6_flowinfo=0, sin6_scope_id=0}, 28) = 0

Aha - from man dhcpd:

When DDNS is enabled at compile time (see includes/site.h)
the server will open both a v4 and a v6 UDP socket on
random ports.  These ports are opened even if DDNS is disabled
in the configuration file.

In the source code, the README says:

A fully-featured implementation of dynamic DNS updates is included in
this release.  It uses libraries from BIND and, to avoid issues with
different versions, includes the necessary BIND version.  The appropriate
BIND libraries will be compiled and installed in the bind subdirectory
as part of the make step.

However, debian/patches/system-bind.patch causes it to link against the
system bind library; this seems to be -ldns-export from package libdns-
export162

apt-get source libdns-export162 pulls in bind9. The CHANGES file says:

4109.   [port]  linux: support reading the local port range from
net.ipv4.ip_local_port_range. [RT # 39379]

However, the strace output from dhcpd shows no attempt to read
ip_local_port_range.

I see the bind code includes these fallback values:

#define ISC_NET_PORTRANGELOW 1024
#define ISC_NET_PORTRANGEHIGH 65535

ISTM that a safer bound would be 49152-65535 (IANA dynamic port range),
or at least the linux default of "32768 60999"

But the fundamental problem here is that for some reason, when dhcpd
links into this code, it isn't making use of the detection of available
Linux port range.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670303

Title:
  dhcpd does not respect ip_local_port _range or ip_local_reserved_ports

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1670303/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1670303] [NEW] dhcpd does not respect ip_local_port _range or ip_local_reserved_ports

[Brian Candler]

Public bug reported:

When isc-dhcp-server starts up, in addition to listening on port 67, it
binds to a random UDP port on an IPv4 socket and another on an IPv6
socket:

# netstat -naup | grep dhcp
udp0  0 0.0.0.0:11075   0.0.0.0:*   
8188/dhcpd
udp0  0 0.0.0.0:67  0.0.0.0:*   
8188/dhcpd
udp6   0  0 :::10800:::*
8188/dhcpd
#

(I am guessing this is for making outbound DNS queries?)  However, this
prevented a later application of mine from working, as it wanted to bind
to port 11075 for accepting incoming data.

Simply doing "service isc-dhcp-server restart" makes it choose new
ports, but this problem may occur again in the future.

In the default configuration, I believe ephemeral ports should only use
32768 and above:

# cat /proc/sys/net/ipv4/ip_local_port_range
3276860999
# cat /proc/sys/net/ipv4/ip_local_reserved_ports

#

I also tried setting a reservation, and this was not respected either.

# sysctl net.ipv4.ip_local_reserved_ports="1-5"
net.ipv4.ip_local_reserved_ports = 1-5

After restarting dhcpd:

# netstat -naup | grep dhcp
udp0  0 0.0.0.0:50610   0.0.0.0:*   
4592/dhcpd
udp0  0 0.0.0.0:67  0.0.0.0:*   
4592/dhcpd
udp6   0  0 :::28891:::*
4592/dhcpd


I can find no way to tell isc-dhcp-server which port range to use. Setting 
"omapi-port" in dhcpd.conf makes it listen for *TCP* connections on the given 
port, and does not affect the UDP behaviour.

I don't know if this is a problem with the application (explicitly
picking a local port), the resolver library (ditto), or the kernel
(ignoring its own ip_local_port_range)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: isc-dhcp-server 4.3.3-5ubuntu12.6
ProcVersionSignature: Ubuntu 4.4.0-64.85-generic 4.4.44
Uname: Linux 4.4.0-64-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
Date: Mon Mar  6 09:30:29 2017
DhServerLeases:
 
InstallationDate: Installed on 2017-03-04 (2 days ago)
InstallationMedia: Ubuntu-Server 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.8)
ProcEnviron:
 SHELL=/bin/bash
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_US
 LANGUAGE=en_US:
SourcePackage: isc-dhcp
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.dhcp.dhcpd.conf: 2017-03-04T09:46:07.987046

** Affects: isc-dhcp (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1670303

Title:
  dhcpd does not respect ip_local_port _range or ip_local_reserved_ports

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/isc-dhcp/+bug/1670303/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1667016] [NEW] tcpdump in lxd container: apparmor blocks writing to stdout/stderr

[Brian Candler]

Public bug reported:

[ubuntu 16.04, lxd 2.0.8 or 2.0.9, tcpdump 4.7.4 or 4.9.0]

If you ssh into an lxd container as a normal user, and inside that
container run "sudo tcpdump", the tcpdump process is blocked from
writing to stdout/stderr.  This appears to be due to apparmor:
disabling apparmor for tcpdump makes the problem go away.

ln -s /etc/apparmor.d/usr.sbin.tcpdump /etc/apparmor.d/disable/

Note: this is a different bug from #1641236. In that bug, the user did
"lxc exec  bash" to get a shell in the container; the stdout
fd was being passed from the outer host to the container.  But in this
case, the pty is being created entirely inside the container by sshd.

Details copied from https://github.com/lxc/lxd/issues/2930

# Steps to reproduce

1. Create two Ubuntu 16.04 lxd containers, one privileged, one not.
2. ssh into each one, and then use `sudo -s` to get root. (Do not use `lxc 
exec` because of issue #1641236)
3. Inside one run `tcpdump -i eth0 -nn not tcp port 22`, and ping from the 
other.

tcpdump in the privileged container works just fine.

tcpdump in the unprivileged container does not show any output. But if I
run strace on it I see errors attempting to access stdout and stderr:

~~~
ioctl(1, TCGETS, 0x7fff97c8d680)= -1 ENOTTY (Inappropriate ioctl for 
device)
...
write(2, "tcpdump: verbose output suppress"..., 75) = -1 EACCES (Permission 
denied)
write(2, "listening on eth0, link-type EN1"..., 74) = -1 EACCES (Permission 
denied)
~~~

This is very weird.  Even more weird: the following command *does*
capture packets:

~~~
tcpdump -i eth0 -nn -w foo.pcap
~~~

The file foo.pcap grows. This proves it's nothing to do with network
capture perms.

But the following command shows no output:

~~~
tcpdump -r foo.pcap -nn
~~~

And again it's because it can't write to stdout:

~~~
fstat(1, 0x7ffe2fb5eb10)= -1 EACCES (Permission denied)
read(3, "", 4096)   = 0
write(1, "14:34:30.618180 IP6 fe80::c609:6"..., 1740) = -1 EACCES (Permission 
denied)
~~~

I had originally thought this was to do with capabilities.  But if I run
`capsh --print` inside both containers, they both have `cap_net_raw` and
`cap_net_admin`.  In fact, the unprivileged container has two additional
capabilities!  (`cap_mac_override` and `cap_mac_admin`)

So now I suspect that apparmor is at fault.

 dmesg

dmesg output generated by the following steps:

* start tcpdump
* wait 5 seconds
* send 1 ping from other side
* wait 5 seconds
* stop tcpdump

~~~
[429020.685987] audit: type=1400 audit(1487774339.708:3597): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-srv2-campus1_" 
profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" 
requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001
[429020.686000] audit: type=1400 audit(1487774339.708:3598): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-srv2-campus1_" 
profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" 
requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001
[429020.686013] audit: type=1400 audit(1487774339.708:3599): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-srv2-campus1_" 
profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" 
requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001
[429020.686022] audit: type=1400 audit(1487774339.708:3600): apparmor="DENIED" 
operation="file_inherit" namespace="root//lxd-srv2-campus1_" 
profile="/usr/sbin/tcpdump" name="/dev/pts/0" pid=12539 comm="tcpdump" 
requested_mask="wr" denied_mask="wr" fsuid=10 ouid=101001
[429020.716725] device eth0 entered promiscuous mode
[429020.741308] audit: type=1400 audit(1487774339.764:3601): apparmor="DENIED" 
operation="file_perm" info="Failed name lookup - disconnected path" error=-13 
namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" 
name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="w" 
denied_mask="w" fsuid=10 ouid=0
[429020.741330] audit: type=1400 audit(1487774339.764:3602): apparmor="DENIED" 
operation="file_perm" info="Failed name lookup - disconnected path" error=-13 
namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" 
name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="w" 
denied_mask="w" fsuid=10 ouid=0
[429021.716785] audit: type=1400 audit(1487774340.740:3603): apparmor="DENIED" 
operation="getattr" info="Failed name lookup - disconnected path" error=-13 
namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" 
name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="r" 
denied_mask="r" fsuid=10 ouid=0
[429030.630448] audit: type=1400 audit(1487774349.652:3604): apparmor="DENIED" 
operation="file_perm" info="Failed name lookup - disconnected path" error=-13 
namespace="root//lxd-srv2-campus1_" profile="/usr/sbin/tcpdump" 
name="apparmor/.null" pid=12539 comm="tcpdump" requested_mask="w" 
denied_mask="w" fsuid=10 ouid=0

[Bug 1541678] Re: if-post-down.d/vlan and if-pre-up.d/vlan should support predictable NIC names

[Brian Candler]

It has been pointed out to me that if you combine "vlan-raw-device" with
"pre-up" then you have a complete workaround:

-
auto eno1.100
iface eno1.100 inet manual
  vlan-raw-device eno1

auto br100
iface br100 inet manual
  bridge_ports eno1.100
  bridge_stp off
  bridge_fd 0
  bridge_maxwait 0
  pre-up ifup eno1.100
-

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541678

Title:
  if-post-down.d/vlan and if-pre-up.d/vlan should support predictable
  NIC names

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1541678] Re: if-post-down.d/vlan and if-pre-up.d/vlan should support predictable NIC names

[Brian Candler]

To avoid the patch in #7, you can set vlan-raw-device explicitly:

-
auto eno1.100
iface eno1.100 inet manual
  vlan-raw-device eno1
-

Note that if you link this to a bridge, then bringing up the bridge
doesn't bring up the vlan bridge ports:

-
auto eno1.100
iface eno1.100 inet manual
  vlan-raw-device eno1

auto br100
iface br100 inet manual
  bridge_portseno1.100
  bridge_stp  off
  bridge_fd   0
  bridge_maxwait  0
-

Result:

-
# ifup br100
interface eno1.100 does not exist!
# brctl show br100
bridge name bridge id   STP enabled interfaces
br100   8000.   no
# cat /proc/net/vlan/config
VLAN Dev name| VLAN ID
Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
#
-

But it *does* work if you explicitly bring up the interface first: in
fact, that also brings up the bridge.

-
# ifdown br100
# ifup eno1.100
# brctl show br100
bridge name bridge id   STP enabled interfaces
br100   8000.001fc69bf7eb   no  eno1.100
# ifup br100
ifup: interface br100 already configured
#
-

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541678

Title:
  if-post-down.d/vlan and if-pre-up.d/vlan should support predictable
  NIC names

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

Rather than backporting slirp fixes from 2.7.0 to 2.5.0, how about qemu
2.7 or 2.8 in backports?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630911] Re: freeipa-client has a hard dependency on "ntp" which is not wanted in lxd environment

[Brian Candler]

> client install expects ntpd to be present

I'm not quite sure what you mean.

"freeipa-client --install" does indeed give NTP errors, but it still
proceeds. Here is a transcript of installing freeipa-client inside a
(privileged) 16.04 lxd container.


root@unifi:~# apt-get install freeipa-client sssd-tools 
...
root@unifi:~# ipa-client-install --domain IPA.EXAMPLE.COM --mkhomedir -p admin 
-W
Discovery was successful!
Client hostname: unifi.int.example.com
Realm: IPA.EXAMPLE.COM
DNS Domain: IPA.EXAMPLE.COM
IPA Server: lon-ipa-1.int.example.com
BaseDN: dc=ipa,dc=example,dc=com

Continue to configure the system with these values? [no]: yes
Synchronizing time with KDC...
Attempting to sync time using ntpd.  Will timeout after 15 seconds
Attempting to sync time using ntpd.  Will timeout after 15 seconds
Attempting to sync time using ntpd.  Will timeout after 15 seconds
Attempting to sync time using ntpd.  Will timeout after 15 seconds
Attempting to sync time using ntpd.  Will timeout after 15 seconds
Unable to sync time with NTP server, assuming the time is in sync. Please check 
that 123 UDP port is opened.
Password for ad...@ipa.example.com:
Successfully retrieved CA cert
Subject: CN=Certificate Authority,O=IPA.EXAMPLE.COM
Issuer:  CN=Certificate Authority,O=IPA.EXAMPLE.COM
Valid From:  Thu Oct 27 15:27:53 2016 UTC
Valid Until: Mon Oct 27 15:27:53 2036 UTC

Enrolled in IPA realm IPA.EXAMPLE.COM
Created /etc/ipa/default.conf
New SSSD config will be created
Configured sudoers in /etc/nsswitch.conf
Configured /etc/sssd/sssd.conf
Configured /etc/krb5.conf for IPA realm IPA.EXAMPLE.COM
trying https://lon-ipa-1.int.example.com/ipa/json
Forwarding 'ping' to json server 'https://lon-ipa-1.int.example.com/ipa/json'
Forwarding 'ca_is_enabled' to json server 
'https://lon-ipa-1.int.example.com/ipa/json'
Systemwide CA database updated.
Adding SSH public key from /etc/ssh/ssh_host_rsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ecdsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_dsa_key.pub
Adding SSH public key from /etc/ssh/ssh_host_ed25519_key.pub
Forwarding 'host_mod' to json server 
'https://lon-ipa-1.int.example.com/ipa/json'
Could not update DNS SSHFP records.
SSSD enabled
Configured /etc/openldap/ldap.conf
NTP enabled
Configured /etc/ssh/ssh_config
Configured /etc/ssh/sshd_config
Configuring IPA.EXAMPLE.COM as NIS domain.
Client configuration complete.
root@unifi:~# id brian.candler
uid=121103(brian.candler) gid=121103(brian.candler) 
groups=121103(brian.candler),121100(admins)


(Note that in my case the KDC itself is in a container, so there is no NTP 
daemon running inside it for the client to talk to anyway)

So enrolment works. The problem is that installation of freeipa-client
inside the client container has forcibly installed and started ntpd,
which cannot possibly work:

root@unifi:~# dpkg-query -l ntp
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion  Architecture Description
+++-===---===
ii  ntp 1:4.2.8p4+dfsg-3 amd64Network Time 
Protocol daemon and utility programs
root@unifi:~# ps auxwww | grep ntpd
root  7649  0.0  0.0 103708  3820 ?Ss   10:49   0:00 /usr/sbin/ntpd 
-p /var/run/ntpd.pid -u 113:117
root  7721  0.0  0.0  11284   944 ?S+   10:53   0:00 grep 
--color=auto ntpd
root@unifi:~# systemctl status ntp
● ntp.service - LSB: Start NTP daemon
   Loaded: loaded (/etc/init.d/ntp; bad; vendor preset: enabled)
   Active: active (running) since Sat 2017-01-14 10:49:18 UTC; 4min 23s ago
 Docs: man:systemd-sysv-generator(8)
  Process: 7629 ExecStop=/etc/init.d/ntp stop (code=exited, status=0/SUCCESS)
  Process: 7639 ExecStart=/etc/init.d/ntp start (code=exited, status=0/SUCCESS)
Tasks: 1
   Memory: 636.0K
  CPU: 31ms
   CGroup: /system.slice/ntp.service
   └─7649 /usr/sbin/ntpd -p /var/run/ntpd.pid -u 113:117

Jan 14 10:49:18 unifi ntpd[7649]: restrict ::: KOD does nothing without LIMITED.
Jan 14 10:49:18 unifi ntpd[7649]: Listen and drop on 0 v6wildcard [::]:123
Jan 14 10:49:18 unifi ntpd[7649]: Listen and drop on 1 v4wildcard 0.0.0.0:123
Jan 14 10:49:18 unifi ntpd[7649]: Listen normally on 2 lo 127.0.0.1:123
Jan 14 10:49:18 unifi ntpd[7649]: Listen normally on 3 eth0 10.0.0.121:123
Jan 14 10:49:18 unifi ntpd[7649]: Listen normally on 4 lo [::1]:123
Jan 14 10:49:18 unifi ntpd[7649]: Listen normally on 5 eth0 
[fe80::216:3eff:fe45:8115%71]:123
Jan 14 10:49:18 unifi ntpd[7649]: Listening on routing socket on fd #22 for 
interface updates
Jan 14 10:49:18 unifi ntpd[7649]: start_kern_loop: ntp_loopfilter.c line 1126: 
ntp_adjtime: Operation not permitted
Jan 14 10:49:18 unifi ntpd[7649]: set_freq: 

[Bug 1580765] Re: Need support for rewriting mount sources

[Brian Candler]

With the same nodes fully updated (kernel 4.4.0-53, lxd 2.0.8, criu
2.6-1ubuntu1~ubuntu16.04.2), I find that live migration now works - yay!

Note: this is only if I don't change the container name. If I do (e.g.
"lxc move sample nuc1:foobar") then I get:

error: migration restore failed
(00.059324) Warn  (criu/apparmor.c:421): apparmor namespace 
/sys/kernel/security/apparmor/policy/namespaces/lxd-sample_ 
already exists, restoring into it
(00.063180) Warn  (criu/cr-restore.c:853): Set CLONE_PARENT | CLONE_NEWPID but 
it might cause restore problem,because not all kernels support such clone flags 
combinations!
(00.168620)  1: Warn  (criu/autofs.c:77): Failed to find pipe_ino option 
(old kernel?)
(00.182952)  1: Error (criu/mount.c:2517): mnt: Can't mount at 
./dev/.lxd-mounts: No such file or directory
(00.201952) Error (criu/cr-restore.c:1024): 5637 killed by signal 9: Killed
(00.230527) Error (criu/cr-restore.c:1890): Restoring FAILED.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1580765

Title:
  Need support for rewriting mount sources

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] Re: Recovery mode won't allow recovery after manually installing the OS incorrectly

[Brian Candler]

BTW, I reproduced the same problem in a different (and arguably more
realistic) scenario:

- install ubuntu 16.04
- configure networking with a bridge interface but a port member that doesn't 
exist when you next boot up (e.g. make br0 with a member which is a USB 
ethernet adapter, and then remove the USB adapter)
- reboot - you find it hangs for about 6 minutes
- so you decide to reboot again, and go into recovery mode to fix the 
networking config

Then you get the same as described before: you get a recovery shell
which works for a few minutes, but then systemd continues with the
bootup and blats over the recovery shell with a new session, making the
system unusable.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  Recovery mode won't allow recovery after manually installing the OS
  incorrectly

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

I have been working with the qemu devs, was able to reproduce the slirp 
networking crashes under valgrind, and they provided a fix:
http://lists.nongnu.org/archive/html/qemu-devel/2016-11/msg02411.html

The fix has also been merged upstream:

commit ea64d5f08817b5e79e17135dce516c7583107f91
Author: Samuel Thibault <samuel.thiba...@ens-lyon.org>
Date:   Sun Nov 13 23:54:27 2016 +0100

slirp: Fix access to freed memory

if_start() goes through the slirp->if_fastq and slirp->if_batchq
list of pending messages, and accesses ifm->ifq_so->so_nqueued of its
elements if ifm->ifq_so != NULL.  When freeing a socket, we thus need
to make sure that any pending message for this socket does not refer
to the socket any more.

Signed-off-by: Samuel Thibault <samuel.thiba...@ens-lyon.org>
    Tested-by: Brian Candler <b.cand...@pobox.com>
Reviewed-by: Stefan Hajnoczi <stefa...@redhat.com>

So now everything is fine as long as I build qemu 2.7.0 + this patch
from source.

I'm not sure whether back-porting this to 2.5.0 would be useful. It
looks like it could apply, but I believe there was a big reworking of
SLIRP around 2.6 which could have fixed other problems.  I can ask the
question on the list if you like.

I'm planning to use 2.7 going forward since that's what I've tested
heavily.  Having qemu 2.7.0 + this patch in xenial-backports would be
helpful for me, but I can also live with having to build from source
until Ubuntu 18.04 is out.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1566930] Re: wget does not support IPv6 address with scoped zone (RFC 4007)

[Brian Candler]

Workaround is to use IPv4/NAT networking instead of link-local
IPv6/http_proxy.

1. configure your lxdbr0 network with (private) IPv4 addresses and DHCP
pool in /etc/default/lxd-bridge. Also set LXD_IPV4_NAT="true" and
LXD_IPV6_PROXY="false". Restart.

2. "lxc profile edit default" to no longer use the IPv6 proxy.

name: default
config: {}
description: Default LXD profile
devices:
  eth0:
name: eth0
nictype: bridged
parent: lxdbr0
type: nic

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1566930

Title:
  wget does not support IPv6 address with scoped zone (RFC 4007)

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

Sorry about this - the repo was open at the time I posted but is
currently closed for layer 9 reasons. I am trying to get permission to
release this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

FYI, update:

- I have upgraded my Mac Mini to 16.04 (plus qemu 2.7.0 from source)
- I have completely replaced the RAM in my Mac Mini
- I have replicated on someone else's Mac Mini with 16.04

I can still replicate the new segfault/libc problems, so I'm sure that
it's not a hardware issue.

The new crashes are harder to obtain, but I can get them if I run the
build process with 1 vCPU, or if I configure 8 vCPUs but run 4 instances
of the build process concurrently.

Anyway, that part of this ticket can be ignored as I'll be raising this
upstream with the qemu project.

The original part of this ticket is that qemu crashes in tcp_output in
its SLIP networking code. I still think the pragmatic solution would be
to have qemu 2.7.0 in xenial-backports.

I personally don't plan on spending time working out where exactly the
fix is and backporting it to qemu 2.5.0; and people using the SLIP
networking code in production are probably quite rare (although
packer.io's qemu builder is an example of this)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630911] Re: freeipa-client has a hard dependency on "ntp" which is not wanted in lxd environment

[Brian Candler]

"the client setup would fail if there's no ntp installed"

In what way?

Is what you're really saying that the client setup would fail if the
clock of the client is not within X seconds of the real time? That's
correct, but is not the same as saying ntp must be installed.

There are other ways of obtaining time sufficiently synchronized for
Kerberos to work; hence my second suggestion of having a virtual package
meaning "the system must have synchronized time (somehow)". This is
similar to the virtual package which says "the system must have a mail-
transport-agent (but I don't care which one)"

However, "recommends" ntp would actually install it in most cases - i.e.
unless the user specifies "--no-install-recommends", or has modified
their apt config.  If the user explicitly asks not to install
"recommended" packages, then they are saying they are happy to deal with
the possible consequences.

Also, I don't think detecting lxc/lxd is a good idea. There are other
virtualization environments which ensure the guest clock is
synchronized, without running NTP on the guest, so this would not be a
generic solution.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630911

Title:
  freeipa-client has a hard dependency on "ntp" which is not wanted in
  lxd environment

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630946] [NEW] ubuntu-server depends on open-iscsi and runs iscsid

[Brian Candler]

Public bug reported:

ubuntu-server has a hard dependency on open-iscsi, which means there is
a daemon running (iscsid), and the package cannot be removed. All
unnecessary daemons are a cause of concern when auditing a system.

Propose moving this to "Recommends" instead, which currently has:

Recommends: lxd, snapd

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: ubuntu-server 1.361
ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19
Uname: Linux 4.4.0-38-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Oct  6 10:43:04 2016
Ec2AMI: ami-c06b1eb3
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1a
Ec2InstanceType: t2.medium
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=xterm-256color
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
 XDG_RUNTIME_DIR=
SourcePackage: ubuntu-meta
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug ec2-images xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630946

Title:
  ubuntu-server depends on open-iscsi and runs iscsid

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630911] Re: freeipa-client has a hard dependency on "ntp" which is not wanted in lxd environment

[Brian Candler]

Or maybe what's needed is a virtual package called e.g. "synchronized-
time", which freeipa-client depends on and is provided by ntp.

Then you could install a dummy package inside the container, which also
provides "synchronized-time"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630911

Title:
  freeipa-client has a hard dependency on "ntp" which is not wanted in
  lxd environment

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630911] [NEW] freeipa-client has a hard dependency on "ntp" which is not wanted in lxd environment

[Brian Candler]

Public bug reported:

[Note: the package is called "freeipa-client" but launchpad only lets me
select "freeipa"]

The "freeipa-client" package has a hard dependency on "ntp".

However: when running Ubuntu inside an lxd container, ntpd cannot run:
the host is responsible for setting the clock, not the container.

Hence I want to "apt-get remove ntp" from inside the container. But if I
do so, this forcibly removes the "freeipa-client" package as well,
because of the dependency. This in turn leaves a whole heap of dangling
packages - see below - which are vulnerable to being accidentally
removed.

Proposal: change to "Recommends: ntp" instead of "Depends: ntp"


---
# apt-get remove ntp
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  bind9utils certmonger cracklib-runtime freeipa-common ieee-data iproute
  libavahi-client3 libavahi-common-data libavahi-common3 libbasicobjects0
  libc-ares2 libcollection4 libcrack2 libcups2 libcurl3 libcurl3-nss libdhash1
  libfreetype6 libini-config5 libipa-hbac0 libjbig0 libjpeg-turbo8 libjpeg8
  liblcms2-2 libldb1 libnfsidmap2 libnl-3-200 libnl-route-3-200 libnspr4
  libnss-sss libnss3 libnss3-nssdb libnss3-tools libopts25 libpam-pwquality
  libpam-sss libpath-utils1 libpwquality-common libpwquality1 libref-array1
  libsmbclient libsss-idmap0 libsss-nss-idmap0 libsss-sudo libtdb1 libtevent0
  libtiff5 libwebp5 libwebpmux1 libxmlrpc-core-c3 libxslt1.1 oddjob
  oddjob-mkhomedir python-bs4 python-cffi python-cffi-backend python-chardet
  python-cryptography python-dbus python-decorator python-dnspython
  python-enum34 python-gi python-gssapi python-html5lib python-idna
  python-imaging python-ipaclient python-ipaddress python-ipalib
  python-jwcrypto python-ldap python-libipa-hbac python-lxml python-memcache
  python-netaddr python-nss python-pil python-pkg-resources python-ply
  python-pyasn1 python-pycparser python-qrcode python-setuptools python-six
  python-sss python-talloc python-usb python-yubico samba-libs sssd sssd-ad
  sssd-ad-common sssd-common sssd-ipa sssd-krb5 sssd-krb5-common sssd-ldap
  sssd-proxy
Use 'apt autoremove' to remove them.
The following packages will be REMOVED:
  freeipa-client ntp
0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.
1 not fully installed or removed.
After this operation, 2002 kB disk space will be freed.
Do you want to continue? [Y/n] n
Abort.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: freeipa-client 4.3.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
NonfreeKernelModules: nfsd auth_rpcgss nfs_acl lockd grace sunrpc 
ip6table_filter ip6_tables xt_conntrack ufs msdos xfs binfmt_misc veth 
ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 
nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack isofs xt_CHECKSUM iptable_mangle 
xt_tcpudp bridge stp llc iptable_filter ip_tables x_tables zfs zunicode zcommon 
znvpair spl zavl ppdev xen_fbfront syscopyarea sysfillrect sysimgblt 
fb_sys_fops serio_raw parport_pc parport ib_iser rdma_cm iw_cm ib_cm ib_sa 
ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi 
autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor 
async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul 
crc32_pclmul aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd 
psmouse floppy
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Oct  6 09:05:52 2016
Ec2AMI: ami-c06b1eb3
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: eu-west-1a
Ec2InstanceType: t2.medium
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
SourcePackage: freeipa
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug ec2-images xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630911

Title:
  freeipa-client has a hard dependency on "ntp" which is not wanted in
  lxd environment

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

I found that when I have

[ "-smp", "8,sockets=1,cores=4,threads=2" ],

in packer_files/vtp.json, the build completes successfully on my 14.04
Mac Mini with qemu 2.7.0. It worked several times flawlessly.

But if I remove that line (so that only one CPU is emulated by KVM) then
I get errors such as

Oct  5 17:13:03 brian kernel: [99660.108698] qemu-system-x86[26914]:
segfault at 5596d914cfb0 ip 7f1d1244fc5e sp 7f1985bdc770 error 4
in libc-2.19.so[7f1d123d+1ba000]

During the build there is an increasing number of lxd containers
running; so perhaps having so much load on a single emulated CPU is
triggering this condition.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

> how can we reproduce this? Can you give a precise set of steps to
download/build an image and run qemu with it?

(1) The first issue - segfault in slirp/tcp_output.c - which is also
this one:

https://lists.nongnu.org/archive/html/qemu-devel/2014-11/msg03636.html

You can reproduce using the project I am working on:


# See packer.io. "packer" builds images from ISOs.
wget https://releases.hashicorp.com/packer/0.10.2/packer_0.10.2_linux_amd64.zip
unzip https://releases.hashicorp.com/packer/0.10.2/packer_0.10.2_linux_amd64.zip
sudo mv packer /usr/local/bin/

# My project
git clone https://git.nsrc.org/open/vtp.git
cd vtp
./run.sh
~~~

There is a phase where it clones pc-master to pc1, pc2, pc3 etc.
Typically it segfaults somewhere between pc12 and pc20. I saw this with
both ubuntu 14.04 and 16.04 stock qemu, but not with qemu 2.7.0 from
source.

It might be performance-sensitive; both machines tested are Macmini6,2
(Mac Mini Server 2012, quad core) with SSDs.

Note however: you may consider this a low-priority issue, in the sense
that the kvm "slirp" functionality is not normally used in production.
It is used by packer because of its built-in NAT function: the VM gets
10.0.2.15 and it sees the host as "gateway" 10.0.2.2, which gives the VM
a temporary network connection without having to run iptables or dhcpd
on the host.

It certainly seems not to have any attention from qemu upstream, and in
any case they may not be interested in backporting the fix from 2.6 or
2.7 to 2.5.

The quickest and easiest solution I think would be to have qemu 2.7.0 in
xenial-backports.


(2) The subsequent random crashes with qemu 2.7.0, i.e. SEGV in malloc(), 
invalid pointer in free(), on my 14.04 Mac Mini. These don't always reproduce, 
and I have not yet ruled out as being a hardware problem. But by all means see 
if you get them once you get past the slirp issue.

To use a different version of qemu in the build you modify
packer_files/vtp.json:

...
  "builders":
  [
{
  "type": "qemu",
  "qemu_binary": "/usr/local/bin/qemu-system-x86_64",
   ...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

I have now tried this on someone else's Mac Mini, this one running
16.04.1.

With the stock qemu (1:2.5+dfsg-5ubuntu10.5), it crashes in apparently
the same way as mine was doing originally:

Oct  5 14:59:49 s1 kernel: [3982196.302758] qemu-system-x86[20590]:
segfault at 55fc165caa20 ip 55fd12d76ab7 sp 7ffdec4cfab0 error 4
in qemu-system-x86_64[55fd1294f000+64]

Which is good, as it shows the original problem is definitely a software
problem in qemu.

Then I built qemu-2.7.0 from source on this machine. Unfortunately I
don't seem able to attach gdb: using "gdb -p " I get:

Warning:
Cannot insert breakpoint -1.
Cannot access memory at address 0x202210

(gdb) 0x7f199113ff51 in ?? ()

(gdb) cont
Continuing.
Warning:
Cannot insert breakpoint -1.
Cannot access memory at address 0x202210

Command aborted.
(gdb)

I just have to run without gdb. And this time, it ran to completion
without any malloc errors.

So I can't yet conclude whether there is also a hardware issue, until I
upgrade the local machine to 16.04 (at which point I'll lose the ability
to debug the issue in 14.04, but then again, at that point I probably
won't care :-)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

Hmm, a different malloc-type error on next run:

Program received signal SIGABRT, Aborted.
0x7f7b20acbc37 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56 ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0 0x7f7b20acbc37 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1 0x7f7b20acf028 in __GI_abort () at abort.c:89
#2 0x7f7b20b082a4 in __libc_message (do_abort=do_abort@entry=1,
fmt=fmt@entry=0x7f7b20c166b0 "*** Error in `%s': %s: 0x%s ***\n")
at ../sysdeps/posix/libc_fatal.c:175
#3 0x7f7b20b1455e in malloc_printerr (ptr=,
str=0x7f7b20c12801 "free(): invalid pointer", action=1) at malloc.c:4996
#4 _int_free (av=, p=, have_lock=0)
at malloc.c:3840
#5 0x563c539742ea in coroutine_trampoline (i0=,
i1=) at util/coroutine-ucontext.c:78
#6 0x7f7b20ade800 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7 0x7fffc12967b0 in ?? ()
#8 0x in ?? ()
(gdb)

I am going to see if I can run this build on some different hardware.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630225] Re: segfault in qemu-system-x86_64

[Brian Candler]

*** This bug is a duplicate of bug 1630226 ***
https://bugs.launchpad.net/bugs/1630226

Hmm, a different malloc-type error on next run:

Program received signal SIGABRT, Aborted.
0x7f7b20acbc37 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
56  ../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb) bt
#0  0x7f7b20acbc37 in __GI_raise (sig=sig@entry=6)
at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x7f7b20acf028 in __GI_abort () at abort.c:89
#2  0x7f7b20b082a4 in __libc_message (do_abort=do_abort@entry=1,
fmt=fmt@entry=0x7f7b20c166b0 "*** Error in `%s': %s: 0x%s ***\n")
at ../sysdeps/posix/libc_fatal.c:175
#3  0x7f7b20b1455e in malloc_printerr (ptr=,
str=0x7f7b20c12801 "free(): invalid pointer", action=1) at malloc.c:4996
#4  _int_free (av=, p=, have_lock=0)
at malloc.c:3840
#5  0x563c539742ea in coroutine_trampoline (i0=,
i1=) at util/coroutine-ucontext.c:78
#6  0x7f7b20ade800 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x7fffc12967b0 in ?? ()
#8  0x in ?? ()
(gdb)

I am going to see if I can run this build on some different hardware.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630225

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

For comparison I built qemu-2.5.1.1 from the release tarball at
http://wiki.qemu.org/Download, using the same configure options. (I
picked that one as being closest to what's in xenial)

And it crashes in exactly the same place:

Program received signal SIGSEGV, Segmentation fault.
tcp_output (tp=tp@entry=0x563e2b3ae180) at slirp/tcp_output.c:127
127 len = min(so->so_snd.sb_cc, win) - off;
(gdb) bt
#0  tcp_output (tp=tp@entry=0x563e2b3ae180) at slirp/tcp_output.c:127
#1  0x563e28bdce4a in tcp_drop (tp=tp@entry=0x563e2b3ae180,
err=err@entry=0) at slirp/tcp_subr.c:232
#2  0x563e28bde172 in tcp_timers (timer=2, tp=0x563e2b3ae180)
at slirp/tcp_timer.c:287
#3  tcp_slowtimo (slirp=slirp@entry=0x563e2a2bffd0) at slirp/tcp_timer.c:88
#4  0x563e28bd7988 in slirp_pollfds_poll (pollfds=0x563e2a2ac200,
select_error=select_error@entry=0) at slirp/slirp.c:486
#5  0x563e28c11b21 in main_loop_wait (nonblocking=)
at main-loop.c:506
#6  0x563e2897730f in main_loop () at vl.c:1923
#7  main (argc=, argv=, envp=)
at vl.c:4699
(gdb)

Then I built 2.7.0, the latest release. This time the build ran
successfully past where it was crashing before - so it looks like the
fix occurred somewhere on the 2.6 or 2.7 branch - and indeed almost to
the end.

It then crashed with a different problem:

Program received signal SIGSEGV, Segmentation fault.
_int_malloc (av=av@entry=0x7f55445b9760 , bytes=bytes@entry=96)
at malloc.c:3389
3389malloc.c: No such file or directory.
(gdb) bt
#0  _int_malloc (av=av@entry=0x7f55445b9760 , bytes=bytes@entry=96)
at malloc.c:3389
#1  0x7f554427e1dc in __libc_calloc (n=,
elem_size=) at malloc.c:3219
#2  0x7f5544f50669 in g_malloc0 ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x55ee83c2375c in handle_alloc (m=0x55ee896442d8,
bytes=, host_offset=,
guest_offset=5247094784, bs=0x55ee852b43c0) at block/qcow2-cluster.c:1219
#4  qcow2_alloc_cluster_offset (bs=bs@entry=0x55ee852b43c0,
offset=offset@entry=5247094784, bytes=bytes@entry=0x55ee896442cc,
host_offset=host_offset@entry=0x55ee896442d0, m=m@entry=0x55ee896442d8)
at block/qcow2-cluster.c:1361
#5  0x55ee83c1652f in qcow2_co_pwritev (bs=0x55ee852b43c0,
offset=5247094784, bytes=45056, qiov=0x55ee8572ecf0, flags=)
at block/qcow2.c:1589
#6  0x55ee83c445b1 in bdrv_driver_pwritev (bs=bs@entry=0x55ee852b43c0,
offset=offset@entry=5247094784, bytes=bytes@entry=45056,
qiov=qiov@entry=0x55ee8572ecf0, flags=flags@entry=0) at block/io.c:856
#7  0x55ee83c454f1 in bdrv_aligned_pwritev (bs=bs@entry=0x55ee852b43c0,
req=req@entry=0x55ee896444d0, offset=offset@entry=5247094784,
bytes=bytes@entry=45056, align=align@entry=1, qiov=0x55ee8572ecf0,
flags=flags@entry=0) at block/io.c:1320
#8  0x55ee83c46337 in bdrv_co_pwritev (child=,
offset=offset@entry=5247094784, bytes=bytes@entry=45056,
qiov=qiov@entry=0x55ee8572ecf0, flags=0) at block/io.c:1569
#9  0x55ee83c36e3f in blk_co_pwritev (blk=0x55ee852b4200,
offset=5247094784, bytes=45056, qiov=0x55ee8572ecf0, flags=)
at block/block-backend.c:788
#10 0x55ee83c36f7e in blk_aio_write_entry (opaque=0x55ee866efce0)
at block/block-backend.c:982
#11 0x55ee83cb52ea in coroutine_trampoline (i0=,
i1=) at util/coroutine-ucontext.c:78
#12 0x7f5544244800 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#13 0x7ffc813491a0 in ?? ()
#14 0x in ?? ()
(gdb)

This doesn't make any sense to me. ENOENT in malloc.c ?  But I wasn't
able to reproduce this one.

I suspect that qemu 2.5.0 which comes with xenial has similar problems,
unless it has had a fix backported. I'll be able to tell when I rebuild
this system with xenial (planned but won't take place immediately)

I would in any case be interested in seeing qemu 2.7.0 in xenial-
backports.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

It depends on a ton of libraries (literally):

$ ldd /usr/bin/qemu-system-x86_64 | wc -l
100

But using the dev packages I already had around, plus libfdt-dev which
it insisted on, I have done the following:

apt-get source qemu-system-x86
cd qemu-2.0.0+dfsg
./configure --disable-strip --target-list=x86_64-softmmu,x86_64-linux-user
make
sudo make install

For some reason the binaries in pc-bios/ are missing, and "make install"
barfs on this. I located as many as I could:

cp -pr /usr/share/seabios/* pc-bios/
cp /usr/share/misc/sgabios.bin pc-bios/
cp pc-bios/vgabios-isavga.bin pc-bios/vgabios.bin
cp /usr/lib/ipxe/qemu/*
cp -L /usr/share/qemu/* pc-bios/

Still some missing, so I took them out from INSTALL_BLOBS in Makefile

Any way I now have... *something* in /usr/local/bin. And it runs. And
hooray, it fails in the same way and I have a backtrace!

Program received signal SIGSEGV, Segmentation fault.
tcp_output (tp=tp@entry=0x5636d9186db0) at slirp/tcp_output.c:127
127 len = min(so->so_snd.sb_cc, win) - off;
(gdb) bt
#0  tcp_output (tp=tp@entry=0x5636d9186db0) at slirp/tcp_output.c:127
#1  0x5636d5a9067a in tcp_drop (tp=tp@entry=0x5636d9186db0,
err=err@entry=0) at slirp/tcp_subr.c:232
#2  0x5636d5a919a2 in tcp_timers (timer=2, tp=0x5636d9186db0)
at slirp/tcp_timer.c:287
#3  tcp_slowtimo (slirp=slirp@entry=0x5636d824e820) at slirp/tcp_timer.c:88
#4  0x5636d5a8c538 in slirp_pollfds_poll (pollfds=0x5636d8246a00,
select_error=select_error@entry=0) at slirp/slirp.c:488
#5  0x5636d5a3cc37 in main_loop_wait (nonblocking=)
at main-loop.c:487
#6  0x5636d590ff1e in main_loop () at vl.c:2051
#7  main (argc=, argv=, envp=)
at vl.c:4510
(gdb)


(gdb) print so
$1 = (struct socket *) 0x5635d8489920
(gdb) print so->so_snd
Cannot access memory at address 0x5635d84899a0

There's the segfault. And it looks to be the same problem as this:

https://lists.nongnu.org/archive/html/qemu-
devel/2014-11/msg03636.html

Unfortunately that gave no resolution other than "use the tap netdev
instead of slirp"

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

I installed some more *-dbg and *-devel packages (including
libstdc++6-4.8-dbg), and now the backtrace is marginally more helpful -
although possibly this is a different trace?


Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f95f3fff700 (LWP 10149)]
__memcpy_sse2_unaligned ()
at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:35
35  ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S: No such file or 
directory.
(gdb) bt
#0  __memcpy_sse2_unaligned ()
at ../sysdeps/x86_64/multiarch/memcpy-sse2-unaligned.S:35
#1  0x558db62a78c3 in ?? ()
#2  0x558db62a8735 in ?? ()
#3  0x558db641a06b in ?? ()
#4  0x7f9997cbc184 in start_thread (arg=0x7f95f3fff700)
at pthread_create.c:312
#5  0x7f99979e937d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111
(gdb)

A second crash was the same as the first:

Program received signal SIGSEGV, Segmentation fault.
0x557d8732cd20 in ?? ()
(gdb) bt
#0  0x557d8732cd20 in ?? ()
#1  0x557d8732d96a in ?? ()
#2  0x557d8732ec92 in ?? ()
#3  0x557d87329828 in ?? ()
#4  0x557d872d9e77 in ?? ()
#5  0x557d87181bd6 in ?? ()
#6  0x7f200b9ebf45 in __libc_start_main (main=0x557d87180640, argc=17,
argv=0x7ffca5a399c8, init=, fini=,
rtld_fini=, stack_end=0x7ffca5a399b8) at libc-start.c:287
#7  0x557d8718612c in ?? ()
(gdb)


BTW, there have also been single line logs in syslog each segfault time:

$ grep segfault /var/log/kern.log
Oct  3 10:48:20 brian kernel: [137022.004997] qemu-system-x86[13755]: segfault 
at 558bdc2d2e08 ip 7f694e12cd1c sp 7ffcfa8660e8 error 4 in 
libc-2.19.so[7f694e0aa000+1ba000]
Oct  3 18:05:30 brian kernel: [163253.679372] qemu-system-x86[11074]: segfault 
at 565334c7cc10 ip 56542a917d20 sp 7ffd6a51b770 error 4 in 
qemu-system-x86_64[56542a6ce000+4b1000]
Oct  4 06:04:35 brian kernel: [206401.615476] qemu-system-x86[5957]: segfault 
at 559c8d38a350 ip 559d8a9c2d20 sp 7fff4b441040 error 4 in 
qemu-system-x86_64[559d8a779000+4b1000]
Oct  4 07:58:53 brian kernel: [213260.662734] qemu-system-x86[31953]: segfault 
at 55da4168ffb0 ip 55db3f369d20 sp 7ffcaa921340 error 4 in 
qemu-system-x86_64[55db3f12+4b1000]
Oct  4 10:26:01 brian kernel: [222089.607756] qemu-system-x86[4686]: segfault 
at 562f1e888360 ip 56301b98cd20 sp 7ffc2a185260 error 4 in 
qemu-system-x86_64[56301b743000+4b1000]
Oct  4 11:48:09 brian kernel: [227017.723519] qemu-system-x86[24041]: segfault 
at 5647ca92b250 ip 5648c536ad20 sp 7ffc2c0cd040 error 4 in 
qemu-system-x86_64[5648c5121000+4b1000]
Oct  4 12:20:15 brian kernel: [228943.353808] qemu-system-x86[32644]: segfault 
at 55772d989c00 ip 55782a2a8d20 sp 7ffc05ed8340 error 4 in 
qemu-system-x86_64[55782a05f000+4b1000]

I'm aware that hardware errors can cause segfaults. I've not seen this
in anything other than qemu, but that is probably when the system is
being stressed the most.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] Re: segfault in qemu-system-x86_64

[Brian Candler]

Attaching gdb to a running process gives the same result as I got from
the core dump.

(gdb) cont
Continuing.
[Thread 0x7f2877cfe700 (LWP 10805) exited]
[Thread 0x7f2876cfc700 (LWP 10816) exited]
[Thread 0x7f28774fd700 (LWP 10815) exited]
[Thread 0x7f2c015ff700 (LWP 10735) exited]
[Thread 0x7f2c09883700 (LWP 10721) exited]
[Thread 0x7f2c00c2a700 (LWP 10739) exited]
[Thread 0x7f28764fb700 (LWP 10817) exited]
[New Thread 0x7f28764fb700 (LWP 11470)]
[New Thread 0x7f2c00c2a700 (LWP 11473)]
[New Thread 0x7f2c09883700 (LWP 11474)]
[New Thread 0x7f2c015ff700 (LWP 11475)]
[New Thread 0x7f2877fff700 (LWP 11644)]
[New Thread 0x7f28777fe700 (LWP 11665)]
[New Thread 0x7f2876ffd700 (LWP 11836)]
[New Thread 0x7f2875cfa700 (LWP 11837)]
[New Thread 0x7f28754f9700 (LWP 11858)]
[New Thread 0x7f2874cf8700 (LWP 11923)]
[New Thread 0x7f2853fff700 (LWP 11924)]
[New Thread 0x7f28537fe700 (LWP 11925)]
[New Thread 0x7f2852ffd700 (LWP 11926)]
[New Thread 0x7f28527fc700 (LWP 11927)]
[New Thread 0x7f2851ffb700 (LWP 11928)]
[New Thread 0x7f28517fa700 (LWP 11929)]
[New Thread 0x7f2850ff9700 (LWP 11930)]
[Thread 0x7f2c00c2a700 (LWP 11473) exited]
[Thread 0x7f28754f9700 (LWP 11858) exited]
[Thread 0x7f2853fff700 (LWP 11924) exited]
[Thread 0x7f2875cfa700 (LWP 11837) exited]
[Thread 0x7f2877fff700 (LWP 11644) exited]
[Thread 0x7f2874cf8700 (LWP 11923) exited]
[Thread 0x7f28537fe700 (LWP 11925) exited]
[Thread 0x7f2c09883700 (LWP 11474) exited]
[Thread 0x7f2c015ff700 (LWP 11475) exited]
[Thread 0x7f28777fe700 (LWP 11665) exited]
[Thread 0x7f2851ffb700 (LWP 11928) exited]
[Thread 0x7f2876ffd700 (LWP 11836) exited]
[Thread 0x7f2852ffd700 (LWP 11926) exited]
[Thread 0x7f28517fa700 (LWP 11929) exited]
[Thread 0x7f28527fc700 (LWP 11927) exited]
[Thread 0x7f2850ff9700 (LWP 11930) exited]
[New Thread 0x7f2850ff9700 (LWP 12898)]
[New Thread 0x7f28527fc700 (LWP 12955)]
[New Thread 0x7f28517fa700 (LWP 13039)]
[New Thread 0x7f2852ffd700 (LWP 13046)]
[New Thread 0x7f2c09883700 (LWP 13047)]
[New Thread 0x7f2c015ff700 (LWP 13048)]

Program received signal SIGSEGV, Segmentation fault.
0x55cc8dd2fd20 in ?? ()
(gdb) bt
#0  0x55cc8dd2fd20 in ?? ()
#1  0x55cc8dd3096a in ?? ()
#2  0x55cc8dd31c92 in ?? ()
#3  0x55cc8dd2c828 in ?? ()
#4  0x55cc8dcdce77 in ?? ()
#5  0x55cc8db84bd6 in ?? ()
#6  0x7f2c12f5ff45 in __libc_start_main (main=0x55cc8db83640, argc=17,
argv=0x7fff83a85d28, init=, fini=,
rtld_fini=, stack_end=0x7fff83a85d18) at libc-start.c:287
#7  0x55cc8db8912c in ?? ()
(gdb)

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1630226

Title:
  segfault in qemu-system-x86_64

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1630226] [NEW] segfault in qemu-system-x86_64

[Brian Candler]

Public bug reported:

[Ubuntu 14.04 amd64 server, fully patched, xenial HWE kernel, on a 16GB
Mac Mini]

I am using packer (www.packer.io) to create a VM image. Packer starts a
qemu-system-x86_64 process; inside it's running an ubuntu 16.04 image
doing a bunch of work including running ansible to create a bunch of lxd
containers all running mysql. And then the qemu process itself segfaults
:-(

I have caught a coredump but it doesn't seem all that useful:

$ gdb -c /tmp/core_qemu-system-x86.24041 /usr/bin/qemu-system-x86_64
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/qemu-system-x86_64...(no debugging symbols 
found)...done.

warning: core file may not match specified executable file.
[New LWP 24041]
[New LWP 26214]
[New LWP 24045]
[New LWP 26215]
[New LWP 24043]
[New LWP 26321]
[New LWP 26326]
[New LWP 26017]
[New LWP 26325]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/qemu-system-x86_64 -netdev 
user,id=user.0,hostfwd=tcp::3234-:22 -devic'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x5648c536ad20 in ?? ()
(gdb) bt
#0  0x5648c536ad20 in ?? ()
#1  0x5648c536b96a in ?? ()
#2  0x5648c536cc92 in ?? ()
#3  0x5648c5367828 in ?? ()
#4  0x5648c5317e77 in ?? ()
#5  0x5648c51bfbd6 in ?? ()
#6  0x7f4b0e1a9f45 in __libc_start_main (main=0x5648c51be640, argc=17,
argv=0x7ffc2c0cd578, init=, fini=,
rtld_fini=, stack_end=0x7ffc2c0cd568) at libc-start.c:287
#7  0x5648c51c412c in ?? ()
(gdb) info threads
  Id   Target Id Frame
  9Thread 0x7f4fe700 (LWP 26325) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
  8Thread 0x7f47597fa700 (LWP 26017) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
  7Thread 0x7f4b04acd700 (LWP 26326) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
  6Thread 0x7f4776ffd700 (LWP 26321) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
  5Thread 0x7f4affe1d700 (LWP 24043) 0x7f4b0e2791e7 in ioctl ()
at ../sysdeps/unix/syscall-template.S:81
  4Thread 0x7f475bfff700 (LWP 26215) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
  3Thread 0x7f4afe5ff700 (LWP 24045) pthread_cond_wait@@GLIBC_2.3.2 ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  2Thread 0x7f4759ffb700 (LWP 26214) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
* 1Thread 0x7f4b13f24980 (LWP 24041) 0x5648c536ad20 in ?? ()
(gdb) thread apply all bt

Thread 9 (Thread 0x7f4fe700 (LWP 26325)):
#0  sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
#1  0x5648c54ad007 in ?? ()
#2  0x5648c536effc in ?? ()
#3  0x7f4b0e555184 in start_thread (arg=0x7f4fe700)
at pthread_create.c:312
#4  0x7f4b0e28237d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 8 (Thread 0x7f47597fa700 (LWP 26017)):
#0  sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
#1  0x5648c54ad007 in ?? ()
#2  0x5648c536effc in ?? ()
#3  0x7f4b0e555184 in start_thread (arg=0x7f47597fa700)
at pthread_create.c:312
#4  0x7f4b0e28237d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 7 (Thread 0x7f4b04acd700 (LWP 26326)):
#0  sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
#1  0x5648c54ad007 in ?? ()
#2  0x5648c536effc in ?? ()
#3  0x7f4b0e555184 in start_thread (arg=0x7f4b04acd700)
at pthread_create.c:312
#4  0x7f4b0e28237d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7f4776ffd700 (LWP 26321)):
#0  sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
#1  0x5648c54ad007 in ?? ()
#2  0x5648c536effc in ?? ()
#3  0x7f4b0e555184 in start_thread (arg=0x7f4776ffd700)
at pthread_create.c:312
#4  0x7f4b0e28237d in clone ()
---Type  to continue, or q  to quit---
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 

[Bug 1630225] [NEW] segfault in qemu-system-x86_64

[Brian Candler]

Public bug reported:

[Ubuntu 14.04 amd64 server, fully patched, xenial HWE kernel, on a 16GB
Mac Mini]

I am using packer (www.packer.io) to create a VM image. Packer starts a
qemu-system-x86_64 process; inside it's running an ubuntu 16.04 image
doing a bunch of work including running ansible to create a bunch of lxd
containers all running mysql. And then the qemu process itself segfaults
:-(

I have caught a coredump but it doesn't seem all that useful:

$ gdb -c /tmp/core_qemu-system-x86.24041 /usr/bin/qemu-system-x86_64
GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from /usr/bin/qemu-system-x86_64...(no debugging symbols 
found)...done.

warning: core file may not match specified executable file.
[New LWP 24041]
[New LWP 26214]
[New LWP 24045]
[New LWP 26215]
[New LWP 24043]
[New LWP 26321]
[New LWP 26326]
[New LWP 26017]
[New LWP 26325]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Core was generated by `/usr/bin/qemu-system-x86_64 -netdev 
user,id=user.0,hostfwd=tcp::3234-:22 -devic'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x5648c536ad20 in ?? ()
(gdb) bt
#0  0x5648c536ad20 in ?? ()
#1  0x5648c536b96a in ?? ()
#2  0x5648c536cc92 in ?? ()
#3  0x5648c5367828 in ?? ()
#4  0x5648c5317e77 in ?? ()
#5  0x5648c51bfbd6 in ?? ()
#6  0x7f4b0e1a9f45 in __libc_start_main (main=0x5648c51be640, argc=17,
argv=0x7ffc2c0cd578, init=, fini=,
rtld_fini=, stack_end=0x7ffc2c0cd568) at libc-start.c:287
#7  0x5648c51c412c in ?? ()
(gdb) info threads
  Id   Target Id Frame
  9Thread 0x7f4fe700 (LWP 26325) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
  8Thread 0x7f47597fa700 (LWP 26017) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
  7Thread 0x7f4b04acd700 (LWP 26326) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
  6Thread 0x7f4776ffd700 (LWP 26321) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
  5Thread 0x7f4affe1d700 (LWP 24043) 0x7f4b0e2791e7 in ioctl ()
at ../sysdeps/unix/syscall-template.S:81
  4Thread 0x7f475bfff700 (LWP 26215) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
  3Thread 0x7f4afe5ff700 (LWP 24045) pthread_cond_wait@@GLIBC_2.3.2 ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185
  2Thread 0x7f4759ffb700 (LWP 26214) sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
* 1Thread 0x7f4b13f24980 (LWP 24041) 0x5648c536ad20 in ?? ()
(gdb) thread apply all bt

Thread 9 (Thread 0x7f4fe700 (LWP 26325)):
#0  sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
#1  0x5648c54ad007 in ?? ()
#2  0x5648c536effc in ?? ()
#3  0x7f4b0e555184 in start_thread (arg=0x7f4fe700)
at pthread_create.c:312
#4  0x7f4b0e28237d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 8 (Thread 0x7f47597fa700 (LWP 26017)):
#0  sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
#1  0x5648c54ad007 in ?? ()
#2  0x5648c536effc in ?? ()
#3  0x7f4b0e555184 in start_thread (arg=0x7f47597fa700)
at pthread_create.c:312
#4  0x7f4b0e28237d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 7 (Thread 0x7f4b04acd700 (LWP 26326)):
#0  sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
#1  0x5648c54ad007 in ?? ()
#2  0x5648c536effc in ?? ()
#3  0x7f4b0e555184 in start_thread (arg=0x7f4b04acd700)
at pthread_create.c:312
#4  0x7f4b0e28237d in clone ()
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 6 (Thread 0x7f4776ffd700 (LWP 26321)):
#0  sem_timedwait ()
at ../nptl/sysdeps/unix/sysv/linux/x86_64/sem_timedwait.S:101
#1  0x5648c54ad007 in ?? ()
#2  0x5648c536effc in ?? ()
#3  0x7f4b0e555184 in start_thread (arg=0x7f4776ffd700)
at pthread_create.c:312
#4  0x7f4b0e28237d in clone ()
---Type  to continue, or q  to quit---
at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 5 (Thread 

[Bug 1357093] Re: Kernels not autoremoving, causing out of space error on LVM or Encrypted installation or on any installation, when /boot partition gets full

[Brian Candler]

I have two Precise (12.04) servers with

Unattended-Upgrade::Remove-Unused-Dependencies "true";

in 50unattended-upgrades.  One of them cleans up its kernels and only
keeps the last two; one of them accumulates kernels over time, and I
occasionally get alerts about /boot filling up.

On the latter machine, "apt-get autoremove --purge" doesn't remove them.
I end up removing the packages individually; the script "purge-old-
kernels" referred to above doesn't seem to exist.

The main difference I can see is that the latter machine has linux-
image-generic-lts-trusty, whereas the first machine has linux-image-
server.

Both machines have in /etc/apt/apt.conf.d/05aptitude:

aptitude::Keep-Unused-Pattern "^linux-image.*$ | ^linux-restricted-
modules.*$ | ^linux-ubuntu-modules.*$";

So I don't think that's it. I suppose there won't be too many kernel
updates for Precise before it goes end of life now though...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1357093

Title:
  Kernels not autoremoving, causing out of space error on LVM or
  Encrypted installation or on any installation, when /boot partition
  gets full

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1357093/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] Re: Recovery mode won't allow recovery after manually installing the OS incorrectly

[Brian Candler]

> The user would already have setup in the BIOS menu to either be in
UEFI or BIOS mode prior to installation. This would also be user error.

Really? What's wrong with:

- buy computer
- plug in USB stick
- boot it up

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  Recovery mode won't allow recovery after manually installing the OS
  incorrectly

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609715] Re: When installing in UEFI mode, should warn if ESP is missing

[Brian Candler]

*** This bug is a duplicate of bug 1609475 ***
https://bugs.launchpad.net/bugs/1609475

"Comment here only if you think the duplicate status is wrong."

Yes, I think the duplicate status is wrong.

Issue 1. The installer could be more helpful when dealing with UEFI
versus Legacy mode installs. (You can call that "opinion" if you like. I
would call it "feature" or "improvement")

Issue 2. Recovery mode won't allow recovery when the system is broken
(such as after manually installing the OS incorrectly)

Those are two different issues on two different parts of the software.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609715

Title:
  When installing in UEFI mode, should warn if ESP is missing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/1609715/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] Re: recovery mode completely broken by systemd

[Brian Candler]

Let me try one last time to separate the issues.

** The UEFI issue (a side issue)

The installer works in two completely different ways, depending on
whether the system booted via UEFI or BIOS. But it does not show whether
it is installing in UEFI or BIOS mode. Hence the user has little way,
short of guesswork, to know how to partition the system correctly.

Many systems can boot from a USB stick in either mode. If you don't tell
it, you get whatever the system chose. So:

(1) The installer *could* tell you which mode it's running in, but it
doesn't. If you don't realise you've booted via UEFI mode and that the
system is going to configure UEFI booting, and decide to partition
manually, then you don't realise that you need a UEFI boot partition.

(2) The system *could* warn you that you have a missing UEFI boot
partition when installing in UEFI mode, but it doesn't.

Those points have now been raised separately in issue #1609715.

However the only relevance here is it gives a way to reproduce the main
problem.

** Broken recovery mode (the main issue)

The point I tried to raise in this issue is the brokenness of recovery
mode when you have a system with some sort of corruption. The UEFI
missing-boot-partition problem is just one specific way to reproduce the
brokenness in recovery mode. Reproducible cases are good; they allow
things to be fixed. There are however many other different ways the
system could be broken and recovery mode would not work.

With an older version of Ubuntu, I could simply log in, poke around,
look at logs, find the problem and fix it.

With ubuntu 16.04, I have now experienced a situation where recovery
mode is broken. I described what happens at the top of this issue.
Basically you can start a recovery shell, and 50% of your keystrokes are
thrown away; and then a few minutes later the recovery shell quits and
recovery mode locks up. I suspect this is something to do with systemd
sitting in the background launching stuff when it thinks dependencies
have been met, and terminating stuff when it thinks it would be a good
idea to do so.

For recovery mode, I just want a shell. Let me do my job. Please spawn
me a shell connected to the console, reliably. That's it. No shells
vanishing and reappearing. No timeouts because filesystems haven't yet
been mounted or because networking is not up. That's the whole point of
recovery mode - to have sufficient access to be able to fix those
things.

For now, the best workaround seems to be to boot from an Ubuntu 14.04
USB, and then mount the system disk. But it makes me sad that 16.04 has
become less good in this respect than it was before. It seems to be a
regression in how easy it is to recover a broken system.

Of course, this only affects systems which require some sort of
maintenance - but it's a fact of life that systems *do* get into states
which require fixing.

That's it. If you have never had to use recovery mode, and hence don't
care about it, then you are lucky.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] Re: recovery mode completely broken by systemd

[Brian Candler]

Not sure about tag "bios-outdated-0055". The latest BIOS for this machine is 
0055: see
https://downloadcenter.intel.com/product/85254/Intel-NUC-Kit-NUC5CPYH

As for live CD: no, it can't be reproduced that way. The specific
sequence is:

* Boot from USB in UEFI mode
* Repartition the disk, but forget to include a UEFI boot partition
* Continue with installation
* Reboot, things go horribly wrong

Problems are:
(1a) The installer lets you do a UEFI-mode install without a UEFI boot partition
(1b) The installer doesn't maker it clear whether you are making a UEFI-mode 
install or a BIOS-mode install

(These have been raised as separate issues)

(2) The broken system boots but then goes mental; and systemd makes it
*much* harder to diagnose than without systemd.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] ProcInterrupts.txt

[Brian Candler]

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735776/+files/ProcInterrupts.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] ProcCpuinfo.txt

[Brian Candler]

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735775/+files/ProcCpuinfo.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] CurrentDmesg.txt

[Brian Candler]

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735771/+files/CurrentDmesg.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] JournalErrors.txt

[Brian Candler]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735772/+files/JournalErrors.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] UdevDb.txt

[Brian Candler]

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1609475/+attachment/4735778/+files/UdevDb.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] Card0.Codecs.codec.2.txt

[Brian Candler]

apport information

** Attachment added: "Card0.Codecs.codec.2.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735770/+files/Card0.Codecs.codec.2.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] Lspci.txt

[Brian Candler]

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1609475/+attachment/4735773/+files/Lspci.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] PciMultimedia.txt

[Brian Candler]

apport information

** Attachment added: "PciMultimedia.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735774/+files/PciMultimedia.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] WifiSyslog.txt

[Brian Candler]

apport information

** Attachment added: "WifiSyslog.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735779/+files/WifiSyslog.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] Card0.Codecs.codec.0.txt

[Brian Candler]

apport information

** Attachment added: "Card0.Codecs.codec.0.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735769/+files/Card0.Codecs.codec.0.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] CRDA.txt

[Brian Candler]

apport information

** Attachment added: "CRDA.txt"
   https://bugs.launchpad.net/bugs/1609475/+attachment/4735768/+files/CRDA.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] ProcModules.txt

[Brian Candler]

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1609475/+attachment/4735777/+files/ProcModules.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] Re: recovery mode completely broken by systemd

[Brian Candler]

apport information

** Tags added: apport-collected

** Description changed:

  Installing Ubuntu 16.04.1 on an identical pair of Intel NUC5CPYH
  machines (with 8GB RAM and Crucial BX200 SSD).
  
  There is a problem running on this machine, but the problem report here
  is specifically about how systemd makes this impossible to debug.
  
  Symptoms:
  
  * Installation proceeds normally. I installed with 4 partitions: 10GB /, 20GB 
/var, 202GB unused, 8GB swap
  * On reboot strange things happen. The system doesn't come up fully; 
sometimes it reports "NMI watchdog: BUG: soft lockup - CPU#0 stuck for 22s! 
[systemd-udevd:1148]"
  
  So I try to boot again this time following "Advanced options for
  Ubuntu", "Ubuntu, with Linux 4.4.0-31-generic (recovery mode)"
  
  It appears to boot fine. From the Recovery Menu I select "root: Drop to
  root shell prompt", then "Press Enter for maintenance". All is good so
  far: I get a prompt.
  
  However while I sit looking at this screen, after about two minutes a
  bunch of systemd messages scroll up. I captured them as best as I can
  with a camera:
  
  [  OK  ] Reached target Timers.
  [  OK  ] Reached target Login Prompts.
  [  OK  ] Started Stop ureadahead data collection 45s after completed startup
  [  OK  ] Reached target System Time Synchronized.
  [  OK  ] Reached target Sockets.
   Starting Create Volatile Files and Directories...
  [  OK  ]Started Set console scheme.
  [  OK  ] Started Tell Plymouth To Write Out Runtime Data.
  [FAILED] Failed to start Create Volatile Files and Directories.
  See 'systemctl status systemd-tmpfiles-setup.service' for details.
  [FAILED] Failed to start LSB: AppArmor initialization.
  See 'systemctl status apparmor.service' for details.
   Starting Raise network interfaces...
  [  OK  ] Started Raise network interface.
  [  OK  ] Reached target Network.
  [  OK  ] Reached target Network is Online.
   Starting iSCSI initiator daemon (iscsid)...
  [  OK  ] Started Set console font and keymap.
  [  OK  ] Started iSCSI initiator daemon (iscsid).
   Starting Login to default iSCSI targets...
  [  OK  ] Created slice system-getty.slice.
  [  OK  ] Started Login to default iSCSI targets.
  [  OK  ] Reached target Remote File Systems (Pre).
  [  OK  ] Reached target Remote File Systems.
  
  At this point it hangs for a few more seconds. Then a few more lines
  flash up onto the screen - too fast to see, although I think one of the
  lines has the ctrl-D for maintenance message.
  
  Then I can see the Recovery Menu again, *but the keyboard apparently
  does not work*. That is, I cannot move the selection up or down: it
  appears completely dead at this point. Alt-F2 switches me to a screen
  which is completely black apart from flashing cursor, and Alt-F1 puts me
  back to the frozen recovery menu.
  
  However, hitting Enter *does* give me a command line prompt again! But
  then pressing up and down selects the recovery menu. It appears that the
  shell and the recovery menu are both fighting over the keyboard. By
  pressing cursor down repeatedly, it appears about 50% of them cause the
  recovery menu to move.
  
  This is completely pants: if I boot into recovery mode, I *don't* want
  systemd nonsense, I want to see a sequential series of bootup steps; and
  when I get a shell, I want that shell to be mine on the console with no
  interference - and not taken away again.
  
- Lots of people say "systemd sucks", but I am submitting this in the hope
- that providing a *specific* way that it sucks might help get it fixed.
- (I have had a number of other cases of system recovery being frustrated
- by systemd, but this time I thought I would at least document the
- specifics)
+ Lots of people say "systemd sucks", but I am submitting this in the hope that 
providing a *specific* way that it sucks might help get it fixed. (I have had a 
number of other cases of system recovery being frustrated by systemd, but this 
time I thought I would at least document the specifics)
+ --- 
+ AlsaVersion: Advanced Linux Sound Architecture Driver Version 
k4.4.0-31-generic.
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.1
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', 
'/dev/snd/timer'] failed with exit code 1:
+ Card0.Amixer.info: Error: [Errno 2] No such file or directory
+ Card0.Amixer.values: Error: [Errno 2] No such file or directory
+ DistroRelease: Ubuntu 16.04
+ HibernationDevice: RESUME=UUID=8c695f64-12a0-4748-a431-7ab97a1e9042
+ InstallationDate: Installed on 2016-08-04 (33 days ago)
+ InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
+ IwConfig: Error: 

[Bug 1519120] Re: NetworkManager VLAN support fails unless vlan package is manually installed

[Brian Candler]

The second issue (not matching predictable NIC names) is #1541678

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1519120

Title:
  NetworkManager VLAN support fails unless vlan package is manually
  installed

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1519120/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1609475] Re: recovery mode completely broken by systemd

[Brian Candler]

Separate issue #1609715 raised about installer continuing with UEFI
installation even if there is no ESP.

This specific hardware is now working fine.

I would still like recovery mode to be more predictable in the event of
startup problems: after all, the whole point of recovery mode is for
when there are problems during bootup which need investigation/fixing.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1609475

Title:
  recovery mode completely broken by systemd

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Bug 1541678] Re: if-post-down.d/vlan and if-pre-up.d/vlan should support predictable NIC names

[Brian Candler]

Caught by this too. I get enp3s0, and have set net.ifnames=0 as a
workaround.

I agree with the suggestion that the script should be simplified to
match .N, where X is any alphanumeric. More conservatively: the
first X could match a-z only, and the last X could match 0-9 only.

Question is, was there a reason for originally matching only specific
patterns like ethM.N, wlanM.N etc? Was it to exclude certain other valid
interface names which contain a dot but are not VLAN capable? Or perhaps
it was just being overly cautious?

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1541678

Title:
  if-post-down.d/vlan and if-pre-up.d/vlan should support predictable
  NIC names

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

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs