egghelp/eggheads community

Eggdrop Timeouts

2004-12-07T01:43:52-04:00

you need to set my-ip correctly; nat-ip concerns sharing userfile and offered dcc chats only, not outgoing connections

try to use an IRC client from your shell and see what happens; I suspect the problem you've been experiencing is not bot-related

Statistics: Posted by demond — Tue Dec 07, 2004 1:43 am

Eggdrop Timeouts

2004-12-07T00:14:11-04:00

Continuing...
I don't know if this is if use but, I tried playing with some of the conf settings and connecting to a different server in our network, using the numeric IP. Although the bot never connected, this time the log showed errors....

[22:58] (@) EOF socket 4, not a dcc socket, not anything.
[22:59] Trying server [edited to hide IP]:6667
[22:59] Failed connect to [edited to hide IP] (Invalid namespace)
[22:59] (@) EOF socket 4, not a dcc socket, not anything.
[22:59] Trying server [edited to hide IP]:6667
[22:59] Failed connect to [edited to hide IP] (Invalid namespace)
[22:59] (@) EOF socket 4, not a dcc socket, not anything.
[22:59] Trying server [edited to hide IP]:6667
[22:59] Failed connect to [edited to hide IP] (Invalid namespace)
[22:59] (@) EOF socket 4, not a dcc socket, not anything.

Statistics: Posted by MiNdErAsR — Tue Dec 07, 2004 12:14 am

Eggdrop Timeouts

2004-12-06T22:34:38-04:00

experiment by starting the bot with -nct command line options (don't go into background, emulate dcc chat on terminal) and monitor what's happening

The bot ran normally up until it timed out again. Last entries in terminal were as follows...
[19:03] Writing user file...
[19:03] Writing channel file...
[20:03] Writing user file...
[20:03] Writing channel file...

From one of the chatrooms it sits in...
[21:21:22] Locutus «Locutus@borg.cube» has Quit iRC (Client exited)

At this time I got a notice that ssh connection had terminated. Upon logging back in I found the bot was no longer running. The tail of the log was as follows...
[20:03] Writing user file...
[20:03] Writing channel file...
[21:03] Writing user file...
[21:03] Writing channel file...
[21:20] * END OF FILE ON TERMINAL

As an aside, I had commented out set my-hostname and set my-ip and entered the IP address under set nat-IP (prior to starting the bot with -nct), thinking maybe this was the problem. Evidently not. I'm at a loss here.

Statistics: Posted by MiNdErAsR — Mon Dec 06, 2004 10:34 pm

Eggdrop Timeouts

2004-12-04T17:23:59-04:00

experiment by starting the bot with -nct command line options (don't go into background, emulate dcc chat on terminal) and monitor what's happening

Statistics: Posted by demond — Sat Dec 04, 2004 5:23 pm

Eggdrop Timeouts

2004-12-04T16:09:30-04:00

Let me see if I can make myself clear, sorry if I was confusing. The initial problem was the eggdrop (connected locally) timing out and failing to rejoin, with nothing showing in the log. At one point I happened to be connected to the bot thru a dcc chat window when it happened. The bot was unresponsive, yet was still running when checked in the shell. At this point I have to kill the pid and restart the bot.

As suggested, I tried altering the config so the bot would connect to another server on the network. This time the logs showed the connect attempts timing out. I tried using both server names and IP addresses including ports, to no avail. This does indeed point to the firewall as the likely suspect, but I was under the assumption that firewalls blocked incoming and not outgoing connections? Could there be something misconfigured in the conf that I'm missing?

Thanks again for the help.

Statistics: Posted by MiNdErAsR — Sat Dec 04, 2004 4:09 pm

Eggdrop Timeouts

2004-12-04T02:17:54-04:00

you said the opposite

if you meant only local connection problems, then:
most likely screwed (misconfigured) local name server, which takes forever to reverse resolve IPs

if you really meant connection problems anywhere but local:
the most probable reason for that would be your firewall

Statistics: Posted by demond — Sat Dec 04, 2004 2:17 am

Eggdrop Timeouts

2004-12-04T00:13:18-04:00

Interesting...the bot times out trying to connect anywhere else but local. What am I missing?

Statistics: Posted by MiNdErAsR — Sat Dec 04, 2004 12:13 am

Eggdrop Timeouts

2004-12-03T22:24:48-04:00

unload all scripts and monitor the bot's behaviour

try to connect it to other servers, non-local

Statistics: Posted by demond — Fri Dec 03, 2004 10:24 pm

Eggdrop Timeouts

2004-12-03T17:47:56-04:00

I've searched the forums and read the FAQ but was unable to come up with a similar situation, so here goes...

Running v1.6.17, both my-hostname and my-ip are set, never give up is enabled, server cycle wait set to 20, servers are set to my domain name and the IP (I'm running the ircd). The bot times out ocassionally, but fails to return. It's happened while I was connected (dcc chat console) but the bot was unresponsive to commands. I find the bot running in the shell, and have to kill the pid and restart so it connects. Nothing shows up in the log when it times out. Any ideas on what is going on here?

TIA

Statistics: Posted by MiNdErAsR — Fri Dec 03, 2004 5:47 pm