Some bots aren't linking

[rsdl]

Hey,

I have 8 bot configurations running on the same box. I have linked them together using Slennox's tutorial. It works well for the first two to three reboots after that all hell breaks lose. Only 5 bots get linked together while leaving out the other three. does anyone know how to diagnose this problem? or know of a solution?

thanks in advance

-rsdl

[ppslim]

Are they all by any chance, trying to use a single userfile.

Even if they are on the same box, they must all user seperate files.

[rsdl]

nope. everything's seperate. by user file you mean "user.botname" right?

-rsdl

[Photon]

Yes to the user.botname...

out of interest, what address have you set for the bots in each other - the external or internal IP?? (or of course local loopback...)

You have got them all set on different ports as well, dontcha?

P.

[ppslim]

The fact they operate correctly, then fail ater reboots, usualy rules out such settings.

However, system changes between reboots can affect a lot of things.

WHat has been changed between these reboots?

What operating system are you running them on?

Do the bots actualy start up, wihtout error?

WHat are the differances between config files? IE, is it simply a fact of changed values for nick, and file names.

DO you get any errors when manualy linking.

[Photon]

Hmmm .. true - speaking as someone with multiple bots on one machine, until I set the hostmasks pretty strictly I did have some hassles, where it kept complaining during linking that it was getting an imposter. (one bot not the other it was looking for).

This was even with the bots on different ports, and usually after one or the other bots had been seperately rebooted, not the machine... but it could possibly be related.

Make sure that one bots hostmask does not match the other, and vice versa ... *!*@foo.blah is a BAD hostmask, but the standard one that will be given.

[ppslim]

When linking, hostmasks do not come into plan, unless you have strict telnet and that is use.

The imposter message would happen in this circumstance.

BotA - Name: BotA - Has a record called BotB with IP and port information

BotB - Name: eggdrop - Has a record called BotA with IP and port information

If you type ".link botb" in BotA, a connect takes place. BotB will say he is called eggdrop, in the handshake message. However, BotA was expecting him to say BotB, as this is what he thinks he is called. As such, BotA now thinks BotB is an imposter and unlinks it.

If I did a ".chhand botb egdrop" in BotA, then tried ".link eggdrop", all will work well,a s the names now match.

If it is a hostmask issue dropping the connection, the connection literaly drop, wihtout warning as such.

[rsdl]

thanks for the reply.
no, i didn't do any system changes at all. i just rebooted them. and the bots config files are exactly the same, only bot names have been changed. also, the os i'm running the bots on, including the ircd server is FreeBSD 4.7.
WHen you say manually linking you mean i go /ctcp to one of the hub bot and do .link bot ? if so, then this is the error i get:


[03:13] Linking to Aegir at irc.digitalfoundry.ca:3333 ...
[03:13] Telnet connection: h24-80-29-100.vc.shawcable.net/1052
[03:13] Ident failed for h24-80-29-100.vc.shawcable.net: Connection refused
[03:13] Refused telnet@h24-80-29-100.vc.shawcable.net (invalid handle: Helios)
[03:13] Lost Bot: Aegir


as for the ports, all bots are listening to different ports.

[ppslim]

Then you are experiencing thissues discribed above, in regards to imposters.

There is allways 2 bots involved in linking, one to make the link, the other to receive. Look in the second bot, and see the error message posted.