Date: Sun, 23 Jun 2002 03:12:12 -0500 From: Redmond Militante <r-militante@northwestern.edu> To: Jon Noack <noackjr@compgeek.com> Cc: freebsd-questions@freebsd.org Subject: Re: problem installing mysql323-server from ports Message-ID: <20020623031212.A11462@darkpossum> In-Reply-To: <NFBBIJDHKLKEJHKFMLBHEEMDCBAA.noackjr@compgeek.com>; from noackjr@compgeek.com on Sun, Jun 23, 2002 at 12:35:30AM -0500 References: <20020622232907.A11042@darkpossum> <NFBBIJDHKLKEJHKFMLBHEEMDCBAA.noackjr@compgeek.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi thanks for helping me out. On Sun, Jun 23, 2002 at 12:35:30AM -0500, Jon Noack expatiated with great perspicuity: > > Sorry, the host 'fisk246150' could not be looked up. > > i type 'hostname' and i get the correct hostname. > It would be nice if you told us what 'hostname' returns, but I will assume > your hostname is "fisk246150" based on the error above (or > fisk246150.your.domain). > > > the first 2 lines in my /etc/hosts is > > ::1 localhost localhost.my.domain > > 127.0.0.1 localhost localhost.my.domain > Why do these lines matter? While they are necessary and correct, what you > need is an entry in hosts for "fisk246150". Something like: > > BAD = 1.2.3.4 fisk246150.your.domain > GOOD = 1.2.3.4 fisk246150 fisk246150.your.domain > > Actually, if you have a BAD entry, that could cause problems if the script > is using 'hostname -s', because it would trim the domain info off (to form > "fisk246150") and then try to look that up. That lookup would fail, because > just "fisk246150" is not present in the hosts file and DNS will obviously > fail as well. changing my hosts file like you said did it. thanks > > > i did an nslookup on myself and it gives me the > > right hostname. > Again, don't just tell us it's correct -- tell us something like "'nslookup > fisk246150' correctly returns 1.2.3.4". That is actually helpful. As you > are having problems, anything you *think* is correct may not actually *be* > correct (or show symptoms of the true problem). Give us the raw data *and* > your interpretation -- that gives us the chance to get an objective view of > the situation and see what you're thinking. This often allows us to correct > the problem and give you pointers on how to approach problems in the future. > > The error was that it couldn't look up "fisk246150". Please send us the > output of the 'hostname' and 'nslookup' commands and something meaningful > from your hosts file (the localhost info is present on every FreeBSD box). > > I definitely appreciate that you attempted to solve the problem before > posting to the list. I also understand that if you've been working for a > while that the little things seem insignificant and can be glossed over. > Try not to give in to that and post as much info as you can. > yep. long day :) thanks again r. > Jon > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9FYLYFNjun16SvHYRAjBDAJ9Or1qkG41VkozvqFFUPjxzOvujWACghbnq OVHCJocQ5nSccrU8gTcMW2U= =OFJb -----END PGP SIGNATURE----- [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE9FYLcFNjun16SvHYRAv8uAJ9S7RGGs+Qz64e55h3L8SOEPqXT+ACgi0l4 SkbT4W9hkSoU8Cwal7g0Bjc= =E6I/ -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020623031212.A11462>