popfile shutsdown without warning

If POPFile detects a problem that causes it to shut down it may output some console messages indicating what has gone wrong. By default the Windows version of POPFile hides the window used to display these messages.

To see these messages shut down POPFile then re-start POPFile using

Start -- All Programs -- POPFile -- Support -- Message Capture utility

This will start POPFile as usual and also display the console messages in a scrollable window. If you wait until the problem occurs then copy and paste these messages into a message in the HELP forum at http://getpopfile.org/discussion/1 it will help us diagnose the problem.

(If you try to use the Message Capture utility when POPFile is already running then the Message Capture utility will simply report that another copy of POPFile is running - you need to make sure POPFile is not running before you try to use the Message Capture utility.)

Brian

Popfile has still been shutting down. Sometimes without warning and sometimes when I'm clearing history. Yesterday there was an error message in the Capture Utility window. I was in the popfile interface clearing the history and it got hung up. The following error was captured:

DBD::SQLite::st execute failed: database is locked(21) at dbdimp.c line 376 at e:\programs\popfile\POPfile\history.pm line 300, <GEN2615> line5.

Is there anything we can do to keep this from happening. When Popfile goes down email stops coming in. Missy

If you have enabled concurrent POP3 connections I suggest you go back to the default setting.

The CONFIGURATION page in the UI shows the current setting in the "POP3" section.

If the UI shows "Allow concurrent POP3 connections: Yes" and the adjacent button is labelled "Change to No" you need to click this button, shut down POPFile and restart it.

The default setting is reported as: "Allow concurrent POP3 connections: No" and the adjacent button is labelled "Change to Yes". This default setting is safer and may make your system less likely to go wrong.

Brian

Text copied from ticket #120 (that ticket will be closed because all it did was add extra information to the problem first raised here):

Popfile has stopped twice since your last email on 9/23. It stopped on 10/6 and then again today. Attached are is the info the capture utility noted. Please let me know what we can do next to keep this from happening. Emails stops when popfile goes down. Thanks, Missy Hollis

Originally added by rvjohn on 10/08/09 15:25:33 to ticket #122

Replying to brian:

Text copied from ticket #120 (that ticket will be closed because all it did was add extra information to the problem first raised here):

Oops! It was ticket #122 that was the duplicate!

Originally added by rvjohn on 10/08/09 15:27:02 to ticket #123

Text copied from ticket #123 (that ticket will be closed because all it did was add extra information to the problem first raised here):

here's the other log from today, 10/8/09

I am disappointed that you have not answered my question last month about the concurrent POP3 connections setting.

There is no need to create duplicate tickets as this only makes it much harder to read about your problem. This is why tickets #122 and #123 have been closed.

Way back in April I said:

If you wait until the problem occurs then copy and paste these messages into a message in the HELP forum at http://getpopfile.org/discussion/1 it will help us diagnose the problem.

Please use the HELP forum; it is much easier to discuss things there.

Brian

The new option 'bayes_sqlite_journal_mode' added in POPFile v1.1.1 may ease your problem. If you can, please change the option to 'memory' in the Advanced tab.

(Please backup your corpus data (popfile.db) before trying the new option.)

For more information about the options, please see:

http://getpopfile.org/docs/optionreference#classifier_options

Naoki

I have updated popfile to 1.1.1 and made the changes recommended above. I will keep you posted on the results. Thank you, Missy Hollis

I close the ticket due to the reporter does not respond over a year. If you still have the same problem, please reopen this ticket.

Naoki