Installed openmediavault package post installation script subprocess returned error exit status 1

Updated from 5.5.12-1 to 5.6.26-1, unable to install «openmediavault-omvextrasorg 5.6″​ update

Even though I’ve been using OMV for 2 years, I’m still a beginner and need help.

I started with an OMV 5.5.12-1 installation on a Raspberry Pi 3 in september 2020 and installed the MiniDLNA plugin as an extension.

Today I did an update for the first time and everything worked, except that i’m unable to install the update called «openmediavault-omvextrasorg 5.6».

Whenever i check for new updates via the Button in the OMV-Web-Gui i get the following error:

Failed to execute command ‘export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; apt-get update 2>&1’ with exit code ‘100’: Get:1 file:/var/cache/openmediavault/archives InRelease
Ign:1 file:/var/cache/openmediavault/archives InRelease
Get:2 file:/var/cache/openmediavault/archives Release
Ign:2 file:/var/cache/openmediavault/archives Release
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Ign:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Get:3 file:/var/cache/openmediavault/archives Packages
Get:4 file:/var/cache/openmediavault/archives Translation-en
Ign:4 file:/var/cache/openmediavault/archives Translation-en
Hit:5 http://packages.openmediavault.org/public usul InRelease
Get:6 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Hit:7 http://raspbian.raspberrypi.org/raspbian buster InRelease
Hit:8 http://archive.raspberrypi.org/debian buster InRelease
Hit:9 http://httpredir.debian.org/debian buster-backports InRelease
Hit:10 https://download.docker.com/linux/debian buster InRelease
Ign:11 https://dl.bintray.com/openmediavault-plugin-developers/usul buster InRelease
Get:12 https://openmediavault.github.io/packages usul InRelease [12.7 kB]
Err:13 https://dl.bintray.com/openmediavault-plugin-developers/usul buster Release Could not handshake: The TLS connection was non-properly terminated. [IP: 18.184.26.85 443]
Reading package lists.

E: The repository ‘https://dl.bintray.com/openmediavault-plugin-developers/usul buster Release’ no longer has a Release file.

and when i select the «openmediavault-omvextrasorg 5.6» update and click install i get the following (repeating) output:

Reading package lists.

Building dependency tree.

Reading state information.

The following packages will be upgraded:

1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

1 not fully installed or removed.

Need to get 67.1 kB of archives.

After this operation, 2048 B disk space will be freed.

Err:1 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main armhf openmediavault-omvextrasorg all 5.6

Could not handshake: The TLS connection was non-properly terminated. [IP: 18.184.26.85 443]

Setting up openmediavault (5.6.26-1) .

Creating configuration database .

Migrating configuration database .

Running migration conf_5.6.0

Setting up Salt environment .

Processing system modifications .

dpkg: error processing package openmediavault (—configure):

installed openmediavault package post-installation script subprocess returned error exit status 1

Errors were encountered while processing:

openmediavault

Failed to execute command ‘export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; export DEBIAN_FRONTEND=noninteractive; apt-get —yes —allow-downgrades —allow-change-held-packages —fix-broken —fix-missing —auto-remove —allow-unauthenticated —show-upgraded —option DPkg::Options::=»—force-confold» install openmediavault-omvextrasorg 2>&1’ with exit code ‘100’: Reading package lists.

does anyone know how to fix this problem?

Источник

[SOLVED]openmediavault package post-installation script subprocess error

I’ve upgraded OMV according to ryecoaarons post although I hadn’t any (extra) plugins installed at all and run into the following error:

First, with omv-extras installed as the update instructions suggest I’ve got these errors during apt operations:

As I’ve also just got a blank page after logging on to OMV I’ve also tried fixing the /var/lib/php/sessions permissions according to hugns post

and also checked my PHP version according to votdevs post and also reinstalled the package.

Unfortunately nothing helped to get the GUI running. Tested in three different browsers.

SMB and SSH access both worked. So I called it a day.

After powering up today at least the GUIs working again(maybe due to executing apt autoremove ), though the apt errors persist.

So I tried getting rid of omv-extras via GUI at first and just getting an error from openmediavault package now

I was wondering if omv-extras got removed correctly as it still shows up in the GUI and throws an error when i try to access it

dpkg -l | grep openmediavault also still lists the package

Purging the package is not possible as it doesn’t seem to be available.

I’m looking for a way to fix the «openmediavault package post-installation script subprocess returned error exit status 1» error

and reinstalling omv-extras. The system was initially installed with OMV 3 if that’s important to know.

I had the exact same problem after upgrading from 4.x to 5.x the way you did. The problem was in fact in the post-install script, a line couldn’t execute properly.

I was able to solve it by opening the post-install script (openmediavault.postinst) in /var/lib/dpkg/info with a text editor, finding the faulty line in the script and commenting it. When I ran apt-get upgrade again, no error showed up and the package was installed correctly. Then I ran the commented line which didn’t return any error. For me, the problematic line in he script was the following : «omv-salt deploy run —quiet collectd chrony postfix». Don’t know why it was failing and didn’t look out why it was failing though.

After that, everything was working fine and I could install omv-extras without any probem. Don’t have any problem in GUI or whith sstem in general.

Hope that this can help you !

Joe Foster May 6th 2020

thanks a lot for sharing this knowledge!

After commenting the line in the post-install script you mentioned apt-get update succeeded without any errors.

I haven’t tried installing omv-extras yet, but I don’t think this will cause any troubles.

Joe Foster May 6th 2020

I got the same issue on a ARM-based hosted server (OVH ARM-2T).

My solution was to run «omv-salt deploy run —quiet collectd chrony postfix» without the «—quiet» option

I could see that chrony was the culprit, and it needed a configuration update on my system. See Chronyd fails to start service (chronyd[4458]: Fatal error : Failed to load seccomp rules) — General — openmediavault

After that fix, post-install script of openmediavault went smoothly.

I had the exact same problem after upgrading from 4.x to 5.x the way you did. The problem was in fact in the post-install script, a line couldn’t execute properly.

I was able to solve it by opening the post-install script (openmediavault.postinst) in /var/lib/dpkg/info with a text editor, finding the faulty line in the script and commenting it. When I ran apt-get upgrade again, no error showed up and the package was installed correctly. Then I ran the commented line which didn’t return any error. For me, the problematic line in he script was the following : «omv-salt deploy run —quiet collectd chrony postfix». Don’t know why it was failing and didn’t look out why it was failing though.

After that, everything was working fine and I could install omv-extras without any probem. Don’t have any problem in GUI or whith sstem in general.

Hope that this can help you !

This solved my problem too, except it was «omv-salt deploy run —no-color —quiet apt cronapt» which failed in the script. So I did like Aiki, commened the line and ran it manually.

Hardware:
Chassis: Fractal Design Node 304
Board: ASROCK Z87E-ITX
CPU: Intel Core i5-4670T
CPU Cooler Noctua NH-U12S
System storage: 30GB — Kingston SMS200S3/30G
Data storage: 4 x 4TB — WD Red WD40EFRX 4TB
RAM: 16GB
Ethernet Adapter TP-Link TG-3468 (PCIe)

Источник

Всякий блог

Блог о программировании, сетевом и системном администрировании, операционных системах Windows, Linux и электронной коммерции. В основном используется для создания быстрых заметок

Просьба оставить комментарий

Если вам понравился или не понравился топик. Я что то забыл или не дописал, то вы можете оставить свой комментарий и я постараюсь исправить это в ближайшее время.

среда, 19 февраля 2014 г.

Решение ошибки Sub-process /usr/bin/dpkg returned an error code (1)

Обычно это ошибка выскакивает в процессе обновления в автоматическом режиме, причин может быть множество, например когда основной пакет обновлен, а дополнительные пакеты не совместимы с новой версией ПО.

В моем случае было обновление OVM в Debian 6 выскакивала ошибка

dpkg: error processing openmediavault (—configure):
subprocess installed post-installation script returned error exit status 2
configured to not write apport reports
Errors were encountered while processing: openmediavault
E: Sub-process /usr/bin/dpkg returned an error code (1)

Решить можно следующим образом, нужно зайти в папку /var/lib/dpkg/info и удалить все похожие файлы из этого каталога, но только соответствующие точному названию, в случае с OVM было несколько ошибок подобного рода с пакетами openmediavault, openmediavault-rsnapshot и другими, следовательно удаляется только файлы соответствующие этим именам модулей.

Далее делается apt-get update и apt-get upgrade

Источник

5.6.4-1 post-installation script error

Hey guys, I’m running in to an error when updating to 5.6.4-1, and I could use some guidance.

The update itself seems to have applied correctly, as the webgui reports that I’m on 5.6.4-1, but the post-install script is failing on the processing system modifications step.

I poked around a bit in the script and it looks like that step involves checking the versions of things and flagging possible issues? But I don’t know enough about omv under the hood to be sure.

Any help or just a point in the right direction would be appreciated!

Sorry, no solutions but lending credence to the issue. I’m on same boat.

Not the same boat, but you’re on the same lake

right — not sure why you’re running apt-get install -f. Can you try again with omv-upgrade and see if the same error occurs again?

TXJD64 — try apt install openmediavault. If it fails, apt install openmediavault-sftp. If that succeeds, try the first apt command again. What happens?

TXJD64 — try apt install openmediavault. If it fails, apt install openmediavault-sftp. If that succeeds, try the first apt command again. What happens?

Thanks, I’ve already tried both. Removing openmediavault-sftp then leaves openmediavault to exit with a (1) just the same. Doing an install (reinstall) of openmediavault fails with the same error. It seems to be happening at the SALT command when it tries to configure *something* but I’m not able to ascertain what. I’m removed openmediavault-sftp to better isolate the problem. what log can I check to see what exactly is failing in the post installation configuration?

Re-running omv-upgrade gives:

Edited once, last by TXJD64 ( Apr 13th 2021 ).

Afraid that’s above my pay grade. You’re on the right track, but I wouldn’t know where to check for logs either. hope someone more knowledgeable can chime in soon.

right — not sure why you’re running apt-get install -f. Can you try again with omv-upgrade and see if the same error occurs again?

omv-upgrade looks like it’s just running apt-get update and then stopping without doing anything else, not even getting to the post-install script part.

Looking in /var/lib/dpkg/info/openmediavault.postinst as far as I can tell the «processing system modifications» step is checking what version you’re coming from, then running different commands depending on which version it was, but i can’t see how that would be erroring out, so i’m kinda at a loss.

So are you saying that omv-upgrade does not produce any error message at all?

It produces the exact same output as apt-get update and nothing more.

Those target source errors don’t seem relevant, but who knows

There seem to be a number of repositories that I’m not sure should even belong there. they concern me.

Ign:12 http://ftp.nl.debian.org/debian stretch InRelease

Ign:13 https://repo.mongodb.org/apt/ubuntu xenial/mongodb-org/3.6 InRelease

Get:17 https://dl.ubnt.com/unifi/debian unifi-5.13 InRelease [3010 B]

E: Repository ‘https://dl.ubnt.com/unifi/debian unifi-5.13 InRelease’ changed its ‘Suite’ value from ‘testing’ to »

N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Did you add these? Debian Stretch is version 9, and OMV 5 runs on Buster (version 10).

I can’t even begin to imagine what Ubuntu Xenial (that’s 16.04!) and Debian Unifi are doing in there.

I also have a unifi controller running on this machine, those were probably added by it. But I’m not sure how that is relevant to the post-install script erroring out.

Good point. But I’ve seen some strange things in the past. it honestly wouldn’t surprise me if this was part of the problem.

Sorry I can’t be of more help.

An update: after some further testing I got the script to complete successfully by commenting out these 2 sections in /var/lib/dpkg/info/openmediavault.postinst :

I then ran omv-salt deploy run —no-color —quiet apt cronapt separately, and after a reboot everything seems normal. I’m not 100% sure what omv_module_set_dirty nginx is or how to apply it, but things seem to be working ok so far.

Thanks. that’s worked for me as well, though I share your concern about that omv_module_set_dirty nginx line.

Thanks a lot for your investigation. About omv_module_set_dirty nginx line, you have more information on dirty modules from documentation.

openmediavault does not display the submodules that are affected by the configuration changes. If you still want to know which submodules are affected, simply run cat /var/lib/openmediavault/dirtymodules.json in the CLI.

You just need to add ‘nginx’ module in ‘/var/lib/openmediavault/dirtymodules.json’ file. That’s what does this line in the post script.

So I guess it’s not necessary to comment this section in /var/lib/dpkg/info/openmediavault.postinst.

You never need to add anything to the dirtymodules file. If you want nginx config updates, just run sudo omv-salt deploy run nginx

omv 6.1.4-1 Shaitan | 64 bit | 6.1 proxmox kernel | plugins :: omvextrasorg 6.1.1 | kvm 6.2.7 | compose 6.5.1 | mergerfs 6.3.4 | zfs 6.0.12
omv-extras.org plugins source code and issue tracker — github

Please try ctrl-shift-R and read this before posting a question.

Please put your OMV system details in your signature.
Please don’t PM for support. Too many PMs!

right Apr 16th 2021

hi,
i have the same problem,

Paramétrage de openmediavault (5.6.5-1) .

Creating configuration database .

Migrating configuration database .

Setting up Salt environment .

Processing system modifications .

dpkg: erreur de traitement du paquet openmediavault (—configure) :

installed openmediavault package post-installation script subprocess returned error exit status 1

Des erreurs ont été rencontrées pendant l’exécution :

E: Sub-process /usr/bin/dpkg returned an error code (1)

when i run this command sudo omv-salt deploy run nginx

Comment: States ran successfully. Updating debian.

Duration: 2019.287 ms

Duration: 219.673 ms

Duration: 2.33 ms

Name: update-ca-certificates —fresh

Comment: Command «update-ca-certificates —fresh» run

Duration: 1418.091 ms

Clearing symlinks in /etc/ssl/certs.

Updating certificates in /etc/ssl/certs.

126 added, 0 removed; done.

Running hooks in /etc/ca-certificates/update.d.

Duration: 2.885 ms

Summary for debian

Succeeded: 4 (changed=4)

Total states run: 4

Total run time: 1.643 s

Comment: File /etc/nginx/sites-available/openmediavault-webgui is in the correct state

Duration: 230.325 ms

Comment: File /etc/nginx/openmediavault-webgui.d/security.conf updated

Duration: 68.54 ms

add_header X-XSS-Protection «1; mode=block»;

+add_header Permissions-Policy «microphone=(), camera=(), geolocation=(), payment=()» always;

Name: nginx_ensite openmediavault-webgui

Comment: Command «nginx_ensite openmediavault-webgui» run

Duration: 44.713 ms

Site configuration file ‘openmediavault-webgui’ is already enabled.

Comment: Run failed on minions: debian

Duration: 358.911 ms

Data failed to compile:

Rendering SLS ‘base:omv.deploy.monit.default’ failed: Jinja error: tls: Invalid value ‘0’, allowed values are ‘none, ssl, starttls, auto’.

Traceback (most recent call last):

File «/usr/lib/python3/dist-packages/salt/utils/templates.py», line 497, in render_jinja_tmpl

File «/usr/lib/python3/dist-packages/jinja2/asyncsupport.py», line 76, in render

return original_render(self, *args, **kwargs)

File «/usr/lib/python3/dist-packages/jinja2/environment.py», line 1008, in render

return self.environment.handle_exception(exc_info, True)

File «/usr/lib/python3/dist-packages/jinja2/environment.py», line 780, in handle_exception

reraise(exc_type, exc_value, tb)

File «/usr/lib/python3/dist-packages/jinja2/_compat.py», line 37, in reraise

File » «, line 37, in top-level template code

File «/usr/lib/python3/dist-packages/jinja2/sandbox.py», line 438, in call

return __context.call(__obj, *args, **kwargs)

File «/usr/lib/python3/dist-packages/salt/loader.py», line 1235, in __call__

return self.loader.run(run_func, *args, **kwargs)

File «/usr/lib/python3/dist-packages/salt/loader.py», line 2268, in run

return self._last_context.run(self._run_as, _func_or_method, *args, **kwargs)

File «/usr/lib/python3/dist-packages/salt/loader.py», line 2283, in _run_as

return _func_or_method(*args, **kwargs)

File «/var/cache/salt/minion/extmods/modules/omv_conf.py», line 39, in get

objs = db.get(id_, identifier)

File «/usr/lib/python3/dist-packages/openmediavault/config/database.py», line 85, in get

File «/usr/lib/python3/dist-packages/openmediavault/config/database.py», line 726, in execute

File «/usr/lib/python3/dist-packages/openmediavault/config/database.py», line 487, in _elements_to_object

File «/usr/lib/python3/dist-packages/openmediavault/config/object.py», line 236, in validate

File «/usr/lib/python3/dist-packages/openmediavault/config/datamodel.py», line 202, in validate

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 175, in validate

self._validate_type(value, schema, name)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 229, in _validate_type

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 200, in _validate_type

self._validate_object(value, schema, name)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 305, in _validate_object

self._check_properties(value, schema, name)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 519, in _check_properties

self._validate_type(value[propk], propv, path)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 229, in _validate_type

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 209, in _validate_type

self._validate_string(value, schema, name)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 284, in _validate_string

self._check_enum(value, schema, name)

File «/usr/lib/python3/dist-packages/openmediavault/json/schema.py», line 475, in _check_enum

% (valuev, «, «.join(map(str, schema[‘enum’]))),

Источник

Code: Select all

Reading package lists... Done
Building dependency tree       
Reading state information... Done
Note, selecting 'plymouth-theme-sabily' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-ubuntu-mate-text' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-ubuntu-budgie-text' for glob 'plymouth-*'
Note, selecting 'plymouth-themes' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-kubuntu-text' for glob 'plymouth-*'
Note, selecting 'plymouth-theme' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-lubuntu-logo' for glob 'plymouth-*'
Note, selecting 'plymouth-label' for glob 'plymouth-*'
Note, selecting 'plymouth-themes-script' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-lubuntu-next-logo' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-xubuntu-text' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-ubuntu-text' for glob 'plymouth-*'
Note, selecting 'plymouth-themes-spinfinity' for glob 'plymouth-*'
Note, selecting 'plymouth-themes-solar' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-ubuntu-gnome-logo' for glob 'plymouth-*'
Note, selecting 'plymouth-dev' for glob 'plymouth-*'
Note, selecting 'plymouth-drm' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-ubuntu-mate-logo' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-ubuntu-budgie-logo' for glob 'plymouth-*'
Note, selecting 'plymouth-themes-all' for glob 'plymouth-*'
Note, selecting 'plymouth-themes-glow' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-edubuntu' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-spinner' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-hamara' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-kubuntu-logo' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-lubuntu-text' for glob 'plymouth-*'
Note, selecting 'plymouth-themes-fade-in' for glob 'plymouth-*'
Note, selecting 'plymouth-disabler' for glob 'plymouth-*'
Note, selecting 'plymouth-themes-spinner' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-ubuntustudio' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-lubuntu-next-text' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-breeze' for glob 'plymouth-*'
Note, selecting 'plymouth-x11' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-xubuntu-logo' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-ubuntu-logo' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-ubuntu-gnome-text' for glob 'plymouth-*'
Note, selecting 'plymouth-theme-sabily-text' for glob 'plymouth-*'
Note, selecting 'plymouth-themes' instead of 'plymouth-themes-all'
Note, selecting 'plymouth-themes' instead of 'plymouth-themes-fade-in'
Note, selecting 'plymouth-themes' instead of 'plymouth-themes-glow'
Note, selecting 'plymouth-themes' instead of 'plymouth-themes-script'
Note, selecting 'plymouth-themes' instead of 'plymouth-themes-solar'
Note, selecting 'plymouth-themes' instead of 'plymouth-themes-spinfinity'
Note, selecting 'plymouth-themes' instead of 'plymouth-themes-spinner'
The following additional packages will be installed:
  grub2-themes-ubuntustudio
Suggested packages:
  gdm
The following NEW packages will be installed:
  grub2-themes-ubuntustudio plymouth-disabler plymouth-theme-breeze plymouth-theme-edubuntu plymouth-theme-hamara plymouth-theme-kubuntu-logo plymouth-theme-kubuntu-text
  plymouth-theme-lubuntu-logo plymouth-theme-lubuntu-text plymouth-theme-sabily plymouth-theme-sabily-text plymouth-theme-spinner plymouth-theme-ubuntu-budgie-logo
  plymouth-theme-ubuntu-budgie-text plymouth-theme-ubuntu-gnome-logo plymouth-theme-ubuntu-gnome-text plymouth-theme-ubuntu-logo plymouth-theme-ubuntu-mate-logo
  plymouth-theme-ubuntu-mate-text plymouth-theme-ubuntustudio plymouth-theme-xubuntu-logo plymouth-theme-xubuntu-text plymouth-themes plymouth-x11
0 upgraded, 24 newly installed, 2 reinstalled, 0 to remove and 8 not upgraded.
2 not fully installed or removed.
Need to get 4,573 kB of archives.
After this operation, 8,160 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://packages.linuxmint.com uma/upstream amd64 plymouth-label amd64 0.9.4+mint2+ulyssa [42.9 kB]
Get:2 http://ubuntu.mirror.constant.com focal/universe amd64 grub2-themes-ubuntustudio all 0.3 [21.2 kB]
Get:3 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-disabler all 0.1 [3,098 B]
Get:4 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-breeze amd64 5.18.4.1-0ubuntu1 [71.9 kB]
Get:5 http://packages.linuxmint.com uma/upstream amd64 plymouth-theme-spinner amd64 0.9.4+mint2+ulyssa [203 kB]
Get:6 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-edubuntu all 15.12.1 [43.0 kB]
Get:7 http://packages.linuxmint.com uma/upstream amd64 plymouth-theme-ubuntu-logo amd64 0.9.4+mint2+ulyssa [135 kB]
Get:8 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-hamara all 1.0 [299 kB] 
Get:9 http://packages.linuxmint.com uma/upstream amd64 plymouth-theme-ubuntu-text amd64 0.9.4+mint2+ulyssa [45.9 kB]
Get:10 http://packages.linuxmint.com uma/upstream amd64 plymouth-themes amd64 0.9.4+mint2+ulyssa [666 kB]
Get:11 http://packages.linuxmint.com uma/upstream amd64 plymouth-x11 amd64 0.9.4+mint2+ulyssa [44.7 kB]
Get:12 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-kubuntu-logo all 1:20.04.9 [37.2 kB]
Get:13 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-kubuntu-text all 1:20.04.9 [4,456 B]
Get:14 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-lubuntu-logo all 20.04.3 [26.1 kB]
Get:15 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-lubuntu-text all 20.04.3 [3,712 B]
Get:16 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-sabily all 1.3 [1,760 kB]
Get:17 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-sabily-text all 1.3 [9,776 B]
Get:18 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-ubuntu-budgie-logo all 0.12.3 [33.3 kB]
Get:19 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-ubuntu-budgie-text all 0.12.3 [10.1 kB]
Get:20 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-ubuntu-gnome-logo all 20.04.1 [88.8 kB]
Get:21 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-ubuntu-gnome-text all 20.04.1 [10.0 kB]
Get:22 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-ubuntu-mate-logo all 20.04.2 [38.7 kB]
Get:23 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-ubuntu-mate-text all 20.04.2 [15.3 kB]
Get:24 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-ubuntustudio all 20.04.1 [926 kB]
Get:25 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-xubuntu-logo all 20.04.2 [23.4 kB]
Get:26 http://ubuntu.mirror.constant.com focal/universe amd64 plymouth-theme-xubuntu-text all 20.04.2 [10.8 kB]
Fetched 4,573 kB in 1s (3,902 kB/s)                      
Selecting previously unselected package grub2-themes-ubuntustudio.
(Reading database ... 368884 files and directories currently installed.)
Preparing to unpack .../00-grub2-themes-ubuntustudio_0.3_all.deb ...
Unpacking grub2-themes-ubuntustudio (0.3) ...
Selecting previously unselected package plymouth-disabler.
Preparing to unpack .../01-plymouth-disabler_0.1_all.deb ...
Unpacking plymouth-disabler (0.1) ...
Preparing to unpack .../02-plymouth-label_0.9.4+mint2+ulyssa_amd64.deb ...
Unpacking plymouth-label (0.9.4+mint2+ulyssa) over (0.9.4+mint2+ulyssa) ...
Selecting previously unselected package plymouth-theme-breeze.
Preparing to unpack .../03-plymouth-theme-breeze_5.18.4.1-0ubuntu1_amd64.deb ...
Unpacking plymouth-theme-breeze (5.18.4.1-0ubuntu1) ...
Selecting previously unselected package plymouth-theme-edubuntu.
Preparing to unpack .../04-plymouth-theme-edubuntu_15.12.1_all.deb ...
Unpacking plymouth-theme-edubuntu (15.12.1) ...
Selecting previously unselected package plymouth-theme-hamara.
Preparing to unpack .../05-plymouth-theme-hamara_1.0_all.deb ...
Unpacking plymouth-theme-hamara (1.0) ...
Selecting previously unselected package plymouth-theme-kubuntu-logo.
Preparing to unpack .../06-plymouth-theme-kubuntu-logo_1%3a20.04.9_all.deb ...
Unpacking plymouth-theme-kubuntu-logo (1:20.04.9) ...
Selecting previously unselected package plymouth-theme-kubuntu-text.
Preparing to unpack .../07-plymouth-theme-kubuntu-text_1%3a20.04.9_all.deb ...
Unpacking plymouth-theme-kubuntu-text (1:20.04.9) ...
Selecting previously unselected package plymouth-theme-lubuntu-logo.
Preparing to unpack .../08-plymouth-theme-lubuntu-logo_20.04.3_all.deb ...
Unpacking plymouth-theme-lubuntu-logo (20.04.3) ...
Selecting previously unselected package plymouth-theme-lubuntu-text.
Preparing to unpack .../09-plymouth-theme-lubuntu-text_20.04.3_all.deb ...
Unpacking plymouth-theme-lubuntu-text (20.04.3) ...
Selecting previously unselected package plymouth-theme-sabily.
Preparing to unpack .../10-plymouth-theme-sabily_1.3_all.deb ...
Unpacking plymouth-theme-sabily (1.3) ...
Selecting previously unselected package plymouth-theme-sabily-text.
Preparing to unpack .../11-plymouth-theme-sabily-text_1.3_all.deb ...
Unpacking plymouth-theme-sabily-text (1.3) ...
Selecting previously unselected package plymouth-theme-spinner.
Preparing to unpack .../12-plymouth-theme-spinner_0.9.4+mint2+ulyssa_amd64.deb ...
Unpacking plymouth-theme-spinner (0.9.4+mint2+ulyssa) ...
Selecting previously unselected package plymouth-theme-ubuntu-budgie-logo.
Preparing to unpack .../13-plymouth-theme-ubuntu-budgie-logo_0.12.3_all.deb ...
Unpacking plymouth-theme-ubuntu-budgie-logo (0.12.3) ...
Selecting previously unselected package plymouth-theme-ubuntu-budgie-text.
Preparing to unpack .../14-plymouth-theme-ubuntu-budgie-text_0.12.3_all.deb ...
Unpacking plymouth-theme-ubuntu-budgie-text (0.12.3) ...
Selecting previously unselected package plymouth-theme-ubuntu-gnome-logo.
Preparing to unpack .../15-plymouth-theme-ubuntu-gnome-logo_20.04.1_all.deb ...
Unpacking plymouth-theme-ubuntu-gnome-logo (20.04.1) ...
Selecting previously unselected package plymouth-theme-ubuntu-gnome-text.
Preparing to unpack .../16-plymouth-theme-ubuntu-gnome-text_20.04.1_all.deb ...
Unpacking plymouth-theme-ubuntu-gnome-text (20.04.1) ...
Selecting previously unselected package plymouth-theme-ubuntu-logo.
Preparing to unpack .../17-plymouth-theme-ubuntu-logo_0.9.4+mint2+ulyssa_amd64.deb ...
Unpacking plymouth-theme-ubuntu-logo (0.9.4+mint2+ulyssa) ...
Selecting previously unselected package plymouth-theme-ubuntu-mate-logo.
Preparing to unpack .../18-plymouth-theme-ubuntu-mate-logo_20.04.2_all.deb ...
Unpacking plymouth-theme-ubuntu-mate-logo (20.04.2) ...
Selecting previously unselected package plymouth-theme-ubuntu-mate-text.
Preparing to unpack .../19-plymouth-theme-ubuntu-mate-text_20.04.2_all.deb ...
Unpacking plymouth-theme-ubuntu-mate-text (20.04.2) ...
Preparing to unpack .../20-plymouth-theme-ubuntu-text_0.9.4+mint2+ulyssa_amd64.deb ...
Unpacking plymouth-theme-ubuntu-text (0.9.4+mint2+ulyssa) over (0.9.4+mint2+ulyssa) ...
Selecting previously unselected package plymouth-theme-ubuntustudio.
Preparing to unpack .../21-plymouth-theme-ubuntustudio_20.04.1_all.deb ...
Unpacking plymouth-theme-ubuntustudio (20.04.1) ...
Selecting previously unselected package plymouth-theme-xubuntu-logo.
Preparing to unpack .../22-plymouth-theme-xubuntu-logo_20.04.2_all.deb ...
Unpacking plymouth-theme-xubuntu-logo (20.04.2) ...
Selecting previously unselected package plymouth-theme-xubuntu-text.
Preparing to unpack .../23-plymouth-theme-xubuntu-text_20.04.2_all.deb ...
Unpacking plymouth-theme-xubuntu-text (20.04.2) ...
Selecting previously unselected package plymouth-themes.
Preparing to unpack .../24-plymouth-themes_0.9.4+mint2+ulyssa_amd64.deb ...
Unpacking plymouth-themes (0.9.4+mint2+ulyssa) ...
Selecting previously unselected package plymouth-x11.
Preparing to unpack .../25-plymouth-x11_0.9.4+mint2+ulyssa_amd64.deb ...
Unpacking plymouth-x11 (0.9.4+mint2+ulyssa) ...
Setting up plymouth-theme-hamara (1.0) ...
Setting up plymouth-theme-breeze (5.18.4.1-0ubuntu1) ...
Setting up plymouth-disabler (0.1) ...
Setting up initramfs-tools (0.136ubuntu6.6) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-x11 (0.9.4+mint2+ulyssa) ...
update-initramfs: deferring update (trigger activated)
Setting up linux-image-5.4.0-89-generic (5.4.0-89.100) ...
Setting up grub2-themes-ubuntustudio (0.3) ...
Setting up plymouth-theme-ubuntu-text (0.9.4+mint2+ulyssa) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-ubuntu-mate-text (20.04.2) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-xubuntu-text (20.04.2) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-kubuntu-text (1:20.04.9) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-label (0.9.4+mint2+ulyssa) ...
Setting up plymouth-theme-lubuntu-text (20.04.3) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-kubuntu-logo (1:20.04.9) ...
update-initramfs: deferring update (trigger activated)
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-89-generic
Found linux image: /boot/vmlinuz-5.4.0-88-generic
Found initrd image: /boot/initrd.img-5.4.0-88-generic
Found linux image: /boot/vmlinuz-5.4.0-74-generic
Found initrd image: /boot/initrd.img-5.4.0-74-generic
Adding boot menu entry for UEFI Firmware Settings
done
Setting up plymouth-theme-ubuntu-budgie-text (0.12.3) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-ubuntustudio (20.04.1) ...
update-alternatives: using /usr/share/plymouth/themes/ubuntustudio-logo/ubuntustudio-logo.plymouth to provide /usr/share/plymouth/themes/default.plymouth (default.plymouth) in manual mode
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-ubuntu-mate-logo (20.04.2) ...
FRAMEBUFFER=y
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-edubuntu (15.12.1) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-ubuntu-budgie-logo (0.12.3) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-ubuntu-gnome-text (20.04.1) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-sabily-text (1.3) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-lubuntu-logo (20.04.3) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-xubuntu-logo (20.04.2) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-sabily (1.3) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-ubuntu-logo (0.9.4+mint2+ulyssa) ...
update-initramfs: deferring update (trigger activated)
Setting up plymouth-theme-ubuntu-gnome-logo (20.04.1) ...
update-initramfs: deferring update (trigger activated)
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-89-generic
Found linux image: /boot/vmlinuz-5.4.0-88-generic
Found initrd image: /boot/initrd.img-5.4.0-88-generic
Found linux image: /boot/vmlinuz-5.4.0-74-generic
Found initrd image: /boot/initrd.img-5.4.0-74-generic
Adding boot menu entry for UEFI Firmware Settings
done
Setting up plymouth-theme-spinner (0.9.4+mint2+ulyssa) ...
update-initramfs: deferring update (trigger activated)
Sourcing file `/etc/default/grub'
Sourcing file `/etc/default/grub.d/50_linuxmint.cfg'
Sourcing file `/etc/default/grub.d/init-select.cfg'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-5.4.0-89-generic
Found linux image: /boot/vmlinuz-5.4.0-88-generic
Found initrd image: /boot/initrd.img-5.4.0-88-generic
Found linux image: /boot/vmlinuz-5.4.0-74-generic
Found initrd image: /boot/initrd.img-5.4.0-74-generic
Adding boot menu entry for UEFI Firmware Settings
done
Setting up plymouth-themes (0.9.4+mint2+ulyssa) ...
update-initramfs: deferring update (trigger activated)
Processing triggers for initramfs-tools (0.136ubuntu6.6) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-88-generic
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.4.0-88-generic with 1.
dpkg: error processing package initramfs-tools (--configure):
 installed initramfs-tools package post-installation script subprocess returned error exit status 1
Processing triggers for linux-image-5.4.0-89-generic (5.4.0-89.100) ...
/etc/kernel/postinst.d/dkms:
 * dkms: running auto installation service for kernel 5.4.0-89-generic
   ...done.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.4.0-89-generic
E: /usr/share/initramfs-tools/hooks/plymouth failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.4.0-89-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-5.4.0-89-generic (--configure):
 installed linux-image-5.4.0-89-generic package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
 initramfs-tools
 linux-image-5.4.0-89-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

That message is generic. It just means that the dpkg instance called by apt/apt-get failed for some reason. It doesn’t explain why, how, or give hints how to solve it. As a diagnostic message, it is not useful.

You need to read the lines before the message (sometimes quite a number of them) to find the real error that prevents you from completing the installation.

Yeah, but how do I solve it?

There is no single way to solve it. There are so many reasons why this can happen that it’s futile to attempt to list them all in a single post. Each and every circumstance is almost unique to that package/environment.

But, there’s redemption. The fact that you see this message means that probably there is more relevant information in the lines before the message. For illustrative purposes I will use a example:

(Reading database ... 81657 files and directories currently installed.)
 Removing mongodb-10gen ...
 arg: remove
 invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found.
 dpkg: error processing mongodb-10gen (--remove):
  subprocess installed pre-removal script returned error exit status 100
 invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found.
 dpkg: error while cleaning up:
  subprocess installed post-installation script returned error exit status 100
 Errors were encountered while processing:
  mongodb-10gen
 E: Sub-process /usr/bin/dpkg returned an error code (1)

Now, to find the problem, you need to read backwards:

• E: Sub-process /usr/bin/dpkg returned an error code (1) doesn’t tell me anything useful. So moving on.

• Errors were encountered while processing: mongodb-10gen just tells me what package have problems. Is useful but not enough.

• subprocess installed post-installation script returned error exit status 100: this tells me that the script that failed was the postinst, the one executed in post-installation. This will come handy in some situations, but not in this one.

• dpkg: error while cleaning up: nothing useful here.

• invoke-rc.d: unknown initscript, /etc/init.d/mongodb not found. BINGO! This tells us that invoke-rc.d, a binary that controls the init script in most Debian-like system, failed. It failed because it couldn’t find the /etc/init.d/mongodb script. This is bad. We need to create it or copy from somewhere else so it starts working again. Reinstalling the package is also normally an option for file not found errors.

  In this case, reporting a bug is not necessary because is probable that we were the ones that removed the script, but if you are completely sure you didn’t touch the file (a debsums -sla should confirm it) then report a bug.

So, what exactly do you need to get help? Ideally, the complete output of the problem. It’s also helpful to include the output of sudo dpkg -C and sudo apt-get check, and the output of apt-cache policy package1 package2... where «package1 package2 …» includes all the packages with problems.

Если вы столкнулись с ошибкой  с «sub process usr bin dpkg returned an error code 1» при установке программного обеспечения на Ubuntu Linux, вот как вы можете это исправить.

Одной из распространенных проблем в Ubuntu и других дистрибутивах на основе Debian являются ломанные пакеты.

Вы пытаетесь обновить систему или установить новый пакет, и столкиваеиесь с такой ошибкой, как «Sub-process /usr/bin/dpkg returned an error code 1.

Вот что случилось на днях.

Я пытался установить радио приложение на Ubuntu, и система вернула мне эту ошибку:

Unpacking python-gst-1.0 (1.6.2-1build1) ...
Selecting previously unselected package radiotray.
Preparing to unpack .../radiotray_0.7.3-5ubuntu1_all.deb ...
Unpacking radiotray (0.7.3-5ubuntu1) ...
Processing triggers for man-db (2.7.5-1) ...
Processing triggers for desktop-file-utils (0.22-1ubuntu5.2) ...
Processing triggers for bamfdaemon (0.5.3~bzr0+16.04.20180209-0ubuntu1) ...
Rebuilding /usr/share/applications/bamf-2.index...
Processing triggers for gnome-menus (3.13.3-6ubuntu3.1) ...
Processing triggers for mime-support (3.59ubuntu1) ...
Setting up polar-bookshelf (1.0.0-beta56) ...
ln: failed to create symbolic link '/usr/local/bin/polar-bookshelf': No such file or directory
dpkg: error processing package polar-bookshelf (--configure):
subprocess installed post-installation script returned error exit status 1
Setting up python-appindicator (12.10.1+16.04.20170215-0ubuntu1) ...
Setting up python-gst-1.0 (1.6.2-1build1) ...
Setting up radiotray (0.7.3-5ubuntu1) ...
Errors were encountered while processing:
polar-bookshelf
E: Sub-process /usr/bin/dpkg returned an error code (1)

Здесь важны последние три строки:

Errors were encountered while processing:
polar-bookshelf
E: Sub-process /usr/bin/dpkg returned an error code (1)

Это говорит мне, что пакет полярнаяpolar-bookshelf является причиной. Это может иметь решающее значение для устранения этой ошибки.

Решение проблемы Sub-process /usr/bin/dpkg returned an error code (1)

Попробуем исправить этот сломанный пакет.

Я покажу вам несколько методов, которые вы можете попробовать по одному.

Они простые в использовании и просто без проблем осуществимы.

Вы должны попытаться запустить sudo apt update, а затем попытаться установить новый пакет или обновиться после каждого из описанных здесь методов.

Способ 1: переконфигурировать базу данных пакетов

Первый метод, который вы можете попробовать, – перенастроить базу данных пакетов.

Вероятно, база данных повреждена при установке пакета.

Реконфигурация часто устраняет проблему.

sudo dpkg --configure -a

Способ 2: Использовать принудительную установку

Если установка ранее прервалась, вы можете попробовать установить пакет принудительно:

sudo apt-get install -f

Способ 3. Попробуйте удалить проблемный пакет.

sudo apt remove 

Способ 4. Удалите информационные файлы с информацией о проблемном пакете

Это должно быть вашим последним прибежищем.

Вы можете попробовать удалить файлы, связанные с пакетом, из /var/lib/dpkg/info.

Вам нужно немного узнать о базовых командах Linux, чтобы выяснить, что происходит, и как использовать их с вашей проблемой.

В моем случае у меня была проблема с polar-bookhelof.

Поэтому я искал файлы, связанные с ним:

ls -l /var/lib/dpkg/info | grep -i polar-bookshelf
-rw-r--r-- 1 root root 2324811 Aug 14 19:29 polar-bookshelf.list
-rw-r--r-- 1 root root 2822824 Aug 10 04:28 polar-bookshelf.md5sums
-rwxr-xr-x 1 root root     113 Aug 10 04:28 polar-bookshelf.postinst
-rwxr-xr-x 1 root root      84 Aug 10 04:28 polar-bookshelf.postrm

Теперь мне нужно удалить эти файлы:

sudo mv /var/lib/dpkg/info/polar-bookshelf.* /tmp