The "parser.lockfile" is blocking POP3/IMAP fetching

[Jamie Edwards]

DO NOT FOLLOW THESE INSTRUCTIONS ANYMORE. THEY ARE NO LONGER CORRECT.



Hi Geert,

Originally Posted by Geert-Jan

So, for the time being, can I make a cron whit

http://bla.bla.bla/cron/index.php?_t=parser&deletelockfile=1

@ every hour

Yes, this should work well or you can do as posted previously:

Originally Posted by Ryan Lederman

If you are experiencing problems with the parser lock file that are disrupting business, you can apply the following patch to your desk instead of waiting for 3.20.03 (which, by the way, will likely be called 3.30.00)

Take the following files from the latest CVS build and replace the ones on your server with them (make sure to take a backup in case it does not work):

/modules/parser/cron_parser.php
/locale/en-us/emailparser.php

These files also address bug #463 (parser.lock file should automatically expire)

Followed by applying:

Originally Posted by John Haugeland

On line 129, you should see this line:

require_once ("./modules/parser/functions_parser_loopcontrol.php");

Please comment it out by placing two forward slashes and a space before that line, as follows:

// require_once ("./modules/parser/functions_parser_loopcontrol.php");

Also, on line 234, you should see the following line:

$isLoopBlocked = StartLoopBlockCheck($fixedheader);

Comment it out, and then write $isLoopBlocked = false; on the next line (must not be on the same line!), as follows:

 //              $isLoopBlocked = StartLoopBlockCheck($fixedheader);     
                 $isLoopBlocked = false;

Those two modifications should moot the loop cutter until you can upgrade to a unified release.

[Jamie Edwards]

I have cleaned up the thread; please keep it on topic.

Thanks

[John Haugeland]

Please do not follow the &deletefile=1 cron instructions. They are incorrect. Prefer the instructions supplied by staff.

Thank you.

[NC Software]

When will this critical issue be resolved?

[NC Software]

John,

How do you categorize this bug?

1) Show Stopper
2) Critical
3) Medium
4) Low

[Jamie Edwards]

Originally Posted by NC Software

When will this critical issue be resolved?

In the next stable build, 3.30.00, the progress of which you can follow in the bug tracker.

Thanks,

[craigbrass]

You mean 3.30.00...

[NC Software]

Originally Posted by NC Software

John,

How do you categorize this bug?

1) Show Stopper
2) Critical
3) Medium
4) Low

Survey says?

[John Haugeland]

Mr. Culiner, look at the bug. It's already categorized as something not on your list: "fixed".

[FrightFactor]

Originally Posted by NC Software

Survey says?

guys, stop bitchin around. do you really think that you get something done faster at kayako side when you start over and over again to complain about it? No! Of course critical bugs should be fixed immediately, but that's not how kayako works. so get used to it and let it go.

greetz,
saskia

[Jamie Edwards]

Saskia,

The bug has been fixed and was done so quickly. Clear instructions for performing the fix yourself before the next build is released have been provided in this thread.

[FrightFactor]

Hey Jamie,
i know and everything is fine. but some aren't learning ...

[Jamie Edwards]

Hi Saskia,

Well, I was refuting your comment that "critical bugs should be fixed immediately, but that's not how kayako works. so get used to it and let it go"; we do fix critical bugs in good time, and have done in this very thread.

[NC Software]

Originally Posted by John Haugeland

Mr. Culiner, look at the bug. It's already categorized as something not on your list: "fixed".

Respectfully, this critical/show stopper is NOT fixed until it's available to customers via STABLE. It can sit "fixed" in your system for months, while we are suffering from the affects of this bug and others like it, your fix does nothing for us.

I suggest reviewing your procedures for hotfixes and getting critical issues fixed in a timely manner. That's the part where Kayako is failing - TIMELY manner.

[Jamie Edwards]

Neal,

Originally Posted by NC Software

I suggest reviewing your procedures for hotfixes

The hotfix is available here (in this thread): The "parser.lockfile" is blocking POP3/IMAP fetching

this critical/show stopper is NOT fixed until it's available to customers via STABLE

We cannot rush the fixing and testing of other bugs in order to deliver a fix for one particularly critical one. Instead, we have provided patch instructions (which we have, in this thread). Indeed, we need to be releasing smaller and more frequent stable builds - and we are working on doing that and trying a different approach. Following 3.30.00 (the build you are waiting for), our roadmaps will be less than a fifth of the size of the ones previously.

and getting critical issues fixed in a timely manner

The bug was fixed a day after the issue was identified.