Loading Profile...
error log
IntenseDebate crashed my site as soon as we got a bunch of visitors. After getting on the phone with the server owner, we discovered an error log that was filling up at an alarming rate. After 4 hours if high traffic, the log was over 2GB and caused the site to simply stop loading. We deleted the file, but it just started filling up again. Here's a sample of the error log:
2009-01-20 17:40:33 - Successful sending attempt: N; - [{\"operation_id\":null,\"action\":\"save_comment\",\"result\":\"failure\",\"response\":{\"error_code\":110,\"error_msg\":\"Invalid post url\",\"attempt_retry\":false}},{\"operation_id\":null,\"action\":\"save_comment\",\"result\":\"failure\",\"response\":{\"error_code\":110,\"error_msg\":\"Invalid post url\",\"attempt_retry\":false}},{\"operation_id\":null,\"action\":\"save_comment\",\"result\":\"failure\",\"response\":{\"error_code\":110,\"error_msg\":\"Invalid post url\",\"attempt_retry\":false}},{\"operation_id\":null,\"action\":\"save_comment\",\"result\":\"failure\",\"response\":{\"error_code\":110,\"error_msg\":\"Invalid post url\",\"attempt_retry\":false}},{\"operation_id\":null,\"action\":\"save_comment\",\"result\":\"failure\",\"response\":{\"error_code\":110,\"error_msg\":\"Invalid post url\",\"attempt_retry\":false}}]
I deactivated ID in my Wordpress Plugins section, and the error log stopped filling up. I then had to style my WP comments while a ton of people were looking at the site, making me and my team look like amateurs.
What I would like to know is why ID didn't alert me to it before my site crashed. Is it common for a plugin to be generating an error log of that size and not bring it to the admin's attention in the form of a huge red box in the back-end somewhere?
2009-01-20 17:40:33 - Successful sending attempt: N; - [{\"operation_id\":null,\"action\":\"save_comment\",\"result\":\"failure\",\"response\":{\"error_code\":110,\"error_msg\":\"Invalid post url\",\"attempt_retry\":false}},{\"operation_id\":null,\"action\":\"save_comment\",\"result\":\"failure\",\"response\":{\"error_code\":110,\"error_msg\":\"Invalid post url\",\"attempt_retry\":false}},{\"operation_id\":null,\"action\":\"save_comment\",\"result\":\"failure\",\"response\":{\"error_code\":110,\"error_msg\":\"Invalid post url\",\"attempt_retry\":false}},{\"operation_id\":null,\"action\":\"save_comment\",\"result\":\"failure\",\"response\":{\"error_code\":110,\"error_msg\":\"Invalid post url\",\"attempt_retry\":false}},{\"operation_id\":null,\"action\":\"save_comment\",\"result\":\"failure\",\"response\":{\"error_code\":110,\"error_msg\":\"Invalid post url\",\"attempt_retry\":false}}]
I deactivated ID in my Wordpress Plugins section, and the error log stopped filling up. I then had to style my WP comments while a ton of people were looking at the site, making me and my team look like amateurs.
What I would like to know is why ID didn't alert me to it before my site crashed. Is it common for a plugin to be generating an error log of that size and not bring it to the admin's attention in the form of a huge red box in the back-end somewhere?
I’m not a camper of the happy variety.
3
people have this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?No it is not normal for it to ever generate that big of a log. What version of the plugin are you running?
Our latest version of the plugin auto-truncates to ensure the error log never gets above a certain size (considerably less than 2GB). I apologize for the issue. -
Inappropriate?I found out I had this problem in WordPress 2.7 when my server host (BlueHost) suspended my account and notified me that I had a log in public_html/blog/error_log that was 18GB. I finally tracked it down to the IntenseDebate plugin and the log stopped filling up. I tried reinstalling the plug-in and the logs immediately started filling up again with the same stuff you posted above. After just a minute or two I had an error_log that had grown to 38mb!
I have version 2.0.18 installed and I hadn't done anything to my blog settings or backend when this started happening. It's very disappointing so I hope someone can tell us how to fix this.
Here is a sample of the last couple of lines of my error_log in hopes that it will help debug this problem. I've changed some of the things in the log output because I figured it might contain information about my IntenseDebate account.
2009-02-07 16:45:20 - Successful sending attempt: N; - [{\"operation_id\":\"7a239uauf8u9up98u9\",\"action\":\"user_login\",\"result\":\"success\",\"response\":{\"blogKey\":\"afeajif;iIJF;ljifaef\",\"blogID\":\"#####\",\"userID\":\"######\",\"userKey\":\"adkjfaiapIPJPOfjwoa\",\"username\":\"******\",\"blogAcct\":\"\"}}]
' WHERE option_name = 'id_debug_log' made by shutdown_action_hook, do_action, call_user_func_array, id_ping_queue, id_queue->ping, id_queue->send, id_debug_log, id_save_option, update_option
I’m disappointed
