Centos 8 Virtualmin installation script fail

Submitted by peloton on Sat, 02/08/2020 - 17:26

Hello,

I am trying to run the script http://software.virtualmin.com/gpl/scripts/install.sh) to install it on Centos 8 and it crashes. The reason is that it tries to install an older version of EPEL than what I already have installed.

Please find part of the log:

Installing virtualmin-release package: Success.
[2020-02-09 01:16:36 EET] [DEBUG] Phase 2 of 3: Installation
Spin pid is: 8003
2020-02-09 01:16:37 URL:https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm [21844/21844] -> "epel-release-latest-8.noarch.rpm" [1]
Downloading epel-release-latest-8.noarch.rpm: Success.
Spin pid is: 8052
        package epel-release-8-8.el8.noarch (which is newer than epel-release-8-7.el8.noarch) is already installed
Made it here...why?
Installing EPEL release package: [2020-02-09 01:16:38 EET] [ERROR] Failed with error: 2
[2020-02-09 01:16:38 EET] [ERROR] Something went wrong. Exiting.

Thanks!

Status: 
Active

Comments

Ilia's picture
Submitted by Ilia on Sun, 02/09/2020 - 02:27

Hi,

CentOS 8 support is only going to be released with next Webmin and install script releases. There are workarounds to install it right now but it's unofficial and requires more technical knowledge.

Submitted by peloton on Mon, 02/10/2020 - 10:40

Thanks! Is there any release date confirmed?

Ilia's picture
Submitted by Ilia on Tue, 02/11/2020 - 05:05

No, there is no exact date but many people have been asking recently! We are trying to make it as soon as possible.

There are few small bugs left to fix on Webmin side and we are ready to go.

It should be very soon.

Submitted by xstorage on Wed, 04/01/2020 - 13:49

Hi, Any changes that will come up recently? I ask because it is the same mistake yet. Thank you!

Ilia's picture
Submitted by Ilia on Thu, 04/02/2020 - 06:16

Assigned: Unassigned »

Any changes that will come up recently? I ask because it is the same mistake yet. Thank you!

It's been fixed locally a while ago - it will come out as soon as we will be able to recover after data loss and rebuild needed packages.

Sorry about that. I hope for days to have this fixed.

Submitted by greenmeanie on Fri, 04/24/2020 - 20:52

REDHAT is doing the same for me.

Ilia's picture
Submitted by Ilia on Sat, 04/25/2020 - 01:29

What is the error message? Is it about EPEL repos? If so, we fixed it in production and will push changes to the users quite soon.

Submitted by mrcrab on Sun, 04/26/2020 - 01:20

Still same Problem on CentOS 8.1 I publish the whole error messages. Output on a fresh new dedi (Hetzner) with CentOS 8.1 fresh install (they only things ive changed is ssh config of course).

The fix is simple on a fresh new dedi. Before the virtualmin install procedure do:

dnf remove epel-release

Error messages:

Downloading epel-release-latest-8.noarch.rpm                            [  ✔  ]
Installing EPEL release package                                         [ERROR] Failed with error: 2
[  ✘  ]

[ERROR] Something went wrong. Exiting.
[ERROR] The last few log entries were:
Spin pid is: 19603
2020-04-26 08:12:23 URL:https://software.virtualmin.com/vm/6/gpl/centos/8/x86_64/virtualmin-release-latest.noarch.rpm [14112/14112] -> "virtualmin-release-latest.noarch.rpm" [1]
Downloading virtualmin-release-latest.noarch.rpm: Success.
Spin pid is: 19640
warning: virtualmin-release-latest.noarch.rpm: Header V4 RSA/SHA1 Signature, key ID XXXXXXXX: NOKEY
Installing virtualmin-release package: Success.
[2020-04-26 08:12:25 CEST] [DEBUG] Phase 2 of 3: Installation
Spin pid is: 19707
2020-04-26 08:12:25 URL:https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm [21844/21844] -> "epel-release-latest-8.noarch.rpm" [1]
Downloading epel-release-latest-8.noarch.rpm: Success.
Spin pid is: 19756
        package epel-release-8-8.el8.noarch (which is newer than epel-release-8-7.el8.noarch) is already installed
Installing EPEL release package: [2020-04-26 08:12:26 CEST] [ERROR] Failed with error: 2
[2020-04-26 08:12:26 CEST] [ERROR] Something went wrong. Exiting.
[2020-04-26 08:12:26 CEST] [ERROR] The last few log entries were:

Ilia's picture
Submitted by Ilia on Tue, 04/28/2020 - 13:22

It should be no longer an issue. If you still see this issue, try running:

yum clean all

Submitted by mrcrab on Wed, 04/29/2020 - 11:53

You have my gratitude for this GPL release but..... sill many bugs with Virtualmin on a fresh CentOS 8 install (Hetzner Dedi). Virtualmin on CentOS 8.1 date 29.04.2020 :

# dnf install perl -y
# wget http://software.virtualmin.com/gpl/scripts/install.sh
# sudo /bin/sh install.sh --minimal Spin pid is: 17870
        package epel-release-8-8.el8.noarch (which is newer than epel-release-8-                                                                                                                                                             7.el8.noarch) is already installed
Installing EPEL release package: [2020-04-29 04:30:25 CEST] [ERROR] Failed with                                                                                                                                                              error: 2
[2020-04-29 04:30:25 CEST] [ERROR] Something went wrong. Exiting.
[2020-04-29 04:30:25 CEST] [ERROR] The last few log entries were:                                                     
# dnf remove epel-release [16/18] Configuring Webmin                                              ▒▒▒▒▒██Error: Webmin server did not write new PID file
Error
-----
Webmin server did not write new PID file
-----  # /etc/webmin/restart
# sudo /bin/sh install.sh --minimal Checking Configuration from Virtualmin
MySQL does not appear to be installed and running on your system, or has not yet been set up properly in Webmin's MySQL Database module.
If your system does not use MySQL, it should be disabled in Virtualmin's module configuration page.

In fact no password assigned to MYQSL (MariaDB). From shell:

# mysql_secure_installation

When you setup first VHOST status PROFTPD is inactive dead. I tried the fix in this thread, it works 8https://www.virtualmin.com/node/68209)

# ssh-keygen -m PEM -f /etc/proftpd/ssh_host_rsa_key -N '' -t rsa -b 2048
# ssh-keygen -m PEM -f /etc/proftpd/ssh_host_ecdsa_key -N '' -t ecdsa -b 521
# systemctl restart proftpd

if i try to connect trought FTP "425 Unable to build data connection" (FileZilla). I need to change proftpd config file adding:

TLSOptions NoSessionReuseRequired

For let's encrypt you need to

# install certbot
# certbot register
create folder .well-known (strange)in vhosts public_html otherwise auto procedure dont work at all.

And cgi templates are unusable at first time, right now, they require some tuning in CentOS 8, they are not "ready to go" like CentOS 7. (errors: attempt to invoke directory as script... ecc. ecc..)

I repeat, you have my gratitude for this product (it's gpl) and you are my hero. But still too many bugs to be a product "production ready" solution for CentOS 8. I wanted to use it with CentOS 8 but i had to install Virtuamin + CentOS 7 after those things because i'm not sure those are the only bugs.

Ilia's picture
Submitted by Ilia on Thu, 04/30/2020 - 06:12

package epel-release-8-8.el8.noarch (which is newer than epel-release-8- 7.el8.noarch) is already installed

.. to over come this particular error try this patch: https://github.com/virtualmin/virtualmin-install/pull/32/files

The other issues has been fixed already in our production env and will be soon pushed to the public.

I repeat, you have my gratitude for this product (it's gpl)

Appreciate that. I was super busy working on translations for new releases. It will be sorted out in the near future!

Thank you very much for heads up and kind words too! :)

Submitted by neuro17 on Tue, 05/05/2020 - 04:34

We're literally counting days and hours before the official release such that we migrate our VPS' onto Centos 8. Is there a timeline which you can communicate with us?

All the best!

Submitted by facilitator999 on Sun, 01/24/2021 - 14:38

I cant believe it another hetzner customer with the exact issue as me.

Over the last 6 months I changed my hetzner server 3 times thinking its a faulty server which is crashing. I went from cent8 to 7, this gave me 19 days of uptime, usually max 5 days uptime. Great job to virtualmin.

I say f#ck it.

Submitted by facilitator999 on Sun, 01/24/2021 - 14:38

I cant believe it another hetzner customer with the exact issue as me.

Over the last 6 months I changed my hetzner server 3 times thinking its a faulty server which is crashing. I went from cent8 to 7, this gave me 19 days of uptime, usually max 5 days uptime. Great job to virtualmin.

I say f#nk it.

Ilia's picture
Submitted by Ilia on Sun, 01/24/2021 - 17:34

I cant believe it another hetzner customer with the exact issue as me.

What exact issue are you having? Both CentOS 8 and CentOS 8 Stream are supported.