egghelp/eggheads community

Log of public messages stopped

2009-10-24T22:14:47-04:00

The thing is, the pubm function is only called if the keywords match in the bind command.

My only pubm bind kicks users that have "now playing" spam. It would be obvious if that was being called.

Ok, did more digging. I was using grep to search for pubm. Did not realize CHATStats.tcl was in a subdir. It has not been modified since 2004. Logging stopped in May when I updated eggdrop and TCL.

The cs:count function had no return value specified. This has been running fine for years. Must be 1.6.19 or the updated TCL libs now return a default other than 0.

Removed the CHATStats.tcl and now logging works.

Statistics: Posted by robbie-bot — Sat Oct 24, 2009 10:14 pm

Log of public messages stopped

2009-10-24T21:16:14-04:00

The thing is, the pubm function is only called if the keywords match in the bind command.

My only pubm bind kicks users that have "now playing" spam. It would be obvious if that was being called.

Statistics: Posted by robbie-bot — Sat Oct 24, 2009 9:16 pm

Log of public messages stopped

2009-10-24T21:01:02-04:00

It is mentioned here:
http://forum.egghelp.org/viewtopic.php?t=12824&start=0

in the post by nml375.

There is a known "issue" with pubm-bindings in eggdrop1.6.18; If the command invoked returns 1 (TCL_OK), eggdrop will not log the message that triggered the binding.
I would suspect this to be the reason why your bot does not log public chat, that is, there seems to be a script running on your system with a pubm-binding that blocks public chat from being logged on that channel.

.....

Statistics: Posted by willyw — Sat Oct 24, 2009 9:01 pm

Re: Log of public messages stopped

2009-10-24T20:50:32-04:00

This seemed to happen after the upgrade to 1.6.19

I can change logfile all I want. 'p' and 'm' options seem to have no effect. The bot will no longer log public or private messages.
...

I've had this to happen.

For me, it was a script. I'd have to go looking to find it again, but from my memory it was a procedure that had a non-zero return in it.

I'm sorry that I don't have the reference right at my fingertips, to point you to. I bet that if you search this forum, you'll find it mentioned though.

Try an experiment: comment out ALL your scripts. Then .restart .
Does it log normally now? If it does, now you know it is a script that is causing it. Load them one at a time, until you pin it down.

I hope this helps.

Statistics: Posted by willyw — Sat Oct 24, 2009 8:50 pm

Log of public messages stopped

2009-10-19T20:41:53-04:00

lol i had the same problem when i last updates... yes i had the same script on it (bseen.tcl) in saying that i never had the time time to pin point what was causing the problem :/ just know that it worked without it. After a recompile n all that hope it helps.

Statistics: Posted by TCL_no_TK — Mon Oct 19, 2009 8:41 pm

Log of public messages stopped

2009-10-19T13:33:16-04:00

The only msgm binds are in the bseen1.4.2.tcl file. Those file have not changed since 2004.

The config file has p and m in the logfile options.

Statistics: Posted by robbie-bot — Mon Oct 19, 2009 1:33 pm

Log of public messages stopped

2009-10-19T07:54:12-04:00

Check Your settings in eggdrop config file, Also id recommend searching thought the binds, and making sure you dont have any scripts that have

Code:

bind msgm -|- * sum:proc

Type .binds in dcc/telnet with the bot for a list

Statistics: Posted by TCL_no_TK — Mon Oct 19, 2009 7:54 am

Log of public messages stopped

2009-10-19T01:08:59-04:00

This seemed to happen after the upgrade to 1.6.19

I can change logfile all I want. 'p' and 'm' options seem to have no effect. The bot will no longer log public or private messages. It will log /notice or /msg lines from the channel.

I have deleted the channel file, recompiled, tried both the original and Gentoo biulds, same thing.

I got around it by writing a TCL script to add entries by putloglev but would rather use the native log.

I have looked at the config file and even stared at the code and cant see anything that would prevent the messages from being logged.

Statistics: Posted by robbie-bot — Mon Oct 19, 2009 1:08 am