Hostname self-lookup failed.

[prefect]

Now, before you go "OMG READ TEH FAQ", read the whole post.

I only get the Hostname self-lookup failed error. I do not get the message about killing unallocated socket. This is what I've tried:

1. Tried using only my-ip "correct.ip"
2. Tried using only my-hostname "correct.hostname"
3. Tried using both my-ip "correct.ip" and my-hostname "correct.hostname"
4. Tried using my-ip "correct.ip" and my-hostname "localhost"
5. Tried using my-ip "127.0.0.1" and my-hostname "correct.hostname"
6. Tried using my-ip "127.0.0.1" and my-hostname "localhost"
7. Tried adding host and ip in /etc/hosts

Also:
* Host resolves fine on the box itself. The ip resolves fine on the box itself.
* The box is, of course, not nat'ed. The ip is bound to eth0:3 and works fine both ingoing and outgoing with other applications.

I've used eggdrops since the dawn of time, but I still can't get this one working :)
Any help would be appriciated.

[Ofloo]

Not sur what you looking for but you can use to get your ip like this i do it like this i know its not perfect but .. but if you do bump into a perfect sollution plz post it tnx

Code: Select all

set MyIP "" 
foreach a {a b c d e f g h i j k} { 
    catch { 
   set external [socket $a.root-servers.net 53] 
   set MyIP [lindex [fconfigure $external -sockname] 0] 
   close $external             
  } 
if { ![string equal $MyIP ""] } { break } 
}

Or

Code: Select all

proc myIP {} { 
    set s [socket -server "" -myaddr [info hostname] 0]; 
    set ip [lindex [fconfigure $s -sockname] 0] 
    close $s 
    set ip 
} 

[prefect]

Oh, maybe I was unclear.

The bot does not start and it gives me the hostname self-lookup failed.

[egghead]

Oh, maybe I was unclear.

The bot does not start and it gives me the hostname self-lookup failed.

What if you do not set "my-ip" and "my-hostname" i.e. leave them commented out?

[egghead]

Oh, maybe I was unclear.

The bot does not start and it gives me the hostname self-lookup failed.

Are you saying the bot dies? Or it won't connect to IRC?

[prefect]

Oh, maybe I was unclear.

The bot does not start and it gives me the hostname self-lookup failed.

Are you saying the bot dies? Or it won't connect to IRC?

What if you do not set "my-ip" and "my-hostname" i.e. leave them commented out?

No dice

[egghead]

Oh, maybe I was unclear.

The bot does not start and it gives me the hostname self-lookup failed.

Are you saying the bot dies? Or it won't connect to IRC?

What if you do not set "my-ip" and "my-hostname" i.e. leave them commented out?

No dice

So, with the settings given in your original post or without any settings for my-ip and my-hostname, the bot dies?

If you start the bot from the shell, can you paste say the last 10 lines the bot reports in the shell?

[prefect]

So, with the settings given in your original post or without any settings for my-ip and my-hostname, the bot dies?

If you start the bot from the shell, can you paste say the last 10 lines the bot reports in the shell?

I think you missed my "i've been running eggdrops since the mid 90s"'s comment, but I appriciate you trying to help.

The bot does not die. It never gets the chance to die, cause it never starts. And the error-msg is, as stated, hostname self-lookup failed:

Eggdrop v1.4.5 (c)1997 Robey Pointer (c)1999, 2000 Eggheads
[14:14] --- Loading eggdrop v1.4.5 (Sun Aug 10 2003)
[14:14] Module loaded: channels
[14:14] * Hostname self-lookup failed.

And don't preach to me that 1.4.5 is old and that I should run 1.6.x. 1.6.x seem to have forgotten that it's supposed to be a stable branch with developers doing heavy modifications that breaks the bot, i.e. 1.6.15

[bobjuh]

And don't preach to me that 1.4.5 is old and that I should run 1.6.x. 1.6.x seem to have forgotten that it's supposed to be a stable branch with developers doing heavy modifications that breaks the bot, i.e. 1.6.15

is 1.4 series still supported here ?

[caesar]

If you don't *like* the .15 then try the .13 version. I haven't got problems with this version.. Untill now it seemed to be perfect for me.

[prefect]

If you don't *like* the .15 then try the .13 version. I haven't got problems with this version.. Untill now it seemed to be perfect for me.

No, I will not use a branch of eggdrop thats supposed to be stable, but where the developers decide to drasticly alter things. Things that ends up breaking the bot.

But if 1.4.5 (which is a good, stable bot with no known vulnerabilities (which haven't been the case with the 1.6.x tree)) isn't supported here, I'll seek help elsewhere.

[egghead]

I think you missed my "i've been running eggdrops since the mid 90s"'s comment, but I appriciate you trying to help.
And don't preach to me that 1.4.5 is old and that I should run 1.6.x.

I don't care how long or short you have been running eggdrop bots. You came here for help, which people try to give. Instead you now turn on an attitude which is barely appreciated.

1.6.x seem to have forgotten that it's supposed to be a stable branch with developers doing heavy modifications that breaks the bot, i.e. 1.6.15

Nobody forces you to run an 1.6.x bot.

However, your preference to make unsupported statements (especially about vulnerabilities) is extremely unhelpfull to current and future eggdrop developments.

I'll seek help elsewhere.

Yes, please, feel free to do that. Thank you and goodbye.

!next

[Ofloo]

lol

[prefect]

I don't care how long or short you have been running eggdrop bots. You came here for help, which people try to give. Instead you now turn on an attitude which is barely appreciated.

Agreed. I'm sorry for my attitude there.