Installer script failed on debian 8.6

Submitted by horaceng on Mon, 10/24/2016 - 21:28

fresh debian 8.6 amd64 netinst
platform: vsphere HW version 8 VM debian 6 64-bit

virtualmin-install.log:
Use of uninitialized value in numeric eq (==) at /usr/share/webmin/bind8/bind8-lib.pl line 537.^M
Use of uninitialized value in numeric eq (==) at /usr/share/webmin/bind8/bind8-lib.pl line 543.^M
Use of uninitialized value $user in concatenation (.) or string at /usr/share/webmin/bind8/bind8-lib.pl line 2176.^M
Configuring resolv.conf to use my DNS server^M
Enabling status monitoring^M
Hiding the Webmin and Usermin upgrade pages^M
Enabling quotas on filesystem for /home^M
convertquota: You have to specify action to perform.^M
convertquota: Utility for converting quota files.^M
Usage:^M
convertquota [options] mountpoint^M
^M
-u, --user convert user quota file^M
-g, --group convert group quota file^M
-e, --convert-endian convert quota file to correct endianity^M
-f, --convert-format oldfmt,newfmt convert from old to VFSv0 quota format^M
-h, --help show this help text and exit^M
-V, --version output version information and exit^M

it tried to inject 127.0.0.1 to /etc/network/interface and resolve.conf, and after reloading the interface, the IP address of the interface was gone while the interface was actually UP. The installer script then failed miserably here as it couldn't download to proceed. Manual 'ifup eth0' does still work.

Files: 
Plain text icon virtualmin-install.txt
Status: 
Active

Comments

Submitted by andreychek on Mon, 10/24/2016 - 21:58

Howdy -- hmm, the logs you attached seem to indicate that it completed successfully. There are some warnings that pop up during the installation process, but the ones I'm seeing there are normal warnings, and should be safe to ignore. The SpamAssassin message at the end there is the last part of the install.

It appears to have had network connectivity throughout the installation process.

Virtualmin shouldn't ever try to change your network interfaces or IP addresses though. The only time it needs to change the /etc/network/interfaces file is on certain distributions, where the DNS servers need to be added to that file.

On all distros, It does add 127.0.0.1 as a nameserver in the /etc/resolv.conf file.

If your networking isn't working, you may just need to take a look at the /etc/network/interfaces file, and correct anything in there that isn't correct for your network.

After that, it does look like the installation succeeded -- you should then be able to access Virtualmin on port 10000.

Submitted by horaceng on Mon, 10/24/2016 - 22:25

There's nothing wrong with the /etc/network/interfaces and it did work after I run 'ifup eth0'. The ip address of eth0 gone missing after the following:

convertquota: Bugs to jack@suse.cz
Configuring firewall rules
Removing default AWstats cron job
Re-checking supported Webmin modules

I think it was trying to mess with firewall?

Submitted by andreychek on Mon, 10/24/2016 - 23:04

Thanks for the additional input there!

I'll talk to Jamie to see if he has any thoughts on what might be going on to cause any issues.

It does indeed use iptables in order to add firewall rules, though that shouldn't cause your IP address to go missing.

The install script hasn't changed recently though, and I unfortunately haven't been able to reproduce an issue like that.

However, I need to do some work with the install script anyhow, and I'll review it to see if I can determine what might have occurred to cause a problem in your case.

Submitted by JamieCameron on Tue, 10/25/2016 - 19:37

On some Linux distributions, the DNS nameservers are also stored in /etc/network/interfaces , so Virtualmin could potentially modify that file.

Can you attach the interfaces file from after running the installer, so I can see what went wrong with it?