I am getting a whole heap of these notices in the watchdog.. does anybody know how to stop these??

http://www.google.com/url
Message Retrieved new CAPTCHA
Request: POST http://rest.mollom.com/v1/captcha
type = 'image'
ssl = 0
Request headers:
Accept = 'application/xml, application/json;q=0.8, */*;q=0.5'
Content-Type = 'application/x-www-form-urlencoded'
Authorization = 'OAuth oauth_consumer_key="5c1dec2d9eaeedca10467f0c059d5da8", oauth_version="1.0", oauth_nonce="4961f04342f38dd8ae323c4799bca730", oauth_timestamp="1336640105", oauth_signature_method="HMAC-SHA1", oauth_signature="1wbqSPgMK4EasPlidj9ZPDn3x%2B0%3D"'
Response: 200
code = '200'
captcha =
id = '120510401042c76a20'
url = 'http://ip:80/v1/captcha/120510401042c76a20.png'
Retrieved new CAPTCHA

Severity debug
Hostname host

Files: 
CommentFileSizeAuthor
#17 0001-1570504-by-sun-Log-all-messages-on-existing-sites-to.patch806 bytessun
PASSED: [[SimpleTest]]: [MySQL] 6,220 pass(es).
[ View ]
#16 mollom.log-update.16.patch432 bytessun
PASSED: [[SimpleTest]]: [MySQL] 6,908 pass(es).
[ View ]
#14 mollom.log-severity.14.patch3.92 KBsun
PASSED: [[SimpleTest]]: [MySQL] 5,742 pass(es).
[ View ]
#13 mollom.log-severity.13.patch2.12 KBsun
PASSED: [[SimpleTest]]: [MySQL] 6,404 pass(es).
[ View ]
#11 1570504-9-log_threshold_configuration.patch1.32 KBstella
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 1570504-9-log_threshold_configuration.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]
#9 1570504-8-log_threshold_configuration.patch1.32 KBstella
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 1570504-8-log_threshold_configuration.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]
#7 1570504-7-log_threshold_configuration.patch1.35 KBstella
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 1570504-7-log_threshold_configuration.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]

Comments

Title:Watchdog ErrorsWatchdog debug messages
Status:Active» Closed (works as designed)

The severity of the messages is "debug", so they are not notices or errors.

You can ignore them, unless you experience a misbehavior in Mollom's spam protection, in which case the debug messages are required for Mollom support requests in order to figure out what exactly happened.

I understand they are just debug... but I would prefer to stop them if possible... I would like to have them just show the error msgs... is there a way to stop them... I didnt seem to get these until the most recent update..

Tks for your help..

Cheers.

Version:6.x-2.0-beta2» 7.x-2.x-dev
Status:Closed (works as designed)» Active

Since watchdog doesn't allow good filtering for logging in D7 (and probably won't in D8, either), could you at least add a setting for turning logging on or off in the settings (admin/config/content/mollom/settings)? On a few sites, where I like DB logging available for the rare error or notice, the logs have been completely full of mollom messages (this is mostly on high-comment-volume, but low-complexity sites), making the db inserts for watchdog annoyingly frequent.

I added the ability to disable logging for Honeypot, and a lot of users seemed to be happy with the new setting: #1249580: Log blocked form submissions.

I would enable syslog on these particular sites, but (a) other admins need to see the logs, and (b) syslog would still get bombarded with mollom messages (I know I could do filtering...).

Title:Watchdog debug messagesAllow disabling of watchdog debug messages

Updating title.

If you're using syslog, then https://drupal.org/project/syslog_advanced might be of interest for you — it allows to omit/filter all log messages before they are sent to syslog.

That said, by now I'm happy to reconsider this, since the quality, performance, and accuracy of the Mollom service vastly improved over the past months. Additionally, the Mollom service itself provides more sophisticated solutions for handling false-positives as well as uncaught spam posts now. In turn, the need for these log messages decreased.

We can consider to add a checkbox to the global module settings that allows to toggle the logging.

However, internally, the effect would not globally switch logging on or off, but instead, the setting essentially defines the severity threshold for messages to log.

In concrete terms: Enabling the checkbox stores the variable mollom_log_threshold with value warning. Mollom's central log writing function then compares the severity of the message to be logged against the configured threshold first and skips the message if it is less severe than that.

That sounds good; and for systems where syslog is an option, syslog_advanced works great.

Status:Active» Needs review
StatusFileSize
new1.35 KB
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 1570504-7-log_threshold_configuration.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]

Attached patch implements this functionality.

Status:Needs review» Needs work

The last submitted patch, 1570504-7-log_threshold_configuration.patch, failed testing.

Status:Needs work» Needs review
StatusFileSize
new1.32 KB
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 1570504-8-log_threshold_configuration.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]

Patch reroll

Status:Needs review» Needs work

The last submitted patch, 1570504-8-log_threshold_configuration.patch, failed testing.

Status:Needs work» Needs review
StatusFileSize
new1.32 KB
FAILED: [[SimpleTest]]: [MySQL] Unable to apply patch 1570504-9-log_threshold_configuration.patch. Unable to apply patch. See the log in the details link for more information.
[ View ]

Patch reroll, not sure why it's not applying....

Status:Needs review» Needs work

The last submitted patch, 1570504-9-log_threshold_configuration.patch, failed testing.

Title:Allow disabling of watchdog debug messagesDisable logging of non-severe messages by default
Component:User interface» Code
Category:support» task
Status:Needs work» Needs review
StatusFileSize
new2.12 KB
PASSED: [[SimpleTest]]: [MySQL] 6,404 pass(es).
[ View ]

@stella, to clarify: Your patch was not a git patch.

Attached patch turns the new setting into a checkbox (for simplicity), while still allowing developers to set a custom minimum log severity level via $conf in settings.php.

Version:7.x-2.x-dev» 6.x-2.x-dev
StatusFileSize
new3.92 KB
PASSED: [[SimpleTest]]: [MySQL] 5,742 pass(es).
[ View ]

Version:6.x-2.x-dev» 7.x-2.x-dev
Status:Needs review» Fixed

Thanks for reporting, reviewing, and testing! Committed to all branches.

A new development snapshot will be available within the next 12 hours. This improvement will be available in the next official release.

Issue summary:View changes
Status:Fixed» Needs review
StatusFileSize
new432 bytes
PASSED: [[SimpleTest]]: [MySQL] 6,908 pass(es).
[ View ]

Early adopters/testers of the latest development snapshot were severely confused of not seeing any log messages at all and worried whether it stopped working... ;-)

So here's a module update that disables the minimum log severity threshold on existing sites, so as to avoid that confusion and only change the default for new installs.

Version:7.x-2.x-dev» 6.x-2.x-dev
StatusFileSize
new806 bytes
PASSED: [[SimpleTest]]: [MySQL] 6,220 pass(es).
[ View ]

Backport.

Version:6.x-2.x-dev» 7.x-2.x-dev
Status:Needs review» Fixed

Committed to all branches.

Status:Fixed» Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.