[Bug 1904620] Re: Tomcat 8.0.32 does not start with libraries compatible with Java 8 or older but compiled for Java 9
Hi, Please find in attachment a relevant patch for the current Ubuntu Xenial Tomcat 8 source tree. Regards, ** Patch added: "fix-60688.patch" https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1904620/+attachment/5437226/+files/fix-60688.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904620 Title: Tomcat 8.0.32 does not start with libraries compatible with Java 8 or older but compiled for Java 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1904620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904620] Re: Tomcat 8.0.32 does not start with libraries compatible with Java 8 or older but compiled for Java 9
Hi, I've asked the dev team for the most simple reproducer, that i will try to provide ASAP. Please find the necessary commit applied on the 8.0.41 source tree : https://github.com/apache/tomcat80/commit/d491003658865af441a982c52dfaa1d2fa460d5f Regards, -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1904620 Title: Tomcat 8.0.32 does not start with libraries compatible with Java 8 or older but compiled for Java 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1904620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1904620] [NEW] Tomcat 8.0.32 does not start with libraries compatible with Java 8 or older but compiled for Java 9
Public bug reported: An update to the BCEL library has been pushed upstream since Tomcat 8.0.42 : https://bz.apache.org/bugzilla/show_bug.cgi?id=60688 Without this update, loading libraries which are compatible with Java 8 or older but compiled for Java 9 on Tomcat 8.0.32 on Ubuntu Xenial prevents Tomcat from starting. Is it possible to backport this update to the BECL library on Tomcat 8.0.32 ? Thanks in advance. ** Affects: tomcat8 (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/1904620 Title: Tomcat 8.0.32 does not start with libraries compatible with Java 8 or older but compiled for Java 9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat8/+bug/1904620/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1795659] Re: kernel panic using CIFS share in smb2_push_mandatory_locks()
Hi, Unfortunately, the patch does not seem to solve the problem. Running Ubuntu 18.04 LTS with kernel 4.15.0-64, the crash still occurs with the same signature : Oct 14 08:00:01 uzorldsp01 kernel: [109699.415372] BUG: unable to handle kernel NULL pointer dereference at 0038 Oct 14 08:00:01 uzorldsp01 kernel: [109699.420042] IP: smb2_push_mandatory_locks+0x10d/0x3c0 [cifs] Oct 14 08:00:01 uzorldsp01 kernel: [109699.420042] PGD 0 P4D 0 Oct 14 08:00:01 uzorldsp01 kernel: [109699.420042] Oops: [#1] SMP PTI Oct 14 08:00:01 uzorldsp01 kernel: [109699.420042] Modules linked in: btrfs zstd_compress xor raid6_pq ufs qnx4 minix ntfs msdos jfs xfs dm_snapshot dm_bufio cmac arc4 md4 nls_utf8 cifs ccm fscache nf_conntr ack_ipv4 nf_defrag_ipv4 xt_owner xt_conntrack nf_conntrack libcrc32c iptable_security sb_edac kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd intel_rapl_perf input_leds serio_raw hyperv_fb hv_balloon joydev mac_hid sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 hid_generic hid_hyperv hv_util s hv_storvsc ptp hyperv_keyboard hv_netvsc hid scsi_transport_fc pps_core psmouse i2c_piix4 pata_acpi hv_vmbus floppy Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] CPU: 0 PID: 50766 Comm: kworker/0:0 Not tainted 4.15.0-64-generic #73-Ubuntu Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] Workqueue: cifsoplockd cifs_oplock_break [cifs] Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] RIP: 0010:smb2_push_mandatory_locks+0x10d/0x3c0 [cifs] Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] RSP: :ab360da2bdd8 EFLAGS: 00010246 Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] RAX: RBX: 9887646617d8 RCX: Oct 14 08:00:01 uzorldsp01 kernel: [109699.472261] RDX: 1000 RSI: RDI: 98876d006b80 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] RBP: ab360da2be28 R08: 988568596000 R09: 98876d006b80 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] R10: ab360da2bd98 R11: 988568596000 R12: 00aa Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] R13: 9887646617d8 R14: 9887646617c0 R15: 988764d7f200 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] FS: () GS:98876d60() knlGS: Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] CS: 0010 DS: ES: CR0: 80050033 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] CR2: 0038 CR3: 00046d80a003 CR4: 001606f0 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] Call Trace: Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] cifs_oplock_break+0x131/0x410 [cifs] Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] process_one_work+0x1de/0x420 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] worker_thread+0x32/0x410 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] kthread+0x121/0x140 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] ? process_one_work+0x420/0x420 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] ? kthread_create_worker_on_cpu+0x70/0x70 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] ret_from_fork+0x35/0x40 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] Code: c8 00 00 00 00 48 89 45 b0 49 39 c6 0f 84 e5 00 00 00 4d 89 fb 4d 8b 7e 10 49 8b 5e 18 4d 8d 6e 18 49 8b 87 90 00 00 00 4c 39 eb <48> 8b 40 38 48 89 4 5 d0 0f 84 ae 00 00 00 45 31 d2 4c 89 75 b8 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] RIP: smb2_push_mandatory_locks+0x10d/0x3c0 [cifs] RSP: ab360da2bdd8 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] CR2: 0038 Oct 14 08:00:02 uzorldsp01 kernel: [109699.472261] ---[ end trace ee6628b4e2b5174b ]--- -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1795659 Title: kernel panic using CIFS share in smb2_push_mandatory_locks() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795659/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1841566] [NEW] Cloud-Init does not rotate its own log files
Public bug reported: The following log files : /var/log/cloud-init.log /var/log/cloud-init-output.log produced by Cloud-Init are not rotated. As a consequence, they keep growing indefinitely and can fill up the underlying partition. Is it possible to supply a logrotate configuration in the cloud-init package ? Regards ** Affects: cloud-init (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/1841566 Title: Cloud-Init does not rotate its own log files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1841566/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1837227] [NEW] Random mount units sometimes fail, while file system is correctly mounted
Public bug reported: In Ubuntu 18.04 at least, we sometimes get a random server in emergency mode with a failed mount unit (ext4 file system), while the corresponding file system is in fact correctly mounted. It happens roughly once every 1000 reboots. It seems to be related with this bug : https://github.com/systemd/systemd/issues/10872 Is it possible to apply the fix (https://github.com/systemd/systemd/commit/350804867dbcc9b7ccabae1187d730d37e2d8a21) in Ubuntu 18.04 ? Thanks in advance. ** Affects: systemd (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/1837227 Title: Random mount units sometimes fail, while file system is correctly mounted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837227/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
Hi, We are also affected by this bug. Adding linux-meta in the loop because a simple solution could be to now add a tighter dependency on the linux-image-4.4.0-*-generic package, that means linux-base (>= 4.5ubuntu1~16.04.1). ** Changed in: linux-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1820755] Re: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found
** Also affects: linux-meta (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/1820755 Title: Netboot install fails due to linux-image-4.4.0-143-generic.postinst linux-update-symlinks not found To manage notifications about this bug go to: https://bugs.launchpad.net/bluelinux/+bug/1820755/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1803530] [NEW] [Xenial][udev] postinst script should use "invoke-rc.d stop" instead of "systemctl stop"
Public bug reported:
In order to respect the local initscript policy layer that may be
present in /usr/sbin/policy-rc.d, the postinst script of the udev
package should use "invoke-rc.d stop" instead of "systemctl stop".
This direct systemctl call can be found in the handle_service_rename()
function :
handle_service_rename() {
if dpkg --compare-versions "$2" lt "204-1"; then
if [ -d /run/systemd/system ]; then
systemctl stop udev.service udev-control.socket udev-kernel.socket
>/dev/null 2>&1 || true
fi
fi
}
Using "systemctl stop" during unattended-upgrades in shutdown mode hangs
and leaves the dpkg database in a broken state after reboot. Using a
local initscript policy layer that prevents start/stop/restart actions
on this case is a way to prevent those hangs but maintainer scripts have
to use invoke-rc.d instead of direct systemctl calls.
** Affects: systemd (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/1803530
Title:
[Xenial][udev] postinst script should use "invoke-rc.d stop" instead
of "systemctl stop"
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1803530/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Hi Eric, I confirm that this behaviour can only be reproduced in 'uu' context and only in 'shutdown mode'. I can also confirm that the upgrade process is now OK in Bionic with your test package : - unattended-upgrades version after the test package installation : ii unattended-upgrades 1.1ubuntu1.18.04.6+testpkgb1 all automatic installation of security upgrades - dpkg status for linux-cloud-tools-common after reboot + 'uu' in 'shutdown mode' : ii linux-cloud-tools-common 4.15.0-36.39 all Linux kernel version specific cloud tools for version 4.15.0 - APT logs for linux-cloud-tools-common : Start-Date: 2018-11-02 16:28:56 Commandline: /usr/bin/unattended-upgrade Upgrade: linux-cloud-tools-common:amd64 (4.15.0-34.37, 4.15.0-36.39) End-Date: 2018-11-02 16:29:01 Would it also be possible to backport the fix in Xenial, as this version is also impacted ? Thanks a lot for your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Hi Eric, Please find attached the resulting file "shutdown-log.txt". ** Attachment added: "shutdown-log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+attachment/5202460/+files/shutdown-log.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
@Eric : The server was installed with a 4.15.0-34.37 kernel from a corporate OS image, and linux-cloud-tools-common package was also in version 4.15.0-34.37. All packages where in state "ii". I dist-upgrade the server with APT (to version 4.15.0-36.39) and only downgrade the linux-cloud-tools-common package in order to only let unattended-upgrades try to upgrade the linux-cloud-tools-common package and have simpler unattended-upgrades logs to analyze. Upgrading the linux-cloud-tools-common simultaneously with the other kernel packages leeds to the same result. Also, all packages where in state "ii" before running unattended- upgrades. Let me know if you want me to delete the server and deploy it once more with another "fresh" test case. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
@Eric : Sosreport sent by email. Did you try the second time (with cloud-init installed) to reproduce with unattended upgrades on shutdown mode ? I did not mention it but upgrading the package outside of unattended upgrades on shutdown mode works. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
@Eric : Is cloud-init installed on your system. If not, can you install it and try again please ? Indeed, as you can see in my first comment, removing the cloud-init dependency on the linux-cloud-tools-common makes the update process work well. So it seems to be related with cloud-init. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
@Eric, no, it is not necessary. We encountered the same problem on AWS EC2 instances that share the same OS image and also have the linux- cloud-tools-common package installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Hi Eric, The downgrade operation you saw is just because I've used the same server to give you the logs and to test the step-by-step instructions before writing them on this bug report. I can confirm that the issue can be reproduced any time starting from the 2 versions (Xenial : 4.4.0-135.161, Bionic : 4.15.0-34.37), hundreds of our servers were impacted (and therefore we have stopped automatic upgrades on our Production servers). I can also confirm that if i test an unattended-upgrade during shutdown on Bionic from 4.15.0-33.36, the package will be upgraded to version 4.15.0-36.39 without any problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
@David, of course : - Start from an up-to-date Ubuntu Bionic : [root@uzimysut01 ~]# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic - Downgrade linux-cloud-tools-common to version 4.15.0-34.37 : [root@uzimysut01 ~]# apt install linux-cloud-tools-common=4.15.0-34.37 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be DOWNGRADED: linux-cloud-tools-common 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Need to get 58.3 kB of archives. After this operation, 7,168 B disk space will be freed. Do you want to continue? [Y/n] Get:1 https://repos.it.sncf.fr/ubuntu-security bionic-security/main amd64 linux-cloud-tools-common all 4.15.0-34.37 [58.3 kB] Fetched 58.3 kB in 0s (268 kB/s) dpkg: warning: downgrading linux-cloud-tools-common from 4.15.0-36.39 to 4.15.0-34.37 (Reading database ... 37537 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-34.37_all.deb ... Unpacking linux-cloud-tools-common (4.15.0-34.37) over (4.15.0-36.39) ... Setting up linux-cloud-tools-common (4.15.0-34.37) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for man-db (2.8.3-2) ... - Install unattended-upgrades : [root@uzimysut01 ~]# apt install unattended-upgrades - Ensure unattended-upgrades is active, and that it works in "shutdown mode" : [root@uzimysut01 ~]# grep Unattended-Upgrade /etc/apt/apt.conf.d/20auto-upgrades APT::Periodic::Unattended-Upgrade "1"; [root@uzimysut01 ~]# grep InstallOnShutdown /etc/apt/apt.conf.d/50unattended-upgrades Unattended-Upgrade::InstallOnShutdown "true"; - [optional] If you do not want to wait 30 minutes, modify the TimeoutStopSec : [root@uzimysut01 ~]# systemctl edit unattended-upgrades [Service] TimeoutStopSec=300 - Reboot : [root@uzimysut01 ~]# systemctl reboot - After reboot, dpkg is in a broken state : [root@uzimysut01 ~]# apt dist-upgrade E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. - State of the linux-cloud-tools-common package : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 Thanks a lot for your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
@Eric : Logs in attachment. Thanks a lot for your help. ** Attachment added: "apt and unattended-upgrades logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+attachment/5199435/+files/bug-1796376.tgz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1739107] Re: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service
Hi all, I suspect that this fix is now preventing unattended-upgrades (in shutdown down) to upgrade the package linux-cloud-tools-common. The update process hangs during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. I have reported this bug in another bug report : https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376 Thanks for your help. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1739107 Title: linux-cloud-tools-common: Ensure hv-kvp-daemon.service starts before walinuxagent.service To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1739107/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Sorry, i'm not able to run apport through our enterprise Network. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1796376] [NEW] Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
Public bug reported: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1645636] Re: deadlock during lvm snapshot
Hi all, I think we just hit the same bug on a Production server today, with a snapshot on the root filesystem. Here are the relevant logs : kernel: [455151.056975] INFO: task jbd2/dm-0-8:214 blocked for more than 120 seconds. kernel: [455151.149417] INFO: task dmeventd:27193 blocked for more than 120 seconds. kernel: [455151.241272] INFO: task cat:27522 blocked for more than 120 seconds. ... All I/Os on the filesystem were blocked, so we had to reboot the server. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1645636 Title: deadlock during lvm snapshot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1645636/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1618900] [NEW] [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode"
Public bug reported: Using unattended-upgrades 0.90 in "Shutdown mode" on Ubuntu Xenial, we encounter the following systemd dependencies issues : - The network is often down when unattended-upgrades is running, so packages can not be downloaded (can be mitigated by using APT::Periodic::Download-Upgradeable-Packages "1";) : => ERROR An error occurred: 'Could not resolve host: .fr' => ERROR The URI 'https://.fr:33000/ubuntu-security/pool/main/libi/libidn/libidn11_1.32-3ubuntu1.1_amd64.deb' failed to download, aborting - Important mountpoints like /boot are unmounted before unattended-upgrades is running, so newer kernels can not be installed properly (ramdisk and grub configuration can not be generated) ** Affects: unattended-upgrades (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/1618900 Title: [Xenial/0.90] Systemd dependencies issues when used in "Shutdown mode" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1618900/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1516018] [NEW] [7u85-2.6.1-5ubuntu0.12.04.1] security update introduced new libsctp1 dependency that breaks unattended-upgrades
Public bug reported: The openjdk-7 "7u85-2.6.1-5ubuntu0.12.04.1" security update introduces a new dependency on libsctp1. As libsctp1 is not presently in the security pocket, automatic update for those who only activate the ubuntu-security suite with unattended-upgrades fails with : => pkg 'libsctp1' not in allowed origin Is it possible to push libsctp1 in the security pocket, or do we need to upgrade manually all our installed OpenJDKs ? Regards, ** Affects: openjdk-7 (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/1516018 Title: [7u85-2.6.1-5ubuntu0.12.04.1] security update introduced new libsctp1 dependency that breaks unattended-upgrades To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-7/+bug/1516018/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1341628] Re: [needs-packaging]openjdk-8 in 14.04
*** This bug is a duplicate of bug 1368094 *** https://bugs.launchpad.net/bugs/1368094 +1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1341628 Title: [needs-packaging]openjdk-8 in 14.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjdk-8/+bug/1341628/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514428] Re: pvmove hangs while moving LVs
Some more information about this problem : We wanted to pvmove approximately 600GB of data between two (VMWare) disks : /dev/sdb and /dev/sdc - With database activity (PostgreSQL) : pvmove hangs exactly at the same point (60%) - Without database activity (PostgreSQL) : pvmove finishes correctly -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1514428 Title: pvmove hangs while moving LVs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1514428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1514428] [NEW] pvmove hangs while moving LVs
Public bug reported: Operating System : Ubuntu 12.04 LTS LVM version : 2.02.66-4ubuntu7.1 When trying to pvmove from one device to another on an active production system, it seems that we encounter the following bug : https://bugzilla.redhat.com/show_bug.cgi?id=706036 Symptoms : - pvmove command hangs indefinitely - iostat shows busy disks without any I/O - dmesg shows : kernel: [119143.641376] INFO: task jbd2/dm-5-8:1801 blocked for more than 120 seconds. kernel: [119143.641456] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. kernel: [119143.641529] jbd2/dm-5-8 D 81806200 0 1801 2 0x kernel: [119143.641535] 88022d489ac0 0046 88022d489a60 8103ec29 kernel: [119143.641540] 88022d489fd8 88022d489fd8 88022d489fd8 00012800 kernel: [119143.641543] 880232169700 880227d0ae00 88022d489a90 88023fc930c0 kernel: [119143.641547] Call Trace: kernel: [119143.641561] [] ? default_spin_lock_flags+0x9/0x10 kernel: [119143.641568] [] ? __lock_page+0x70/0x70 kernel: [119143.641577] [] schedule+0x3f/0x60 kernel: [119143.641580] [] io_schedule+0x8f/0xd0 kernel: [119143.641584] [] sleep_on_page+0xe/0x20 kernel: [119143.641587] [] __wait_on_bit+0x5f/0x90 kernel: [119143.641590] [] wait_on_page_bit+0x78/0x80 kernel: [119143.641595] [] ? autoremove_wake_function+0x40/0x40 kernel: [119143.641598] [] filemap_fdatawait_range+0x10c/0x1a0 kernel: [119143.641603] [] ? dm_request+0x28/0x40 kernel: [119143.641607] [] ? generic_make_request.part.52+0x74/0xb0 kernel: [119143.641610] [] ? generic_make_request+0x68/0x70 kernel: [119143.641613] [] filemap_fdatawait+0x2b/0x30 kernel: [119143.641617] [] journal_finish_inode_data_buffers+0x70/0x170 kernel: [119143.641621] [] jbd2_journal_commit_transaction+0x677/0x12a0 kernel: [119143.641625] [] ? try_to_del_timer_sync+0xa4/0x110 kernel: [119143.641629] [] kjournald2+0xbb/0x220 kernel: [119143.641632] [] ? add_wait_queue+0x60/0x60 kernel: [119143.641635] [] ? commit_timeout+0x10/0x10 kernel: [119143.641638] [] kthread+0x8c/0xa0 kernel: [119143.641646] [] kernel_thread_helper+0x4/0x10 kernel: [119143.641649] [] ? flush_kthread_worker+0xa0/0xa0 kernel: [119143.641652] [] ? gs_change+0x13/0x13 The system has been resetted in order to become operational. I'm unable to use apport-collect on our servers as it does not seem to use proxy settings. ** Affects: lvm2 (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/1514428 Title: pvmove hangs while moving LVs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1514428/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507935] Re: linux: 3.2.0-92.131 -proposed tracker
Hi, Will this kernel update be integrated in the security pocket, as we are severely affected by a bug (#1507658) and we only automatically sync our internal repository with security updates ? If not, is it possible to have a list of URLs, in order to download all needed packages (amd64 & i386) with wget and put them in our bugfix internal repository ? Thanks. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507935 Title: linux: 3.2.0-92.131 -proposed tracker To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1507935/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507658] Re: [3.2.0-91-generic] kernel BUG at /build/linux-_q8eS2/linux-3.2.0/fs/jbd2/journal.c:832!
Kernel has been installed without problem on 3 servers. I/O stress test is in progress... I will update this bug in a couple of hours with results. Thanks for your help ! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507658 Title: [3.2.0-91-generic] kernel BUG at /build/linux- _q8eS2/linux-3.2.0/fs/jbd2/journal.c:832! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507658] Re: [3.2.0-91-generic] kernel BUG at /build/linux-_q8eS2/linux-3.2.0/fs/jbd2/journal.c:832!
No more instability after 5 hours of I/O stress on the 3 updated servers (lvcreate, lvremove, mkfs, resize2fs, etc...). I can confirm that the bug is fixed with this kernel release. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507658 Title: [3.2.0-91-generic] kernel BUG at /build/linux- _q8eS2/linux-3.2.0/fs/jbd2/journal.c:832! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507658] [NEW] [3.2.0-91-generic] kernel BUG at /build/linux-_q8eS2/linux-3.2.0/fs/jbd2/journal.c:832!
Public bug reported: Since kernel 3.2.0-91 update in Ubuntu server 12.04 LTS, 5 of our servers have encountered a serious problem and needed to be rebooted after making random I/O operations (LVM, resize2fs, etc...). All servers that were impacted reported this error in dmesg : kernel BUG at /build/linux-_q8eS2/linux-3.2.0/fs/jbd2/journal.c:832! This seems to be related to this discussion : http://permalink.gmane.org/gmane.linux.kernel.stable/151231 ** Affects: linux (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/1507658 Title: [3.2.0-91-generic] kernel BUG at /build/linux- _q8eS2/linux-3.2.0/fs/jbd2/journal.c:832! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1507658] Re: [3.2.0-91-generic] kernel BUG at /build/linux-_q8eS2/linux-3.2.0/fs/jbd2/journal.c:832!
Unable to use apport-collect on our servers as it does not seem to use proxy settings. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1507658 Title: [3.2.0-91-generic] kernel BUG at /build/linux- _q8eS2/linux-3.2.0/fs/jbd2/journal.c:832! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1507658/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470165] [NEW] sysstat data corruption when adding or removing VCPUs
Public bug reported: Using sysstat 10.0.3-1 on Ubuntu Precise 12.04 LTS. When we add or remove VCPUs to virtual machines (KVM or VMWare in our case), sysstat data starts to be corrupted the next day. All sysstat data will be corrupted, until the current data file is deleted as a workaround. - Symptom : [root@server ~]# sar -A -f /var/log/sysstat/sa30 Invalid system activity file: /var/log/sysstat/sa30 - Workaround : [root@server ~]# rm -f /var/log/sysstat/sa30 - Attachment : Sysstat data archive with : - Correct data : sa22, sa23 - Corrupted data : sa24 = sa29 - Correct data since workaround : sa30 ** Affects: sysstat (Ubuntu) Importance: Undecided Status: New ** Attachment added: sysstat.tar.gz https://bugs.launchpad.net/bugs/1470165/+attachment/4422529/+files/sysstat.tar.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1470165 Title: sysstat data corruption when adding or removing VCPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1470165/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1470165] [NEW] sysstat data corruption when adding or removing VCPUs
Public bug reported: Using sysstat 10.0.3-1 on Ubuntu Precise 12.04 LTS. When we add or remove VCPUs to virtual machines (KVM or VMWare in our case), sysstat data starts to be corrupted the next day. All sysstat data will be corrupted, until the current data file is deleted as a workaround. - Symptom : [root@server ~]# sar -A -f /var/log/sysstat/sa30 Invalid system activity file: /var/log/sysstat/sa30 - Workaround : [root@server ~]# rm -f /var/log/sysstat/sa30 - Attachment : Sysstat data archive with : - Correct data : sa22, sa23 - Corrupted data : sa24 = sa29 - Correct data since workaround : sa30 ** Affects: sysstat (Ubuntu) Importance: Undecided Status: New ** Attachment added: sysstat.tar.gz https://bugs.launchpad.net/bugs/1470165/+attachment/4422529/+files/sysstat.tar.gz -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to sysstat in Ubuntu. https://bugs.launchpad.net/bugs/1470165 Title: sysstat data corruption when adding or removing VCPUs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sysstat/+bug/1470165/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1231529] [NEW] Unattended-upgrades is unable to upgrade language-selector-common
Public bug reported: We're using unattended-upgrades in Ubuntu 12.04 LTS, configured to only update packages from ubuntu-security repository. language-selector-common (0.79.4) was added to ubuntu-security repository on Friday 2013/09/13. This package depends on accountsservice (= 0.6.15-2ubuntu9.5), but this version is not presend in the ubuntu-security repository (0.6.15-2ubuntu9.1). As a matter of fact, our systems can not upgrade this package : The following packages have been kept back: language-selector-common ** Affects: language-selector (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/1231529 Title: Unattended-upgrades is unable to upgrade language-selector-common To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-selector/+bug/1231529/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
