wtf?

sloth · Post by **sloth** » Mon Jun 10, 2002 9:42 am

Ok here's the deal. My bot was working just fine. Then the host box went down for a couple of days while the admin did God knows what to it. Now when I try to start the bot, I get this:

[10:59] * Hostname self-lookup failed.
[10:59] Attempt to kill un-allocated socket 0 !!

Obviously something has been changed on the host machine. My question is, where do i need to make this adjustment in the bot inorder for it to start, and what exactly does this mean?

Any help would be greatly appreciated, ty

Petersen · Post by **Petersen** » Mon Jun 10, 2002 10:21 am

you need to set the value of my-ip correctly (and put it before anything runs that requires an ip, eg listen ports)

sloth · Post by **sloth** » Mon Jun 10, 2002 6:00 pm

hmmm ok well would that be in my .conf? cuz like, i don't see anything there resembling "my-ip".

i don't understand how it is that the bot worked just fine several times before, and then after the host downtime, it didnt work anymore.
I have spoken with the administrator and he says nothing was changed, the box just crashed and was restarted when he returned home; yet, alas, me eggy still will not start now.
if all else fails i can always re-install it, but i want to know why this is and how to fix it so that in the future, i will have the diagnostic knowledge of the bot.
anyways, /me will go back to trying to locate the problem...

ppslim · Post by **ppslim** » Tue Jun 11, 2002 8:48 am

Read through the eggdrop.complete.conf file, and look at the section about my-ip

Most eggdrop's need this setting.

If the default route on a machine i setup as the local network, then this is the problemwith the system.

If you set the value of my-ip, then this issue will resolve itself.

A lot of systems require this.

sloth · Post by **sloth** » Tue Jun 11, 2002 2:53 pm

aight man that seemed to do the trick
thanx alot w00t!