Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[digitally drunken]

Hey there:
for all, who have problems with amule, because it cant connect:
(cant find official-hostname... / error 22)

Here is the way to fix it:


1. starting the application "Terminal"
2. by type "hostname" you can find out, whats your hostname
3. type "sudo pico hostconfig" (opens hostconfig)
4. you have to type your password eventually
5. change the line "HOSTNAME=-AUTOMATIC-" to "HOSTNAME=myname" (if this line isnt already there, just write it...)
6. save (Ctrl-O) and close (Ctrl-X)

7. starting the application "NetInfo Manager"
8. go to "machines"
9. go to "localhost"
10. make shure, that this window is not locked (in the left bottom)
11. type "apple-D" for duplicating the "localhost"-entry
12. klick on the "localhost copy" entry
13. then choose the value for the field 'name'
14. here you have to type in the name that you have choosen in the "hostconfig" (in this example: "myname")
15. restart... and it wil work!

after this, amule is working pretty well and your hostname is not automatic given by your router, etc...

it is working pretty well at my computer (but i wont to give a garuantee for it)

and i hope, ich could help some people with this thread

good luck

[lionel77]

I'm a little confused. I thought the "can't find official hostname" message was benign and could be safely ignored. But now you are saying that the message is accompanied by actual problems with connecting to clients/servers?

If that's really the case we should definitively try to find a solution that does not require a workaround using the Terminal.

Thanks by the way, for figuring this out.

[digitally drunken]

Yes, cause many people have this problem I think.
I, for example needed a lot of time to find this error! And especially since version 2.1.1 (where the error-message for the error 22 is disabled...) it ist a way harder to find the roots of the problem, your amule isnt connecting to any server. (I found a lot of people in different boards, all having the same problem)
But since this configuration everything is working fine!

[lionel77]

Thanks a lot for the explanation. Looks like we definitively need to do something about this.

/me rubs his ken summoning lamp...

[ken]

Hmm.   I thought it was benign.  Unfortunately, I don't really have time to devote to figuring this out.

/me strikes his Kry-summoning gong

[mindreaper]

I've done everything just like you mention, and I still get the same error message (cannot get the official hostname. Error 22: invalid argument)

First I've looked for my hostname, which is telenetPC.
In the "hostconfig" window of terminal, I have typed HOSTNAME=telenetPC
And now everytime I open that window, it does say HOSTNAME=telenetPC

I've also done what you said in NetInfo Manager, and now in the list of machines I have one that appears under the name telenetPC.

So have I done anything wrong?

[verdun1916]

Great work! Thank you sooo much! I searched so long, why aMule won't connect, I was getting crazy. With your help the Problem is fixed now! Thanks a lot!!!

[mouloud]

works fine for me (Mac OS 10.4.6 - amule 2.1.3) thanks !

[obis]

First off, for those who don't know, hostconfig is a file in /etc.

Second, you can do this in a more straightforward way (I think) by just:

1) Edit the /etc/hostconfig file. Look for the line starting with HOSTNAME and change it to HOSTNAME=mymac
You'll probably have to add the HOSTNAME line

2) Edit the /etc/hosts file. The first line should be "127.0.0.1 localhost". Add the same hostname you used above to the end of this line, "127.0.0.1 localhost mymac".

And finally, WTF? Why did the aMule developers suddenly stop respecting the hostname set by the system and require it to be set this way?

[wuischke]

And finally, WTF? Why did the aMule developers suddenly stop respecting the hostname set by the system and require it to be set this way?

*peep*
Visit wxwindows.org and blame them.

[BlackLeopard]

I am trying to do what you are saying but nothing happens.  Is there another way to do it?

[lionel77]

Originally posted by ken
/me strikes his Kry-summoning gong

I am starting to suspect that my ken-summoning lamb works better than your kry-summoning gong...

[ken]

If you're rubbing a lamb, well, that's just...  wrong.  

[lionel77]

lol

Well...moving on...

I hope that we can get Kry interested in this issue once his moving situation is worked out, as there seem to be quite a number of users affected by it.

[jochen]

I found that this problem (can't connect to any server) appears when I assign a static IP and hostname via DHCP (static DHCP on my router). If I leave the hostname field on the router empty, amule works as normal.

Edit: it also works if you use a hostname with suffix ".local" in static DHCP hostnames.