Parser log cleared / deleted early

[Merit]

I noticed recently after implementing the mail parser that my parser logs were being cleared rapidly. Despite having set the log churn in the mail pareser settings to 30 days, they were being deleted prior to this date.

I discovered after a little investigation that the daily cleanup cron job is what does the clearing of the parser log. The issue is that within the cron cleanup, there is a bug in which it uses the log clearing timeline as set in the "CPU Optimization & Server Settings" NOT the mail parser "Log Churn Timeline" as it should.

Thsi is simply due to the fact that in the code contained in cron_cleanup.php, there is no line that reads the value for the mail parser log churn, it just uses the one specified on the server settings page.

** No warranty, liability or support provided for implementing the following code. Do so at your own risk! **

Simply ADD the following line of code to the top of the if statement shown below in cron_cleanup.php in the modules\core folder:

$cleartime = DATENOW - (intval($_SWIFT["settings"]["pr_logchurndays"])*86400);

	if ($module->isRegistered(MODULE_PARSER))
	{
		$cleartime = DATENOW - (intval($_SWIFT["settings"]["pr_logchurndays"])*86400);
		$_parserlogidlist = array();
		$dbCore->query("SELECT `parserlogid` FROM `". TABLE_PREFIX ."parserlogs` WHERE `dateline` < '". intval($cleartime) ."';");
		while ($dbCore->nextRecord())
		{
			$_parserlogidlist[] = $dbCore->Record["parserlogid"];
		}

		if (count($_parserlogidlist))
		{
			$dbCore->query("DELETE FROM `". TABLE_PREFIX ."parserlogs` WHERE `parserlogid` IN (". buildIN($_parserlogidlist) .");");
			$dbCore->query("DELETE FROM `". TABLE_PREFIX ."parserlogdata` WHERE `parserlogid` IN (". buildIN($_parserlogidlist) .");");
		}

	}

[Davr]

Hi,

I have the same exact problem (which is a little worrying, since the bug was reported over two years ago and is still not fixed), however I'm running the hosted version and am not able to edit the PHP files. Is there any recommended solution for this in that case? Should I just increase the time for the server logs?

Mainly I would like to keep parser logs for a couple weeks, so I can browse it every once in a while, just to make sure I'm not missing any emails.

[John Haugeland]

Yeah, it's really easy to lose things in vBulletin; I don't think anyone's ever seen this. That's why we try so hard to get people to open a bug tracker entry or send a support ticket to bugs@ when they discover a bug. There is no guaranteed support on the forums. Bugs need to be reported.

I'll file this today.

[Davr]

Ah ok, I was just following the steps in the Member's Area >> Get Support, I was on step #3 (post in the community forums). If I hadn't heard anything in a day or two I would have gone to the ticketing thing next.

[John Haugeland]

And, to be clear: THE FORUMS ARE NOT WHERE TO REPORT BUGS. OPEN A SUPPORT TICKET.

There is no way, in vBulletin, to list things which haven't been handled yet.

[John Haugeland]

This is now tracked as issue 869.
Kayako Bug Tracker - Viewing Issue #869 - Possibly incorrect log clearing behavior

[Patje]

hi,

I have the same problem and I tried to add the given line, but our is a binary:

[root@apache1 core]# less cron_cleanup.php
"cron_cleanup.php" may be a binary file. See it anyway?

How can I prevent logs from being deleted too quickly?

thanks, Patrick