Howdy all,
I've just rolled out the first install.sh (version 6.0.11) with support for Ubuntu 18.04 LTS. I've also created a new virtualmin-bionic repository with 18.04 LTS binary packages.
This should be considered a beta release. Please test your use case thoroughly before counting on it in production! We always expect issues to be found when new distributions are released, because things change in subtle ways. Versions of underlying software changes, paths may change, default options might change, etc. In my testing of the most common installation scenarios, it seems to work well, but Virtualmin has a gazillion options and manages a bazillion moving parts, so surely y'all will find something borked once you start using it.
Known issues:
If you run into any bugs, please let me know in the issue tracker.
Cheers,
Joe
Edit 7/10/2018: Updated to specifically mention the netplan issue, which is ongoing. So, still beta. Read the whole thread and links for more info on the status of that, if you want to install on 18.04 today. You must use the old network configuration scripts for now.
New known issue on Ubuntu 18.04:
Ubuntu's default network configuration system changed completely in 17.10 to something called netplan. I didn't notice because the test systems I spun up at a virtual machine provider I frequently use had been configured to use the old network configuration system.
Jamie is planning to implement support for netplan in Webmin in the coming weeks. But, and this is a big but: This is a whole new service with it's own configuration files, its own management tools, and its own way of doing things. It is not a minor juggling of config file locations or some new management tools stacked on top of the old thing. Thus, it's gonna take some real work to support it. I do not know how long; Jamie can't dig in until this weekend, so we won't even know the scope of the work until then. Jamie is wicked fast, but even he is human, so I think an optimistic estimate for supporting netplan is at least a couple of weeks and probably longer.
So...that means if you want to install Virtualmin on Ubuntu 18.04 today, you'll need to convert your system to using the old network configuration scripts. This isn't hugely complicated from what I've found, but I haven't tried it yet, so I dunno for sure. There have been several discussions about this change and how to revert it at Ask Ubuntu among other places. I'll find a provider that has Ubuntu instances that use the new configuration in the next day or two (or make my own new image for Cloudmin and spin it up on one of our servers), so I can try it out and document how to change it.
Anyway, I wanted to get this out, since I finally sorted out today that all of the disparate bug reports I've gotten were actually this same problem, even though the reports were about a bunch of different services. (Folks didn't notice that the installer bailed before it finished...fatal errors will exit the installer before completing the rest of the config...so you can't ignore a fatal installer error. The system isn't expected to be configured correctly after a fatal error during install.)
--
Check out the forum guidelines!
Thank you so much Joe, you folks are amazing awesome. I'll stick to 16.04 in the meantime.
Rinus
Inbox distro upgrades seem to also work. I had no issues with both my machines running Pro on 1 and the GPL version on the other.
Joseph Dobransky
FWIW, there are 2 versions of Ubuntu 18.04 server installer ISO. A new "live" version and an "alternate" old version. Unsure if the net config on each is different.
EDIT: just did 3 cloudmin KVM installs of 18.04. Using mini.iso, using live.iso, using alt.iso. All 3 default to netplan config in /etc/netplan/*.cfg. Only difference I saw in my quick install tests was the live.iso got an IPV6 automatically and didn't ask for or care if it had IPV4.
I'd be happy to let you test with these KVMs, or an empty system.
There isn't really anything to test until we've got netplan support in Webmin. The installer currently works (close to perfectly, as far as I can tell, though I'd still recommend testing a bit before putting into production) if the system is using the old method of configuring networks, and will not work if the system is using netplan.
So...we're waiting on Jamie to have enough spare time to implement some netplan support in Webmin, and then I'll make the installer aware of netplan. My part of it is small, and shouldn't take more than a day or so, but Jamie's part is big. It's probably not so awful, since at least it uses a well-known existing config file format (YAML), so Jamie doesn't have to write a new custom parser (though he's good as heck at doing that, it's still more work than just using a library), but he'll still need to munge the data into data structures the Webmin network module understands so it can be presented in the UI and be interacted with by other modules, like Virtualmin.
--
Check out the forum guidelines!
Just to note that the installer has curl set up as so:
/usr/bin/curl -f -s -L -Othis needs the
-kswitch to get it past the invalid certificate warning on the https://software.virtualmin.com/lib/slib.sh script.Otherwise, so far so good :)
Signature on it's way...
Hi all,
Is support for installing Ubuntu 18.04 LTS with install.sh imminent?
Trying to decide whether I should hold off for a few days or go with 16.4 now.... would hate to find out install.sh would have installed 18.04 if I had just waited another day or two :)
Chris
oh, FYI, it says on the install.sh script that 18.04 is supported... I'll assume this thread is more up to date and that's a leftover...
It's still beta and netplan is still unsupported. I changed the OS support list in the installer a little prematurely because I didn't know about the netplan issue (my test instances at our VPS did not use netplan, so everything Just Worked in my testing).
--
Check out the forum guidelines!
Yesteday I install Ubuntu 18.04 and latest Virtualmin. Installation was ok, but Network/DNS configuration can be done only manual. So we must wait for compliant Virtualmin version. Does anyone know date when it can be happen?
This is work in progress. See also
https://github.com/webmin/webmin/search?q=netplan&type=Commits
But progress seems to have stalled a bit.
Just a quick update on this:
Jamie is finishing up the new Webmin release with Netplan support as we speak, with expectation to roll it out within the next few hours (barring any problems).
Once that gets rolled out, I'll do some testing and make any modifications we need to the install script and the virtualmin-config Net plugin.
Hopefully, y'all will be able to try it out before the end of the week, and it should be production-ready within a week or so (I assume any new OS needs some testing by real users before it's really solid).
--
Check out the forum guidelines!
Awesome, thanks for the update!
Another update: Webmin 1.890 with netplan support is in the repos. I should be able to do some testing and make any necessary updates in the next day or two for Ubuntu 18.04 support.
--
Check out the forum guidelines!
Thanks, Joe!
Will Ubuntu 18.04 now be mentioned in the install script?
When it's finished it will be. So, another day or two.
--
Check out the forum guidelines!
install script with LEMP bundle option on Ubuntu 18.04 LTS produces an installation that does not come back from a reboot. the host becomes unreachable.
When install completes, I connect via port 10000 and complete the wizard. the dashboard says a reboot is needed, so I reboot it and then the host becomes unreachable. I reinstalled Ubuntu 18.04 on the vps and ran the install.sh script again with the same result. I have not been able to locate the issue as of yet.
install with LAMP works and I was able to manually install nginx which produced a working server.
Let me know if anyone else can reproduce this problem.
I am having the same problem on a LEMP install on DigitalOcean, Ubuntu 18.04.1 as well. When install completes, I can't even access port 10000 though. After rebooting, I can no longer access SSH remotely.
I faced a similar problem with EC2. I used LAMP with -m and after reboot I can't access it anymore either through SSH or webmin.
Well today, my working LAMP installation on Ubuntu 18.04 got some updates and after installing them, needed a reboot. never came back from the reboot. so let's just say at this time, virtualmin does not work on Ubuntu 18.04 whether you select the LAMP or LEMP bundle. I am now falling back to Ubuntu 16.04
I am testing this on Digital Ocean and I am still able to access the VPS from their console VNC access but not from the outer internet. I tried shutting down firewalld to no avail.
There was a configuration corruption issue in Webmin 1.890 with netplan-based distributions in some cases. I never saw it in my tests, but several folks reported it, and we think it's been fixed in 1.891. Try a fresh install and let us know what happens.
Also, no installation options will make any difference with this problem...there's no need to test different options. It will either work or it won't, regardless of whether it is LAMP, LEMP or minimal mode installation. The problem was (and maybe still is if we missed something) with the network configuration step, which happens the same across all installation modes.
--
Check out the forum guidelines!
I've done a fresh install of Ubuntu 18.04 and virtualmin and it is looking good so far. if anything goes wrong, I'll update this thread.
Thanks!
I redid it again just now and after the restart everything seems to works fine. Thanks Joe
I tried installing again on DigitalOcean but the installation turned up some errors:
Installing updates to Virtualmin-related packages [ â ]
â£â£â£ Phase 3 of 3: Configuration
[1/23] Configuring AWStats [ â ]
[2/23] Configuring Bind [ â ]
[3/23] Configuring ClamAV [ â ]
[4/23] Configuring Dovecot [ â ]
[5/23] Configuring Firewalld [ â ]
[6/23] Configuring MySQL [ â ]
[7/23] Configuring NTP [ â ]
[8/23] Configuring Net âââââââE rror: No interface named macaddress found
Error
-----
No interface named macaddress found
-----
â£â£â£ Cleaning up
[WARNING] The following errors occurred during installation:
â Postinstall configuration returned an error.
[WARNING] The last few lines of the log file were:
[2018/08/09 16:19:55] [INFO] - Code: 0 Result: success
[2018/08/09 16:19:55] [INFO] - Code: 0 Result: success
[2018/08/09 16:19:56] [INFO] - Code: 0 Result: success
[2018/08/09 16:19:56] [INFO] - Code: 0 Result: Warning: ZONE_ALREADY_SET: public
success
[2018/08/09 16:19:56] [INFO] - Succeeded
[2018/08/09 16:19:56] [INFO] - Configuring MySQL
[2018/08/09 16:20:00] [INFO] - Succeeded
[2018/08/09 16:20:00] [INFO] - Configuring NTP
[2018/08/09 16:20:01] [INFO] - System clock source is kvm-clock, skipping NTP
[2018/08/09 16:20:01] [INFO] - Succeeded
[2018/08/09 16:20:01] [INFO] - Configuring Net
[2018-08-09 16:20:01 UTC] [DEBUG] Cleaning up temporary files in /tmp/.virtualmi n-1197.
[2018-08-09 16:20:01 UTC] [WARNING] The following errors occurred during install ation:
[2018-08-09 16:20:01 UTC] [WARNING] The last few lines of the log file were:
EDIT: The problem seems to happen only when private networking is enabled on DigitalOcean.
This is the netplan config of the offending droplet (eth1):
network:version: 2
ethernets:
eth0:
addresses:
- 142.93.118.130/20
- 2604:A880:0400:00D1:0000:0000:088D:1001/64
- 10.10.0.5/16
gateway4: 142.93.112.1
gateway6: 2604:a880:0400:00d1:0000:0000:0000:0001
match:
macaddress: ee:79:ef:d2:d2:7b
nameservers: &id001
addresses:
- 67.207.67.3
- 67.207.67.2
search: []
set-name: eth0
eth1:
addresses:
- 10.136.108.102/16
match:
macaddress: 86:68:26:48:4e:93
nameservers: *id001
set-name: eth1
Wondering if anything could be done about this?
[EDITED]
Did some further tests. On DigitalOcean droplets, with Private Networking disabled, installation completes successfully. However, connection is still lost upon a reboot.
Noted that my /etc/netplan/50-cloud-init.yaml config is changed by Virtualmin as follows:
network:version: 2
ethernets:
eth0:
addresses: ['/32']
gateway4: 142.93.112.1
gateway6: 2604:a880:0400:00d1:0000:0000:0000:0001
nameservers:
addresses: [127.0.0.53,127.0.0.1]
Doing netplan apply returns an error, stating that the the format of 'addresses' being wrong.
With private networking enabled, installation doesn't even complete. Modifying 50-cloud-init.yaml to remove eth1 allows installation to complete, but upon rebooting, I lose access again.
Fresh install. I'm using LEMP stack. Working like a charm. Thank you!
Just one minor issue... after replacing MySQL with MariaDB, I told apparmor about MariaDB to %$#@ off.
ln -s /etc/apparmor.d/usr.sbin.mysqld /etc/apparmor.d/disable/I have just tried to install on Azure Cloud Ubuntu 18.04...it falls over at step 9...
[9/23] Configuring Net error: No interface named match found.
What does this mean? I also dont have a virtualmin log in /var/log there is a virtualmin license in /etc/ but not virtualmin (webmin and usermin are both present)
Is my issue to do with Ubuntu 18 or something i have done wrong with Azure?
edit...i just rolled an Ubuntu 16.04 vm on Azure with identical resource and network settings and it worked perfectly.
https://ajecreative.com.au
Just installed on 18.04 on my Worldstream server and all looks ok, but if I reboot the system, it doesn't work. I get the error "ERR_TUNNEL_CONNECTION_FAILED". Any idea?
I did another test on Digital Ocean and this time I saved a backup of the file /etc/netplan/50-cloud-init.yaml before installing Virtualmin.
I also temporarily set a short password for root so as to make it easier to enter it manually to log in from the VNC console that does not support copying / pasting.
After installing Virtualmin and rebooting (and confirming the server was unreachable), I logged in from the Digital Ocean VNC console and comparing the new 50-cloud-init.yaml file with the backup I saw that the Virtualmin file had the following entry:
addresses: ['/32']
while the backup had:
addresses: - MY_DROPLET_IP_ADDRESS/20 - 10.10.0.6/16
so I copied the addresses: lines from the backup and after "netplan apply" and reboot the server is now accessible.
By the way the original 50-cloud-init.yaml also shows additional lines such as "macaddress" while the Virtualmin does not have them (not sure about how important they are) but just resetting the addresses line seems to be enough to regain connectivity.
If I launch do-release-upgrade on 16.04 LTS, add your new repo and update, should I expect Webmin to work? And Cloudmin? Thanks!
The old network configuration works. The new netplan does not (at least not for everyone and not with every configuration).
I don't know whether release-upgrade would switch the network to netplan (but, I doubt it).
It's not a mystery what's not working (and I think the next Webmin will fix it for everyone). Netplan is a completely new (and very complex) network configuration system, and support for it is still spotty and buggy in Webmin. If you want to install/run Virtualmin, you probably need to use the old network configuration system. How you get there is up to you (though I think upgrading from 16.04 would do it, it's probably simpler to just switch the network config on an 18.04 system).
--
Check out the forum guidelines!
By the way in 18.04 I found javascript-common.conf enabled for Apache which aliases /javascript to /usr/share/javascript/ thus breaking a number of sites. "a2disconf javascript-common" should fix this nuisance.
Is it possible for Virtualmin to ask us if we want to just "switch Ubuntu 18 over to use the old network configuration system" ????
(I would click yes if prompted)
We're very close to a new release of Webmin that'll fix the remaining issues (I hope/think). I wouldn't want to invest time implementing a network config switcher, as it would basically need to understand both the old and new network config systems...which is what we're having a hard time implementing, already!
--
Check out the forum guidelines!
There's a new Webmin in the repos that Jamie believes fixes all of the known netplan issues. Give it another try, if you're waiting for Ubuntu 18.04 support. I'll be doing some testing today, as well.
--
Check out the forum guidelines!
Hi Joe, thanks for the update.
Unfortunately, still receiving the following error when installing on DigitalOcean: https://pastebin.com/KracG4Sh
Can you tell me the exact settings you used when creating your Droplet? I've been testing on Digital Ocean and I'm not seeing this error. I'd like to setup an environment where this error happens so I can let Jamie interact with it.
Edit: Nevermind, I haven't reproduced this exact error, but I see how it could happen, probably, and I'm seeing the root cause and I've handed off a server to Jamie that's exhibiting the problem. Should be able to sort it soon.
--
Check out the forum guidelines!
Hi Joe, just wondering if there is any update in this regard? would love to give 18.04 another go. Thanks! :)
Private networking, ipv6 and backups enabled.
Not sure if this is related but I installed virtualmin on 18.04 and all seems to be fine except LetsEncrypt certificates are not installing. It seems that the necessary files in .well-known are not being created so the verification callback fails.
You wouldn't have an .htaccess file with mod_rewrite on in your public_html dir?
nothing at all, it's a totally empty domain.
If you add a file in the public_html directory, you can access it through the domain name?
That side of things is fine, I've tested. The problem is that the /.well-known/ directory and the necessary files within it are simply not generated at all. Is there any way I can find logs to give me some idea of what is happening?
OK I've found the letsencrypt logs in /var/log. And I found this line
2018-09-12 00:12:34,535:DEBUG:certbot.plugins.webroot:Attempting to save validation to /home/prod/public_html/.well-known/acme-challenge/0tn42AAtDk8wWBtjH6EBC6_b7q_XITel5oURR6a-DmsBut no error message and no file is ever created.
I'm just following up to say that I eventually tracked down the issue and it is unrelated to 18.04 - it was tied to the fact that there was an IPv6 IP on that domain and Virtualmin had not set the host to respond on IPv6. This was combined with the fact that certbot now deletes the challenge files after use - something that my old CentOS machines don't do - so I was mistakenly thinking the files were never created. In fact, they were created then deleted.
sudo do-release-upgrade Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,258 kB] Fetched 1,259 kB in 0s (0 B/s) authenticate 'bionic.tar.gz' against 'bionic.tar.gz.gpg' extracting 'bionic.tar.gz'
Reading cache
Checking package manager
Continue running under SSH?
This session appears to be running under ssh. It is not recommended to perform a upgrade over ssh currently because in case of failure it is harder to recover.
If you continue, an additional ssh daemon will be started at port '1022'. Do you want to continue?
Continue [yN]
Starting additional sshd
To make recovery in case of failure easier, an additional sshd will be started on port '1022'. If anything goes wrong with the running ssh you can still connect to the additional one. If you run a firewall, you may need to temporarily open this port. As this is potentially dangerous it's not done automatically. You can open the port with e.g.: 'iptables -I INPUT -p tcp --dport 1022 -j ACCEPT'
To continue please press [ENTER]
Reading package lists... Done Building dependency tree Reading state information... Done Hit http://mirror.hetzner.de/ubuntu/packages xenial InRelease Get:1 http://mirror.hetzner.de/ubuntu/packages xenial-backports InRelease [107 kB] Hit http://de.archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://mirror.hetzner.de/ubuntu/packages xenial-updates InRelease [109 kB] Get:3 http://de.archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB] Get:4 http://mirror.hetzner.de/ubuntu/security xenial-security InRelease [107 kB] Get:5 http://de.archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB] Get:6 http://security.ubuntu.com/ubuntu xenial-security InRelease [107 kB] Hit http://ppa.launchpad.net/ondrej/apache2/ubuntu xenial InRelease Hit http://ppa.launchpad.net/ondrej/php/ubuntu xenial InRelease Hit http://software.virtualmin.com/vm/6/gpl/apt virtualmin-xenial InRelease Ign http://download.webmin.com/download/repository sarge InRelease Hit http://software.virtualmin.com/vm/6/gpl/apt virtualmin-universal InRelease Hit http://download.webmin.com/download/repository sarge Release Fetched 646 kB in 0s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done
Updating repository information
Third party sources disabled
Some third party entries in your sources.list were disabled. You can re-enable them after the upgrade with the 'software-properties' tool or your package manager.
To continue please press [ENTER]
Get:1 http://de.archive.ubuntu.com/ubuntu bionic InRelease [242 kB] Get:2 http://de.archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB] Get:3 http://de.archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB] Get:4 http://security.ubuntu.com/ubuntu bionic-security InRelease [83.2 kB] Get:5 http://de.archive.ubuntu.com/ubuntu bionic/main amd64 Packages [1,019 kB] Get:6 http://de.archive.ubuntu.com/ubuntu bionic/main i386 Packages [1,007 kB] Get:7 http://de.archive.ubuntu.com/ubuntu bionic/main Translation-en [516 kB] Get:8 http://de.archive.ubuntu.com/ubuntu bionic/restricted amd64 Packages [9,184 B] Get:9 http://de.archive.ubuntu.com/ubuntu bionic/restricted i386 Packages [9,156 B] Get:10 http://de.archive.ubuntu.com/ubuntu bionic/restricted Translation-en [3,584 B] Get:11 http://de.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages [8,570 kB] Get:12 http://de.archive.ubuntu.com/ubuntu bionic/universe i386 Packages [8,531 kB] Get:13 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages [167 kB] Get:14 http://de.archive.ubuntu.com/ubuntu bionic/universe Translation-en [4,941 kB] Get:15 http://de.archive.ubuntu.com/ubuntu bionic/multiverse amd64 Packages [151 kB] Get:16 http://de.archive.ubuntu.com/ubuntu bionic/multiverse i386 Packages [144 kB] Get:17 http://de.archive.ubuntu.com/ubuntu bionic/multiverse Translation-en [108 kB] Get:18 http://de.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [322 kB] Get:19 http://de.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages [286 kB] Get:20 http://de.archive.ubuntu.com/ubuntu bionic-updates/main Translation-en [122 kB] Get:21 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [192 kB] Get:22 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe i386 Packages [192 kB] Get:23 http://de.archive.ubuntu.com/ubuntu bionic-updates/universe Translation-en [90.1 kB] Get:24 http://de.archive.ubuntu.com/ubuntu bionic-updates/multiverse amd64 Packages [4,180 B] Get:25 http://de.archive.ubuntu.com/ubuntu bionic-updates/multiverse i386 Packages [4,336 B] Get:26 http://de.archive.ubuntu.com/ubuntu bionic-updates/multiverse Translation-en [2,740 B] Get:27 http://de.archive.ubuntu.com/ubuntu bionic-backports/universe amd64 Packages [2,704 B] Get:28 http://de.archive.ubuntu.com/ubuntu bionic-backports/universe i386 Packages [2,704 B] Get:29 http://de.archive.ubuntu.com/ubuntu bionic-backports/universe Translation-en [1,136 B] Get:30 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages [132 kB] Get:31 http://security.ubuntu.com/ubuntu bionic-security/main Translation-en [62.9 kB] Get:32 http://security.ubuntu.com/ubuntu bionic-security/universe amd64 Packages [66.6 kB] Get:33 http://security.ubuntu.com/ubuntu bionic-security/universe i386 Packages [66.5 kB] Get:34 http://security.ubuntu.com/ubuntu bionic-security/universe Translation-en [39.2 kB] Get:35 http://security.ubuntu.com/ubuntu bionic-security/multiverse amd64 Packages [1,444 B] Get:36 http://security.ubuntu.com/ubuntu bionic-security/multiverse i386 Packages [1,608 B] Get:37 http://security.ubuntu.com/ubuntu bionic-security/multiverse Translation-en [996 B] Fetched 27.3 MB in 0s (0 B/s)
Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done
Calculating the changes
Calculating the changes No candidate ver: linux-image-4.13.0-36-generic No candidate ver: linux-image-4.13.0-38-generic No candidate ver: linux-image-4.13.0-39-generic No candidate ver: linux-image-4.13.0-41-generic No candidate ver: linux-image-4.13.0-43-generic No candidate ver: linux-image-4.13.0-45-generic No candidate ver: linux-image-extra-4.13.0-36-generic No candidate ver: linux-image-extra-4.13.0-38-generic No candidate ver: linux-image-extra-4.13.0-39-generic No candidate ver: linux-image-extra-4.13.0-41-generic No candidate ver: linux-image-extra-4.13.0-43-generic No candidate ver: linux-image-extra-4.13.0-45-generic
Do you want to start the upgrade?
3 installed packages are no longer supported by Canonical. You can still get support from the community.
16 packages are going to be removed. 226 new packages are going to be installed. 625 packages are going to be upgraded.
You have to download a total of 530 M. This download will take about 1 hour 7 minutes with a 1Mbit DSL connection and about 20 hours with a 56k modem.
Fetching and installing the upgrade can take several hours. Once the download has finished, the process cannot be canceled.
Continue [yN] Details [d]
No longer supported: gcc-5-base gcc-6-base tcl
Remove: apache2 libnss3-nssdb libperl5.22 perl-modules-5.22 php-curl php-imagick php7.0-curl virtualmin-lamp-stack
Remove (was auto installed) apache2-bin apache2-suexec-custom libapache2-mod-fcgid libapache2-mod-php7.2 libcurl3 libmagickcore-6.q16-2 libmagickwand-6.q16-2 php7.2-curl
Install: autopoint binutils-common binutils-x86-64-linux-gnu btrfs-progs cpp-7 dh-autoreconf dirmngr e2fsprogs-l10n fdisk firebird3.0-common firebird3.0-common-doc fontconfig fonts-droid-fallback fonts-noto-mono g++-7 gcc-7 gcc-7-base gcc-8-base geoip-database gnupg-l10n gnupg-utils gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm ibverbs-providers imagemagick-6-common libalgorithm-c3-perl libarchive-cpio-perl libasan4 libass9 libassuan0 libauthen-sasl-perl libavcodec57 libavdevice57 libavfilter6 libavformat57 libavresample3 libavutil55 libb-hooks-endofscope-perl libb-hooks-op-check-perl libbind9-160 libbinutils libbluray2 libboost-filesystem1.65.1 libboost-iostreams1.65.1 libboost-system1.65.1 libcairo2 libcdio-cdda2 libcdio-paranoia2 libcdio17 libchromaprint1 libclass-c3-perl libclass-c3-xs-perl libclass-data-inheritable-perl libclass-method-modifiers-perl libcom-err2 libcrypt-openssl-bignum-perl libcrypt-openssl-rsa-perl libcryptsetup12 libcurl4 libdata-optlist-perl libdatrie1 libdevel-callchecker-perl libdevel-caller-perl libdevel-globaldestruction-perl libdevel-lexalias-perl libdevel-stacktrace-perl libdist-checkconflicts-perl libdns-export1100 libdns1100 libdynaloader-functions-perl libegl-mesa0 libegl1 libemail-date-format-perl libeval-closure-perl libevent-2.1-6 libevent-core-2.1-6 libexception-class-perl libext2fs2 libfastjson4 libfcgi-bin libgbm1 libgcc-7-dev libgdbm-compat4 libgdbm5 libgdk-pixbuf2.0-0 libgdk-pixbuf2.0-bin libgdk-pixbuf2.0-common libgl1 libglvnd0 libglx-mesa0 libglx0 libhunspell-1.6-0 libibverbs1 libicu60 libidn2-0 libio-socket-ssl-perl libip4tc0 libip6tc0 libipc-shareable-perl libiptc0 libisc-export169 libisc169 libisccc160 libisccfg160 libisl19 libjson-c3 libksba8 libldap-common libllvm3.9 liblog-dispatch-perl liblwres160 libmagic-mgc libmail-dkim-perl libmailtools-perl libmime-lite-perl libmime-types-perl libmodule-implementation-perl libmodule-runtime-perl libmpfr6 libmpg123-0 libmpx2 libmro-compat-perl libmysofa0 libnamespace-autoclean-perl libnamespace-clean-perl libnet-smtp-ssl-perl libnl-route-3-200 libnpth0 libnss-systemd libopendkim11 libopenjp2-7 libopenmpt0 libpackage-stash-perl libpackage-stash-xs-perl libpadwalker-perl libpango-1.0-0 libpangocairo-1.0-0 libpangoft2-1.0-0 libparams-classify-perl libparams-util-perl libparams-validationcompiler-perl libperl5.26 libpixman-1-0 libpng16-16 libpostproc54 libprocps6 libpsl5 libpython3.6 libpython3.6-minimal libpython3.6-stdlib libreadline7 libreadonly-perl libref-util-perl libref-util-xs-perl librole-tiny-perl librsvg2-2 librsvg2-common librubberband2 libruby2.5 libsdl2-2.0-0 libsndio6.1 libspecio-perl libstdc++-7-dev libsub-exporter-perl libsub-exporter-progressive-perl libsub-identify-perl libsub-install-perl libsub-name-perl libsub-quote-perl libswresample2 libswscale4 libtfm1 libthai-data libthai0 libtommath1 libtry-tiny-perl libunistring2 libva-drm2 libva-x11-2 libva2 libvariable-magic-perl libvorbisfile3 libvpx5 libwayland-client0 libwayland-cursor0 libwayland-egl1-mesa
:
Continue [yN] Details [d]d
No longer supported: gcc-5-base gcc-6-base tcl
Remove: apache2 libnss3-nssdb libperl5.22 perl-modules-5.22 php-curl php-imagick php7.0-curl virtualmin-lamp-stack
Remove (was auto installed) apache2-bin apache2-suexec-custom libapache2-mod-fcgid libapache2-mod-php7.2 libcurl3 libmagickcore-6.q16-2 libmagickwand-6.q16-2 php7.2-curl
(if you use code blocks, your text will be much easier to read!!)
This text: < code > sample < /code > (without the spaces)
Like this:
samplesample
sample
sample
Installed 18.04 on Rackspace Cloud Server yesterday. Failed after reboot on 5 successive attempts.
Tried to update machine first, ie apt update / apt upgrade, then reboot. Reboot was good. Did install. No errors. Could connect via GUI fine.
After install: apt update
All packages are up to date.N: Usage of apt_auth.conf(5) should be preferred over embedding login information directly in the sources.list(5) entry for 'http://software.virtualmin.com/vm/6/apt'
N: Usage of apt_auth.conf(5) should be preferred over embedding login information directly in the sources.list(5) entry for 'http://software.virtualmin.com/vm/6/apt'
Post installation wizard "lost connection to server" for about 10 seconds after "next" click on the "memory use" screen.
Virtualmin now gives me a warning
Warning!Recent package updates (such as a new kernel version) require a reboot to be fully applied.
Reboot and all connection from outside of Rackspace fails. I can still connect from the Rackspace console.
Pages