[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
Brian, On Dec 3rd I installed from xenial-proposed version 1.1ubuntu1.18.04.7~16.04.0. On Dec 4th unattended-upgrades installed new kernel and rebooted, as it should. Today, Dec 5 unattended-upgrades removed old kernels, which it should do, and then rebooted which it shouldn't do. I have attached unattended-upgrades.log for the relevant days. On a side note unattended-upgrades emailed me after it installed the new kernel on Dec 4th, as it should, but did not email me after removing old kernels on Dec 5th. It should have. Let me know if I can provide any other information or do any further testing. My system is Ubuntu 16.04.5 LTS server. Barry ** Attachment added: "unattended-upgrades.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1458204/+attachment/5219447/+files/unattended-upgrades.log -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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 1458204] Re: removing kernels should not require a restart afterward
@tjaalton My 16.04 server doesn't have update-notifier installed but does have update-notifier-common installed. If I install update-notifier from propose it will install a slew of other packages. If I install update- notifier-common from propose it just installs the new update-notifier- common version 3.168.10. So should i test update-notifier-common instead of update-notifier? -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+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/ListHe
[Touch-packages] [Bug 1458204] Re: removing kernels should not require a restart afterward
I also can verify 1.1ubuntu1.18.04.7~16.04.1. Yesterday new kernels were installed and a reboot performed. Today old kernel was removed and no reboot performed. This test also used the new update-notifier-common version 3.168.10. Yesterday I received an email telling me that new kernels had been installed and a reboot was performed, as it should, but today I received no email stating the old kernel had been removed. I expected one. Is this a new bug? -- 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/1458204 Title: removing kernels should not require a restart afterward Status in unattended-upgrades: New Status in update notifier: New Status in linux package in Ubuntu: Confirmed Status in unattended-upgrades package in Ubuntu: Fix Released Status in update-notifier package in Ubuntu: Fix Released Status in unattended-upgrades source package in Xenial: Fix Committed Status in update-notifier source package in Xenial: Fix Committed Status in linux source package in Artful: Won't Fix Status in unattended-upgrades source package in Artful: Won't Fix Status in update-notifier source package in Artful: Won't Fix Bug description: [Impact] The rationale behind the SRU to Xenial is that with latest unattended- upgrades SRU it starts removing unused kernels, but all older kernels are not removed in a single run. With update-notifier and u-u not fixed they place /var/run/reboot-required asking for a reboot when it is not needed. [Test Case] 1. Perform a kernel upgrade normally via "apt-get dist-upgrade". 2. Reboot. 3. Run "apt-get autoremove" to delete the old kernel packages. 4. "System Notification Helper" now reports that the computer requires a reboot. The "autoremove" operation shouldn't require a reboot, logically speaking, because it's just removing files that are unused by the OS. [ Regression Potential ] If the check for skipping placing the /var/run/reboot-required file is too broad it may make kernel upgrades fail to ask for reboot. The fix changes a hook called by maintainer scripts and a failure in the hook can make kernel package installations fail. The fix is simple and was tested in several releases thus regressing in these ways is unlikely. [ Original Bug Text ] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: apt 1.0.1ubuntu2.7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 Uname: Linux 3.13.0-53-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE Date: Sat May 23 12:47:15 2015 InstallationDate: Installed on 2013-08-31 (629 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) SourcePackage: apt UpgradeStatus: Upgraded to trusty on 2014-04-26 (391 days ago) --- ApportVersion: 2.14.1-0ubuntu3.11 Architecture: amd64 CurrentDesktop: KDE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=66f11ff7-00bb-4452-9168-003cf9078308 InstallationDate: Installed on 2013-08-31 (632 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MachineType: System manufacturer System Product Name Package: linux (not installed) ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-53-generic root=UUID=02741f1f-8107-4a0f-b9a6-31ef470b1389 ro libata.force=noncq quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.13.0-53.89-generic 3.13.11-ckt19 RelatedPackageVersions: linux-restricted-modules-3.13.0-53-generic N/A linux-backports-modules-3.13.0-53-generic N/A linux-firmware 1.127.12 RfKill: Tags: trusty Uname: Linux 3.13.0-53-generic x86_64 UpgradeStatus: Upgraded to trusty on 2014-04-26 (395 days ago) UserGroups: adm cdrom dialout dip fuse lightdm lpadmin plugdev sambashare sudo WifiSyslog: _MarkForUpload: True dmi.bios.date: 08/12/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4210 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P9X79 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4210:bd08/12/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP9X79:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: System Product Name dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/unattended-upgrades/+bug/1458204/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://laun
[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades
lukasz, After a kernel update yesterday I can confirmed that the old kernel was removed and the was no reboot today. apt-cache policy unattended-upgrades unattended-upgrades: Installed: 1.1ubuntu1.18.04.7~16.04.1 Candidate: 1.1ubuntu1.18.04.7~16.04.1 Also installed from xenial-proposed: apt-cache policy update-notifier-common update-notifier-common: Installed: 3.168.10 Candidate: 3.168.10 My system: lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.5 LTS Release:16.04 Codename: xenial tag:verification-done ** Tags added: verification-done-xenial -- 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/1702793 Title: Full backport SRU for unattended-upgrades Status in unattended-upgrades package in Ubuntu: In Progress Status in unattended-upgrades source package in Xenial: Fix Committed Bug description: [Impact] * I would like to propose a one-off full backport of unattended-upgrades 1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because selectively backporting fixes for crashes and for issues that made u-u unreliable would be more risky thanks to the huge number of fixes and the inter-dependencies between them. [Test Case] * Since this backport involves fixing several bugs and this bug itself covers the full backport this is an overview of all LP bugs the upload fixes: - most important bugs (feel free to add more) + LP: #1615381 : apt-get autoremove may remove current kernel All LP bugs fixed by the backport, comments are welcome: + LP: #1230246 could use SRU template but seems straightforward + LP: #1260041 SRU template ok + LP: #1396787 SRU template ok + LP: #1446552 SRU template ok + LP: #1455097 SRU template ok + LP: #1458204 could use SRU template but seems straightforward + LP: #1577215 could use SRU template but seems straightforward + LP: #1602536 SRU template ok + LP: #1615381 could use SRU template but seems straightforward + LP: #1624644 SRU template ok + LP: #1649709 not affecting xenial + LP: #1654070 could use SRU template but seems straightforward + LP: #1654600 SRU template ok + LP: #1675079 SRU template ok + LP: #1680599 could use SRU template but seems straightforward + LP: #1686470 SRU template ok + LP: #1690980 SRU template ok + LP: #1698159 SRU template ok + LP: #1702793 this bug + LP: #1714019 just a merge request + LP: #1718419 just a merge request + LP: #1719630 SRU template ok + LP: #1722426 just a merge request + LP: #1737442 SRU template ok + LP: #1737635 SRU template ok + LP: #1737637 SRU template ok + LP: #1737717 SRU template ok + LP: #1741579 SRU template ok + LP: #1764797 just a merge request + LP: #1773033 SRU template ok + LP: #1775292 SRU template ok + LP: #1775307 SRU template ok + LP: #1778219 SRU template ok + LP: #1778800 SRU template ok + LP: #1779157 SRU template ok + LP: #1781176 SRU template ok + LP: #1781183 SRU template ok + LP: #1781446 SRU template ok + LP: #1781586 SRU template ok + LP: #1785093 SRU template ok + LP: #1789637 SRU template ok + LP: #1803749 SRU template ok [Regression Potential] * Due to this update covering the full backport unattended-upgrades can regress in any imaginable way including failing to install, upgrade, run, or removing essential packages from the system. Those are unlikely.* There are open bugs about u-u being slower than in the past, thus this may be a likely regression but IMO the pending speed optimizations should not be blocking the backport because the reliability issues are more important to fix and speed optimizations can be cherry-picked later. [Other Info] I asked for an exception for the package in following the SRU process: https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html I'm preparing the backport in ppa:rbalint/scratch and also run autopkgtests on it in addition to testing it manually in VMs. [Original Bug Text] Changes to support day-of-week patching and logging to syslog were added to upstream (https://github.com/mvo5/unattended-upgrades) over a year ago. These changes are not present in the latest Xenial nor Trusty packages (0.90 and 0.82.1) - requesting that these changes be pulled from upstream. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1702793/+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 1626345] Re: After rebooting for updates, reboot is still required.
Brian, Yesterday we had kernel updates. My server, which is set to automatically reboot, reboot fine and no /var/run/reboot-required. This morning there was no second reboot, so everything was as expected. The I ran autoremove to remove the stale kernel. Then I had /var/run/reboot- required and /var/run/reboot-required.pkgs contained linux-base. So I wouldn't think removing a kernel should require a reboot. So is this a bug or am I not understand how this should work? I confirmed this on a second 16.04 server Attached are the /var/log/apt/history.logs from before autoremove and after. ** Attachment added: "before_history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4760019/+files/before_history.log -- 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/1626345 Title: After rebooting for updates, reboot is still required. Status in One Hundred Papercuts: Confirmed Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1626345/+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 1626345] Re: After rebooting for updates, reboot is still required.
And the after autoremove log ** Attachment added: "after_history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4760020/+files/after_history.log -- 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/1626345 Title: After rebooting for updates, reboot is still required. Status in One Hundred Papercuts: Confirmed Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1626345/+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 1626345] [NEW] After rebooting for updates, reboot is still required.
Public bug reported: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New ** Tags: reboot ** Attachment added: "apport.unattended-upgrades.x41_ij8b.apport" https://bugs.launchpad.net/bugs/1626345/+attachment/4745785/+files/apport.unattended-upgrades.x41_ij8b.apport -- 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/1626345 Title: After rebooting for updates, reboot is still required. Status in unattended-upgrades package in Ubuntu: New Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+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 1626345] Re: After rebooting for updates, reboot is still required.
Brian, File attached. ** Attachment added: "history.log" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+attachment/4746383/+files/history.log -- 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/1626345 Title: After rebooting for updates, reboot is still required. Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+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 1626345] Re: After rebooting for updates, reboot is still required.
Brian, I don't have that file as it was removed by the reboot, but I do believe it said "Linux base", same as the day before. -- 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/1626345 Title: After rebooting for updates, reboot is still required. Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1626345/+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 1626345] Re: After rebooting for updates, reboot is still required.
Brian, This weekend we had updates for libssl and a libssl regression. Both required a reboot and no second reboot. In other words worked as expected. Perhaps the bug only occurs for kernel updates. I have had this happen a few times in the past. So the next time it happens I will not run autoremove manually, to see what happens. What files and logs can I provide at that time that will help? -- 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/1626345 Title: After rebooting for updates, reboot is still required. Status in One Hundred Papercuts: Confirmed Status in unattended-upgrades package in Ubuntu: Incomplete Bug description: Yesterday unattended-upgrades required a reboot for kernel updates as expected. But today unattended-upgrades required a reboot even though there were no updates. 2016-09-20 05:20:10,409 INFO Initial blacklisted packages: 2016-09-20 05:20:10,410 INFO Initial whitelisted packages: 2016-09-20 05:20:10,411 INFO Starting unattended upgrades script 2016-09-20 05:20:10,411 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-20 05:21:13,118 INFO Packages that will be upgraded: linux-generic linux-headers-generic linux-image-generic linux-libc-dev 2016-09-20 05:21:13,119 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2016-09-20 05:24:17,405 INFO All upgrades installed 2016-09-20 05:24:24,959 WARNING Found /var/run/reboot-required, rebooting 2016-09-21 05:10:54,080 INFO Initial blacklisted packages: 2016-09-21 05:10:54,088 INFO Initial whitelisted packages: 2016-09-21 05:10:54,089 INFO Starting unattended upgrades script 2016-09-21 05:10:54,089 INFO Allowed origins are: ['o=Ubuntu,a=xenial-security', 'o=Ubuntu,a=xenial-updates'] 2016-09-21 05:11:02,624 INFO No packages found that can be upgraded unattended and no pending auto-removals 2016-09-21 05:11:02,624 WARNING Found /var/run/reboot-required, rebooting On this machine (16.04 server) unattended-upgrades is configured to reboot automatically. This also happened on another 16.04 server with default unattended- upgrades configuration. It displayed the ***System restart required*** message. The same on a 14.04 server and a 14.04 desktop. Expected behaviour: Not to do an unnecessary reboot. Let me know what other information I can provide. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1626345/+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 1541730] Re: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot
I have noticed this too, at least with logrotate not running. I thought this was because the reboot happens right after, or during, unattended-upgrades. So I set the time to reboot to 7:30 AM in /etc/apt/apt.conf/50unattended-upgrades to give the rest of cron.daily time to run. However logrotate still did not run. And I assume neither did the rest of cron.daily. I believe unattended-upgrades issues shutdown -r 07:30 in my case. So I wondered if the impending shutdown was blocking logrotate, and the rest of cron.daily. However searching the Internet I could not confirm that theory. So I too think cron.daily/apt should be the last thing run in cron.daily. One more issue that may be related. After the reboot /var/run/reboot-required and /var/run/reboot-required.pkgs still exist and the "*System restart required" message appearers at logoin. ** Attachment added: "Apport report and 50unatended-upgrades file" https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1541730/+attachment/4692505/+files/apport.unattended-upgrades.fttw5049.apport -- 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/1541730 Title: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When unattended-upgrades is configured to apply updates and Unattended-Upgrade::Automatic-Reboot is set to "true", and there's an update that requires a reboot, you'll find that none of the scripts in /etc/cron.daily were executed on that day. (To be more precise, none that are alphabetically after the 'apt' script, which is most of them.) It would be good if unattended-upgrades did the reboot from /etc/cron.daily/zzz-unattended-upgrade-reboot, so the other scripts get a chance to run first. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2.4 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Feb 4 10:02:38 2016 PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to trusty on 2014-09-16 (505 days ago) mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2014-10-09T09:04:05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1541730/+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 1541730] Re: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot
Can't seem to edit my own post. Disregard the last paragraph about reboot-required, I need to look into that a little further, -- 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/1541730 Title: all cron.daily scripts are skipped on a day when unattended-upgrades triggers a reboot Status in unattended-upgrades package in Ubuntu: Confirmed Bug description: When unattended-upgrades is configured to apply updates and Unattended-Upgrade::Automatic-Reboot is set to "true", and there's an update that requires a reboot, you'll find that none of the scripts in /etc/cron.daily were executed on that day. (To be more precise, none that are alphabetically after the 'apt' script, which is most of them.) It would be good if unattended-upgrades did the reboot from /etc/cron.daily/zzz-unattended-upgrade-reboot, so the other scripts get a chance to run first. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: unattended-upgrades 0.82.1ubuntu2.4 ProcVersionSignature: Ubuntu 3.13.0-77.121-generic 3.13.11-ckt32 Uname: Linux 3.13.0-77-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 Date: Thu Feb 4 10:02:38 2016 PackageArchitecture: all SourcePackage: unattended-upgrades UpgradeStatus: Upgraded to trusty on 2014-09-16 (505 days ago) mtime.conffile..etc.apt.apt.conf.d.50unattended.upgrades: 2014-10-09T09:04:05 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1541730/+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 1581892] [NEW] Download fails on already athenticated site
Public bug reported: I have a personal website that I use Apache's AuthType Basic to authenticate. >From my phone ( Nexas 4 Mako OTA10 ) I can access the page and login OK. When >I download a file I get a HttpError: 401-Unathorized. More in depth: When I press the "GetFile" link Apache logs (in access.log): 192.168.0.67 - barry [14/May/2016:17:47:11 -0500] "GET /briefcase/getfile.php?id=45 HTTP/1.1" 200 154936 "http://192.168.0.101/briefcase/index.php?tab=search"; "Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36" On my phone the the Download Dialog pops up and I press download apache logs 192.168.0.67 - - [14/May/2016:17:47:33 -0500] "GET /briefcase/getfile.php?id=45 HTTP/1.1" 401 728 "http://192.168.0.101/briefcase/index.php?tab=search"; "Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36" The difference is the first has my user name "barry" in it and the second doesn't. In comparison when doing the same thing from my desktop (14.04) and FireFox Apache logs 192.168.0.2 - barry [14/May/2016:18:04:49 -0500] "GET /briefcase/getfile.php?id=45 HTTP/1.1" 200 492086 "http://192.168.0.101/briefcase/index.php?tab=search"; "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0" and displays the "What should FireFox do with this file" dialog and Apache logs nothing further. On my phone this behavior is the same whether I press "Download" or "Choose an application" from the Download dialog. Also if I long press the link and choose "Save link" the download fails also. When I tried to download a file from a commercial site I have to log into, the download succeeded. I suspect the difference is the commercial site probably uses something beside "AuthType Basic". I'm happy to provide any logs or to do more testing. Thanks ** Affects: webbrowser-app (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1581892 Title: Download fails on already athenticated site Status in webbrowser-app package in Ubuntu: New Bug description: I have a personal website that I use Apache's AuthType Basic to authenticate. From my phone ( Nexas 4 Mako OTA10 ) I can access the page and login OK. When I download a file I get a HttpError: 401-Unathorized. More in depth: When I press the "GetFile" link Apache logs (in access.log): 192.168.0.67 - barry [14/May/2016:17:47:11 -0500] "GET /briefcase/getfile.php?id=45 HTTP/1.1" 200 154936 "http://192.168.0.101/briefcase/index.php?tab=search"; "Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36" On my phone the the Download Dialog pops up and I press download apache logs 192.168.0.67 - - [14/May/2016:17:47:33 -0500] "GET /briefcase/getfile.php?id=45 HTTP/1.1" 401 728 "http://192.168.0.101/briefcase/index.php?tab=search"; "Mozilla/5.0 (Linux; Ubuntu 14.04 like Android 4.4) AppleWebKit/537.36 Chromium/35.0.1870.2 Mobile Safari/537.36" The difference is the first has my user name "barry" in it and the second doesn't. In comparison when doing the same thing from my desktop (14.04) and FireFox Apache logs 192.168.0.2 - barry [14/May/2016:18:04:49 -0500] "GET /briefcase/getfile.php?id=45 HTTP/1.1" 200 492086 "http://192.168.0.101/briefcase/index.php?tab=search"; "Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:46.0) Gecko/20100101 Firefox/46.0" and displays the "What should FireFox do with this file" dialog and Apache logs nothing further. On my phone this behavior is the same whether I press "Download" or "Choose an application" from the Download dialog. Also if I long press the link and choose "Save link" the download fails also. When I tried to download a file from a commercial site I have to log into, the download succeeded. I suspect the difference is the commercial site probably uses something beside "AuthType Basic". I'm happy to provide any logs or to do more testing. Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1581892/+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
