.. your system is not ready for use by Virtualmin.

8 posts / 0 new
Last post
#1 Wed, 06/10/2015 - 18:54
Datamac

.. your system is not ready for use by Virtualmin.

Your system has 1.83 GB of memory, which is at or above the Virtualmin recommended minimum of 256 MB.

Virtualmin is configured to setup DNS zones, but this system is not setup to use itself as a DNS server. Either add 127.0.0.1 to the list of DNS servers, or turn off the BIND feature on the module config page. It appears that DHCP is being used to dynamically configure your network interfaces, which can cause the DNS servers to be set based on settings provided by the DHCP server. Using a static IP address is strongly recommended with Virtualmin.

The above output is returned after running Re-check and refresh configuration. I would like some help in resolving this. I was just presented with a solution for editing the /etc/resolv.conf file and adding "nameserver 127.0.0.1 which fixed the problem of Apache2 not restarting. It now starts cleanly. My question is how to have a clean return of info regarding Virtualmin functioning properly on the server? Also, I did not perform this install myself. A NOC engineer did it for me since my server is quite a distance from me. There are references to another web site domain that I own but, in reality, has nothing to do with the web site domain to be hosted on this server. I have httpd.conf file info posted on pastebin.

Wed, 06/10/2015 - 22:15
andreychek

Howdy,

My question is how to have a clean return of info regarding Virtualmin functioning properly on the server?

Hmm, I'm not sure I follow what you're asking, what is it you're after there?

It sounds like you were able to correct that issue, so you could always go back into System Settings -> Re-Check Config to see if it detects any additional problems.

And yeah it's possible that Virtualmin was installed after a domain was setup, but that's not likely the cause of the error you shared above.

-Eric

Thu, 06/11/2015 - 06:52 (Reply to #2)
Datamac

Eric,

Regarding Virtualmin being installed after a domain was setup is a good reference point to begin this issue resolution on.

  1. After resolving the previous issue, the first thing I did was recheck and refresh the configuration which produces the error message we are now seeing (actually, same Virutalmin error).

  2. The domain that was setup before the Virtualmin install was performed a few years ago and is hosted by a hosting company that has nothing to do with this server.

  3. The error message produced by Virtualmin indicates that the server is not ready for use by Virtualmin which makes me think where is the actual issue? With the server O/S preparation or Virtualmin install?

  4. Had previous issue with Apache2 not restart from command line which had me examining the httpd.conf file posted on pastebin. (Not sure if it helps to examin this file but there are, of course, entries created by Virtualmin in it) : http://pastebin.com/hxxxYQT6

Thu, 06/11/2015 - 08:57
andreychek

Howdy,

Your Virtualmin installation is likely fine, but there's a file on your server that appears to be changing regularly.

The most common cause for that is due to your server using DHCP, rather than a static IP address. That can cause the /etc/resolv.conf file to change.

That's a fairly common issue, and isn't a "problem", per-se, it just means a change to how IP addresses are assigned needs to be applied.

You can see details on how to resolve that particular issue in the document below:

https://www.virtualmin.com/documentation/dns/faq#Received_Virtualmin_err...

Any problems you're experiencing with Apache would be unrelated to the above error.

Are you still seeing an Apache issue?

-Eric

Thu, 06/11/2015 - 10:46
flickerfly

If you are not using the DNS server on the box, you can also just turn off that module and this won't be checked, I believe. Is that correct Eric?

Thu, 06/11/2015 - 10:57 (Reply to #5)
Datamac

Correct, I am not using DHCP for the server. It has a static IP public address. Is there a straight tutorial for installing Virtualmin and using it to create the first virtual web site?

Thu, 06/11/2015 - 11:02
andreychek

Yup, absolutely correct! If your server isn't going to be acting as a nameserver for all your domains (meaning, some other server/service will be handling the DNS functions for your domains), the DNS feature can be disabled in Virtualmin.

Once the DNS service is disabled, it will no longer check /etc/resolv.conf.

-Eric

Thu, 06/11/2015 - 11:52
Diabolico
Diabolico's picture

This is how i sort resolv.conf changes after every server restart - made new file with same name in /root with this content:

search domain1.com domain2.com domain3.com
nameserver 127.0.0.1
nameserver 8.8.8.8
nameserver 8.8.4.4
nameserver xxx.xxx.xxx.xxx
nameserver yyy.yyy.yyy.yyy

and then in rc.local i put this line /bin/cp /root/resolv.conf /etc/resolv.conf. Now each time my server restart i have back resolf.conf as i want to be.

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