I assume the affected system is a live USB/installer system? It is not
quite obvious from the description.
I am having the same issue of missing logrotation when using the Ubuntu
Desktop 14.04.3 LTS installer
(http://releases.ubuntu.com/14.04.3/ubuntu-14.04.3-desktop-amd64.iso) as
basis for a
Thanks @ollisa.
I had the same thoughts about 1.0.1f-1ubuntu2 so I found a downloadable
build at https://launchpad.net/ubuntu/+source/openssl/1.0.1f-
1ubuntu2.19. Installing just the ubuntu2.19 version of libssl1.0.0
solved the issue;
wget
The issue is not limited to Ubuntu 16.04 and PHP 7.
We experience a similar issue on Ubuntu 14.04 using PHP 5.5 (se exact
system info below).
Tonight's unattended openssl update from 1.0.1f-1ubuntu2.19 to 1.0.1f-
1ubuntu2.20 (http://www.ubuntu.com/usn/usn-3087-1/,
Thanks for the fix.
I too can verify that our system doesn't segfault on Ubuntu 14.04
(trusty) using latest libssl1.0.0 (=1.0.1f-1ubuntu2.21);
# dpkg -l |grep libssl1.0.0
ii libssl1.0.0:amd64 1.0.1f-1ubuntu2.21
amd64Secure Sockets
Follow up to my comment #7:
Inspecting log files I find what to me looks like a bad recursion in
dependency checking when setting up the package gcr (GNOME crypto
services). The apt-term log shows 50 of the same error message about
unability to run triggers for gconf2 because python3 is
Hit this same problem while upgrading from 15.10 to 16.04 using the GUI
distribution upgrader.
During upgrade I got a dialog reporting the gconf2 dependency problem.
The terminal indicates this happened on unpacking the inkscape package.
See upper screenshot of attached image.
The upgrade
I am also seing this on a 14.04 server using logrotate package version
3.8.7-1ubuntu1:
$ dpkg -l|grep logrotate
ii logrotate 3.8.7-1ubuntu1
amd64Log rotation utility
$ lsb_release -a
No LSB modules are available.
An annoyance about this change is that it reuses the apt-daily.timer for
only download and lets the upgrade be triggered by a new apt-daily-
upgrade.timer.
Systems using apt <1.2.24 which were sensitive to the upgrade point of
time would typically have overridden the apt-daily.timer to happen at
Sorry, apt 1.2.24 was not a SRU so the point about it being unattended
is not valid, others are.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
https://bugs.launchpad.net/bugs/1686470
Title:
Apt updates
** Package changed: unattended-upgrades (Ubuntu) => redmine (Ubuntu)
--
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/1706740
Title:
ruby upgrade broke redmine
Public bug reported:
On a Ubuntu 16.04 system deploying a Redmine issue tracker using the
Ubuntu redmine package this night's (the systemd apt-daily timer has
been rescheduled to run at 00:30) unattended upgrade of USN-3365
security updates to Ruby packages
Am affected by the missing sntp binary also.
For reference the Debian bug mentioned in comment #4 is
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793837.
Also note that the workaround mentioned in #15 does not (AFAICT from
https://github.com/ntp-project/ntp/blob/master/ntpdate/ntpdate.c)
This happened to me yesterday on a 16.04 desktop system using update-
manager. Apparently failed during setup of package unattended-upgrades.
Below is apt/history.log, apt/term.log, ps and debconf version taken
while the GUI has been hanging (greyed out and unresponsive) for ~15
hours. GUI
This is caused by insufficient disk space on /boot partition where
kernels are stored, excerpts from the attachments:
update-initramfs: Generating /boot/initrd.img-4.4.0-139-generic
cat: write error: No space left on device
Filesystem 1K-blocks Used Available Use% Mounted
This particular issue seems to be caused by a mismatch between a
specific software suspend partition being specified in ininitramfs-tools
config and the available partitions. Not inadequate storage on /boot.
See end of DpkgTerminalLog.txt;
update-initramfs: Generating
This seems to be caused by bad installation state of package initramfs-
tools-core which should have provided file /usr/share/initramfs-
tools/scripts/functions together with /usr/sbin/mkinitramfs tool.
See end of DpkgTerminalLog.txt;
update-initramfs: Generating
Seems plausible that this is caused by inadequate storage on /boot.
See Df.txt;
/dev/sda1 240972 191360 37171 84% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-45-generic
Error 24 : Write error : cannot write compressed block
E:
Seems plausible that this is caused by inadequate storage on /boot.
See Df.txt;
/dev/sda1 240972 192901 35630 85% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-39-generic
Error 24 : Write error : cannot write
Seems plausible that this is caused by inadequate storage on /boot.
See Df.txt;
/dev/sdb2 241965 197598 31875 87% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-29-generic
Error 24 : Write error : cannot write compressed
This one is different from other initramfs-tools post-installation
errors. /boot is on / which has plenty of space, but update-initramfs is
missing /boot/initrd.img-5.4.0-37-generic.new.
See Df.txt;
/dev/sda5 436953712 8324136 406363876 3% /
/dev/sda1 523248 4523244 1%
Seems plausible that this is caused by inadequate storage on /boot.
See Df.txt;
/dev/md0 235691 183367 35848 84% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic
Error 24 : Write error : cannot write compressed block
E:
Like #3 experienced, logs seems to make it plausible that this is caused
by inadequate storage on /boot.
See Df.txt;
/dev/sda1 240972190591 37940 84% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating /boot/initrd.img-5.4.0-26-generic
Error 24 :
Public bug reported:
Upgrading from 18.04 to 20.04.
No space left on /boot.
Solved by changing compression from lz4 to xz and regenerating before reboot.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.7
ProcVersionSignature: Ubuntu 5.4.0-147.164-generic
The issue I experienced here, with ~0 bytes free on /boot, produces a
more clear "no space left" error than other initramfs-tools post-
installation bugs.
See Df.txt;
/dev/sda1 238924232193 0 100% /boot
See end of DpkgTerminalLog.txt;
update-initramfs: Generating
24 matches
Mail list logo
