On Fri, Sep 22, 2017 at 9:29 AM, ethan.hsieh <email address hidden> wrote:
> @Balint
>
> Here is test result for InstallOnShutdown:true
>
> "Errors were encountered while processing: apport"
> u-u still has packages to upgrade after this issue happens.
> So, when I reboot system every time, u-u still tries to upgrade package.
> We expect that there are 30 mins to do the update.
> But, dependency problem will prevent u-u from upgrading packages.
>
> 1. unattended-upgrades-shutdown.log: (Please check full log as attached)
> ----------------
> 2017-09-22 14:54:25,865 WARNING - Running unattended-upgrades in shutdown mode
> 14:54:25~14:55:54 => 1:29, u-u only takes 1:29 to upgrade packges.
> 2017-09-22 14:57:02,183 WARNING - Running unattended-upgrades in shutdown mode
> 14:57:02~14:58:30 => 1:28
> 2017-09-22 15:00:00,233 WARNING - Running unattended-upgrades in shutdown mode
> 15:00:00~15:01:28 => 1:28
> ----------------
>
> 2. unattended-upgrades-dpkg.log:
> ----------------
> Log started: 2017-09-22 14:34:24
> ...
> Preparing to unpack .../apport_2.20.1-0ubuntu2.10_all.deb ...
> Failed to get load state of apport-forward.socket: Connection reset by peer
> 2017-09-22 14:37:26,769 WARNING SIGTERM received, will stop
> Log ended: 2017-09-22 14:37:26
> ----------------
Thanks for the tests and the logs!
It looks like this is an apport issue and u-u can't do much about it.
I think upgrading services _during shutdown_ is something they are
generally not prepared for and to support InstallOnShutdown:true
system-wide packages need to be tested and be prepared with that
scenario in mind.
@Ethan
On Fri, Sep 22, 2017 at 9:29 AM, ethan.hsieh <email address hidden> wrote: wn:true upgrades- shutdown. log: (Please check full log as attached) upgrades- dpkg.log: 2.20.1- 0ubuntu2. 10_all. deb ... forward. socket: Connection reset by peer
> @Balint
>
> Here is test result for InstallOnShutdo
>
> "Errors were encountered while processing: apport"
> u-u still has packages to upgrade after this issue happens.
> So, when I reboot system every time, u-u still tries to upgrade package.
> We expect that there are 30 mins to do the update.
> But, dependency problem will prevent u-u from upgrading packages.
>
> 1. unattended-
> ----------------
> 2017-09-22 14:54:25,865 WARNING - Running unattended-upgrades in shutdown mode
> 14:54:25~14:55:54 => 1:29, u-u only takes 1:29 to upgrade packges.
> 2017-09-22 14:57:02,183 WARNING - Running unattended-upgrades in shutdown mode
> 14:57:02~14:58:30 => 1:28
> 2017-09-22 15:00:00,233 WARNING - Running unattended-upgrades in shutdown mode
> 15:00:00~15:01:28 => 1:28
> ----------------
>
> 2. unattended-
> ----------------
> Log started: 2017-09-22 14:34:24
> ...
> Preparing to unpack .../apport_
> Failed to get load state of apport-
> 2017-09-22 14:37:26,769 WARNING SIGTERM received, will stop
> Log ended: 2017-09-22 14:37:26
> ----------------
Thanks for the tests and the logs! wn:true
It looks like this is an apport issue and u-u can't do much about it.
I think upgrading services _during shutdown_ is something they are
generally not prepared for and to support InstallOnShutdo
system-wide packages need to be tested and be prepared with that
scenario in mind.