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.

Tcl error [sl_ctcp]

Old posts that have not been replied to for several years.
Locked
User avatar
Alchera
Revered One
Posts: 3344
Joined: Mon Aug 11, 2003 12:42 pm
Location: Ballarat Victoria, Australia
Contact:

Tcl error [sl_ctcp]

Post by Alchera »

Hi,

I just jumped a bot to another DALnet server and got the following message whilst in DCC....

[12:41] <Natale> [10:41] Tcl error [sl_ctcp]: expected boolean value but got "5:30"
[12:41] <Natale> [10:41] CTCP VERSION: from acoolScan (VerScan@DALnet)

Edited:

The above error was generated by the sentinel.tcl component of netbots
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM
User avatar
slennox
Owner
Posts: 593
Joined: Sat Sep 22, 2001 8:00 pm
Contact:

Post by slennox »

Probably an error in your settings. First find out if some smarty pants tried a ".set sl_ccflood 5:30" or the like, which will mess things up because the script won't get a chance to process the setting.

If you can rule that one out, paste the sentinel.tcl settings section from your netset.tcl and we'll see if the error stems from there.
User avatar
Alchera
Revered One
Posts: 3344
Joined: Mon Aug 11, 2003 12:42 pm
Location: Ballarat Victoria, Australia
Contact:

The settings

Post by Alchera »

Hi,

Settings as below:

# sentinel.tcl settings
set nb_component(sentinel) 1
nb_set LeReveur,L`Africaine,Mecanicien,Merveilleux nb_component(sentinel) 0
set sl_bcflood 5:30
set sl_bmflood 6:20
set sl_ccflood 5:20
set sl_avflood 6:20
set sl_tsunami 10
set sl_txflood 80:30
set sl_boflood 4:20
set sl_jflood 6:20
set sl_nkflood 6:20
set sl_ban 1440
set sl_boban 1440
set sl_globalban 0
set sl_wideban 1
set sl_banmax 100
set sl_igtime 240
set sl_masktype 2
set sl_ilocktime 120
set sl_mlocktime 60
set sl_shortlock 1
set sl_bfmaxbans 19
set sl_note ""
set sl_cfnotice "Channel locked temporarily due to flood, sorry for any inconvenience this may cause :-)"
set sl_bfnotice "Channel locked temporarily due to full ban list, sorry for any inconvenience this may cause :-)"
set sl_lockcmds 2
set sl_lockflags "o"
set sl_bxsimul 1

Hope this helps :)
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM
User avatar
slennox
Owner
Posts: 593
Joined: Sat Sep 22, 2001 8:00 pm
Contact:

Post by slennox »

It would appear to rule out the settings as the cause and bounce us back to the other possibility I suggested :-?

Can you reproduce the error at will or does it only occur with some CTCPs?
User avatar
Alchera
Revered One
Posts: 3344
Joined: Mon Aug 11, 2003 12:42 pm
Location: Ballarat Victoria, Australia
Contact:

Post by Alchera »

Hi,

I am the only person with dcc access to any bot on the botnet and I didn't pop in any uneeded setting (well, I hope not). :) I only jump bots individually via DCC if DALnet is playing up otherwise I simply jump them all via your netbots script.

It's interesting that it coincided with the version scan from acoolScan (VerScan@DALnet), which is new to DALnet. They have never had bots versioning anyone that I am aware of until now.

I have jumped the same bot twice onto the same server without any error and apparently no version scanning. Weird! LOL
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM
User avatar
Sir_Fz
Revered One
Posts: 3794
Joined: Sun Apr 27, 2003 3:10 pm
Location: Lebanon
Contact:

Post by Sir_Fz »

well this scan is only on the acool server, and I think its temporarly.
User avatar
Alchera
Revered One
Posts: 3344
Joined: Mon Aug 11, 2003 12:42 pm
Location: Ballarat Victoria, Australia
Contact:

Post by Alchera »

That scan sort of got me by surprise although I have 4 bots on PhaZeNet where there has always been version scanning and there's no apparent error being generated because of it on those bots.
Add [SOLVED] to the thread title if your issue has been.
Search | FAQ | RTM
Locked