Virtualmin-config version 6.0.27

Howdy all,

I’ve just rolled out version 6.0.27 of the virtualmin-config package. This package only impacts new installs (or later runs of the virtualmin config-system command). It has a few fixes for CentOS 8, and a couple of minor bugfixes (PEM cert for ProFTPd on fresh install and compatibility with older clients via NoSessionReuseRequired, some minor config tweaks).



I’ve just failed to install GPL version on Ubuntu 18.0.4.
My steps:

  1. Create new droplet from Digital Ocean (template Ubuntu 18.04 LTS)
  2. Run apt dist-upgrade -y to make sure the system is up to date.
  3. Run the file (follow the guide on website)

The error is printed (my domain & IP is masked)

root@s2:~# ./ -n -m -f
2020-05-22 09:10:57 URL: [22146/22146] -> "" [1]
[INFO] Started installation log in /root/virtualmin-install.log

▣□□ Phase 1 of 3: Setup
Downloading RPM-GPG-KEY-virtualmin-6                                    [  ✔  ]
Downloading RPM-GPG-KEY-webmin                                          [  ✔  ]
Installing Virtualmin 6 key                                             [  ✔  ]
Installing Webmin key                                                   [  ✔  ]
Updating apt metadata                                                   [  ✔  ]
Downloading repository metadata                                         [  ✔  ]
Enabling universe repositories, if not already available                [  ✔  ]
Disabling cdrom: repositories                                           [  ✔  ]
Cleaning out old metadata                                               [  ✔  ]

▣▣□ Phase 2 of 3: Installation
Installing Webmin                                                       [  ✔  ]
Installing Usermin                                                      [  ✔  ]
Installing fail2ban                                                     [  ✔  ]
Removing nginx (if installed) before LAMP installation.                 [  ✔  ]
Removing unneeded packages that could confict with LAMP stack.          [  ✔  ]
Installing postfix                                                      [  ✔  ]
Installing virtualmin-lamp-stack-minimal                                [  ✔  ]
Installing Virtualmin and plugins                                       [  ✔  ]
22 May 09:15:31 ntpdate[7008]: adjust time server offset 0.017881 sec
Installing updates to Virtualmin-related packages                       [  ✔  ]

▣▣▣ Phase 3 of 3: Configuration
Can't locate Virtualmin/ in @INC (you may need to install the Virtualmin::Config module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.26.1 /usr/local/share/perl/5.26.1 /usr/lib/x86_64-linux-gnu/perl5/5.26 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.26 /usr/share/perl/5.26 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/bin/virtualmin-config-system line 9.
BEGIN failed--compilation aborted at /usr/bin/virtualmin-config-system line 9.
▣▣▣ Cleaning up

[WARNING] The following errors occurred during installation:

  ◉ Postinstall configuration returned an error.

The file /root/virtualmin-install.log content:

Yes, it looks like vendor_perl is no longer included in @INC by default. I’m working on a fix now.

1 Like

I am reverting the Debian/Ubuntu repos to the previous package, which may or may not fix the problem…but, worth a shot while I try to figure it out.

You may need to apt-get clean and --uninstall (but, don’t ever run --uninstall on a production system or one with anything you don’t want to lose, as it is very destructive) before re-running

There is an ongoing ticket about the Ubuntu vendor_perl issue in virtualmin-config here:

Please post any follow-up there, as I don’t want to try to keep up with a split conversation about it.

so should i run this update on my debian 9 virtualmin pro system or not?

It doesn’t matter. It is normally only used during Virtualmin installation. (It can be used later when adding services that weren’t enabled during installation, such as adding mail processing tools to a system that was originally installed with --minimal).

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.