Following the guide: https://github.com/virtualmin/virtualmin-install/blob/master/README.md#p...
Doing a GPL install to test things out and it fails.
In looking into it I output the file it's looking for and got: http://software.virtualmin.com/vm/6/gpl/centos/7/x86_64/virtualmin-relea... Downloading virtualmin-release-latest.noarch.rpm [ ✔ ]
Yet virtualmin-release-latest.noarch.rpm does not exist, so I think it's downloading that page and sayings it's all good.
http://software.virtualmin.com/vm/6/gpl/centos/7/x86_64/virtualmin-relea...
Not Found
The requested URL /vm/6/gpl/centos/7/x86_64/virtualmin-release-latest.noarch.rpm was not found on this server.
After I changed the file to "virtualmin-release-6.0-2.centos.noarch.rpm" (line 550): I got more errors. This may have been because I reran on the same system that just failed.
Installing yum-utils [2017-06-10 07:07:15 UTC] [] Failed with error: 1\n ... etc
Upon outputting and executing the command from "$install yum-utils" (line 696), echo $? outputs 0? Not sure where it gets 1 from.
/usr/bin/yum -y install yum-utils... Loading mirror speeds from cached hostfile * base: mirror.netaddicted.ca * epel: ca.mirror.babylon.network * extras: mirror.csclub.uwaterloo.ca * updates: mirror.netaddicted.ca Package yum-utils-1.1.31-40.el7.noarch already installed and latest version Nothing to do
echo $?0
So a bit minor. For your readme, wget statement misses output file: wget -O https://raw.githubusercontent.com/virtualmin/virtualmin-install/master/v...
Probably meant or just to omit it? wget -O install.sh https://raw.githubusercontent.com/virtualmin/virtualmin-install/master/v...
https://github.com/virtualmin/virtualmin-install/blob/master/README.md
Comments
Submitted by jackalyst on Sat, 06/10/2017 - 09:27 Pro Licensee Comment #1
Sorry for the formatting. I didn't know this uses markdown. Should have clicked "more information about text formats" instead of just assumed this was a Drupal textarea.
Submitted by jackalyst on Sat, 06/10/2017 - 09:38 Pro Licensee Comment #2
Reformatted.
Following the guide:
https://github.com/virtualmin/virtualmin-install/blob/master/README.md#p...
Doing a GPL install to test things out and it fails.
In looking into it I output the file it's looking for and got:
Yet virtualmin-release-latest.noarch.rpm does not exist, so I think it's downloading that page and sayings it's all good.
For http://software.virtualmin.com/vm/6/gpl/centos/7/x86_64/virtualmin-relea...
After I changed the file to "virtualmin-release-6.0-2.centos.noarch.rpm" (line 550 & 549): I got more errors. This may have been because I reran on the same system that just failed.
Upon outputting and executing the command from "$install yum-utils" (line 696), echo $? outputs 0? Not sure where it gets 1 from.
So a bit minor. For your readme, wget statement misses output file:
Probably meant or just to omit it?
Hey, thanks for the heads up. Looks like a missed some bits when setting up the GPL repo. Should be fixed.
Though, I'm surprised you didn't get an error when it wasn't found. My download function is still broken, it seems! Will work on that now.
Also, thanks for trying out VM6! I'm testing it as I get time, but across six distros and two architectures, it's gonna take days or weeks to get them all tried out. (And, I'm also still working on adding a reasonable default firewalld and fail2ban configuration to the default install, which I'm rolling out today or tomorrow.)
OK, I've also fixed the downloader so that it will actually error if it fails to download; for some wacky reason, curl defaults to always returning a success status code (0), unless you explicitly tell it that it's allowed to fail with the -f option. I've added that option to the virtualmin-install.sh download command detection, so it should fail and bail correctly now if something is wrong with the link it was told to download.
I'm rolling new Virtualmin-Config and new yum groups in the next couple of hours, and I'll try my tests with the GPL version; I've been testing with a Pro license against the Pro repos, so I've probably missed a variety of problems with the GPL repos.
Submitted by jackalyst on Sun, 06/11/2017 - 16:21 Pro Licensee Comment #5
Ah, yeah I was testing GPL even though I'll be running this with a license later.
I'm surprised about the number of systems that you want to support to be honest. cPanel only supports CentOS systems. Here you have CentOS/RHEL, Debian/Ubuntu, both architectures... current and previous LTS. With a much much smaller team.
Installation went much more smoothly:
/usr/sbin/setenforce: SELinux is disabled[2017-06-11 17:59:32 UTC] [WARNING] setenforce 0 failed: 1
which: no dnf in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/.local/bin:/root/bin)
Updating yum Groups [ ✔ ]
Downloading virtualmin-release-latest.noarch.rpm [ ✔ ]
Installing virtualmin-release package [ ✔ ]
Downloading epel-release-latest-7.noarch.rpm [ ✔ ]
Installing EPEL release package [ ✔ ]
error: /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-*: import read failed(2).
Installing yum-utils [ ✔ ]
Enabling extras repository [ ✔ ]
Installing scl-utils [ ✔ ]
Install Software Collections release package [ ✔ ]
Installing PHP7 [ ✔ ]
Marking 'Virtualmin LAMP Stack' for install [ ✔ ]
Marking 'Virtualmin Core' for install [ ✔ ]
Installing dependencies and system packages [ ✔ ]
Installing Virtualmin and all related packages [2017-06-11 18:03:26 UTC] [ERROR] Failed with error: 1
....
Which seems to be related to
Error: Package: virtualmin-config-6.0.0-4.el7.centos.noarch (virtualmin-universal)Requires: perl(Term::Spinner::Color)
Executed from
yum groupinstall --setopt=group_package_types=mandatory,default 'Virtualmin Core'Really looking forward to Virtualmin 6!
Just as an aside. I know you support so many systems, but is there one you prefer to test on? Right now I'm assuming you like using Debian systems?
Edit: Same thing using my license key (not completely fresh. I'll do a fresh install non-GPL here).
Edit 2: Completed for non-GPL. I think it's pretty much that one file that's in the repo now. There was something about freshclam, but wanted to let you know that non-GPL works.
Submitted by andreychek on Sun, 06/11/2017 - 17:19 Comment #6
Thanks for the input, I'll make sure Joe knows about that issue.
All the Grade A supported distros should work super-well, though Joe and Jamie prefer CentOS and use that on their own personal systems and on the virtualmin.com server. I personally prefer Ubuntu :-)
We try to ensure that they all get a good bit of testing though.
Good bug! I didn't spot that missing package because I already had perl-Term-Spinner installed from the previous successful Pro install test! Will be fixed shortly.
And, yeah, I prefer CentOS. But, we have enough demand for Ubuntu to make it worth supporting...Debian falls out almost automatically from Ubuntu support. So, that's how we do. I do fight pretty hard against supporting new distros, though. We've have some folks asking for Devuan support (which is Debian 8 minus systemd). So far, I'm pushing it out to the future, as it just seems like a lot of work for a small number of users. Also, several of the new features in Virtualmin 6 (and some that'll be added during the VM6 release cycle) will require systemd, I think. I don't think firewalld runs on a system without D-bus, and I don't think you can get D-bus without systemd (but I might be wrong about that; it's an open standard, but I don't think anyone has stepped up to build D-bus without systemd).
Any of the latest versions of our grade A systems you want to test on is useful. I know the older versions are broken for now (the repos aren't complete), but I kinda expect the latest version of CentOS, Debian, and Ubuntu LTS to all mostly work, and so any problems that shake out in testing are useful and will tell me something I don't know. And, the new versions are the only ones that get the new features, like the default firewall.
So...there's more surface area for the new distros, too. We're gonna punt on those old pre-systemd distros and not try to make up for missing packages with an alternative that requires a whole separate pile of code (and that'll be obsolete in a year or two). Anyway, old distros are less interesting. They'll get tested once all the new features are working and installable reliably on the new ones. But, since they won't get the new features, there's a lot less that can go wrong.