[Touch-packages] [Bug 1742586] Re: package linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code
I have the default number of kernels installed with unattended upgrades & autoremove, so 3. I have configured xz compression, which normally stops this. /boot is undersized due to this install being done with a Xenial pre-release (before the default /boot size was increased). I don't know what changed that had apport flag this as a new bug. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1742586 Title: package linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d /initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: automatic upgrades failed somehow, possibly undersized /boot ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2 ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Jan 11 10:49:51 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2016-02-26 (684 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1742586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1742586] [NEW] package linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return co
Public bug reported: automatic upgrades failed somehow, possibly undersized /boot ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2 ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Jan 11 10:49:51 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2016-02-26 (684 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1742586 Title: package linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d /initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: automatic upgrades failed somehow, possibly undersized /boot ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2 ProcVersionSignature: Ubuntu 4.13.0-25.29~16.04.2-generic 4.13.13 Uname: Linux 4.13.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Jan 11 10:49:51 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 InstallationDate: Installed on 2016-02-26 (684 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.24 SourcePackage: initramfs-tools Title: package linux-image-extra-4.13.0-25-generic 4.13.0-25.29~16.04.2 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1742586/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
All charms using snaps are currently failing, so I'm looking forward to a snapd release with the commented out Nice. The alternative is adding the systemd override workaround to the snap layer and making everyone rebuild and republish their charms. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in Snap Layer: New Status in snapd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Artful: Fix Released Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). To manage notifications about this bug go to: https://bugs.launchpad.net/layer-snap/+bug/1709536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1709536] Re: snapd 2.26.14 on ubuntu-core won't start in containers anymore
** Also affects: layer-snap Importance: Undecided Status: New ** Changed in: layer-snap Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1709536 Title: snapd 2.26.14 on ubuntu-core won't start in containers anymore Status in Snap Layer: New Status in snapd: New Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Confirmed Status in systemd source package in Artful: Fix Released Bug description: It looks like snapd in ubuntu-core (2.26.14 here) has been modified to use a negative Nice value in systemd. Systemd seems to treat a failure to apply the requested Nice value as critical to unit startup. Unprivileged LXD containers do not allow the use of negative nice values as those are restricted to the real root user. I believe the optimal fix would be for systemd to ignore permission errors when attempting to setup such custom nice values in containers but if that can't be resolved quickly, then it means that snapd will now fail to start inside containers. Aug 09 05:54:37 core systemd[1]: snapd.service: Main process exited, code=exited, status=201/NICE Aug 09 05:54:37 core systemd[1]: snapd.service: Unit entered failed state. Aug 09 05:54:37 core systemd[1]: snapd.service: Failed with result 'exit-code'. I have confirmed that setting up a unit override by hand which sets Nice=0 does resolve the problem, confirming that the negative Nice value is the problem (snapd.service has Nice=-5 here). To manage notifications about this bug go to: https://bugs.launchpad.net/layer-snap/+bug/1709536/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [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
It also requires a complete reinstall if your boot partition is too small (ie. you accepted the defaults with an LVM or encrypted disk install pre 16.04 release). Machines upgraded from 14.04 will continue to fail and be directed here. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in 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 Status in unattended-upgrades: New Status in unattended-upgrades package in Ubuntu: Fix Released Bug description: Currently if one chooses to use LVM or encrypted install, a /boot partition is created of 236Mb Once kernel updates start being released this partition soon fills until people are left unable to upgrade. While you and I might know that we need to watch partition space, many of the people we have installing think that a windows disk is a disk and not a partition, education is probably the key - but in the meantime support venues keep needing to deal with the fact the partition is too small and/or old kernels are not purged as new ones install. For workaround and sytem repair, see https://help.ubuntu.com/community/RemoveOldKernels To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1357093/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1442649] Re: nautilus trash doesn't include btrfs and zfs subvolumes
Work around is to use the trash-cli package and empty trash from the command line. Upstream fixes in nautilus seems stalled, per https://bugzilla.gnome.org/show_bug.cgi?id=604015 , with no comments from maintainers for the several months that patches have been available. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1442649 Title: nautilus trash doesn't include btrfs and zfs subvolumes Status in GLib: Incomplete Status in glib2.0 package in Ubuntu: Triaged Status in gvfs package in Ubuntu: Triaged Status in nautilus package in Ubuntu: Triaged Bug description: Files in `/path/to/subvolume/.Trash-1000` aren't listed in the global trash. Comment by bug triage team: comment 4 has a spot-on analysis of where this issue is coming from, an inconsistency between trash handling in gvfs and glib/gio. The problem has been around for quite a while. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1442649/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1603898] Re: DNS resolution fails when using VPN and routing all traffic over it
I see this with IPv6 disabled completely on the laptop: $ cat /etc/sysctl.d/99-noipv6.conf net.ipv6.conf.all.disable_ipv6 = 1 net.ipv6.conf.default.disable_ipv6 = 1 net.ipv6.conf.lo.disable_ipv6 = 1 I can confirm that both ipv4 and ipv6 settings have both 'Use this connection only for resources on its network' and 'Ignore automatically obtained routes' disabled, and when I try connecting the ipv6 method is 'ignore'. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1603898 Title: DNS resolution fails when using VPN and routing all traffic over it Status in network-manager package in Ubuntu: Confirmed Status in network-manager source package in Xenial: Confirmed Bug description: When using our company VPN, the Network Manager configured dnsmasq ends up in a weird state where its unable to answer queries because it's (incorrectly) sending them to 127.0.0.1:53 where nothing is listening. | root@ornery:~# nmcli con show 'Canonical UK - All Traffic' | grep -i dns | ipv4.dns: | ipv4.dns-search: | ipv4.dns-options: (default) | ipv4.ignore-auto-dns: no | ipv6.dns: | ipv6.dns-search: | ipv6.dns-options: (default) | ipv6.ignore-auto-dns: no | IP4.DNS[1]: 10.172.192.1 | root@ornery:~# ps auxfw | grep [4]035 | nobody4035 0.0 0.0 52872 1620 ?SJun29 6:39 \_ /usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces --pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 --cache-size=0 --proxy-dnssec --enable-dbus=org.freedesktop.NetworkManager.dnsmasq --conf-dir=/etc/NetworkManager/dnsmasq.d | root@ornery:~# Querying the DNS server provided by the VPN connection works; querying dnsmasq doesn't: | root@ornery:~# dig +short @10.172.192.1 www.openbsd.org | 129.128.5.194 | root@ornery:~# dig @127.0.1.1 www.openbsd.org | | ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @127.0.1.1 www.openbsd.org | ; (1 server found) | ;; global options: +cmd | ;; Got answer: | ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 6996 | ;; flags: qr rd ra ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 | | ;; QUESTION SECTION: | ;www.openbsd.org. IN A | | ;; Query time: 0 msec | ;; SERVER: 127.0.1.1#53(127.0.1.1) | ;; WHEN: Mon Jul 18 10:25:48 CEST 2016 | ;; MSG SIZE rcvd: 33 | | root@ornery:~# While running 'dig @127.0.1.1 www.openbsd.org': | root@ornery:~# tcpdump -i lo port 53 -v -n | tcpdump: listening on lo, link-type EN10MB (Ethernet), capture size 262144 bytes | 10:26:04.728905 IP (tos 0x0, ttl 64, id 56577, offset 0, flags [none], proto UDP (17), length 72) | 127.0.0.1.54917 > 127.0.1.1.53: 32273+ [1au] A? www.openbsd.org. (44) | 10:26:04.729001 IP (tos 0x0, ttl 64, id 49204, offset 0, flags [DF], proto UDP (17), length 61) | 127.0.1.1.53 > 127.0.0.1.54917: 32273 Refused$ 0/0/0 (33) | root@ornery:~# netstat -anp | grep 127.0.[01].1:53 | tcp0 0 127.0.1.1:530.0.0.0:* LISTEN 4035/dnsmasq | udp0 0 127.0.1.1:530.0.0.0:* 4035/dnsmasq | root@ornery:~# You can see below a) that dnsmasq thinks it is configured to use a DNS server provided by the VPN, and/but that b) it tries to answer a non local query like www.openbsd.org locally. | root@ornery:~# kill -USR1 4035; tail /var/log/syslog | grep dnsmasq | Jul 18 09:29:22 ornery dnsmasq[4035]: time 1468830562 | Jul 18 09:29:22 ornery dnsmasq[4035]: cache size 0, 0/0 cache insertions re-used unexpired cache entries. | Jul 18 09:29:22 ornery dnsmasq[4035]: queries forwarded 1880976, queries answered locally 375041 | Jul 18 09:29:22 ornery dnsmasq[4035]: queries for authoritative zones 0 | Jul 18 09:29:22 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 792, retried or failed 0 | root@ornery:~# dig +short @127.0.1.1 www.openbsd.org | root@ornery:~# kill -USR1 4035; tail /var/log/syslog | grep dnsmasq | Jul 18 09:29:22 ornery dnsmasq[4035]: queries for authoritative zones 0 | Jul 18 09:29:22 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 792, retried or failed 0 | Jul 18 09:29:37 ornery dnsmasq[4035]: time 1468830577 | Jul 18 09:29:37 ornery dnsmasq[4035]: cache size 0, 0/0 cache insertions re-used unexpired cache entries. | Jul 18 09:29:37 ornery dnsmasq[4035]: queries forwarded 1880976, queries answered locally 375042 | Jul 18 09:29:37 ornery dnsmasq[4035]: queries for authoritative zones 0 | Jul 18 09:29:37 ornery dnsmasq[4035]: server 10.172.192.1#53: queries sent 792, retried or failed 0 | root@ornery:~# This is on Ubuntu 16.04, with the following packages: | james@ornery:
[Touch-packages] [Bug 645404] Re: Support Private PPAs
Private PPAs are accessed with basic auth using https: URLs to private- ppa.launchpad.net. https://stub:secretkeyfromlp@private- ppa.launchpad.net/teamname/ppaname/ubuntu It would be great if add-apt-repository accepted this or a similar URL, use it to retrieve the signing key security and add it as a source. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/645404 Title: Support Private PPAs Status in software-properties package in Ubuntu: Confirmed Bug description: Software properties add-apt-repository currently does not support adding private PPAs. software-properties should connect to the API and observe that it gets permission denied trying to read the ppa. Then it can reconnect to the API asking for authentication, which will open a browser window where you can do the openid ritual. Then using that token it ought to be possible for it to get the password etc. ProblemType: BugDistroRelease: Ubuntu 12.04 Package: python-software-properties 0.82.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/645404/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1595066] [NEW] Assumes end users know correct package name
Public bug reported: 'ubuntu-bug snap' is reporting bugs against the snap package, which is exactly what the docs say it should do, and not what users who do not have the snap package installed want it to do. They probably want it to report a bug against the snapd package, which owns /usr/bin/snap. Some extra heuristics to target the bug correctly could be useful, taking into account if the package is installed or if a binary with the provided name is found in $PATH. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 22 14:31:11 2016 InstallationDate: Installed on 2016-02-26 (116 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apport (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1595066 Title: Assumes end users know correct package name Status in apport package in Ubuntu: New Bug description: 'ubuntu-bug snap' is reporting bugs against the snap package, which is exactly what the docs say it should do, and not what users who do not have the snap package installed want it to do. They probably want it to report a bug against the snapd package, which owns /usr/bin/snap. Some extra heuristics to target the bug correctly could be useful, taking into account if the package is installed or if a binary with the provided name is found in $PATH. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10 Uname: Linux 4.4.0-24-generic x86_64 NonfreeKernelModules: zfs zunicode zcommon znvpair zavl nvidia_uvm nvidia_modeset nvidia ApportLog: ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 22 14:31:11 2016 InstallationDate: Installed on 2016-02-26 (116 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160224) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1595066/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1554848] Re: Please randomise automatic updates over a longer period
** Tags added: canonical-is -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1554848 Title: Please randomise automatic updates over a longer period Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: Load on the main Ubuntu archive servers is rather peakish, and tends to create a traffic peak on our Internet links at fairly regular times each day, preventing customers from accessing the archive. This impacts the cloud archive mirrors using the ubuntu-repository-cache charm also, because they are hitting a squid cache which is backed by the main archive. This effect will be even more pronounced under the recently-announced automatic update policy for xenial. One solution which would alleviate this to some extent would be to spread the load over a longer period by increasing the random sleep time in the daily update script from 30 minutes to, say, 1-2 hours. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1554848/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
stub@aargh:~$ sudo systemctl status lxc ● lxc.service - LXC Container Initialization and Autoboot Code Loaded: loaded (/lib/systemd/system/lxc.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2015-10-12 16:57:31 ICT; 20h ago Process: 1190 ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-containers start (code=exited, status=0/SUCCESS) Process: 1175 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load (code=exited, status=0/SUCCESS) Process: 1166 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-devsetup (code=exited, status=0/SUCCESS) Main PID: 1190 (code=exited, status=0/SUCCESS) Memory: 0B CPU: 0 CGroup: /system.slice/lxc.service Oct 12 16:57:31 aargh systemd[1]: Starting LXC Container Initialization and Autoboot Code... Oct 12 16:57:31 aargh lxc-devsetup[1166]: Creating /dev/.lxc Oct 12 16:57:31 aargh lxc-devsetup[1166]: /dev is devtmpfs Oct 12 16:57:31 aargh lxc-devsetup[1166]: Creating /dev/.lxc/user Oct 12 16:57:31 aargh systemd[1]: Started LXC Container Initialization and Autoboot Code. stub@aargh:~$ sudo service lxc status ● lxc.service - LXC Container Initialization and Autoboot Code Loaded: loaded (/lib/systemd/system/lxc.service; enabled; vendor preset: enabled) Active: active (exited) since Mon 2015-10-12 16:57:31 ICT; 20h ago Process: 1190 ExecStart=/usr/lib/x86_64-linux-gnu/lxc/lxc-containers start (code=exited, status=0/SUCCESS) Process: 1175 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-apparmor-load (code=exited, status=0/SUCCESS) Process: 1166 ExecStartPre=/usr/lib/x86_64-linux-gnu/lxc/lxc-devsetup (code=exited, status=0/SUCCESS) Main PID: 1190 (code=exited, status=0/SUCCESS) Memory: 0B CPU: 0 CGroup: /system.slice/lxc.service Oct 12 16:57:31 aargh systemd[1]: Starting LXC Container Initialization and Autoboot Code... Oct 12 16:57:31 aargh lxc-devsetup[1166]: Creating /dev/.lxc Oct 12 16:57:31 aargh lxc-devsetup[1166]: /dev is devtmpfs Oct 12 16:57:31 aargh lxc-devsetup[1166]: Creating /dev/.lxc/user Oct 12 16:57:31 aargh systemd[1]: Started LXC Container Initialization and Autoboot Code. stub@aargh:~$ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1490110 Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 Status in lxc package in Ubuntu: Incomplete Bug description: Error during do-releas-update -d from 15.04 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: lxc 1.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu7 Architecture: amd64 Date: Sat Aug 29 10:13:04 2015 DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2015-08-13 (15 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: lxc Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1504496] Re: package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Is this Bug #1490110 ?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1504496
Title:
package lxc 1.1.4-0ubuntu0.1 failed to install/upgrade: subprocess
installed post-installation script returned error exit status 1
Status in lxc package in Ubuntu:
New
Bug description:
A dist-upgrade failed in the maintainer scripts while trying to
restart the lxc networking, I think:
Reading package lists... Done
The following NEW packages will be installed:
linux-image-3.19.0-31-generic{a} linux-image-extra-3.19.0-31-generic{a}
linux-signed-image-3.19.0-31-generic{a}
The following packages will be upgraded:
juju juju-core juju-local liblxc1 linux-image-generic linux-libc-dev
linux-signed-image-generic
lxc lxc-templates mutt python3-lxc
The following packages are RECOMMENDED but will NOT be installed:
citadel-mta courier-mta dma dma:i386 esmtp-run exim4-daemon-heavy
exim4-daemon-light
lsb-invalid-mta masqmail msmtp-mta nullmailer opensmtpd postfix qmail-run
sendmail-bin ssmtp
xmail
11 packages upgraded, 3 newly installed, 0 to remove and 0 not upgraded.
Need to get 0 B/90.5 MB of archives. After unpacking 259 MB will be used.
Do you want to continue? [Y/n/?]
(Reading database ... 357199 files and directories currently installed.)
Preparing to unpack .../python3-lxc_1.1.4-0ubuntu0.1_amd64.deb ...
Unpacking python3-lxc (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
Preparing to unpack .../lxc-templates_1.1.4-0ubuntu0.1_amd64.deb ...
Unpacking lxc-templates (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
Preparing to unpack .../liblxc1_1.1.4-0ubuntu0.1_amd64.deb ...
Unpacking liblxc1 (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
Preparing to unpack .../lxc_1.1.4-0ubuntu0.1_amd64.deb ...
Unpacking lxc (1.1.4-0ubuntu0.1) over (1.1.2-0ubuntu3.2) ...
Selecting previously unselected package linux-image-3.19.0-31-generic.
Preparing to unpack .../linux-image-3.19.0-31-generic_3.19.0-31.36_amd64.deb
...
Done.
Unpacking linux-image-3.19.0-31-generic (3.19.0-31.36) ...
Selecting previously unselected package linux-image-extra-3.19.0-31-generic.
Preparing to unpack
.../linux-image-extra-3.19.0-31-generic_3.19.0-31.36_amd64.deb ...
Unpacking linux-image-extra-3.19.0-31-generic (3.19.0-31.36) ...
Preparing to unpack .../linux-image-generic_3.19.0.31.30_amd64.deb ...
Unpacking linux-image-generic (3.19.0.31.30) over (3.19.0.30.29) ...
Preparing to unpack .../linux-libc-dev_3.19.0-31.36_amd64.deb ...
Unpacking linux-libc-dev:amd64 (3.19.0-31.36) over (3.19.0-30.34) ...
Selecting previously unselected package linux-signed-image-3.19.0-31-generic.
Preparing to unpack
.../linux-signed-image-3.19.0-31-generic_3.19.0-31.36_amd64.deb ...
Unpacking linux-signed-image-3.19.0-31-generic (3.19.0-31.36) ...
Preparing to unpack .../linux-signed-image-generic_3.19.0.31.30_amd64.deb ...
Unpacking linux-signed-image-generic (3.19.0.31.30) over (3.19.0.30.29) ...
Preparing to unpack .../mutt_1.5.23-3ubuntu1_amd64.deb ...
Unpacking mutt (1.5.23-3ubuntu1) over (1.5.23-3) ...
Preparing to unpack .../juju-core_1.24.6-0ubuntu1~15.04.1_amd64.deb ...
Unpacking juju-core (1.24.6-0ubuntu1~15.04.1) over
(1.23.2-0ubuntu1~14.10.1~juju1) ...
Preparing to unpack .../juju_1.24.6-0ubuntu1~15.04.1_all.deb ...
Unpacking juju (1.24.6-0ubuntu1~15.04.1) over (1.23.2-0ubuntu1~14.10.1~juju1)
...
Preparing to unpack .../juju-local_1.24.6-0ubuntu1~15.04.1_all.deb ...
Unpacking juju-local (1.24.6-0ubuntu1~15.04.1) over
(1.23.2-0ubuntu1~14.10.1~juju1) ...
Processing triggers for man-db (2.7.0.2-5) ...
Processing triggers for ureadahead (0.100.0-19) ...
ureadahead will be reprofiled on next reboot
Processing triggers for doc-base (0.10.6) ...
Processing 1 changed doc-base file...
Registering documents with scrollkeeper...
Processing triggers for gnome-menus (3.10.1-0ubuntu5) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu3) ...
Processing triggers for bamfdaemon (0.5.1+15.04.20150202-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for mime-support (3.58ubuntu1) ...
Setting up liblxc1 (1.1.4-0ubuntu0.1) ...
Setting up python3-lxc (1.1.4-0ubuntu0.1) ...
Setting up lxc (1.1.4-0ubuntu0.1) ...
Installing new version of config file
/etc/apparmor.d/lxc/lxc-default-with-nesting ...
Installing new version of config file /etc/bash_completion.d/lxc ...
Installing new version of config file /etc/init/lxc.conf ...
Job for lxc-net.service failed. See "systemctl status lxc-net.service" and
"journalctl -xe" for details.
invoke-rc.d: initscript lxc-net, action "start" failed.
dpkg: error processing package lxc (--configure):
subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of
[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
** Attachment added: "apt-term.log" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+attachment/4478083/+files/apt-term.log -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1490110 Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 Status in lxc package in Ubuntu: New Bug description: Error during do-releas-update -d from 15.04 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: lxc 1.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu7 Architecture: amd64 Date: Sat Aug 29 10:13:04 2015 DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2015-08-13 (15 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: lxc Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
** Attachment added: "main.log" https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+attachment/4478084/+files/main.log ** Changed in: lxc (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1490110 Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 Status in lxc package in Ubuntu: New Bug description: Error during do-releas-update -d from 15.04 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: lxc 1.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu7 Architecture: amd64 Date: Sat Aug 29 10:13:04 2015 DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2015-08-13 (15 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: lxc Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
Upgrade to wily failed here with this error. Possible trigger was having juju-local installed, which seemed to create a bit of a dependency mess with juju-local, lxc-templates and lxc. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1490110 Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 Status in lxc package in Ubuntu: Incomplete Bug description: Error during do-releas-update -d from 15.04 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: lxc 1.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu7 Architecture: amd64 Date: Sat Aug 29 10:13:04 2015 DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2015-08-13 (15 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: lxc Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1490110] Re: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100
2015-09-29 10:30:55,881 INFO cache.commit() 2015-09-29 10:30:55,881 DEBUG failed to SystemUnLock() (E:Not locked) 2015-09-29 11:04:11,358 ERROR got an error from dpkg for pkg: 'lxc': 'subprocess installed post-installation script returned error exit status 100' 2015-09-29 11:04:11,358 DEBUG running apport_pkgfailure() lxc: subprocess installed post-installation script returned error exit status 100 2015-09-29 11:04:11,362 ERROR got an error from dpkg for pkg: 'lxc': 'subprocess installed post-installation script returned error exit status 100' 2015-09-29 11:04:36,574 ERROR got an error from dpkg for pkg: 'lxc-templates': 'dependency problems - leaving unconfigured' 2015-09-29 11:04:36,574 DEBUG running apport_pkgfailure() lxc-templates: dependency problems - leaving unconfigured 2015-09-29 11:04:36,574 DEBUG dpkg error because of dependency problems, not reporting against lxc-templates 2015-09-29 11:04:36,574 ERROR got an error from dpkg for pkg: 'lxc-templates': 'dependency problems - leaving unconfigured' 2015-09-29 11:04:38,001 ERROR got an error from dpkg for pkg: 'juju-local': 'dependency problems - leaving unconfigured' 2015-09-29 11:04:38,001 DEBUG running apport_pkgfailure() juju-local: dependency problems - leaving unconfigured 2015-09-29 11:04:38,001 DEBUG dpkg error because of dependency problems, not reporting against juju-local 2015-09-29 11:04:38,001 ERROR got an error from dpkg for pkg: 'juju-local': 'dependency problems - leaving unconfigured' 2015-09-29 11:05:14,645 ERROR got an error from dpkg for pkg: 'lxc': 'subprocess installed post-installation script returned error exit status 100' 2015-09-29 11:05:14,645 DEBUG running apport_pkgfailure() lxc: subprocess installed post-installation script returned error exit status 100 2015-09-29 11:05:14,650 ERROR got an error from dpkg for pkg: 'lxc': 'subprocess installed post-installation script returned error exit status 100' 2015-09-29 11:05:18,267 ERROR not handled expection: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned an error code (1) 2015-09-29 11:05:18,267 DEBUG running apport_crash() 2015-09-29 11:05:23,083 ERROR SystemError from cache.commit(): installArchives() failed 2015-09-29 11:05:39,322 ERROR not handled expection: Traceback (most recent call last): File "/tmp/ubuntu-release-upgrader-fr1j7u5b/DistUpgrade/DistUpgradeController.py", line 1137, in doDistUpgrade res = self.cache.commit(fprogress,iprogress) File "/tmp/ubuntu-release-upgrader-fr1j7u5b/DistUpgrade/DistUpgradeCache.py", line 267, in commit apt.Cache.commit(self, fprogress, iprogress) File "/usr/lib/python3/dist-packages/apt/cache.py", line 505, in commit if fetch_progress is None: SystemError: installArchives() failed During handling of the above exception, another exception occurred: TypeError: wait_for_child() takes 1 positional argument but 2 were given 2015-09-29 11:05:39,322 DEBUG running apport_crash() -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1490110 Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 Status in lxc package in Ubuntu: Incomplete Bug description: Error during do-releas-update -d from 15.04 ProblemType: Package DistroRelease: Ubuntu 15.10 Package: lxc 1.1.3-0ubuntu1 ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3 Uname: Linux 4.1.0-3-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.18-0ubuntu7 Architecture: amd64 Date: Sat Aug 29 10:13:04 2015 DuplicateSignature: package:lxc:1.1.3-0ubuntu1:subprocess installed post-installation script returned error exit status 100 ErrorMessage: subprocess installed post-installation script returned error exit status 100 InstallationDate: Installed on 2015-08-13 (15 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) ProcCmdline: BOOT_IMAGE=/vmlinuz-4.1.0-3-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: lxc Title: package lxc 1.1.3-0ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 100 UpgradeStatus: Upgraded to wily on 2015-08-29 (0 days ago) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1490110/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1472142] [NEW] /var/cache/lxc not world readable
Public bug reported: I am interested in priming the lxc cache on new hosts, but this is problematic because /var/cache/lxc is not world readable. Could it become world readable? This bug should be WONTFIX if the cache can contain secrets or 'private' images. But ideally these would be declared private and protected at the next level down. ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1472142 Title: /var/cache/lxc not world readable Status in lxc package in Ubuntu: New Bug description: I am interested in priming the lxc cache on new hosts, but this is problematic because /var/cache/lxc is not world readable. Could it become world readable? This bug should be WONTFIX if the cache can contain secrets or 'private' images. But ideally these would be declared private and protected at the next level down. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1472142/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1018307] Re: SSL renegotiation fails
** Changed in: postgresql (Juju Charms Collection) Status: Triaged => In Progress ** Changed in: postgresql (Juju Charms Collection) Assignee: (unassigned) => Stuart Bishop (stub) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1018307 Title: SSL renegotiation fails Status in openssl package in Ubuntu: Confirmed Status in postgresql-9.4 package in Ubuntu: Confirmed Status in postgresql package in Juju Charms Collection: In Progress Bug description: With PostgreSQL 9.1, SSL renegotiation is enabled by default. This fails under Ubuntu 12.04, most noticeably when using streaming replication as the renegotiation limit is hit quickly. On the master: 2012-06-25 16:16:26 PDT LOG: SSL renegotiation failure 2012-06-25 16:16:26 PDT LOG: SSL error: unexpected record 2012-06-25 16:16:26 PDT LOG: could not send data to client: Connection reset by peer On the hot standby: 2012-06-25 11:12:11 PDT FATAL: could not receive data from WAL stream: SSL error: sslv3 alert unexpected message 2012-06-25 11:12:11 PDT LOG: record with zero length at 1C5/95D2FE00 If our SSL libraries do not support SSL renegotiation, the default setting is wrong and perhaps warnings emitted if attempts are made to enable it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: postgresql-9.1 9.1.4-0ubuntu12.04 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Wed Jun 27 16:38:33 2012 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: postgresql-9.1 UpgradeStatus: Upgraded to precise on 2012-04-27 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1018307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1018307] Re: SSL renegotiation fails
** Also affects: postgresql (Juju Charms Collection) Importance: Undecided Status: New ** Changed in: postgresql (Juju Charms Collection) Status: New => Triaged ** Changed in: postgresql (Juju Charms Collection) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1018307 Title: SSL renegotiation fails Status in openssl package in Ubuntu: Confirmed Status in postgresql-9.4 package in Ubuntu: Confirmed Status in postgresql package in Juju Charms Collection: Triaged Bug description: With PostgreSQL 9.1, SSL renegotiation is enabled by default. This fails under Ubuntu 12.04, most noticeably when using streaming replication as the renegotiation limit is hit quickly. On the master: 2012-06-25 16:16:26 PDT LOG: SSL renegotiation failure 2012-06-25 16:16:26 PDT LOG: SSL error: unexpected record 2012-06-25 16:16:26 PDT LOG: could not send data to client: Connection reset by peer On the hot standby: 2012-06-25 11:12:11 PDT FATAL: could not receive data from WAL stream: SSL error: sslv3 alert unexpected message 2012-06-25 11:12:11 PDT LOG: record with zero length at 1C5/95D2FE00 If our SSL libraries do not support SSL renegotiation, the default setting is wrong and perhaps warnings emitted if attempts are made to enable it. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: postgresql-9.1 9.1.4-0ubuntu12.04 ProcVersionSignature: Ubuntu 3.2.0-25.40-generic 3.2.18 Uname: Linux 3.2.0-25-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu8 Architecture: amd64 Date: Wed Jun 27 16:38:33 2012 ProcEnviron: LANGUAGE=en_AU:en TERM=xterm PATH=(custom, user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: postgresql-9.1 UpgradeStatus: Upgraded to precise on 2012-04-27 (60 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1018307/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
