Bot just stopped working.........sorta

[DrTongue]

Ok, in a nutshell. Bot has been working fine for a LONG time. During the night, it 'pinged out' and has yet to return online. Have ssh'd to the shell, re-started the bot, I get the usual 'start up' dialog confirming launched into the background, but the other bots that are usually linked to it don't even try to link and when done manually, it times out. I've even tried to telnet connect, which also times out. It's like it's online, but NOT working. Nothing was changed settings wise, it just simply pinged out. Also, there is another bot on this shell that is on another network and it is working just fine. I understand that no one can probably tell me "This is the problem, do this and it'll fix it".....but can anyone at least point me in the right direction as to what to look for to find out what has caused this?

Thank you.

[strikelight]

The ip the bot uses may have changed or been null-routed...
Confirm the my-ip setting, and if the machine uses vhosts, try using a different vhost for your my-ip/my-hostname settings.

Also, if telnetting fails, and you want to see what is going on,
start your eggdrop up so it doesn't go into the background by using the -n switch... (./eggdrop -n)

[DrTongue]

Thank you Sir, that was it. The vhost was/is still listed on the shell, but I swithced IP's and the vhost and it popped up right on line. Thank you again.