Forum

Forum > Software > Others > Problem updating the system libssl1.1
Full Version: Problem updating the system libssl1.1
You're currently viewing a stripped down version of our content. View the full version with proper formatting.

naox

11th Dec, 2017, 06:12 AM
I can't do
Code:
apt-get upgrade
nor
Code:
apt-get autoremove
nor
Code:
sudo dpkg --configure -a
, all of them ending with the same error. Maybe there ir a broken package/dependency?

it says
Terminal
1 not fully installed or removed
, I think it's because of my previous tries and should be libssl

Terminal

xbian@xbian:~$ sudo apt-get update && sudo apt-get upgrade
Ign:1 http://deb.debian.org/debian stretch InRelease
Hit:2 http://deb.debian.org/debian stretch Release
Hit:3 http://apt.xbian.org stable InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
dbus iproute2 libcurl3 libcurl3-gnutls libdbus-1-3 libicu57 libsmbclient libssl1.0.2 libwbclient0 openssh-client
openssh-server openssh-sftp-server openssl python-samba samba samba-common samba-common-bin samba-libs tzdata wget
wpasupplicant
21 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
1 not fully installed or removed.
Need to get 0 B/21.1 MB of archives.
After this operation, 7,168 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Create a snapshot of '/run/btrfs-snap/root/@' in '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2017-12-10-2009'
Delete subvolume (no-commit): '/run/btrfs-snap/root/@last_good_known'
Create a snapshot of '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2017-12-10-2009' in '/run/btrfs-snap/root/@last_good_known'
Delete subvolume (no-commit): '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2017-12-10-2008'
@btrfs-auto-snap_apt-run-2017-12-10-2009, 1 created snapshots, 1 destroyed snapshots, 0 warnings.
debconf: Perl may be unconfigured (fields.pm did not return a true value at /usr/share/perl5/Debconf/DbDriver.pm line 12.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/DbDriver.pm line 13.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 9.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 9.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at (eval 1) line 4.
BEGIN failed--compilation aborted at (eval 1) line 4.
) -- aborting
Setting up libssl1.1:armhf (1.1.0f-3+deb9u1) ...
fields.pm did not return a true value at /usr/share/perl5/Debconf/Template.pm line 15.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Template.pm line 15.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 8.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 8.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7.
Compilation failed in require at /usr/share/debconf/frontend line 6.
BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
dpkg: error processing package libssl1.1:armhf (--configure):
subprocess installed post-installation script returned error exit status 5
Errors were encountered while processing:
libssl1.1:armhf
E: Sub-process /usr/bin/dpkg returned an error code (1)


EDIT:

Following this https://www.raspberrypi.org/forums/viewtopic.php?t=31079, now I have two problems, deconf and libssl1.1:armhf

I tried
Code:
sudo apt-get install --reinstall debconf

An the error:

Terminal
xbian@xbian:~$ sudo apt-get install --reinstall debconf
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 21 not upgraded.
1 not fully installed or removed.
Need to get 159 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://deb.debian.org/debian stretch/main armhf debconf all 1.5.61 [159 kB]
Fetched 159 kB in 0s (455 kB/s)
Create a snapshot of '/run/btrfs-snap/root/@' in '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2017-12-10-2020'
Delete subvolume (no-commit): '/run/btrfs-snap/root/@last_good_known'
Create a snapshot of '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2017-12-10-2020' in '/run/btrfs-snap/root/@last_good_known'
Delete subvolume (no-commit): '/run/btrfs-snap/root/@btrfs-auto-snap_apt-run-2017-12-10-2009'
@btrfs-auto-snap_apt-run-2017-12-10-2020, 1 created snapshots, 1 destroyed snapshots, 0 warnings.
debconf: Perl may be unconfigured (fields.pm did not return a true value at /usr/share/perl5/Debconf/DbDriver.pm line 12.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/DbDriver.pm line 13.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 9.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 9.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at (eval 1) line 4.
BEGIN failed--compilation aborted at (eval 1) line 4.
) -- aborting
(Reading database ... 33029 files and directories currently installed.)
Preparing to unpack .../debconf_1.5.61_all.deb ...
Unpacking debconf (1.5.61) over (1.5.61) ...
Setting up debconf (1.5.61) ...
fields.pm did not return a true value at /usr/share/perl5/Debconf/Template.pm line 15.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Template.pm line 15.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 8.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 8.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7.
Compilation failed in require at /usr/share/debconf/frontend line 6.
BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
dpkg: error processing package debconf (--configure):
subprocess installed post-installation script returned error exit status 5
dpkg: dependency problems prevent configuration of libssl1.1:armhf:
libssl1.1:armhf depends on debconf (>= 0.5) | debconf-2.0; however:
Package debconf is not configured yet.
Package debconf-2.0 is not installed.
Package debconf which provides debconf-2.0 is not configured yet.

dpkg: error processing package libssl1.1:armhf (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
debconf
libssl1.1:armhf
E: Sub-process /usr/bin/dpkg returned an error code (1)

then I tried this:

Code:
wget http://cdn-fastly.deb.debian.org/debian/pool/main/d/debconf/debconf_1.5.61_all.deb
and
Code:
dpkg -i debconf_1.5.61_all.deb

And the error is

Terminal
xbian@xbian:/tmp$ sudo dpkg -i debconf_1.5.61_all.deb
(Reading database ... 33029 files and directories currently installed.)
Preparing to unpack debconf_1.5.61_all.deb ...
Unpacking debconf (1.5.61) over (1.5.61) ...
Setting up debconf (1.5.61) ...
fields.pm did not return a true value at /usr/share/perl5/Debconf/Template.pm line 15.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Template.pm line 15.
Compilation failed in require at /usr/share/perl5/Debconf/Question.pm line 8.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Question.pm line 8.
Compilation failed in require at /usr/share/perl5/Debconf/Config.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Config.pm line 7.
Compilation failed in require at /usr/share/perl5/Debconf/Log.pm line 10.
Compilation failed in require at /usr/share/perl5/Debconf/Db.pm line 7.
BEGIN failed--compilation aborted at /usr/share/perl5/Debconf/Db.pm line 7.
Compilation failed in require at /usr/share/debconf/frontend line 6.
BEGIN failed--compilation aborted at /usr/share/debconf/frontend line 6.
dpkg: error processing package debconf (--install):
subprocess installed post-installation script returned error exit status 5
Errors were encountered while processing:
debconf

Maybe a corrupted SD as pointed there?

Nachteule

11th Dec, 2017, 07:47 AM
Hmmm, what happened before?

What sd-card are you using?

If you're using Samsung, maybe card is broken and read-only now. That leads in very very strange behavior (that's my own experience Sad)

naox

11th Dec, 2017, 09:34 AM
(11th Dec, 2017 07:47 AM)Nachteule Wrote: [ -> ]Hmmm, what happened before?

What do you mean? I'm not sure if I understand you. I just checked for updates with apt-get update, I saw about 20 updates so I tried to update the system with apt-get upgrade

(11th Dec, 2017 07:47 AM)Nachteule Wrote: [ -> ]What sd-card are you using?

If you're using Samsung, maybe card is broken and read-only now. That leads in very very strange behavior (that's my own experience Sad)

It's samsung but I can write.

With dmesg I've seen some lines similar to this one:

Terminal
[43173.940173] BTRFS info (device mmcblk0p7): csum failed ino 315323 extent 1359003648 csum 2566472073 wanted 2577832520 mirror 0

bad news I think Sad

Nachteule

11th Dec, 2017, 10:46 AM
(11th Dec, 2017 09:34 AM)naox Wrote: [ -> ]
(11th Dec, 2017 07:47 AM)Nachteule Wrote: [ -> ]Hmmm, what happened before?

What do you mean? I'm not sure if I understand you. I just checked for updates with apt-get update, I saw about 20 updates so I tried to update the system with apt-get upgrade

Ok, so no crash or anything else, sound like the Samsung sd-card issue

Quote:
(11th Dec, 2017 07:47 AM)Nachteule Wrote: [ -> ]What sd-card are you using?

If you're using Samsung, maybe card is broken and read-only now. That leads in very very strange behavior (that's my own experience Sad)

It's samsung but I can write.

How did you checked this?

The problem is, that the sd-card always reports 'everything ok' to the system after write operation. So, the only way to check if sd-card is on read-only mode is to write a file to card, for example by "sudo touch /check-rw" and after rebooting system checking if this file is still there.

Quote:With dmesg I've seen some lines similar to this one:

Terminal
[43173.940173] BTRFS info (device mmcblk0p7): csum failed ino 315323 extent 1359003648 csum 2566472073 wanted 2577832520 mirror 0

bad news I think Sad

Agree, if write test fails (see above) your card is damaged

naox

12th Dec, 2017, 04:18 AM
(11th Dec, 2017 07:47 AM)Nachteule Wrote: [ -> ]How did you checked this?

The problem is, that the sd-card always reports 'everything ok' to the system after write operation. So, the only way to check if sd-card is on read-only mode is to write a file to card, for example by "sudo touch /check-rw" and after rebooting system checking if this file is still there.

I assumed that because the bash history is saved after reboot. I'm going to do some test and I'll come back.

Edit:

I re-confirm, I can write, I created a file and is present after reboot.

Can I do a fsck on reboout with noobs and xbian? I can't find a way to do it.

Nachteule

12th Dec, 2017, 05:16 AM
(12th Dec, 2017 04:18 AM)naox Wrote: [ -> ]
(11th Dec, 2017 07:47 AM)Nachteule Wrote: [ -> ]How did you checked this?

The problem is, that the sd-card always reports 'everything ok' to the system after write operation. So, the only way to check if sd-card is on read-only mode is to write a file to card, for example by "sudo touch /check-rw" and after rebooting system checking if this file is still there.

I assumed that because the bash history is saved after reboot. I'm going to do some test and I'll come back.

Edit:

I re-confirm, I can write, I created a file and is present after reboot.

Can I do a fsck on reboout with noobs and xbian? I can't find a way to do it.

1) you need attached USB keyboard at your Pi
2) you have to enable initramfs
3) Reboot XBian, when message "To dropdown to shell, press and hold shift on usb attached keyboard...! appears, press left shift key. That will enter rescue mode [1]
4) When in rescue mode, run
rum
btrfs check /dev/root
btrfs check --repair /dev/root

[1] it is a bit tricky to enter rescue mode via shift key. An alternate method is adding rescue to /boot/cmdline.txt like this:
Terminal

root@kmxbilr2 ~ # cat /boot/cmdline.txt
rescue telnet zswap.enabled=1 zswap.compressor=lz4 console=tty1 ......

naox

13th Dec, 2017, 07:37 AM
I followed you indications but finally the system didn't boot anymore (except in recovery mode). It got stuck while initiating the network (I tried several times).

I got tired and I flashed a image to set it up from scratch since I did a backup. Now seems to work fine (the system and the sd card).

Thank you very much!
Forum > Software > Others > Problem updating the system libssl1.1
Reference URL's