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

My installation command:

bash hst-install.sh --nginx yes --phpfpm yes --apache no --multiphp yes --mysql yes --postgresql no --vsftpd yes --proftpd no --iptables yes --fail2ban yes --quota no --named no --exim no --dovecot no --spamassassin no --clamav no --hostname site.ru --port 36423 --email [email protected] --password pa$$ --lang ru --api no --interactive no

The following server components will be installed on your system:

   - NGINX Web / Proxy Server
   - Multi-PHP Environment
   - MariaDB Database Server
   - Vsftpd FTP Server
   - Firewall (Iptables) + Fail2Ban Access Monitor

====================================================================

Installation backup directory: /root/hst_install_backups/120520200340
Installation log file: /root/hst_install_backups/hst_install-120520200340.log

Adding required repositories to proceed with installation:

(*) NGINX
(*) PHP
(*) MariaDB
(*) Hestia Control Panel

Updating currently installed packages, please wait...-E: Sub-process /usr/bin/dpkg returned an error code (1)

And silence…

It is a fresh server on Debian 10, only today installed. Putty hangs, not even interrupted

Putty login in again to view log, install MC:

root@ded:~# apt-get install mc
E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

root@ded:~/hst_install_backups/120520200340# cat /root/hst_install_backups/hst_install-120520200340.l og
Reading package lists…
Building dependency tree…
Reading state information…
Calculating upgrade…
The following packages were automatically installed and are no longer required:
libevent-2.1-6 libgnutls-dane0 libunbound8
Use ‘apt autoremove’ to remove them.
The following packages have been kept back:
libxml2
The following packages will be upgraded:
libargon2-1 libidn2-0 libmariadb3 libpcre2-8-0 libpcre3 libssl1.1
mariadb-common mysql-common openssl
9 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 3,213 kB of archives.
After this operation, 153 kB disk space will be freed.
Get:1 https://packages.sury.org/php buster/main amd64 libpcre3 amd64 2:8.43-1+0~20190710.6+debian10~1.g bpbfc49f [343 kB]
Get:2 https://packages.sury.org/php buster/main amd64 libidn2-0 amd64 2.2.0-2+0~20200302.4+debian10~1.g bpf85c2e [83.0 kB]
Get:3 https://packages.sury.org/php buster/main amd64 libargon2-1 amd64 0~20190702-0.1+0~20190710.3+deb ian10~1.gbp2fb167 [19.8 kB]
Get:4 https://packages.sury.org/php buster/main amd64 libssl1.1 amd64 1.1.1g-1+0~20200421.17+debian10~1 .gbpf6902f [1,542 kB]
Get:5 https://packages.sury.org/php buster/main amd64 libpcre2-8-0 amd64 10.34-7+0~20191220.5+debian10~ 1.gbp555bb9 [233 kB]
Get:6 https://packages.sury.org/php buster/main amd64 openssl amd64 1.1.1g-1+0~20200421.17+debian10~1.g bpf6902f [837 kB]
Get:7 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.4/debian buster/main amd64 mysql-common all 1:10.4.12+maria~buster [5,560 B]
Get:8 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.4/debian buster/main amd64 mariadb-common al l 1:10.4.12+maria~buster [3,524 B]
Get:9 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.4/debian buster/main amd64 libmariadb3 amd64 1:10.4.12+maria~buster [146 kB]
apt-listchanges: Reading changelogs…
Preconfiguring packages …
Fetched 3,213 kB in 0s (6,596 kB/s)
(Reading database … 30718 files and directories currently installed.)
Preparing to unpack …/libpcre3_2%3a8.43-1+0~20190710.6+debian10~1.gbpbfc49f_amd64.deb …
Unpacking libpcre3:amd64 (2:8.43-1+0~20190710.6+debian10~1.gbpbfc49f) over (2:8.39-12) …
Setting up libpcre3:amd64 (2:8.43-1+0~20190710.6+debian10~1.gbpbfc49f) …
(Reading database … 30718 files and directories currently installed.)
Preparing to unpack …/libidn2-0_2.2.0-2+0~20200302.4+debian10~1.gbpf85c2e_amd64.deb …
Unpacking libidn2-0:amd64 (2.2.0-2+0~20200302.4+debian10~1.gbpf85c2e) over (2.0.5-1+deb10u1) …
Setting up libidn2-0:amd64 (2.2.0-2+0~20200302.4+debian10~1.gbpf85c2e) …
(Reading database … 30719 files and directories currently installed.)
Preparing to unpack …/0-libargon2-1_0~20190702-0.1+0~20190710.3+debian10~1.gbp2fb167_amd64.deb …
Unpacking libargon2-1:amd64 (0~20190702-0.1+0~20190710.3+debian10~1.gbp2fb167) over (0~20171227-0.2) … .
Preparing to unpack …/1-mysql-common_1%3a10.4.12+maria~buster_all.deb …
Unpacking mysql-common (1:10.4.12+maria~buster) over (5.8+1.0.5) …
Preparing to unpack …/2-mariadb-common_1%3a10.4.12+maria~buster_all.deb …
Unpacking mariadb-common (1:10.4.12+maria~buster) over (1:10.3.22-0+deb10u1) …
Preparing to unpack …/3-libssl1.1_1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f_amd64.deb …
Unpacking libssl1.1:amd64 (1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f) over (1.1.1d-0+deb10u3) …
Preparing to unpack …/4-libmariadb3_1%3a10.4.12+maria~buster_amd64.deb …
Unpacking libmariadb3:amd64 (1:10.4.12+maria~buster) over (1:10.3.22-0+deb10u1) …
Preparing to unpack …/5-libpcre2-8-0_10.34-7+0~20191220.5+debian10~1.gbp555bb9_amd64.deb …
Unpacking libpcre2-8-0:amd64 (10.34-7+0~20191220.5+debian10~1.gbp555bb9) over (10.32-5) …
Preparing to unpack …/6-openssl_1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f_amd64.deb …
Unpacking openssl (1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f) over (1.1.1d-0+deb10u3) …
Setting up mysql-common (1:10.4.12+maria~buster) …

Configuration file ‘/etc/mysql/my.cnf’ (actually ‘/etc/mysql/mariadb.cnf’)
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer’s version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** my.cnf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package mysql-common (–configure):
end of file on stdin at conffile prompt
Setting up libssl1.1:amd64 (1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f) …
Setting up libargon2-1:amd64 (0~20190702-0.1+0~20190710.3+debian10~1.gbp2fb167) …
dpkg: dependency problems prevent configuration of mariadb-common:
mariadb-common depends on mysql-common; however:
Package mysql-common is not configured yet.

dpkg: error processing package mariadb-common (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libmariadb3:amd64:
libmariadb3:amd64 depends on mariadb-common; however:
Package mariadb-common is not configured yet.

dpkg: error processing package libmariadb3:amd64 (–configure):
dependency problems - leaving unconfigured
Setting up libpcre2-8-0:amd64 (10.34-7+0~20191220.5+debian10~1.gbp555bb9) …
Setting up openssl (1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f) …
Installing new version of config file /etc/ssl/openssl.cnf …
Processing triggers for man-db (2.8.5-2) …
Processing triggers for libc-bin (2.28-10) …
Errors were encountered while processing:
mysql-common
mariadb-common
libmariadb3:amd64

This isnt related to hestia, apt-get upgrade fails on your system, run it manually and check the output, if it works manualy, start the installation again.

1 Like

I was running “apt-get upgrade” before installation - everything was fine

Is it actually advisable to execute this command often before the installation and also after the installation of hestiacp or could there be problems?

sudo apt-get update && sudo apt-get dist-upgrade

root@ded:~# apt update
Hit:1 http://install.mirror.hoztnode.net/debian buster InRelease
Hit:2 http://mirror.hoztnode.net/debian buster InRelease
Get:3 http://mirror.hoztnode.net/debian buster-updates InRelease [49.3 kB]
Get:4 http://mirror.hoztnode.net/debian buster-backports InRelease [46.7 kB]
Hit:5 http://mirror.hoztnode.net/debian-security buster/updates InRelease
Hit:6 https://packages.sury.org/php buster InRelease
Hit:7 http://nginx.org/packages/mainline/debian buster InRelease
Hit:8 http://ams2.mirrors.digitalocean.com/mariadb/repo/10.4/debian buster InRel                                                                                                                        ease
Ign:9 http://mirror.hoztnode.net/debian buster-backports/main amd64 Packages.dif                                                                                                                        f/Index
Ign:9 http://mirror.hoztnode.net/debian buster-backports/main amd64 Packages.dif                                                                                                                        f/Index
Ign:10 http://mirror.hoztnode.net/debian buster-backports/main amd64 Packages
Get:10 http://mirror.hoztnode.net/debian buster-backports/main amd64 Packages [3                                                                                                                        01 kB]
Hit:11 https://apt.hestiacp.com buster InRelease
Fetched 397 kB in 1s (519 kB/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
1 package can be upgraded. Run 'apt list --upgradable' to see it.
root@ded:~#

Yesterday, “apt update” said there was nothing to update

Following attempt:

Adding required repositories to proceed with installation:

() NGINX
(
) PHP
() MariaDB
(
) Hestia Control Panel

Updating currently installed packages, please wait…-E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable)
E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process using it?

Now installing Hestia Control Panel and all required dependencies.
NOTE: This process may take 10 to 15 minutes to complete, please wait… -
() Configuring system settings…
(
) Configuring Hestia Control Panel…
cp: cannot stat ‘/usr/local/hestia/install/deb/sudo/admin’: No such file or directory
chmod: cannot access ‘/etc/sudoers.d/admin’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/logrotate/hestia’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/packages’: No such file or directory
sed: can’t read /usr/local/hestia/data/packages/.pkg: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/templates’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/templates/web/unassigned/index.html’: No such file or directory
cp: cannot stat '/usr/local/hestia/install/deb/templates/web/skel/document_errors/
‘: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/firewall’: No such file or directory
() Generating default self-signed SSL certificate…
hst-install-debian.sh: line 1109: /usr/local/hestia/bin/v-generate-ssl-cert: No such file or directory
(
) Adding SSL certificate to Hestia Control Panel…
sed: -e expression #1, char 3: unexpected ,' sed: -e expression #1, char 1: unknown command: ,’
cp: cannot stat ‘/usr/local/hestia/install/deb/ssl/dhparam.pem’: No such file or directory
(*) Configuring NGINX…
cp: cannot stat ‘/usr/local/hestia/install/deb/nginx/nginx.conf’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/nginx/status.conf’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/nginx/phpmyadmin.inc’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/nginx/phppgadmin.inc’: No such file or directory
cp: cannot stat ‘/usr/local/hestia/install/deb/logrotate/nginx’: No such file or directory
sed: can’t read /etc/nginx/nginx.conf: No such file or directory
sed: can’t read /usr/local/hestia/nginx/conf/nginx.conf: No such file or directory
Failed to start nginx.service: Unit nginx.service not found.
Error: nginx start failed

It 's weird to hear the answer that it 's not related to the panel. But I didn 't try to put anything else on the server.

It seem that you used the installer from the master on a non 20.04 server.

Please use the release file
wget https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh

And then update with the command that you can use here…

Only for ubuntu 20.04 for testing purpose there is difference be we have added the packages to the repositories.

I used command
wget https://raw.githubusercontent.com/hestiacp/hestiacp/release/install/hst-install.sh
From the home page https://hestiacp.com/

Maybe the reason is that the first attempt to install blocked some resource, and then putty hung, and so hangs?

Do you run is at root? Looks like apt-get is blocked somehow.

Yes, I login as root

Probaly try with a fresh install, something is buggy with your server. Or maybe a reboot should be enough.

Set a new server Debian 10. Run:

bash hst-install.sh --nginx yes --phpfpm yes --apache no --multiphp yes --mysql yes --postgresql no --vsftpd yes --proftpd no --iptables yes --fail2ban yes --quota no --named no --exim no --dovecot no --spamassassin no --clamav no --hostname site.ru --port 36423 --email [email protected] --password pa$$ --lang ru --api no --interactive no

Welcome to the Hestia Control Panel installer!

Please wait a moment while we update your system’s repositories and
install any necessary dependencies required to proceed with the installation…

(*) Installing dirmngr…
!!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!!

WARNING: The following packages are already installed
exim4*

It is highly recommended that you remove them before proceeding.

!!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!! !!!

Would you like to remove the conflicting packages? [y/n]

enter “y”

The following server components will be installed on your system:

  • NGINX Web / Proxy Server
  • Multi-PHP Environment
  • MariaDB Database Server
  • Vsftpd FTP Server
  • Firewall (Iptables) + Fail2Ban Access Monitor

====================================================================

Installation backup directory: /root/hst_install_backups/120520201821
Installation log file: /root/hst_install_backups/hst_install-120520201821.log

Adding required repositories to proceed with installation:

() NGINX
(
) PHP
() MariaDB
(
) Hestia Control Panel

Updating currently installed packages, please wait…-E: Sub-process /usr/bin/dpkg returned an error code (1)

Same as the first time. Putty hangs, does not respond
The server is empty, install only curl and mc

root@ded:~# cat /root/hst_install_backups/hst_install-120520201821.log
Reading package lists…
Building dependency tree…
Reading state information…
The following additional packages will be installed:
gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server
gpgconf gpgsm libassuan0 libksba8 libnpth0 pinentry-curses
Suggested packages:
dbus-user-session pinentry-gnome3 tor parcimonie xloadimage scdaemon
pinentry-doc
The following NEW packages will be installed:
dirmngr gnupg gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client
gpg-wks-server gpgconf gpgsm libassuan0 libksba8 libnpth0 pinentry-curses
0 upgraded, 14 newly installed, 0 to remove and 0 not upgraded.
Need to get 7,089 kB of archives.
After this operation, 14.9 MB of additional disk space will be used.
Get:1 Index of /debian/ buster/main amd64 libassuan0 amd64 2.5.2-1 [49.4 kB]
Get:2 Index of /debian/ buster/main amd64 gpgconf amd64 2.2.12-1+deb10u1 [510 kB]
Get:3 Index of /debian/ buster/main amd64 libksba8 amd64 1.3.5-2 [99.7 kB]
Get:4 Index of /debian/ buster/main amd64 libnpth0 amd64 1.6-1 [18.4 kB]
Get:5 Index of /debian/ buster/main amd64 dirmngr amd64 2.2.12-1+deb10u1 [712 kB]
Get:6 Index of /debian/ buster/main amd64 gnupg-l10n all 2.2.12-1+deb10u1 [1,010 kB]
Get:7 Index of /debian/ buster/main amd64 gnupg-utils amd64 2.2.12-1+deb10u1 [861 kB]
Get:8 Index of /debian/ buster/main amd64 gpg amd64 2.2.12-1+deb10u1 [865 kB]
Get:9 Index of /debian/ buster/main amd64 pinentry-curses amd64 1.1.0-2 [64.5 kB]
Get:10 Index of /debian/ buster/main amd64 gpg-agent amd64 2.2.12-1+deb10u1 [617 kB]
Get:11 Index of /debian/ buster/main amd64 gpg-wks-client amd64 2.2.12-1+deb10u1 [485 kB]
Get:12 Index of /debian/ buster/main amd64 gpg-wks-server amd64 2.2.12-1+deb10u1 [478 kB]
Get:13 Index of /debian/ buster/main amd64 gpgsm amd64 2.2.12-1+deb10u1 [604 kB]
Get:14 Index of /debian/ buster/main amd64 gnupg all 2.2.12-1+deb10u1 [715 kB]
Fetched 7,089 kB in 0s (110 MB/s)
Selecting previously unselected package libassuan0:amd64.
(Reading database … 31272 files and directories currently installed.)
Preparing to unpack …/00-libassuan0_2.5.2-1_amd64.deb …
Unpacking libassuan0:amd64 (2.5.2-1) …
Selecting previously unselected package gpgconf.
Preparing to unpack …/01-gpgconf_2.2.12-1+deb10u1_amd64.deb …
Unpacking gpgconf (2.2.12-1+deb10u1) …
Selecting previously unselected package libksba8:amd64.
Preparing to unpack …/02-libksba8_1.3.5-2_amd64.deb …
Unpacking libksba8:amd64 (1.3.5-2) …
Selecting previously unselected package libnpth0:amd64.
Preparing to unpack …/03-libnpth0_1.6-1_amd64.deb …
Unpacking libnpth0:amd64 (1.6-1) …
Selecting previously unselected package dirmngr.
Preparing to unpack …/04-dirmngr_2.2.12-1+deb10u1_amd64.deb …
Unpacking dirmngr (2.2.12-1+deb10u1) …
Selecting previously unselected package gnupg-l10n.
Preparing to unpack …/05-gnupg-l10n_2.2.12-1+deb10u1_all.deb …
Unpacking gnupg-l10n (2.2.12-1+deb10u1) …
Selecting previously unselected package gnupg-utils.
Preparing to unpack …/06-gnupg-utils_2.2.12-1+deb10u1_amd64.deb …
Unpacking gnupg-utils (2.2.12-1+deb10u1) …
Selecting previously unselected package gpg.
Preparing to unpack …/07-gpg_2.2.12-1+deb10u1_amd64.deb …
Unpacking gpg (2.2.12-1+deb10u1) …
Selecting previously unselected package pinentry-curses.
Preparing to unpack …/08-pinentry-curses_1.1.0-2_amd64.deb …
Unpacking pinentry-curses (1.1.0-2) …
Selecting previously unselected package gpg-agent.
Preparing to unpack …/09-gpg-agent_2.2.12-1+deb10u1_amd64.deb …
Unpacking gpg-agent (2.2.12-1+deb10u1) …
Selecting previously unselected package gpg-wks-client.
Preparing to unpack …/10-gpg-wks-client_2.2.12-1+deb10u1_amd64.deb …
Unpacking gpg-wks-client (2.2.12-1+deb10u1) …
Selecting previously unselected package gpg-wks-server.
Preparing to unpack …/11-gpg-wks-server_2.2.12-1+deb10u1_amd64.deb …
Unpacking gpg-wks-server (2.2.12-1+deb10u1) …
Selecting previously unselected package gpgsm.
Preparing to unpack …/12-gpgsm_2.2.12-1+deb10u1_amd64.deb …
Unpacking gpgsm (2.2.12-1+deb10u1) …
Selecting previously unselected package gnupg.
Preparing to unpack …/13-gnupg_2.2.12-1+deb10u1_all.deb …
Unpacking gnupg (2.2.12-1+deb10u1) …
Setting up libksba8:amd64 (1.3.5-2) …
Setting up libnpth0:amd64 (1.6-1) …
Setting up libassuan0:amd64 (2.5.2-1) …
Setting up gnupg-l10n (2.2.12-1+deb10u1) …
Setting up gpgconf (2.2.12-1+deb10u1) …
Setting up gpg (2.2.12-1+deb10u1) …
Setting up gnupg-utils (2.2.12-1+deb10u1) …
Setting up pinentry-curses (1.1.0-2) …
Setting up gpg-agent (2.2.12-1+deb10u1) …
Setting up gpgsm (2.2.12-1+deb10u1) …
Setting up dirmngr (2.2.12-1+deb10u1) …
Setting up gpg-wks-server (2.2.12-1+deb10u1) …
Setting up gpg-wks-client (2.2.12-1+deb10u1) …
Setting up gnupg (2.2.12-1+deb10u1) …
Processing triggers for man-db (2.8.5-2) …
Processing triggers for libc-bin (2.28-10) …
Reading package lists…
Building dependency tree…
Reading state information…
Calculating upgrade…
The following packages were automatically installed and are no longer required:
libevent-2.1-6 libgnutls-dane0 libunbound8
Use ‘apt autoremove’ to remove them.
The following packages have been kept back:
libxml2
The following packages will be upgraded:
libargon2-1 libidn2-0 libmariadb3 libpcre2-8-0 libpcre3 libssl1.1
mariadb-common mysql-common openssl
9 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
Need to get 3,213 kB of archives.
After this operation, 153 kB disk space will be freed.
Get:1 Index of /php/ buster/main amd64 libpcre3 amd64 2:8.43-1+0~20190710.6+debian10~1.gbpbfc49f [343 kB]
Get:2 Index of /php/ buster/main amd64 libidn2-0 amd64 2.2.0-2+0~20200302.4+debian10~1.gbpf85c2e [83.0 kB]
Get:3 Index of /php/ buster/main amd64 libargon2-1 amd64 0~20190702-0.1+0~20190710.3+debian10~1.gbp2fb167 [19.8 kB]
Get:4 Index of /php/ buster/main amd64 libssl1.1 amd64 1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f [1,542 kB]
Get:5 Index of /php/ buster/main amd64 libpcre2-8-0 amd64 10.34-7+0~20191220.5+debian10~1.gbp555bb9 [233 kB]
Get:6 Index of /php/ buster/main amd64 openssl amd64 1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f [837 kB]
Get:7 Index of /mariadb/repo/10.4/debian/ buster/main amd64 mysql-common all 1:10.4.12+maria~buster [5,560 B]
Get:8 Index of /mariadb/repo/10.4/debian/ buster/main amd64 mariadb-common all 1:10.4.12+maria~buster [3,524 B]
Get:9 Index of /mariadb/repo/10.4/debian/ buster/main amd64 libmariadb3 amd64 1:10.4.12+maria~buster [146 kB]
apt-listchanges: Reading changelogs…
Preconfiguring packages …
Fetched 3,213 kB in 1s (6,167 kB/s)
(Reading database … 31311 files and directories currently installed.)
Preparing to unpack …/libpcre3_2%3a8.43-1+0~20190710.6+debian10~1.gbpbfc49f_amd64.deb …
Unpacking libpcre3:amd64 (2:8.43-1+0~20190710.6+debian10~1.gbpbfc49f) over (2:8.39-12) …
Setting up libpcre3:amd64 (2:8.43-1+0~20190710.6+debian10~1.gbpbfc49f) …
(Reading database … 31311 files and directories currently installed.)
Preparing to unpack …/libidn2-0_2.2.0-2+0~20200302.4+debian10~1.gbpf85c2e_amd64.deb …
Unpacking libidn2-0:amd64 (2.2.0-2+0~20200302.4+debian10~1.gbpf85c2e) over (2.0.5-1+deb10u1) …
Setting up libidn2-0:amd64 (2.2.0-2+0~20200302.4+debian10~1.gbpf85c2e) …
(Reading database … 31312 files and directories currently installed.)
Preparing to unpack …/0-libargon2-1_0~20190702-0.1+0~20190710.3+debian10~1.gbp2fb167_amd64.deb …
Unpacking libargon2-1:amd64 (0~20190702-0.1+0~20190710.3+debian10~1.gbp2fb167) over (0~20171227-0.2) …
Preparing to unpack …/1-mysql-common_1%3a10.4.12+maria~buster_all.deb …
Unpacking mysql-common (1:10.4.12+maria~buster) over (5.8+1.0.5) …
Preparing to unpack …/2-mariadb-common_1%3a10.4.12+maria~buster_all.deb …
Unpacking mariadb-common (1:10.4.12+maria~buster) over (1:10.3.22-0+deb10u1) …
Preparing to unpack …/3-libssl1.1_1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f_amd64.deb …
Unpacking libssl1.1:amd64 (1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f) over (1.1.1d-0+deb10u3) …
Preparing to unpack …/4-libmariadb3_1%3a10.4.12+maria~buster_amd64.deb …
Unpacking libmariadb3:amd64 (1:10.4.12+maria~buster) over (1:10.3.22-0+deb10u1) …
Preparing to unpack …/5-libpcre2-8-0_10.34-7+0~20191220.5+debian10~1.gbp555bb9_amd64.deb …
Unpacking libpcre2-8-0:amd64 (10.34-7+0~20191220.5+debian10~1.gbp555bb9) over (10.32-5) …
Preparing to unpack …/6-openssl_1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f_amd64.deb …
Unpacking openssl (1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f) over (1.1.1d-0+deb10u3) …
Setting up mysql-common (1:10.4.12+maria~buster) …

Configuration file ‘/etc/mysql/my.cnf’ (actually ‘/etc/mysql/mariadb.cnf’)
==> File on system created by you or by a script.
==> File also in package provided by package maintainer.
What would you like to do about it ? Your options are:
Y or I : install the package maintainer’s version
N or O : keep your currently-installed version
D : show the differences between the versions
Z : start a shell to examine the situation
The default action is to keep your current version.
*** my.cnf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing package mysql-common (–configure):
end of file on stdin at conffile prompt
Setting up libssl1.1:amd64 (1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f) …
Setting up libargon2-1:amd64 (0~20190702-0.1+0~20190710.3+debian10~1.gbp2fb167) …
dpkg: dependency problems prevent configuration of mariadb-common:
mariadb-common depends on mysql-common; however:
Package mysql-common is not configured yet.

dpkg: error processing package mariadb-common (–configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libmariadb3:amd64:
libmariadb3:amd64 depends on mariadb-common; however:
Package mariadb-common is not configured yet.

dpkg: error processing package libmariadb3:amd64 (–configure):
dependency problems - leaving unconfigured
Setting up libpcre2-8-0:amd64 (10.34-7+0~20191220.5+debian10~1.gbp555bb9) …
Setting up openssl (1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f) …
Installing new version of config file /etc/ssl/openssl.cnf …
Processing triggers for man-db (2.8.5-2) …
Processing triggers for libc-bin (2.28-10) …
Errors were encountered while processing:
mysql-common
mariadb-common
libmariadb3:amd64

The i9 processor is on the server. Why does it install amd modules?

This is the first line of the log with the word “error…” And the following errors are also associated with the mysql.

AMD64 is commonly used to refer to the 64-bit architecture across Intel and AMD CPUs:

1 Like

I can give someone from the administration access to the server if you want to see more)