What is the output of:
apt-config dump | grep Reboot
?
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Incomplete
--
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
sudo apt-config dump | grep -i reboot
Yielded no lines.
--
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/1887655
Title:
unattended-upgrades triggers reboot desp
As this is server such thing is quite unbelievably bad, is then the only
way in production to remove this package altogether. Its not ideal for
Ubuntu reputation for servers indeed.
** Changed in: unattended-upgrades (Ubuntu)
Status: Expired => New
--
You received this bug notification be
Hi, why this has expired without any confirmation/non-confirmation? This
sounds like a terrible way to resolve bugs?!
I just had the same on a pretty vanilla 20.04 server which kernel was/is
compiled Nov 13 11:40:37 UTC 2020.
below command returns nothing:
apt-config dump | grep Reboot
also:
fgr
[Expired for unattended-upgrades (Ubuntu) because there has been no
activity for 60 days.]
** Changed in: unattended-upgrades (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unatt
Confirming that we see this behaviour on Ubuntu 20.04 servers (reboots
happening even though `Unattended-Upgrade::Automatic-Reboot` is set to
false).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubunt
Also seeing this issue on 20.04. Same behaviour as above (occurence is
random and the symptoms and log information is the same).
--
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.launc
For anyone experiencing this behaviour, have you explicitly set
`Unattended-Upgrade::Automatic-Reboot "false";` or are you just relying
on it defaulting to this setting?
Also, when you say the occurrence is random have you checked for the
presence of a file `/var/run/reboot-required`? My understan
What's in the unattended-upgrades logs?
# zless /var/log/unattended-upgrades/unattended-upgrades.log*
I'm assuming you have a line that says:
WARNING Found /var/run/reboot-required, rebooting
That would confirm that unattended-upgrades is 1) finding the file
telling it to reboot and 2) rebooting
I can confirm this behavior on our server with Ubuntu Server 20.04. The
occurence is random and the symptoms and log information is the same.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
https
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unattended-upgrades in
Ubuntu.
11 matches
Mail list logo
