aMule Forum
English => aMule Help => Topic started by: macias on January 09, 2006, 10:27:52 AM
-
Hi there,
aMule 2.0.3 -- no problems. I've just upgraded to aMule 2.1.0 and when I am starting it there is a message saying "Cannot get the official hostname". What does that mean and how I can fix it?
OSSuSE 10.1A3.
thanks for your help
bye
PS. Besides that everything works fine.
-
Set a hostname for your box?
-
Originally posted by Kry
Set a hostname for your box?
You mean:
macias@flatline:~> hostname
flatline
? So, it was and it is set. As I said, with aMule 2.0.3 no such problems.
have a nice day
bye
-
Yeah well 2.0.3 is not the same as 2.1.0. the wxWdigets wxGetFullHostname call is obviously failing in your box for some reason.
-
*shamelessly copy'n'pasting*
lionel77 wrote somewhere else:
The "Cannot get the official hostname" error seems to only show up on a small number of machines and we haven't figured out yet what the reason for this is (see here (http://forum.amule.org/thread.php?threadid=7587&boardid=49)).
For now I would suggest the following temporary workaround:
- open the Terminal (in /Applications/Utilities)
- paste "sudo hostname mydnsdomain" and hit return
- then enter your admin password and hit return again
Unfortunately, you have to do this after each reboot of OS X until we provide a fixed version. On the positive side you are not making any permanent changes to your system with this workaround.
-
The problem is that wxGetFullHostname requires that the hostname be a fully-qualified domain name. So, instead of "flatline", it would have to be "flatline.somedomain.sometld".
And, by the way Kry, eat your words (http://forum.amule.org/thread.php?postid=47985#post47985). :P
-
I don't have a FQDN and it works here.
-
Originally posted by ken
The problem is that wxGetFullHostname requires that the hostname be a fully-qualified domain name. So, instead of "flatline", it would have to be "flatline.somedomain.sometld".
Wait, why does the "sudo hostname mydnsdomain" workaround work then? That's not a FQDN, right?
-
I don't think "mydnsdomain" was meant to be taken literally. The user who issues this command is meant to substitute their computer's (fully-qualified) domain name.
-
OK, I've reduced the severity of this problem. The message should now just print to the aMule log instead of putting up a dialog box.