This is a very annoying bug. Last morning unattended-upgrade failed on
a machine, so I set APT::Periodic::Verbose to "3" and this morning I got
a very verbose email showing that it succeeded.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Yurii: can you clarify how that broke unattended upgrades?
I also don't see how a cron script might get different PATH values from one day
to the other.
I just had another instance of this bug on a third Ubuntu 14.04 LTS server
(this one a physical machine, not a VPS) where unattended-upgrades
For me this happened in 14.04.
I've found that root cause was PATH environment variable that lack /sbin and
/usr/sbin
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721294
Title:
Unattended
Well, I got the debug output this time (a whole megabyte of it, split in
two different emails), but unattended-upgrades succeeded, so I still
don't know what the original problem was.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The good news is the problem is reproducible.
The bad news is APT::Periodic::Verbose "1" doesn't make unattended-
upgrade produce any more output in its failure email:
Unattended upgrade returned: False
Packages that attempted to upgrade:
dh-apparmor libapparmor1
(By reading that script I've discovered the existence of
APT::Periodic::Verbose. We'll see what happens next morning with this
set to "1"!)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721294
The thing is, whenever I run it interactively over ssh, unattended-
upgrade succeeds. It's only the cron job that fails.
If there's no separate config file, I'll edit /etc/cron.daily/apt
directly. (This server is still on Ubuntu 14.04 LTS).
--
You received this bug notification because you
Try running it with the --debug switch.
1514 parser.add_option("-d", "--debug",
1515 action="store_true", default=False,
1516 help=_("print debug messages"))
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
This happened again. Can I tweak some config file to enable verbose
mode for unattended-upgrades and see if it'll fail when run from cron
tomorrow night?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This happened again, while trying to upgrade libpq-dev libpq5
postgresql-9.3 postgresql-client-9.3.
Running `unattended-upgrade -v` over an interactive SSH session
succeeded.
I'm not sure what's different. Locale? The successful installation log
contains some non-ASCII characters, specifically
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721294
Can you try manually running the upgrade with the verbose switch? e.g.
'unattended-upgrade -v'.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1721294
Title:
Unattended upgrade fails with "Error in
This happened again this morning, on a different VPS, while trying to
upgrade curl libcurl3 libcurl3-gnutls linux-libc-dev.
My guess that this had something to do with ca-certificates upgade
printing non-ASCII strings to the output was proven wrong.
--
You received this bug notification because
13 matches
Mail list logo
