Odd little Server connecting error

[Weirdo]

[11:07:07] <Minako> [11:07] #Weirdo# jump kazuko.faereal.net 6667
[11:07:07] <Minako> Jumping servers......
[11:07:08] <Minako> [11:07] Trying server kaz:6667
[11:07:08] <Minako> [11:07] Failed connect to kaz (DNS lookup failed)

Am running Eggdrop 1.6.15, anyone else getting this peculiarity? Any ideas how i can fix it?

Oh, and it seems like it doesnt affect Windrop 1.6.13 at all

[11:10:30] <Natsuki-Chan> [11:10] Trying server kazuko.faereal.net:6667
[11:10:31] <Natsuki-Chan> [11:10] Connected to kazuko.faereal.net
[11:10:31] <Natsuki-Chan> [11:10] -NOTICE- *** Looking up your hostname...
[11:10:31] <Natsuki-Chan> [11:10] -NOTICE- *** Checking Ident
[11:10:31] <Natsuki-Chan> [11:10] -NOTICE- *** Found your hostname

Veeery random

[caesar]

Is the dns module loaded on the 1.6.15? Also, do they run from the same box? If not, this can be a server dns problem, not necesarly an eggdrop one.

[Weirdo]

Two completely different machines. Dont have admin access at all to the server that Minako is hosted on. The DNS module is loaded tho

[corax]

[11:07:07] <Minako> [11:07] #Weirdo# jump kazuko.faereal.net 6667
[11:07:07] <Minako> Jumping servers......
[11:07:08] <Minako> [11:07] Trying server kaz:6667
[11:07:08] <Minako> [11:07] Failed connect to kaz (DNS lookup failed)

Am running Eggdrop 1.6.15, anyone else getting this peculiarity? Any ideas how i can fix it?

This is neither a DNS problem nor an eggdrop problem. I've been trying to resolve the same thing on my home system, seems like forever now. This is an OS problem, but damned if I can figure out where it is. I recompiled TCL, upgraded my cron, nothing I have tried has changed a thing.

Modify your crontab entry so it will mail you the bot's output before it goes into background; you will probably find that it says it is listening on a port number one higher than your config file states. Internally, however, it thinks it is listening on the correct port. If you run something like ethereal or tcpdump, you will find the bot is sending TCP traffic OK, but it isn't receiving a damn thing --again, because the return traffic is coming in on a port one higher than the bot is listening to.

However, run the damn thing from the commandline, and it will probably run OK -- mine does.

Curiously, however, I wrote a short TCL test script that listens on a port, and sends a reply if it hears anything on that port -- works just fine from a crontab.

I've tried several bot versions -- 1.6.5, 1.6.13, 1.6.15, and even 1.4.5 -- I have tried running them all with and without the autobotchk script -- and they all behave the same way.

[]Kami[]

I haid same problem couple of time, try jump again and problem will dissapire i think i did this and problem was over

Greetings

[Ctho]

I have a somewhat different problem..not sure if it is related or not. Mine says Invalid namespace. I set my server in the server:port:password format. not sure what's wrong now. I looked for extra spaces but can't find any...Any ideas????

[qriff]

I've got the same problem last week.
I have narrowed down the reasons,
I originally transfered my custom configfile (.conf * 1)
to another machine with a fresh eggdrop install.

When I run eggdrop with the custom configfile,
I get this (DNS lookup failed),

BUT

when I run eggdrop with the original configfile,
there's NO problems.

The major difference I've found between theese two files
are the added ipv6 lines

# If you're using IPv6 support, set the IPv6 IP address and hostname to bind to
# here. You still need to set my-ip.
#set my-hostname6 "virtual.host.com"
#set my-ip6 "2001:1:1:1::1"

that weren't! in the first "Eggdrop 1.6.15" release.

---
---

"I would like to know when someone tweaking the source would mind adding at least some diagnostics with the generally worst problem with eggdrop, LINKING!!! =)

Ever seen the following...? >)
[02:42] Linked to bot_1.
[02:42] Downloading user file from bot_1
[02:42] Lost userfile transfer from bot_1; aborting.
[02:42] (Userlist download aborted.)

*duh* We know its lost, what about some reasons..."

[gumbydammit]

heh its definately a dns problem...
1) on a unix box... edit /etc/resolv.conf and put a valid nameserver
2) on a windows box.. edit resolv.tcl (comes with your windrop i believe)
3) if both 1 and 2 are done.. your nameserver is probably just down for the time being.. use another one.. or wait

if you have no access to change resolv.conf on your shell.. well talk to your sysadmin.. in the meantime dont use hostnames for servers.... and it should work.. this is a bandaid.. not a fix by any means.

.jump 55.66.77.88 6667 instead of .jump the.ircd.server 6667

[Alchera]

I get the same problem on the rare occasion when connecting to DALnet servers, I just either rehash the bot or restart it and it then reconnects to the server I originally intended it to connect to. Seems to happen after DALnet has had some drama I noticed.