Reinstallation

Actually, can I run the setup script again to reinstall VirtualMin?

After installation of virtualMin, would it open port 10000 and some ports like 80,22,21,53 for me?

They were not opened for me.
I worry if my installation had errors that I want to reinstall it.

In the installation few weeks ago, the recheck of config didn’t show me warning of “quota is not enabled” but this time it does. I didn’t touch quota thing at all.

Also, after creating a hosting like domain.com.
http://mail.domain.com
http://ftp.domain.com
http://www.doamin.com
can also open the site.
Can you set only domain.com and www.domain.com can read the site by default?

Thanks very much for your time.
VirtualMin is very cool.

You should never run the install.sh script on a system that is already in service. It is for installation. If there were errors during installation, sometimes it is useful to run the uninstall process and run install.sh again after correcting whatever problem caused the error(s). But, if you install weeks ago, and have been using it…it is not a good idea to run install.sh again.

The virtualmin-base package does include a step that attempts to open all of the necessary ports on the local firewall, but if it failed once, it’ll almost certainly fail again. It cannot accommodate custom firewalls very well (though it handles most of the common ones–the Red Hat default firewall, for example, can exist or not, and the install script works either way…but oddball stuff like APF are broken by design, and don’t interact with other firewall rules politely).

So…the question is: Do you have any Virtualmin accounts you want to keep? If not, you could run:

install.sh --uninstall

And then run install.sh again. Watch carefully for errors, and bring them up here if you see any, and we’ll try to help you deal with them.

If you haven’t changed any configuration in Virtualmin that you want to keep, you could also just re-install virtualmin-base. This won’t (or shouldn’t…make backups anyway) break any of your Virtualmin accounts, but will restore the default configuration of many services and try to enable quotas and such.

To do that:

rpm -e virtualmin-base
yum install virtualmin-base

Or:

dpkg -r virtualmin-base
apt-get install virtualmin-base

This is still potentially disruptive, so you don’t want to do it on a production box.

Did it affect the rest part of the script?

Yes. Looks like nothing in virtualmin-base actually ran, if that’s the entirety of the log between “install virtualmin-base” and “Install of virtualmin-base completed”. There should have been a dozen or so “Configuring…” lines in there. Oh, wait, you’ve sent the SSH log. Look in /root/virtualmin-install.log, as well…I believe we’re logging everything that really ought to happen.

I’m looking into this particular issue…sounds like maybe the default aliases file on CentOS now contains something that it didn’t when we built the virtualmin-base package. I’ll probably need to accommodate that.

After figuring out problems of Mail, Web, DNS for a few days, I now can create a web site and upload files to it. But I still can't connect to mail server at port smtps(SSL smtp) due to missing SSL cert.

virtualmin-base doesn’t configure smtps. Because it requires a certificate, and many users don’t have one, or have it in place on the system, this is a step that is saved for later. I’ve answered your thread about this with more detail about how to setup a cert for Postfix.

I also found that were some misconfiguration in the default Postfix config like mailbox_size_limit and message_size_limit.

Hmm…I was thinking that only adversely effected the Debian virtualmin-base. I’ll have to roll a new one for CentOS/RHEL, too. As mentioned in the thread about this particular problem, just remove those two options from /etc/postfix/main.cf, and this error will go away. Will be fixed in the next version.

Thanks.

In the /root/virtualmin-install.log,
there is no error and as you said, there are many "downloading" and "processing dependency" and a few "Enabling" and "Configuring" things.

So… should I ./install.sh --uninstall and then install it again? or should I reinstall Centos as well to clear all config data? Actually, I think most things work fine now but only a cert is missing. I want to know whether reinstallation of virtualmin would make things better or give me more problems…

Thanks very much for your time.

Unless you had a fatal error, no. --uninstall isn’t useful.

Run the less dramatic option instead:

rpm -e virtualmin-base
yum install virtualmin-base

Don’t reinstall CentOS. That’d just be a waste of your time. Our installer is actually pretty smart about dealing with things in various states (except when we break it as we did last week).

Actually, I think most things work fine now but only a cert is missing. I want to know whether reinstallation of virtualmin would make things better or give me more problems...

What cert? Webmin creates a self-signed certificate for itself and one for Usermin. No other certificates are created or expected to be. We don’t really recommend using self-signed certs, in general.

Ok… I will try to reinstall it later.
I mean the SSL cert for smtps. But it’s ok. I will create one later.

Thanks very much for your time.

Thanks for your quick reply.

This is my SSH log when I was installing virtualmin.

INFO - Installing Virtualmin and all related packages now using the command:
INFO - yum -y -d 2 install virtualmin-base
INFO - …in progress, please wait…
-Error: A mail alias called default- already exists
Error

A mail alias called default- already exists

\error: %post(virtualmin-base-1.0-53.rh.noarch) scriptlet failed, exit status 1
INFO - …in progress, please wait… Succeeded.
INFO - Installation of virtualmin-base completed.

Did it affect the rest part of the script?
I ran the install script on a freshly installed Centos5, so I didn’t know what was wrong with the “default-” thing.

After figuring out problems of Mail, Web, DNS for a few days, I now can create a web site and upload files to it. But I still can’t connect to mail server at port smtps(SSL smtp) due to missing SSL cert.

I found from google that the decovot had a small bug which can be solved. see:
http://www.cyberciti.biz/tips/rhel-dovecot-error-while-loading-shared-libraries.html

I also found that were some misconfiguration in the default Postfix config like mailbox_size_limit and message_size_limit.

I wonder if all these(+ the script didn’t open ports) resulted from the error in the installation of the script. If it is really the reason, I can’t wait reinstalling virtualMin. :slight_smile: But, will the current error or incorrect config be inherited? Do I need to reinstall Centos5 to have a clean installation of VirtualMin?

Thanks very much for your time.

Thanks for your quick reply.

This is my SSH log when I was installing virtualmin.

INFO - Installing Virtualmin and all related packages now using the command:
INFO - yum -y -d 2 install virtualmin-base
INFO - …in progress, please wait…
-Error: A mail alias called default- already exists
Error

A mail alias called default- already exists

\error: %post(virtualmin-base-1.0-53.rh.noarch) scriptlet failed, exit status 1
INFO - …in progress, please wait… Succeeded.
INFO - Installation of virtualmin-base completed.

Did it affect the rest part of the script?
I ran the install script on a freshly installed Centos5, so I didn’t know what was wrong with the “default-” thing.

After figuring out problems of Mail, Web, DNS for a few days, I now can create a web site and upload files to it. But I still can’t connect to mail server at port smtps(SSL smtp) due to missing SSL cert.

I found from google that the decovot had a small bug which can be solved. see:
http://www.cyberciti.biz/tips/rhel-dovecot-error-while-loading-shared-libraries.html

I also found that were some misconfiguration in the default Postfix config like mailbox_size_limit and message_size_limit.

I wonder if all these(+ the script didn’t open ports) resulted from the error in the installation of the script. If it is really the reason, I can’t wait reinstalling virtualMin. :slight_smile: But, will the current error or incorrect config be inherited? Do I need to reinstall Centos5 to have a clean installation of VirtualMin?

Thanks very much for your time.

So, this is what got Webmin and Virtualmin up and running for me on CentOS 7 after I updated and used the command sudo yum autoremove! Definitely not doing that again.

I ran:

yum install virtualmin-base

and webmin and virtualmin came gloriously back to life!