These forums are locked and archived, but all topics have been migrated to the new forum. You can search for this topic on the new forum: Search for Webmin version 1.890 released on the new forum.
Web Hosting and Cloud Computing Control Panels
Hi Joe
My operating system is Ubuntu Linux 14.04.2. As soon as I update to Webmin version 1.890 the Servers Status of ProFTPD FTP Server changed to stopped. I tried several things but nothing seemed to work until I restarted the entire server. Then I was able to start ProFTPD.
Can you check to see if the init system is being detected correctly? I remember we had some issues with detection because Ubuntu went through old style initscripts, upstart, and then systemd, in the span of just a few years, and there's some overlap in which tools are available across versions...so things are really messy there, and we've had to refine init system detection several times for Ubuntu.
You can see this in Webmin->System->Bootup and Shutdown
The top of the page will say "Boot system: xxx" where "xxx" is something like systemd, upstart, and initscripts (or something, I don't remember the exact wording).
I don't actually remember which init system is used on 14.04...upstart, probably?
--
Check out the forum guidelines!
Hi Joe.
It is
Bootup and Shutdown Boot system : Upstart
Hi Joe,
I noticed there are two bug reports related to netplan already in the issue tracker, both marked as fixed (pending). I'm wondering when the new webmin version with bugfixes to netplan will be released, any hint? Currently I'm unable to complete virtualmin installation on Ubuntu 18.04 in DigitalOcean, it fails at "Configuring Net" step. I'm not sure where the problem is, but I was hoping to try thew new version, maybe a fix is already there. I could test, and if the issue is not fixed in webmin 1.891, then I could file another bug report with more details.
Thanks! Leszek
A release isn't scheduled precisely. Jamie's been traveling, so hasn't been able to do a new release yet, but it should come soon.
The bug in question (at least the one I know about) only affects some systems.
I think you're seeing a different issue (possibly another bug). On my test Digital Ocean system, in order to test behavior when /etc/network/interfaces is missing I moved that file. It is possible that if it is present Webmin is detecting it as a non-netplan system and then failing because it is a netplan system. Can you try moving that file out of the way, performing an
--uninstalland then trying the install again?--
Check out the forum guidelines!
I run a few tests, and it doesn't make a difference whether the
interfacesfile is present in/etc/network. I tried installing virtualmin on a fresh server with the/etc/network/interfacesmoved - also failed at the same stage. And I tried to--uninstalland then install without touching the/etc/network/interfacesand it succeeded.The Configuring Net step fail with
Error: No interface named macaddress founderror, and I see/etc/netplan/50-cloud-init.yamlhas the macaddress keyword, so maybe there is a parsing issue. Looks like Virtualmin installation touches the netplan file, because after the installation it's corrupted, and networking stack does not start after reboot so access to the server is only possible through recovery console.netplan applyerrors out with this:Error in network definition //etc/netplan/50-cloud-init.yaml line 9 column 23: malformed address '/32', must be X.X.X.X/NN or X:X:X:X:X:X:X:X/NN./etc/netplan/50-cloud-init.yaml before installation:
# This file is generated from information provided by# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
addresses:
- 206.189.147.42/20
- 2400:6180:0000:00D1:0000:0000:04ED:C001/64
- 10.15.0.5/16
gateway4: 206.189.144.1
gateway6: 2400:6180:0000:00D1:0000:0000:0000:0001
match:
macaddress: 8e:a9:ed:77:d3:4e
nameservers: &id001
addresses:
- 67.207.67.3
- 67.207.67.2
search: []
set-name: eth0
eth1:
addresses:
- 10.130.42.163/16
match:
macaddress: 46:27:b2:b5:f6:f1
nameservers: *id001
set-name: eth1
/etc/netplan/50-cloud-init.yaml after installation:
# This file is generated from information provided by# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
addresses: [/32,/32/64]
gateway4: 206.189.144.1
gateway6: 2400:6180:0000:00D1:0000:0000:0000:0001
nameservers:
addresses: [127.0.0.1,127.0.0.53]
eth1:
addresses:
addresses: [/32,/32/64]
nameservers:
addresses: [127.0.0.1,127.0.0.53]
macaddress: 46:27:b2:b5:f6:f1
So weird. I've been trying and to reproduce this on my Digital Ocean instance. But, it does seem like there's a bug or two in the parser. I'll poke Jamie to see if we can get a new Webmin dev release in the next day or two.
--
Check out the forum guidelines!
Thanks Joe, I would love to see Virtualmin installing clean in Digital Ocean :-). If that helps, my droplet is in Singapore and the settings are: enabled IPv6 and Private Networking.
Ah, I bet that's where it's going wrong. A more complex network configuration is confusing the netplan config parser.
I just rolled 1.891 into the repo, and it probably fixes the problem. It's too late for me to tackle another test install tonight, but I'll try in the morning with those settings and see how we're doing.
--
Check out the forum guidelines!
Hi Joe, thank you for releasing updates. I did some testing, I see I'm getting the new Webmin (1.891) when installing using Virtualmin install script. I did some testing, and unfortunately the problem is not solved. On droplet with IPv6 and Private Networking enabled, the installer still fails at the same stage as previously. I tried on a droplet without IPv6 and Private Networking enabled, and the installer does complete without errors, but netplan file still ends up corrupted, and restarting the server makes it unreachable - ip addressing is not enabled after reboot and I have to use the console to get in. Here is the netplan file in this simplified scenerio (no ipv6 and private networking), before installing Virtualmin:
# This file is generated from information provided by# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
addresses:
- 178.128.XX.XX/20
- 10.15.0.5/16
gateway4: 178.128.XX.XX
match:
macaddress: 42:43:a4:XX:XX:XX
nameservers:
addresses:
- 67.207.67.2
- 67.207.67.3
search: []
set-name: eth0
And after:
# This file is generated from information provided by# the datasource. Changes to it will not persist across an instance.
# To disable cloud-init's network configuration capabilities, write a file
# /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
# network: {config: disabled}
network:
version: 2
ethernets:
eth0:
addresses: ['/32']
gateway4: 178.128.XX.XX
nameservers:
addresses: [127.0.0.1,127.0.0.53]
I replaced some numbers with
XXto protect others who will get these addresses after I destroy my droplet :-).Hi Joe, just checking in, curious if you've seen my last reply.
Thank you :-).
Yeah, we've still got some quirks in netplan handling. I think Jamie has checked in more fixes, but we don't yet have a new devel package, so we're still in a bit of a holding pattern. netplan systems are still quirky (might work, probably won't, though, seems to be the consensus). Switching to the old network configuration system is currently the only way to get a fully functional Virtualmin installation on Ubuntu 18.04. (And, we just found out that Debian is also switching to a new network configuration system, and it's different from the new Ubuntu one. So complexity and incompatibility is just exploding in this area, even across Debian and Ubuntu, which have historically been pretty close to each other. Very frustrating.)
--
Check out the forum guidelines!
Thank you Joe for your reply. That sounds like
And I can relate to that so I understand the pain. I will try to disable Netplan and progress with this a bit, I was holding setting up a new server because of the issues discussed in this topic.
Joe, you mentioned "Debian is also switching to a new network configuration system"... what is it called??
err. read previous wrong. Delete.