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 stuck at hostname on the new forum.
Web Hosting and Cloud Computing Control Panels
I saw this also. Not sure if what I did is the "official" way to fix it or not....
Even though I had the hostname and domain set correctlly, I still got the error. So, its just looking for the current hostname, I just entered a FQDN hostname at a bash prompt.
hostname bob.foobar.com (using my correct FQDN).
Then did the install. It worked and I have no issues, so I assume all is well.
John P.
You need a real domain name, or fake it as for an exampel "customer.server.com", the install.sh will run as you expekt!
-------------------
There is a bug that exhibits itself on some platforms, due to the way I use the hostname command. It will be corrected in subsequent releases (probably from tonight going forward).
You may get past it, as suggested by others, by assigning a fully qualified hostname:
hostname fully.qualified.domain
However, <i>please</i> be sure you choose a real domain that is suitable for the server. There are several issues that can arise later, if you don't have a fully qualified hostname (for real...not just during installation). So, make sure your system has a real hostname permanently configured, and during installation. (The check isn't there to annoy folks. It really is important for many components of the system.)
--
Check out the forum guidelines!
i get this as the script fails,
Downloading virtualmin-release package for SuSE Linux 10.0...
Welcome to the YaST2 Package Manager!
This tool is meant for debugging purpose only.
failed to detect sources on http://19995:PASSWORD@software.virtualmin.com/suse/10.0/x86_64
ERROR(InstSrc:E_no_instsrc_on_media)
[[1]] y2pm]
What do I have to do to fix it? I run suse 10.0
Thanks
Hey Adam,
Wait until SUSE on x86_64 is supported. ;-)
Sorry, I haven't built x86_64 packages for SUSE. I'm actually working on it today, so it won't be more than a few days before it is available. But, right now, only RHEL/Fedora/CentOS are supported on x86_64.
--
Check out the forum guidelines!
I seem to have the same problem on Jan 24 '06
Hey Michael,
I believe at this point if you're getting this error, you really need to set an appropriate hostname--I don't think any bugs remain in the code that checks for a FQDN. Your box does need to have an FQDN before installation.
You can check with the command:
hostname -f
If this returns a fully qualified hostname (i.e. host.domain or host.domain.tld or domain.tld) and you are hitting this error with the current installer, then a bug may remain. But if not, you'll need to correct the hostname.
On many systems, just editing /etc/hosts and adding an entry for your system will do the trick. Reverse DNS resolution can also resolve this (though it might give a name you don't like). And, if you <i>know</i> you will have correct DNS resolution in the future for the name, you can "force" it with:
hostname -f domain.tld
This check occurs because Postfix insists on having a fully qualified domain name for many actions. Also, Virtualmin will create domains with this value as the primary name server. In both cases, changing it later is possible, but changing a large number of NS records can be a nuisance (sed makes it quicker, though).
--
Check out the forum guidelines!
Im going to give you my beginners knowledge, so take it or leave it. Ir you really did set a true host name during setup of the OS, or afterwards for that matter. I set mine dring the network setup part of suse 10.0 and put www in the first box and my hosting domain name in the second box.
Didnt work for me either, so just be running install.sh I opened up a terminal and type in "hostname www.mydomain.com" without the quotes of course and replacing the mydomain.com with my real domain name. That got Virtualmin Pro installed since it now had a full hoostname to work with.
[[
But since I had no idea when this would actually be fixed, I had to find some way of setting the hostname should the power go out and the backup batteries go flat, so after installing virtualmin pro, I went intothe "system" tab of webmin and clicked on Botup and shutdown, and added a new Bootup and shutdown action called hostname, and it's so simple, , click on create a new bootup and shutdown action at the top of the bootup and shutdown screen, give it any name you want, I like knowing what things are so I called it hostname.I then put a brief description like fix hostname and in the bootup commands I simply typed in hostname www.mydomain.com where mydomain.com is my real fully qualified domain name, then I clicked on the radio button to start at boot time. I left the shutdown commands blank as theres no reason to put anything in there that I can think of. Then hit the create button. Now everytime you shutdown your server or have a blackout and your generators out of fuel, when the system comes back, it will run that simple command to reset your hostname while booting up. If its truly fixed, I dont think this hursts anything by having it in here as its not done any harm to my server. Now just try it out, shut down your server and restart it, open a terminal window and type hostname (in suses I dont need the -f, because it returns that the host name is www.mydomain.com where mydomain.com really is my hosting server domain name.
I hope this helps you if nothing else works for you.
Hey Adam,
Different distros have different ways of setting this using configuration tools, but the canonical way to "fix" it, is simply to add an entry (or edit an existing entry) to /etc/hosts for your primary IP address. For example, on virtualmin.com I have:
[[virtualmin@virtualmin centos-4-x86_64]]$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost
206.251.184.110 virtualmin.com virtualmin
And a hostname -f results in:
[[virtualmin@virtualmin centos-4-x86_64]]$ hostname -f
virtualmin.com
Which is all the Virtualmin installer needs (and this will be picked up correctly by all of the components that need to have this information).
Note, however, that this only gets applied on most systems on a reboot, so you do end up having to force the hostname to get updated. A network restart on Red Hat-based systems will do it, I believe. You can also, of course, simply set it with "hostname virtualmin.com" on the command line. There is no problem with doing this, assuming the name you give it is really the name this server will be using later for real services (like mail and DNS).
Red Hat-based systems have a HOSTNAME entry that can appear in several of the network configuration files...but I've never been able to make much sense out of where/when they get applied.
--
Check out the forum guidelines!
Is there some command that I can issue somewhere that will do the same as if I was at the bash so that if the machine gets shut down for some reason, when it comes back up it will get the command hostname mydomain.com ?
Just bought today and got the same "not qualified" response. I have SUSE 9.3 with a fully functional domain name server on it that responds perfectly from outside the system. The host name "ns1" is set through SUSE and it appends the domain name to it to form the host name. I cannot fake anything. The host name and domain is legit and recognized by the whole world except Virtualmin.
What now?
Adam, John,
Look at the General Discussion Item
SuSE 10.0 install for some insight. I have had my system setup this way for about a month now with no problems.
John,
A diferent problem that might come up on SuSE is corvered in Closed bug #172. I have severl bugs in the tracker that deal only with SuSE. You might want to look over them.
At the resurgence of activity in this thread I was reminded that I hadn't actually uploaded the fixed install.sh version. That has now been done. hostname problems should no longer happen. I hope.
I know this check is a bit annoying, but things go wrong in a lot of places later on if this detail is not correct. It can be extremely time-consuming down the road to correct a hostname that is not fully qualified (and postfix will fail to operate correctly in many cases). Hand correcting, or even sed-correcting, dozens of incorrect BIND hosts files and troubleshooting the problems that arise before such corrections are made, among other things, is a mind-numbing bit of work that we'd all rather avoid.
As soon as I figure out a general way to set the hostname permanently on every OS we'll be supporting, I will add a step that allows folks to set the hostname during install, if one doesn't exist. That'll be nicer than just bailing.
--
Check out the forum guidelines!
what is the process of running this fixed install.sh file, do we just run it on top of the original and it will fix it, or do we have to unintall the existing virtualmin and then reinstall everything agaain including domains, backups of domains and mysql databases etc?
Hey Adam,
I'm confused...Is this a Virtualmin GPL installation we're talking about here? If so, the upgrade to Pro is not exactly smooth yet. I have new code going into the install.sh in a day or two (after a lot of testing) that will allow for minimal installation that doesn't touch any of your configuration or domains. As it stands now, there are problems with replacing a .wbm installed Virtualmin with an RPM-installed Virtualmin (this is RPM's fault, not really ours...it doesn't know about the existence of the .wbm installed files or the existing configuration files and so it doesn't respect them), and I <i>don't</i> recommend it on a production system. This is a very strong recommendation, not wishy-washy "well, if you really wanna try it you can" sort of recommendation, and that's why there's a big warning as the very first thing you see when you run the installer. Really, do not do an upgrade from GPL on a production system yet. I mean it.
If it's a Virtualmin Professional installation, then you never need to run the install.sh again (and you <i>really</i> don't want to after you've started adding domains). All upgrades are handled via RPM and yum/yast/up2date. The problem this thread is about would have prevented <i>any</i> installation, and so if you're past the installation it doesn't apply to you. All this issue does it prevent installation on some systems, and the installer bails with an error before even getting started.
That said, for any problems you do have after installation you can file an issue about them and I'll help resolve them. I believe I'm in the midst of working with you on an issue in the tracker at the moment, but I could be misremembering (I'm in the middle of several issues at the moment...it's Joe's Bugday today, it seems).
--
Check out the forum guidelines!