heres a log...
[12:44:15] * Xero (~Xero@win-150-59.home.cgocable.net) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * Dr_Pepper (Techdude@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * Jossabot (PennyLane@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * BlaatBot (PennyLane@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * NiKKiBoT (PennyLane@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * w00h00 (PennyLane@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * Grass (PennyLane@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * Stinky (PennyLane@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * Maantje (PennyLane@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * Sterretje (PennyLane@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * BunnY (~baby_rikku@win-201-32.tnt2.bel-air.md.da.uu.net) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:15] * DevNull (DevNull@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * Adam (someone@win-100-134.cpe.net.cable.rogers.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66z (~RX-66z@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66y (~RX-66y@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66x (~RX-66x@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66w (~RX-66w@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66v (~RX-66v@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66u (~RX-66u@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66t (~RX-66t@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66s (~RX-66s@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66r (~RX-66r@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66q (~RX-66q@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66p (~RX-66p@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66o (~RX-66o@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66n (~RX-66n@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66m (~RX-66m@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66l (~RX-66l@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66k (~RX-66k@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66j (~RX-66j@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66i (~RX-66i@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66h (~RX-66h@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66g (~RX-66g@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66f (~RX-66f@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66e (~RX-66e@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66d (~RX-66d@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66c (~RX-66c@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66b (~RX-66b@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * RX-66a (~RX-66a@Bots.WorldIRCNet.com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * Void (~Void@win-224-85.kabel.telenet.be) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * Mountain_Dew (~Mountain_D@win-224-85.kabel.telenet.be) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:16] * TechBot (~TechBot@Bots.WorldIRCNet.Com) Quit (staff.Worldircnet.com Belgium.WorldIRCNet.Com)
[12:44:25] * BunnY (~baby_rikku@win-201-32.tnt2.bel-air.md.da.uu.net) has joined #techdude
[12:44:26] <@G> [JuLiE] o.o
[12:44:51] <@Techdude> grrrrrrrr ba
...
[12:45:42] * Dr_Pepper (Techdude@Bots.WorldIRCNet.com) has joined #techdude
...
[12:57:22] * LoLBot sets mode: +l 26
...
[13:00:22] * Tokes sets mode: +l 66
[13:01:17] * Dr_Pepper sets mode: +l 27
[13:02:23] * Lamer sets mode: +l 66
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.
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.
chanlimit sets wrong limits after netsplit
Netsplits are not propergated the same to all IRC servers.
Due to speed/bandwidth restrictions, servers may be setup, so that the recieve netsplits at a certain speed.
They may not send messages to channels regarding the split ont hat server, to reduce A: server load, B: bandwidth. In witch case, they will be marked officialy as quit, after a timeout period.
There are obviouly 2 limit scripts in operation. Which on is which? IE, which one is making which limit change. Are they even the same type of bot (are they both eggdrop?)?
It depends where they get the information regarding the ammount of users in the channel.
OK, back to the causes
2 bots, each on different servers.
1st server shows a netsplit as a quit, with the 2 servers in the quit message.
2nd server just shows a quit (not all servers tell you it's a netsplit, or least in a way eggdrop detects (eggdrop only detects the first method))
As such, the 2 bots have different records. One knows there are 66 users (this is correct. once the split comes back, the limit should be such,t hat they can gain entry), the 2nd doesn't know, as far as it's aware, the users all quit, and are not coming back.
I would sugest that either this is the cause, or that another client is not detecting netsplits, and setting modes inappropriatly.
As such, setting the channel +l 66 was the right answer.
Due to speed/bandwidth restrictions, servers may be setup, so that the recieve netsplits at a certain speed.
They may not send messages to channels regarding the split ont hat server, to reduce A: server load, B: bandwidth. In witch case, they will be marked officialy as quit, after a timeout period.
There are obviouly 2 limit scripts in operation. Which on is which? IE, which one is making which limit change. Are they even the same type of bot (are they both eggdrop?)?
It depends where they get the information regarding the ammount of users in the channel.
OK, back to the causes
2 bots, each on different servers.
1st server shows a netsplit as a quit, with the 2 servers in the quit message.
2nd server just shows a quit (not all servers tell you it's a netsplit, or least in a way eggdrop detects (eggdrop only detects the first method))
As such, the 2 bots have different records. One knows there are 66 users (this is correct. once the split comes back, the limit should be such,t hat they can gain entry), the 2nd doesn't know, as far as it's aware, the users all quit, and are not coming back.
I would sugest that either this is the cause, or that another client is not detecting netsplits, and setting modes inappropriatly.
As such, setting the channel +l 66 was the right answer.
-
LLifeAdeth
Chanlimit is killing me!!!
problem #1
Undernet is not having a good year. The net splits are very often and are playing havock on my channels. The bots fail to recognize and set proper chanlimits for netsplits. My channel users are getting locked out of the channel due to the bots not being able to react properly to netsplits and setting the chanlimit to low levels.(sure they fix this after a few min but by that time another net split has occured and now its evan more jacked up)
Problem #2
For no reason that i can figure out the bots sometimes just decide to keep uping the chanlimit, usally by increments of 10. The channel may only have say 200 users but the bots set the channel to 6 over according to the chanlimit settings. so now its 206 as it should be. then a bot will continue to set 216...then 226 and so on. I cant figure it out. I restart the bot and its fixed(rehash dont fix it). sometimes it dont happen again for a month or 2 sometimes it just keeps doing it and then fixes its self. What info/logs do you need to try to figure this thing out.
I beg you slennox please bump this up on your priority list. We need a better chanlimit! especially to fix problem #1.
....I'll stop crying now..
Life
Undernet is not having a good year. The net splits are very often and are playing havock on my channels. The bots fail to recognize and set proper chanlimits for netsplits. My channel users are getting locked out of the channel due to the bots not being able to react properly to netsplits and setting the chanlimit to low levels.(sure they fix this after a few min but by that time another net split has occured and now its evan more jacked up)
Problem #2
For no reason that i can figure out the bots sometimes just decide to keep uping the chanlimit, usally by increments of 10. The channel may only have say 200 users but the bots set the channel to 6 over according to the chanlimit settings. so now its 206 as it should be. then a bot will continue to set 216...then 226 and so on. I cant figure it out. I restart the bot and its fixed(rehash dont fix it). sometimes it dont happen again for a month or 2 sometimes it just keeps doing it and then fixes its self. What info/logs do you need to try to figure this thing out.
I beg you slennox please bump this up on your priority list. We need a better chanlimit! especially to fix problem #1.
....I'll stop crying now..Life
I spent about half an hour writing a "solution" only to find the script already deals with splits in the same way already (though without the verification function of the new thing I did).
Everything depends on your bot's wait-split setting (currently 600, or 10 minutes, by default). For splits that are shorter than 600 seconds, the bot still sees the split users as being on the channel, and chanlimit.tcl should too, so it should not reduce the limit as if they'd all just quit. If they don't rejoin from the split before the 600 seconds is up, they are "lost" in the netsplit and chanlimit will calculate the limit as if they're no longer on the channel. If they do rejoin from the split before 600 seconds is up, the script should act as if they'd never left.
In short, if there are no single splits lasting longer than 10 minutes, there shouldn't be any problem. If the network is commonly experiencing longer splits, increase your wait-split setting to 900 or 1200. And if servers are splitting for an hour or more, there's not much you can do (with splits lasting that long, I don't see the limiting being frequent enough to causing real disruption anyway).
If it doesn't work in practice as I'm describing here then something else is wrong. Incidentally, your second problem sounds completely alien to me. What version of chanlimit.tcl are you using and is it unmodified?
Everything depends on your bot's wait-split setting (currently 600, or 10 minutes, by default). For splits that are shorter than 600 seconds, the bot still sees the split users as being on the channel, and chanlimit.tcl should too, so it should not reduce the limit as if they'd all just quit. If they don't rejoin from the split before the 600 seconds is up, they are "lost" in the netsplit and chanlimit will calculate the limit as if they're no longer on the channel. If they do rejoin from the split before 600 seconds is up, the script should act as if they'd never left.
In short, if there are no single splits lasting longer than 10 minutes, there shouldn't be any problem. If the network is commonly experiencing longer splits, increase your wait-split setting to 900 or 1200. And if servers are splitting for an hour or more, there's not much you can do (with splits lasting that long, I don't see the limiting being frequent enough to causing real disruption anyway).
If it doesn't work in practice as I'm describing here then something else is wrong. Incidentally, your second problem sounds completely alien to me. What version of chanlimit.tcl are you using and is it unmodified?
-
LLifeAdeth
Thanks for the info to problem #1 (netsplits) I will work on that.
As for problem #2 (increasing chanlimit....with no new channel joins) I think it is a problem with the shell. I use an unedited chanlimit ver4.09.1.
I noticed in my logs only one bot was doing it. I removed chanlimit form that bot and have had no problems since. Also I had a channel user peak tcl runniing on a bot from that same shell and it could not properly count users either. Some how that shell is dorked up...the bots on that shell just cant count!
Problem #2 is solved I think. I am going to up the timer on my bots for problem #1 and hopefully that will be solved as well!
Thanks !!!
LifeADeth
As for problem #2 (increasing chanlimit....with no new channel joins) I think it is a problem with the shell. I use an unedited chanlimit ver4.09.1.
I noticed in my logs only one bot was doing it. I removed chanlimit form that bot and have had no problems since. Also I had a channel user peak tcl runniing on a bot from that same shell and it could not properly count users either. Some how that shell is dorked up...the bots on that shell just cant count!
Problem #2 is solved I think. I am going to up the timer on my bots for problem #1 and hopefully that will be solved as well!
Thanks !!!
LifeADeth