Virtualmin 6 beta available for testing

114 posts / 0 new
Last post
#1 Sat, 06/24/2017 - 00:26
Joe
Joe's picture

Virtualmin 6 beta available for testing

Howdy all,

I've been banging on the installer and the new virtualmin config-system command, along with some other bits and pieces for the Virtualmin 6 installation process, and I think it's ready to be called beta. It is, I believe, feature complete now, though some of those features might not work right off the bat.

Changes since the alpha release a week or whatever ago:

  • Firewalld is now enabled on systems that support it (e.g. any system with systemd). It falls back to iptables for older non-systemd systems (I think firewalld needs d-bus, and there is no implementation of d-bus without systemd, as far as a I know, so firewalld only works on systemd systems). The iptables fall-back is completely untested. I'm testing on new distros first because those should be what 95%+ of users are installing (you should only install an older system if you're recovering from a disaster and want to come back up on the same distro and version), and it doesn't actually do much at the moment. The firewalld setup includes a basic firewall with all of the necessary ports for virtual hosting, and everything else blocked.
  • Fail2ban is now enabled and configured with a sensible set of defaults for a Virtualmin system. This includes watching the Webmin log, sshd, some mail related logs, and responding appropriately with firewalld rules (or iptables rules). Again, untested on older distros at this time.

Debian 9 support is underway but isn't in this release...but, will likely follow in a day or two. Edit: Debian 9 should be mostly functional. Problem reports welcome.

As always, don't run the installer on a production Virtualmin system. This isn't an upgrade tool; if you've got a Virtualmin system and you're staying on top of updates, you're already running a version of Virtualmin and Webmin that has most of these features available (they just aren't setup by default), as we have rolled Webmin 1.844 and Virtualmin 5.99 (the beta of 6.0) out to all repos including the current repos. Once Virtualmin 6 goes gold and I'm confident it's working correctly, I'll roll the virtualmin config-system command out for the old repos, so you can configure the new features in a mostly automatic, and mostly safe, way.

Problems should be expected; so don't use this new installer if you have to have a Virtualmin server in production in 20 minutes. We support a ridiculous array of distributions and they can be installed in a huge variety of configurations, and my ability to test them all is highly limited by time. So. I welcome feedback. If you try it and it breaks, file a ticket, or just chime in here on this thread.

Also, I'm now welcoming reports about old versions of our supported distros (CentOS 6, Debian 7, and Ubuntu 14.04), so if you want to try it on those, I welcome feedback...but, expect more troubles. I haven't even tried them yet, though I've written code that should accommodate them now (it automatically should use iptables instead of firewalld, and also deal gracefully with not having systemd).

Finally, I bet 32 bit distros are missing packages, so it's probably not worth trying on those yet, until I have time to go through and insure all packages are in the 32 bit repos.

Let me know what breaks!

Here's the link to the current beta Virtualmin 6 install script: http://software.virtualmin.com/gpl/scripts/vm6-install.sh

Here's some github links for the various components of the installer if you find yourself wanting to work on new stuff:

These are the tools the shell script uses to actually perform the installation and configuration. vm6-install.sh sets up package repositories, installs the yum groups or the metapackages, and then uses Virtualmin-Config to perform the initial configuration steps, like turning on services, making service configuration changes, etc.

Virtualmin-Config: a post-modern post-installation configuration tool

virtualmin-yum-groups: Package groups for CentOS and Fedora

virtualmin-lamp-stack-deb: Metapackage for the LAMP stack on Debian

virtualmin-lamp-stack-ubu: Metapackage for the LAMP stack on Ubuntu

virtualmin-core-deb: Metapackage for the Virtualmin core packages on Debian and Ubuntu

Cheers,

Joe

Sat, 06/24/2017 - 20:23
Diabolico
Diabolico's picture

What will happen in situations like mine where all Centos 7 are using iptables instead of filewalld?
What will happen with new installations on Centos 7 if i dont want to use firewalld?

- I often come to the conclusion that my brain has too many tabs open. -
Failing at desktop publishing & graphic design since 1994.

Sun, 06/25/2017 - 05:01 (Reply to #2)
Joe
Joe's picture

The installation still wants to run on a freshly installed OS; which, if it's CentOS 7, is gonna have firewalld after install (unless you do a minimal install of the OS).

But, nothing else would change...you'd just configure it to not start firewalld and start iptables instead and remove the fail2ban-firewalld package, if you want to use fail2ban with iptables. So, you'd do the same things you'd do without Virtualmin on the system, but you'd do it after Virtualmin is installed. You could use the virtualmin config-system --include firewall command to setup the iptables firewall once you've disabled firewalld and turned it off.

The other option would be a semi-automated install, which is a (mostly untested and undocumented) feature of the new installer. You can pick and choose what bits of the install process you want to use.

We're not forcing you to use any feature. But, a firewall was a very frequently requested feature, so we did a bunch fo research, testing, etc. and settled on firewalld as the best compromise of features, compatibility across our supported distros, existing Webmin support, popularity, etc. But, we don't care what firewall you use. The Webmin module for iptables will stick around indefinitely (until a few years after nftables comes along and replaces it in common usage).

--

Check out the forum guidelines!

Sun, 06/25/2017 - 15:04 (Reply to #3)
Diabolico
Diabolico's picture

Bollocks. If you are not forcing anything then why we have to deal with unwanted software and only after Virtualmin installation we can remove/disable to install something else? Why not leaving both to be set after Virtualmin installation? The only one who is using firewalld are (mostly) people new to server management. I rarely see any "old school" person switching from iptables to firewalld.

Can we have this option to be set AFTER Virtualmin installation?

- I often come to the conclusion that my brain has too many tabs open. -
Failing at desktop publishing & graphic design since 1994.

Sun, 06/25/2017 - 19:02 (Reply to #4)
Joe
Joe's picture

Bollocks right back at ya.

Here's another thing I said in that same comment:

"The other option would be a semi-automated install, which is a (mostly untested and undocumented) feature of the new installer. You can pick and choose what bits of the install process you want to use."

The new installer is flexible as hell. I just haven't finished documenting it or making it easy to use. You can pick and choose any options you want; as I mentioned, there's a command for making changes to iptables firewalls, too.

The default is a firewalld firewall for all the reasons I mentioned. You can pick and choose anything else you want. If you can find something more flexible than Virtualmin on this front, I'll eat my hat (I don't have a hat...I'll eat a figurative hat).

--

Check out the forum guidelines!

Sun, 06/25/2017 - 05:06 (Reply to #6)
Joe
Joe's picture

If firewalld is available, that's what the installer sets up. We're not really making a recommendation; you can use whatever you like. But, the default will be to install firewalld, configure it to be mostly closed by default, and to open up the ports Virtualmin and the services it manages need. It's in there because people wanted a firewall. Firewalld was a good balance of features, ease of use (kinda), good Webmin support (again, kinda, but we're improving it for VM6), good support in fail2ban, and it has the bonus of being kinda future-proof, as the filter backend can evolve to suit whatever kernel it runs on.

Fail2ban is orthogonal to the firewall. It gets setup regardless of whether your system has iptables or firewalld. Fail2ban isn't a firewall, it's a log analysis tool that adds firewall rules (or performs other actions) based on log activity. It can work with firewalld or iptables.

--

Check out the forum guidelines!

Sun, 06/25/2017 - 19:00
cruiskeen

It's not clear to me where you want reports of problems - I never could get the alpha installer to work. I now cannot get the beta installer to work - a stock centos 7 system does this:

sh ./vm6-install.sh

  Welcome to the Virtualmin GPL installer, version 6.0.1

  The installation is quite stable and functional when run on a freshly
  installed supported Operating System. We strongly recommend you use
  the latest supported version of your preferred distribution.

  Please read the Virtualmin Installation Guide before proceeding if
  your system is not a freshly installed and supported OS.

  This script does not update or upgrade Virtualmin! It should only be
  used to perform your initial Virtualmin installation. Updates and
  upgrades can be performed from within Virtualmin or via the system
  package manager. License changes can be performed with the
  "virtualmin change-license" command.

  The systems currently supported by install.sh are:

    CentOS/RHEL Linux 6 and 7 on x86_64
    Debian 7 and 8 on i386 and amd64
    Ubuntu 14.04 LTS and 16.04 LTS, on i386 and amd64

  If your OS/version is not listed above, this script will fail. More
  details about the systems supported by the script can be found here:

  http://www.virtualmin.com/os-support

Continue? (y/n) y
[2017-06-25 18:44:14 CDT] [INFO] Started installation log in /root/virtualmin-install.log
which: no dnf in (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/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-25 18:54:12 CDT] [ERROR] Failed with error: 1
[  ✘  ]

[2017-06-25 18:54:12 CDT] [ERROR] Fatal Error Occurred: Installation failed: 0
Cannot continue installation.
Removing virtualmin-release                                             [  ✔  ]
[2017-06-25 18:54:13 CDT] [ERROR] Removing temporary directory and files.
[2017-06-25 18:54:13 CDT] [ERROR] If you are unsure of what went wrong, you may wish to review the log
[2017-06-25 18:54:13 CDT] [ERROR] in /root/virtualmin-install.log
./slib.sh: line 15: kill:  19651 19797 19822 19874 19893 19914 20023 20041 20092 20162 20372 20417 20462 21146 21196: arguments must be process or job IDs
Sun, 06/25/2017 - 19:05 (Reply to #8)
Joe
Joe's picture

This works for reporting problems. Ticket tracker works too.

Can you post the last few lines of /root/virtualmin-install.log? I'd like to know what packages are failing.

That's actually really close to success, and it's probably just a missing package. Is this a 32-bit or 64-bit system?

--

Check out the forum guidelines!

Sun, 06/25/2017 - 19:12 (Reply to #9)
cruiskeen

64 bit --- it's perl(Term::Spinner::Color) that's apparently missing:

Marking 'Virtualmin Core' for install: Success.
Spin pid is: 20462
Delta RPMs disabled because /usr/bin/applydeltarpm not installed.
warning: /var/cache/yum/x86_64/7/epel/packages/clamav-0.99.2-1.el7.x86_64.rpm: Header V3 RSA/SHA256 Signature, key ID 352c64e5: NOKEY
Public key for clamav-0.99.2-1.el7.x86_64.rpm is not installed
Importing GPG key 0x352C64E5:
Userid     : "Fedora EPEL (7) <epel@fedoraproject.org>"
Fingerprint: 91e9 7d7c 4a5e 96f1 7f3e 888f 6a2f aea2 352c 64e5
Package    : epel-release-7-9.noarch (installed)
From       : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
Installing dependencies and system packages: Success.
Spin pid is: 21146
Error: Package: virtualmin-config-6.0.0-4.el7.centos.noarch (virtualmin-universal)
           Requires: perl(Term::Spinner::Color)
You could try using --skip-broken to work around the problem
You could try running: rpm -Va --nofiles --nodigest
Installing Virtualmin and all related packages: [2017-06-25 18:54:12 CDT] [ERROR] Failed with error: 1
[2017-06-25 18:54:12 CDT] [ERROR] Fatal Error Occurred: Installation failed: 0
Spin pid is: 21196
warning: /etc/yum.repos.d/virtualmin.repo saved as /etc/yum.repos.d/virtualmin.repo.rpmsave
Removing virtualmin-release: Success.
[2017-06-25 18:54:13 CDT] [ERROR] Removing temporary directory and files.
[2017-06-25 18:54:13 CDT] [ERROR] If you are unsure of what went wrong, you may wish to review the log
[2017-06-25 18:54:13 CDT] [ERROR] in /root/virtualmin-install.log
Sun, 06/25/2017 - 20:01 (Reply to #10)
Joe
Joe's picture

Dang. I was sure I'd added that package! Should be fixed now for real. Thanks for the heads up!

--

Check out the forum guidelines!

Tue, 06/27/2017 - 16:22
cruiskeen

Soo --- something has happened to the posts about the new VIrtualmin 6 stuff - Joe's initial posts are all missing, and there are just comments - which makes it impossible to retrieve where the links are. Is this intentional to stop people from testing or ????

Wed, 06/28/2017 - 00:01 (Reply to #12)
Joe
Joe's picture

Not intentional at all. I have no idea what happened there. Two posts have been deleted. That's really strange.

The link is the same as the previous VM6 announcement: http://software.virtualmin.com/gpl/scripts/vm6-install.sh

I'm gonna look through the logs and see if I can figure out where the heck the original post went.

--

Check out the forum guidelines!

Wed, 06/28/2017 - 00:04 (Reply to #13)
Joe
Joe's picture

Weirdly, the content is still in the database, it just isn't displaying. I have no idea why.

I did a Drupal update a couple days ago...I wonder if it's somehow related.

--

Check out the forum guidelines!

Wed, 06/28/2017 - 00:37 (Reply to #14)
Joe
Joe's picture

Fixed! I have no idea why this changed, and I have no idea why only a handful of posts were effected. But, I found errors about the PHP option always_populate_raw_post_data in the logs, so I disabled that option, and now everything's back to normal.

Drupal is such a damned mystery sometimes.

--

Check out the forum guidelines!

Wed, 06/28/2017 - 10:45 (Reply to #15)
cruiskeen

Did you happen to upgrade to PHP 7 ? That was deprecated in 5.6 and removed in 7 -

Wed, 06/28/2017 - 09:30
cruiskeen

Tell me about it, since about 98% of my practice here is Drupal work. By the way, I DID successfully do an install with the script yesterday - there were a few nits. I'll post real issues about them when I get a chance. Mostly I was surprised that firewalld was not set up when finished so I could not access port 10000 . After I got that fixed things started working better.

Fri, 06/30/2017 - 01:33 (Reply to #17)
Joe
Joe's picture

Yep, I saw the firewalld bug in my own testing. For anyone else that runs into it, you can re-do the firewalld step manually after install with:

# virtualmin config-system --include Firewalld

That'll complain a bit about some existing rules (also fixed in the next version), but will set up firewalld correctly. It'll be fixed tomorrow when I have time to roll out a new version.

--

Check out the forum guidelines!

Thu, 06/29/2017 - 02:40
skelgaard

hey @Joe, any new ETA on the debian 9 intergration to the installer ?

Fri, 06/30/2017 - 01:34 (Reply to #19)
Joe
Joe's picture

I'd planned to wrap it up today, but we had a server crash which took most of my day (getting back online wasn't too long, but I also spent some time setting up a mirror and getting it working with the license server).

--

Check out the forum guidelines!

Fri, 06/30/2017 - 02:34 (Reply to #20)
skelgaard

server crash sucks, but glad to hear... i have a machines ready to test it ;) just waiting for you hehe :)

Fri, 06/30/2017 - 08:29
noisemarine

Just downloaded and ran the beta on a fresh Debian 8 x86_64 minimum install OpenVZ VPS. Installer ran smoothly except for the following.

Installer had this error. ntpdate failing is normal due to OpenVZ. I'm not sure if the other error is due to it or unrelated.

30 Jun 22:47:17 ntpdate[27371]: Can't adjust the time of day: Operation not permitted
Undefined subroutine &Virtualmin::Config::LAMP::has_command called at /usr/share/perl5/Virtualmin/Config/LAMP.pm line 18.

Post install in webmin:

Had to stop firewalld to be able to access webmin.

Selected "Run ClamAV server scanner? Yes". Got the following error. I continued the setup with "No".

A problem occurred testing the ClamAV server scanner :

ERROR: Could not lookup : Servname not supported for ai_socktype

----------- SCAN SUMMARY -----------
Infected files: 0
Time: 0.000 sec (0 m 0 s)

After specifying a mysql root password, I had an error of DBI_CONNECT failed, or some such. Returned to previous page and tried again successfully. Maybe a timing issue?

That's it. Hopefully that's the kind of things you were looking for. I'm looking forward to the Debian 9 installer. ;)

Edit: Also needed to "apt-get install libapache2-mod-fastcgi" to correct an error about PHP-FPM not configured in Re-Check Configuration.

Resolved: Upgraded to Webmin 1.850: Edit 2: Also seeing this on the System Information page: "system-status::list_system_info failed : Illegal division by zero at /usr/share/webmin/system-status/system_info.pl line 216. ".

Fri, 06/30/2017 - 15:35 (Reply to #22)
Joe
Joe's picture

ERROR: Could not lookup : Servname not supported for ai_socktype

Egads. I can't believe this is still an issue! We're waiting like 90 seconds for it to start at this point. I'm running out of ideas for fixing it. I haven't seen the error in my testing, since I increased the wait time, but I guess I need to increase it even more.

I believe it's actually working...but, the problem is that the clamd server takes a long time to start. It feels like years...but, it's really about a minute, or a minute and a half. We don't want to wait forever when testing it (because something could actually be wrong), but we also don't want to make it look like it's not working when it (probably) is. They add ~9000 hashes per day to the clamav virus database, so it's just taking a really long time to load. There's a new project where they're trying to reduce the size of the virus database, but it's likely months away from being a core part of ClamAV. So, we're stuck with this awful user experience.

I covered the firewalld problem in a comment above. It'll be fixed in the next roll out of the virtualmin-config package, and can be fixed immediately with the command I gave above.

Edit: Can you check to be sure you have an /etc/clamav/clamd.conf or /etc/clamd.conf file? And, let me know which one you have, if you do. That may also be an issue. ClamAV has horrible, broken-by-default, configuration on every distro (it's because the upstream clamav documentation recommends stupidly complicated configurations, on the assumption that people will be running multiple scanners for multiple purposes on a single machine...which is a thoroughly nonsensical assumption). So, we may not be tweaking it correctly on Debian.

--

Check out the forum guidelines!

Fri, 06/30/2017 - 21:21 (Reply to #23)
noisemarine

This system has /etc/clamav/clamd.conf. Understood on the ClamAV issues. I was seeing some issues in the Re-Check Configuration step that I tracked down as freshclam not connecting to the remote site. It resolved when I restarted clamav-freshclam. Maybe due to the initial firewalld issue?

Cool beans on the firewalld fix. Sorry, was late at night for me and the context of your post got lost amongst the discussion about missing posts. :)

Tue, 07/04/2017 - 16:01 (Reply to #24)
Joe
Joe's picture

The new version of virtualmin-config package should fix the firewalld issue (though it's untested on Debian).

I'll have to look into the clamav-freshclam issue. It shouldn't be firewalld related. Each task is mostly independent, and the local firewall shouldn't prevent freshclam from talking to the world.

I'll hopefully have the issues with my Debian 9 VM sorted out today and will be able to run some successful installs (or fix whatever's broke so they end up successful) and then get on to the task of seeing what goes wrong during postinstall wizard and checking configuration steps. (I know some of this is likely not Debian 9 specific, but I've been focused on getting the Debian 9 VM in good shape so we could roll it out for Cloudmin, and so I can get the Virtualmin install working, too. So, no time for testing on other distros in the past couple days.)

--

Check out the forum guidelines!

Sat, 07/01/2017 - 02:48
skelgaard

seems the debian 9 changes didn't make it into the file, as it is still not working... hope for it to come asap :)

Tue, 07/04/2017 - 00:56 (Reply to #26)
Joe
Joe's picture

Debian 9 might work now, but it's way untested. I've been fighting with my VM for Debian 9 (I had to make one from scratch, as we don't currently have any in the Cloudmin image repos, and I couldn't find a suitable KVM image in the wild). It's got a bunch of broken stuff, and I can't figure out which is the Virtualmin installer breaking or what's already broken in the image.

But, all the packages should be in the virtualmin-stretch repo, and the new virtualmin-lamp-stack package should have the right bits for Debian 9 (php7.0 and php, which is cool), and the vm6-install.sh knows about Debian 9. So, it might work fine, but I'd consider it alpha (while the other distros are probably beta-ish quality).

--

Check out the forum guidelines!

Mon, 07/03/2017 - 06:13
skelgaard

@Joe i can see you have updated the script, and mostly working... i can see it gives a few errors at the end, which i have no idea what means :)

[2017-07-03 12:53:39 CEST] [INFO] Started installation log in /root/virtualmin-install.log
[2017-07-03 12:53:39 CEST] [INFO] apt-get repos: virtualmin-stretch virtualmin-universal
Downloading Virtualmin repository metadata                              [  ✔  ]
Enabling universe repositories, if not already available                [  ✔  ]
Disabling cdrom: repositories                                           [  ✔  ]
Cleaning out old metadata                                               [  ✔  ]
Downloading apt.conf.noninteractive                                     [  ✔  ]
Downloading RPM-GPG-KEY-virtualmin-6                                    [  ✔  ]
Downloading RPM-GPG-KEY-webmin                                          [  ✔  ]
Installing Virtualmin 6 key                                             [  ✔  ]
Installing Webmin key                                                   [  ✔  ]
Removing non-standard Webmin package, if installed                      [  ✔  ]
Installing Webmin                                                       [  ✔  ]
Installing Usermin                                                      [  ✔  ]
Installing OS packages that Virtualmin needs                            [  ✔  ]
Installing Virtualmin and plugins                                       [  ✔  ]
3 Jul 13:06:41 ntpdate[14209]: adjust time server 217.198.219.102 offset -0.000575 sec
Configuring Apache                                                      [  ✔  ]
Configuring Bind                                                        [  ✔  ]
Configuring ClamAV                                                      ▒▒░░░░░ERROR: Could not lookup : Servname not supported for ai_socktype                                                  [  ✔  ]
Configuring Dovecot                                                     [  ✔  ]
Configuring Fail2ban                                                    [  ✔  ]
Configuring Firewall                                                    [  ✔  ]
Configuring MySQL                                                       [  ✔  ]
Configuring NTP                                                         [  ✔  ]
Configuring Net                                                         [  ✔  ]
Configuring Postfix                                                     [  ✔  ]
Configuring ProFTPd                                                     [  ✔  ]
Configuring Procmail                                                    [  ✔  ]
Configuring Quotas
The filesystem / could not be remounted with quotas enabled.
You may need to reboot your system, and enable quotas in the Disk
Quotas module.                                                          [  ✘  ]
Configuring SASL                                                        [  ✔  ]
Configuring Shells                                                      [  ✔  ]
Configuring SpamAssassin                                                [  ✔  ]
Configuring Status                                                      [  ✔  ]
Configuring Upgrade                                                     [  ✔  ]
Configuring Usermin                                                     [  ✔  ]
Configuring Webalizer                                                   [  ✔  ]
Configuring Webmin                                                      [  ✔  ]
Configuring AWStats                                                     [  ✔  ]
Configuring Virtualmin                                                  [  ✔  ]
Configuring Extra                                                       [  ✔  ]
Installing updates to Virtualmin-related packages                       [  ✔  ]

[2017-07-03 13:09:17 CEST] [SUCCESS] Installation Complete!
[2017-07-03 13:09:17 CEST] [SUCCESS] If there were no errors above, Virtualmin should be ready
[2017-07-03 13:09:17 CEST] [SUCCESS] to configure on port 10000.
vm6-install.sh: 15: kill: Illegal number: 17925  847 1354 1372 1390 1412 1435 1456 1474 1798 2149 2170 3277 3650 13114 17906
Mon, 07/03/2017 - 23:12 (Reply to #28)
Joe
Joe's picture

ClamAV has apparently gotten even slower since I wrote that module a few weeks ago. It's long past ridiculous. The ai_socktype error usually just means clamd failed to start during after a minute and a half of waiting. I probably need to just skip testing it, and do something else to make sure the service has started; it's already to the point where testing clamd takes as long as the entire rest of the install (on a fast network).

Quotas are expected to fail frequently on a CentOS 7 system, because you can't enable quotas on a boot or root XFS filesystem without a system reboot. After a reboot, quotas may turn on on their own, but some virtual machines need to have additional boot options added on the host machine (so, in some cases disk quotas can't be turned on at all).

In other words, that's almost certainly successful install! (The "kill: Illegal number" bit can be ignored; it'll go away in the next roll of install.sh.)

--

Check out the forum guidelines!

Tue, 07/04/2017 - 00:35
noisemarine

@Joe

Is it possible to change the order of things. Instead of install clamav and wait to see what happened, how about install clamav, go do other things, then check what happened later in the process?

Tue, 07/04/2017 - 15:55 (Reply to #30)
Joe
Joe's picture

Yes, that would be one solution; I don't currently do anything async in the installer (except the progress indicators, which spin while other stuff happens in the background), because usually if something goes wrong, we often can't continue successfully (and in fact, a few of the current bugs I know about are that we don't give up on the install in some cases where we should).

The more I think about it, though, the more I think clamd just shouldn't be started, even temporarily for testing, during the initial install. It can be disabled during a semi-automatic install, but it'd likely cause trouble on a small system with less than 768MB. So, it's probably worth just removing that test. We'll install the stuff, hope it's right, and let it get tested if/when the user turns it on during the postinstall wizard.

--

Check out the forum guidelines!

Tue, 07/04/2017 - 08:02
noisemarine

Is Webmin 1.850 available in the new repository? I'm getting the divide by zero error again on the System Information page with 1.842, and last time I got prompted to upgrade to 1.850 and that fixed it. Not getting prompted this time. Debian 9 install this time.

Tue, 07/04/2017 - 15:56 (Reply to #32)
Joe
Joe's picture

It's supposed to be, but my Webmin roll-up script might be missing some of the new repos. I'll check.

Edit: Fixed now. And the roll-up script has been corrected to include the new vm6 repos.

--

Check out the forum guidelines!

Tue, 07/04/2017 - 18:14
skelgaard
cat /var/log/firewalld

2017-07-05 00:52:15 WARNING: '/sbin/iptables-restore -n' failed: 2017-07-05 00:52:15 ERROR: COMMAND_FAILED

I can't access the webserver og webmin/usermin from external, works fine with lynx on localhost so i think its something with the firewalld as that is new...

if i then run /etc/init.d/firewalld stop i can get to them

Tue, 07/04/2017 - 19:12
noisemarine

1.850 fixed my issue.

On Debian 9 minimal install, the only installation error I had was about $clocksource and I suspect that is because I'm on an OpenVZ VPS. Oh, and shutting off firewalld as above. Everything went smoothly, even ClamAV. :)

Nice job, Joe. ;)

@skelgaard I had that, too. I disabled and removed firewalld. I'm sticking with iptables for now as I have my own standard script I use to set things up. The Webmin->Networking->Linux Firewall module seems to handle things OK. I'll revisit firewalld a bit further down the track.

Thu, 07/06/2017 - 05:47 (Reply to #35)
Joe
Joe's picture

If you see the $clocksource error again, could you post the exact message? I don't have any OpenVZ systems here to test on. I see a couple of places in the code where it could go wrong, but I'm not sure how to deal with it without more detail.

Is there a "/sys/devices/system/clocksource/clocksource0/current_clocksource" file in your VZ container? If so, what's in it?

--

Check out the forum guidelines!

Thu, 07/06/2017 - 04:38
Ned

My DHCP Server can't start. When i try to start it, i get this Error:

Starting isc-dhcp-server (via systemctl): isc-dhcp-server.serviceJob for isc-dhcp-server.service failed because the control process exited with error code. See "systemctl status isc-dhcp-server.service" and "journalctl -xe" for details. failed!

I am configuring new Debian 9 web server with virtualmin and i have problem. Nothing works how it should be.

I can't make my websites to be visible on Internet. Sad.

I have Debian 8 with virtualmin and all is working fine.

This Debian 9!!!

Thu, 07/06/2017 - 05:52 (Reply to #37)
Joe
Joe's picture

We don't touch DHCP, so that one is probably entirely unrelated to Virtualmin or the installer.

There may be something going on with the "can't make websites visible" problem, but we'd need more detail to sort out what.

--

Check out the forum guidelines!

Thu, 07/06/2017 - 04:40
skelgaard

have you checked "systemctl status isc-dhcp-server.service" to see what the error is... you proberly have both ipv4 and ipv6 interfaces and not defined for all. Your config is 99% at fault, not virtualmin

Thu, 07/06/2017 - 09:11 (Reply to #39)
Ned

Yes, my config is 99% at fault, not virtualmin!

Cheers!

Thu, 07/06/2017 - 09:08
Ned

This is the result after installing Virtualmin 6 beta:

[2017-07-06 17:04:06 EEST] [INFO] Started installation log in /root/virtualmin-install.log
[2017-07-06 17:04:06 EEST] [INFO] apt-get repos: virtualmin-stretch virtualmin-universal
Downloading Virtualmin repository metadata                              [  ✔  ]
Enabling universe repositories, if not already available                [  ✔  ]
Disabling cdrom: repositories                                           [  ✔  ]
Cleaning out old metadata                                               [  ✔  ]
Downloading apt.conf.noninteractive                                     [  ✔  ]
Downloading RPM-GPG-KEY-virtualmin-6                                    [  ✔  ]
Downloading RPM-GPG-KEY-webmin                                          [  ✔  ]
Installing Virtualmin 6 key                                             [  ✔  ]
Installing Webmin key                                                   [  ✔  ]
Removing non-standard Webmin package, if installed                      [  ✔  ]
Installing Webmin                                                       [  ✔  ]
Installing Usermin                                                      [  ✔  ]
Installing OS packages that Virtualmin needs                            [  ✔  ]
Installing Virtualmin and plugins                                       [  ✔  ]
6 Jul 17:04:35 ntpdate[3384]: no server suitable for synchronization found
Configuring Apache                                                      [  ✔  ]
Configuring Bind                                                        [  ✔  ]
Configuring ClamAV                                                      [  ✔  ]
Configuring Dovecot                                                     [  ✔  ]
Configuring Fail2ban                                                    [  ✘  ]
Configuring Firewall                                                    [  ✔  ]
Configuring MySQL                                                       [  ✔  ]
Configuring NTP                                                         ░░░░░░▒ 6 Jul 17:05:26 ntpdate[4344]: no server suitable for synchronization found
[  ✔  ]
Configuring Net                                                         [  ✔  ]
Configuring Postfix                                                     ░░░░▒▒▒Failed to start Postfix!
[  ✔  ]
Configuring ProFTPd                                                     [  ✔  ]
Configuring Procmail                                                    [  ✔  ]
Configuring Quotas                                                            
The filesystem / could not be remounted with quotas enabled.
You may need to reboot your system, and enable quotas in the Disk
Quotas module.                                                          [  ✘  ]
Configuring SASL                                                        [  ✔  ]
Configuring Shells                                                      [  ✔  ]
Configuring SpamAssassin                                                [  ✔  ]
Configuring Status                                                      [  ✔  ]
Configuring Upgrade                                                     [  ✔  ]
Configuring Usermin                                                     [  ✔  ]
Configuring Webalizer                                                   [  ✔  ]
Configuring Webmin                                                      [  ✔  ]
Configuring AWStats                                                     [  ✔  ]
Configuring Virtualmin                                                  [  ✔  ]
Configuring Extra                                                       [  ✔  ]
Installing updates to Virtualmin-related packages                       [  ✔  ]

[2017-07-06 17:06:08 EEST] [SUCCESS] Installation Complete!
[2017-07-06 17:06:08 EEST] [SUCCESS] If there were no errors above, Virtualmin should be ready
[2017-07-06 17:06:08 EEST] [SUCCESS] to configure on port 10000.
./vm6-install.sh: 15: kill: Illegal number:  6638  1789 2547 2565 2583 2610 2646 2680 2711 2938 3164 3257 3289 3321 3353 6607
Thu, 07/06/2017 - 15:56 (Reply to #41)
Joe
Joe's picture

What distro and version are you installing on? There are interesting problems there I'd like to sort out. Postfix failing to start is a weird one that I haven't seen in any testing, so far.

--

Check out the forum guidelines!

Fri, 07/07/2017 - 08:44 (Reply to #42)
Ned

Debian 9 64Bit.

Fri, 07/07/2017 - 10:02 (Reply to #43)
nfz300zx

I'm also getting this on a basic Debian 9 install. Do we have a fix or ETA on when Debian 9 is fully supported? im looking to rebuild my server and am holding out for this.

Fri, 07/07/2017 - 10:05 (Reply to #44)
noisemarine

If more people would provide useful feedback, it would go more quickly. Why not delve in your virtualmin_install.log, or post the exact error you get?

Fri, 07/07/2017 - 10:18 (Reply to #45)
nfz300zx

Funny enough, I am just doing that now. Had to rebuild my machine again from scratch to reproduce it again.

Fri, 07/07/2017 - 11:36 (Reply to #46)
nfz300zx

OK, screen shot of the error : https://chimera-labs.com/misc/debian-error.png

And the install log is below:

etting up webmin-virtual-server (5.99.gpl) ...
virtual-server
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up libemail-date-format-perl (1.005-1) ...
Setting up libipc-shareable-perl (0.61-1) ...
Setting up webmin-virtualmin-awstats (5.1) ...
virtualmin-awstats
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up webmin-ruby-gems (1.4) ...
ruby-gems
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up webmin-virtualmin-registrar (2.4) ...
virtualmin-registrar
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up webmin-virtualmin-init (2.5) ...
virtualmin-init
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up libmime-lite-perl (3.030-2) ...
Setting up libmime-types-perl (2.13-1) ...
Setting up webmin-php-pear (1.5) ...
php-pear
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up libmail-sendmail-perl (0.79.16-2) ...
Setting up webmin-virtualmin-dav (3.8) ...
virtualmin-dav
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up libdevel-globaldestruction-perl (0.14-1) ...
Setting up webmin-virtualmin-slavedns (1.8) ...
virtualmin-slavedns
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up webmin-virtualmin-htpasswd (2.6) ...
virtualmin-htpasswd
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Processing triggers for man-db (2.7.6.1-2) ...
Setting up libparams-classify-perl (0.013-6+b1) ...
Setting up webmin-jailkit (0.1) ...
jailkit
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up libterm-spinner-color-perl (0.02-1) ...
Setting up webmin-virtualmin-git (1.7) ...
virtualmin-git
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up webmin-virtualmin-sqlite (1.5) ...
virtualmin-sqlite
Can't locate WebminCore.pm in @INC (you may need to install the WebminCore module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.24.1 /usr/local/share/perl/5.24.1 /usr/lib/x86_64-linux-gnu/perl5/5.24 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.24 /usr/share/perl/5.24 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at /usr/share/webmin/run-postinstalls.pl line 6.
BEGIN failed--compilation aborted at /usr/share/webmin/run-postinstalls.pl line 6.
Setting up libmodule-runtime-perl (0.014-2) ...
Setting up virtualmin-config (6.0.6-1) ...
Setting up libdist-checkconflicts-perl (0.11-1) ...
Setting up libmodule-implementation-perl (0.09-1) ...
Setting up libparams-validate-perl (1.26-1) ...
Setting up virtualmin-core (6.0.1) ...
Setting up liblog-dispatch-perl (2.58-1) ...
W: --force-yes is deprecated, use one of the options starting with --allow instead.
W: --force-yes is deprecated, use one of the options starting with --allow instead.
Made it here...why?
Installing Virtualmin and plugins: Success.
[2017/07/07 17:25:47] [INFO] - Starting init-system log...
[2017/07/07 17:25:49] [INFO] - Configuring Apache
[2017/07/07 17:25:49] [INFO] - Code: 0 Result: Enabling module cgi.
To activate the new configuration, you need to run:
  systemctl restart apache2
[2017/07/07 17:25:49] [INFO] - Code: 0 Result: Enabling module suexec.
To activate the new configuration, you need to run:
  systemctl restart apache2
[2017/07/07 17:25:49] [INFO] - Code: 0 Result: Enabling module actions.
To activate the new configuration, you need to run:
  systemctl restart apache2
[2017/07/07 17:25:49] [INFO] - Code: 0 Result: Module fcgid already enabled
[2017/07/07 17:25:49] [INFO] - Code: 0 Result: Considering dependency setenvif for ssl:
Module setenvif already enabled
Considering dependency mime for ssl:
Module mime already enabled
Considering dependency socache_shmcb for ssl:
Enabling module socache_shmcb.
Enabling module ssl.
See /usr/share/doc/apache2/README.Debian.gz on how to configure SSL and create self-signed certificates.
To activate the new configuration, you need to run:
  systemctl restart apache2
[2017/07/07 17:25:49] [INFO] - Code: 0 Result: Enabling module dav.
To activate the new configuration, you need to run:
  systemctl restart apache2
[2017/07/07 17:25:49] [INFO] - Code: 0 Result: Considering dependency proxy_balancer for lbmethod_byrequests:
Considering dependency proxy for proxy_balancer:
Enabling module proxy.
Considering dependency alias for proxy_balancer:
Module alias already enabled
Considering dependency slotmem_shm for proxy_balancer:
Enabling module slotmem_shm.
Enabling module proxy_balancer.
Enabling module lbmethod_byrequests.
To activate the new configuration, you need to run:
  systemctl restart apache2
[2017/07/07 17:25:49] [INFO] - Code: 0 Result: Site 000-default disabled.
To activate the new configuration, you need to run:
  systemctl reload apache2
[2017/07/07 17:25:49] [INFO] - Code: 0 Result: Considering dependency setenvif for ssl:
Module setenvif already enabled
Considering dependency mime for ssl:
Module mime already enabled
Considering dependency socache_shmcb for ssl:
Module socache_shmcb already enabled
Module ssl already enabled
[2017/07/07 17:25:50] [INFO] - Succeeded
[2017/07/07 17:25:50] [INFO] - Configuring Bind
[2017/07/07 17:25:50] [INFO] - Succeeded
[2017/07/07 17:25:50] [INFO] - Configuring ClamAV
[2017/07/07 17:26:23] [INFO] - Code: 0 Result:
[2017/07/07 17:26:26] [INFO] - Succeeded
[2017/07/07 17:26:26] [INFO] - Configuring Dovecot
[2017/07/07 17:26:27] [INFO] - Succeeded
[2017/07/07 17:26:27] [INFO] - Configuring Fail2ban
[2017/07/07 17:26:32] [INFO] - Succeeded
[2017/07/07 17:26:32] [INFO] - Configuring Firewall
[2017/07/07 17:26:32] [INFO] - Succeeded
[2017/07/07 17:26:32] [INFO] - Configuring MySQL
[2017/07/07 17:26:40] [INFO] - Succeeded
[2017/07/07 17:26:40] [INFO] - Configuring NTP
[2017/07/07 17:26:50] [INFO] - Code: 0 Result:  7 Jul 17:26:50 ntpdate[44420]: adjust time server 85.199.214.101 offset -0.001655 sec
[2017/07/07 17:26:50] [INFO] - Succeeded
[2017/07/07 17:26:50] [INFO] - Configuring Net
[2017/07/07 17:26:52] [INFO] - Succeeded
[2017/07/07 17:26:52] [INFO] - Configuring Postfix
[2017/07/07 17:26:59] [INFO] - Succeeded
[2017/07/07 17:26:59] [INFO] - Configuring ProFTPd
[2017/07/07 17:27:03] [INFO] - Succeeded
[2017/07/07 17:27:03] [INFO] - Configuring Procmail
[2017/07/07 17:27:03] [INFO] - Succeeded
[2017/07/07 17:27:03] [INFO] - Configuring Quotas
[2017/07/07 17:27:03] [INFO] - Succeeded
[2017/07/07 17:27:03] [INFO] - Configuring SASL
[2017/07/07 17:27:04] [INFO] - Code: 0 Result:
[2017/07/07 17:27:04] [INFO] - Code: 0 Result: Adding user `postfix' to group `sasl' ...
Adding user postfix to group sasl
Done.
[2017/07/07 17:27:04] [INFO] - Code: 0 Result:
[2017/07/07 17:27:05] [INFO] - Succeeded
[2017/07/07 17:27:05] [INFO] - Configuring Shells
[2017/07/07 17:27:05] [INFO] - Succeeded
[2017/07/07 17:27:05] [INFO] - Configuring SpamAssassin
[2017/07/07 17:27:06] [INFO] - Succeeded
[2017/07/07 17:27:06] [INFO] - Configuring Status
[2017/07/07 17:27:07] [INFO] - Succeeded
[2017/07/07 17:27:07] [INFO] - Configuring Upgrade
[2017/07/07 17:27:07] [INFO] - Succeeded
[2017/07/07 17:27:07] [INFO] - Configuring Usermin
[2017/07/07 17:27:11] [INFO] - Succeeded
[2017/07/07 17:27:12] [INFO] - Configuring Webalizer
[2017/07/07 17:27:14] [INFO] - Succeeded
[2017/07/07 17:27:14] [INFO] - Configuring Webmin
[2017/07/07 17:27:31] [INFO] - Succeeded
[2017/07/07 17:27:31] [INFO] - Configuring AWStats
[2017/07/07 17:27:32] [INFO] - Succeeded
[2017/07/07 17:27:32] [INFO] - Configuring Virtualmin
[2017/07/07 17:27:32] [INFO] - Succeeded
[2017/07/07 17:27:32] [INFO] - Configuring Extra
[2017/07/07 17:27:32] [INFO] - Succeeded
Spin pid is: 46386
Reading package lists...
Building dependency tree...
Reading state information...
postfix is already the newest version (3.1.4-7).
virtualmin-lamp-stack is already the newest version (6.0.1+deb-9).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Installing updates to Virtualmin-related packages: Success.
[2017-07-07 17:27:34 BST] [SUCCESS] Installation Complete!
[2017-07-07 17:27:34 BST] [SUCCESS] If there were no errors above, Virtualmin should be ready
[2017-07-07 17:27:34 BST] [SUCCESS] to configure on port 10000.
Wed, 07/12/2017 - 15:40 (Reply to #47)
Joe
Joe's picture

That looks mostly fine. There's a quota error, which is really common on virtual machines, as we often can't actually start quotas without changes to the boot options (either inside or outside of the VM) and a reboot of the VM.

And, there's a kill error because of a bug in the process cleanup at the end, but that's harmless. And, I see a bug in our Webmin module packages (all of them), but it's also harmless, I think, as most of them do not have postinstall scripts that need to run. But, I'll see about getting that fixed.

--

Check out the forum guidelines!

Fri, 07/07/2017 - 14:35
Pathways

Installation using vm6-install.sh on Debian 9 went smoothly. The System Information page reports Virtualmin 5.99 rather than 6.

Sat, 07/08/2017 - 02:37 (Reply to #49)
Joe
Joe's picture

That's correct. We'll bump rev to 6.0 when the beta is over. 5.99 is feature complete for 6 but needs testing.

--

Check out the forum guidelines!

Sun, 07/09/2017 - 05:08
cinterpro
cinterpro's picture

Hi Joe. Please see the result f mine (fesh) install on debian 9
used this to install: wget -O install.sh https://raw.githubusercontent.com/virtualmin/virtualmin-install/master/virtualmin-install.sh

<br>[2017-07-09 11:52:50 CEST] [INFO] Started installation log in /root/virtualmin-install.log
hostname: Name or service not known
[2017-07-09 11:52:50 CEST] [WARNING] Hostname  is not fully qualified.
Please enter a fully qualified hostname (for example, host.example.com): host.webinterno.es
Error: either "dev" is duplicate, or "ro" is a garbage.
awk: 1: unexpected character '`'
[2017-07-09 11:53:03 CEST] [WARNING] Unable to determine IP address of primary interface.
Please enter the name of your primary network interface:
enp2s0
./install.sh: 469: ./install.sh: log_debugPrimary address detected as 192.168.1.22: not found
[2017-07-09 11:53:11 CEST] [INFO] apt-get repos: virtualmin-stretch virtualmin-universal
Downloading Virtualmin repository metadata                              [  ✔  ]
Enabling universe repositories, if not already available                [  ✔  ]
Disabling cdrom: repositories                                           [  ✔  ]
Cleaning out old metadata                                               [  ✔  ]
Downloading apt.conf.noninteractive                                     [  ✔  ]
Downloading RPM-GPG-KEY-virtualmin-6                                    [  ✔  ]
Downloading RPM-GPG-KEY-webmin                                          [  ✔  ]
Installing Virtualmin 6 key                                             [  ✔  ]
Installing Webmin key                                                   [  ✔  ]
Removing non-standard Webmin package, if installed                      [  ✔  ]
Installing Webmin                                                       [  ✔  ]
Installing Usermin                                                      [  ✔  ]
Installing OS packages that Virtualmin needs                            [  ✔  ]
Installing Virtualmin and plugins                                       [  ✔  ]
9 Jul 11:57:48 ntpdate[5551]: adjust time server 192.33.96.102 offset -0.002803 sec
Configuring Apache                                                      [  ✔  ]
Configuring Bind                                                        [  ✔  ]
Configuring ClamAV                                                      ▒▒▒▒▒▒▒ERROR: Could not lookup : Servname not supported for ai_socktype                                                                                       [  ✔  ]
Configuring Dovecot                                                     [  ✔  ]
Configuring Fail2ban                                                    [  ✔  ]
Configuring Firewall                                                    [  ✔  ]
Configuring MySQL                                                       [  ✔  ]
Configuring NTP                                                         [  ✔  ]
Configuring Net                                                         [  ✔  ]
Configuring Postfix                                                     [  ✔  ]
Configuring ProFTPd                                                     [  ✔  ]
Configuring Procmail                                                    [  ✔  ]
Configuring Quotas
The filesystem / could not be remounted with quotas enabled.
You may need to reboot your system, and enable quotas in the Disk
Quotas module.                                                          [  ✘  ]
Configuring SASL                                                        [  ✔  ]
Configuring Shells                                                      [  ✔  ]
Configuring SpamAssassin                                                [  ✔  ]
Configuring Status                                                      [  ✔  ]
Configuring Upgrade                                                     [  ✔  ]
Configuring Usermin                                                     [  ✔  ]
Configuring Webalizer                                                   [  ✔  ]
Configuring Webmin                                                      [  ✔  ]
Configuring AWStats                                                     [  ✔  ]
Configuring Virtualmin                                                  [  ✔  ]
Configuring Extra                                                       [  ✔  ]
Installing updates to Virtualmin-related packages                       [  ✔  ]

[2017-07-09 11:59:26 CEST] [SUCCESS] Installation Complete!
[2017-07-09 11:59:26 CEST] [SUCCESS] If there were no errors above, Virtualmin should be ready
[2017-07-09 11:59:26 CEST] [SUCCESS] to configure on port 10000.
./install.sh: 15: kill: Illegal number:  9019  2290 2670 2688 2706 2733 2768 2801 2831 3173 3542 3617 5471 5844 4464 9000


going to : https://192.168.1.22:10000 it doesnt start
Hope it helps.
regards,
Paco

Mon, 07/10/2017 - 16:12 (Reply to #51)
Joe
Joe's picture

So, I see two problems, and I'll get them sorted for the next release. There may be others.

First up is the address and network parsing and hostname setting code is broken. That one is tricky; the format we're working with has changed a couple of times across the distros/versions we support, so I'm gonna have to have multiple code paths, and I hate that in shell scripts, but it's gotta be done.

Next, for some reason it configured Firewall (iptables) instead of Firewalld. Which is wrong for Debian 9, where firewalld is available.

The latter problem is probably why you can't reach Webmin. Try running:

# virtualmin config-system --include Firewalld

See if that makes Webmin accessible. (Test ssh access after doing this before you end your current session, as I think someone else reported that one of the firewall config modules broke all of their access...which shouldn't happen, and I can't figure out how it could happen, but better safe than sorry if it's a remote system.)

--

Check out the forum guidelines!

Pages

Topic locked