This is the new home of the egghelp.org community forum.
All data has been migrated (including user logins/passwords) to a new phpBB version.


For more information, see this announcement post. Click the X in the top right-corner of this box to dismiss this message.

Eggdrop not connecting anymore

Old posts that have not been replied to for several years.
Locked
F
Feanixxx
Voice
Posts: 23
Joined: Sun Jul 27, 2003 11:30 am

Eggdrop not connecting anymore

Post by Feanixxx »

Hi all

I've had an eggdrop running for some months.

Yesterday it pinged out and, since then, just cycles through its server list, always displaying the message: "Timeout: connect to abc.server.xyz" where "abc.server.xyz" is one of the servers on its list.

I've restarted but to no avail.

Any clues or suggestions as to what has changed/gone wrong?

Thanks
User avatar
Sir_Fz
Revered One
Posts: 3794
Joined: Sun Apr 27, 2003 3:10 pm
Location: Lebanon
Contact:

Post by Sir_Fz »

was the server lagged at the time, or maybe your shell was lagged ?

try to kill the bot, and start it again.
F
Feanixxx
Voice
Posts: 23
Joined: Sun Jul 27, 2003 11:30 am

Post by Feanixxx »

Thanks for that - I've just killed it and restarted but it still times out trying to connect. It's been like it for 24 hours now.

Could it be a shell problem i.e. shell lost IRC connection or such?
User avatar
strikelight
Owner
Posts: 708
Joined: Mon Oct 07, 2002 10:39 am
Contact:

Post by strikelight »

Wrong forum for this but...

Check your my-ip settings in your .conf .. It could be your shell provider got a new subnet and thus ip's possibly changed.
It could also be that the admin has null routed the ip you are using due to DDoS attacks, in which case you should use a different vhost/ip.

If this doesn't work, you should speak to your shell admin.
F
Feanixxx
Voice
Posts: 23
Joined: Sun Jul 27, 2003 11:30 am

Post by Feanixxx »

Hmm, how odd, this was showing on the eggdrop forum then vanished and reappeared here! Whatever. .

Yes, thank you for that, I shall check the Vhosts and also check with the shell provider to see if anything has changed.

UPDATE:

I removed the VHost the bot was using in My-IP as you suggested and it connected fine. The shell has obviously been messing with the VHosts.

Many thanks
Locked