POPFile has run flawlessly on my computer for years. This past week, however, the program crashes 3-4 times a day while downloading mail. I am running WinVista and get a popup dialog that says "POPFile has stopped running."
Once I restart POPFile, it works fine until it stops running again.
I have not made any significant changes to my computer set up, nor installed any new programs. Any suggestions as to where the problem might lie?
Thanks.
Mitch
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Are you using the latest version? We released version 1.0 recently. There have been some fixes in recent versions for strange spam emails that would cause POPFile to crash.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I stopped using the tray icon long ago because of the problems it caused. I will enable logging and the next time it crashes, I will post the log. Thanks for your suggestions. Have a good weekend.
Mitch
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
OK, my log is below. I copied it immediately after POPFile crashed while I was trying to recategorize some emails. What is the diagnosis, doc? Thanks for your help.
2008/1/18 18:04:47 4916: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/18 18:04:47 4916: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/18 18:04:48 4916: pop3: 668: POP3 proxy done
2008/1/18 18:09:58 4916: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/18 18:09:58 4916: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/18 18:09:59 4916: pop3: 668: POP3 proxy done
2008/1/18 18:10:16 4916: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/18 18:10:16 4916: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/18 18:10:17 4916: pop3: 668: POP3 proxy done
2008/1/19 15:16:13 4992: bayes: 747: Attempting to connect to dbi:SQLite2:dbname=C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile/popfile.db (1)
2008/1/19 15:16:15 4992: bayes: 753: Using SQLite library version 2.8.15
2008/1/19 15:18:10 4992: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
2008/1/19 15:36:04 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 15:36:04 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 15:36:27 4992: pop3: 668: POP3 proxy done
2008/1/19 15:40:57 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 15:40:57 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 15:40:58 4992: pop3: 668: POP3 proxy done
2008/1/19 15:46:17 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 15:46:17 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 15:46:18 4992: pop3: 668: POP3 proxy done
2008/1/19 15:51:19 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 15:51:19 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 15:51:23 4992: pop3: 668: POP3 proxy done
2008/1/19 15:56:24 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 15:56:24 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 15:56:25 4992: pop3: 668: POP3 proxy done
2008/1/19 16:01:29 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:01:29 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:01:30 4992: pop3: 668: POP3 proxy done
2008/1/19 16:06:42 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:06:42 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:06:43 4992: pop3: 668: POP3 proxy done
2008/1/19 16:12:02 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:12:02 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:12:03 4992: pop3: 668: POP3 proxy done
2008/1/19 16:17:07 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:17:07 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:17:08 4992: pop3: 668: POP3 proxy done
2008/1/19 16:22:12 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:22:12 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:22:16 4992: pop3: 668: POP3 proxy done
2008/1/19 16:27:21 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:27:21 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:27:22 4992: pop3: 668: POP3 proxy done
2008/1/19 16:32:28 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:32:28 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:32:31 4992: pop3: 668: POP3 proxy done
2008/1/19 16:37:47 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:37:47 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:37:48 4992: pop3: 668: POP3 proxy done
2008/1/19 16:42:57 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:42:57 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:42:58 4992: pop3: 668: POP3 proxy done
2008/1/19 16:48:02 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:48:02 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:48:03 4992: pop3: 668: POP3 proxy done
2008/1/19 16:53:20 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:53:20 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:53:21 4992: pop3: 668: POP3 proxy done
2008/1/19 16:58:25 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:58:25 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:58:26 4992: pop3: 668: POP3 proxy done
2008/1/19 17:03:30 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 17:03:30 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 17:03:31 4992: pop3: 668: POP3 proxy done
2008/1/19 17:08:31 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 17:08:31 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 17:08:32 4992: pop3: 668: POP3 proxy done
2008/1/19 17:10:50 4992: bayes: 486: Reclassification from spam to info
2008/1/19 17:10:50 4992: history: 409: Change slot classification of 2295 to info
2008/1/19 17:13:34 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 17:13:34 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 17:13:35 4992: pop3: 668: POP3 proxy done
2008/1/19 17:16:15 4992: bayes: 486: Reclassification from unclassified to info
2008/1/19 17:16:15 4992: history: 409: Change slot classification of 2216 to info
2008/1/19 17:17:16 4992: bayes: 486: Reclassification from to main
2008/1/19 17:17:16 4992: history: 409: Change slot classification of 2161 to main
2008/1/19 17:19:11 4440: bayes: 747: Attempting to connect to dbi:SQLite2:dbname=C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile/popfile.db (1)
2008/1/19 17:19:11 4440: bayes: 753: Using SQLite library version 2.8.15
2008/1/19 17:19:16 4440: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
2008/1/19 17:19:49 2612: bayes: 747: Attempting to connect to dbi:SQLite2:dbname=C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile/popfile.db (1)
2008/1/19 17:19:49 2612: bayes: 753: Using SQLite library version 2.8.15
2008/1/19 17:19:52 2612: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
2008/1/19 17:19:59 2612: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 17:19:59 2612: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 17:20:00 2612: pop3: 668: POP3 proxy done
2008/1/19 17:20:22 2612: bayes: 486: Reclassification from unclassified to info
2008/1/19 17:20:23 2612: history: 409: Change slot classification of 2216 to info
2008/1/19 17:20:23 2612: bayes: 486: Reclassification from unclassified to main
2008/1/19 17:20:23 2612: history: 409: Change slot classification of 2161 to main
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
2008/1/21 07:40:40 5004: bayes: 747: Attempting to connect to dbi:SQLite2:dbname=C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile/popfile.db (1)
2008/1/21 07:40:40 5004: bayes: 753: Using SQLite library version 2.8.15
2008/1/21 07:40:42 5004: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As you have no doubt figured out by now, each time it crashes, the same error message appears. It always looks like this:
2008/1/21 11:42:52 596: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
Thoughts and suggestions?? Many thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
That part (the warnings) is normal POPFile startup. That is just the warning you get when POPFile starts if you don't have all the optional parts installed. The crash should be just above that. I didn't recognize anything unusual from the longer log you sent. The crash sees to be happening when you reclassify message 2161. Is it always the same message, is there anything unusual about the message? Try turning up the logger level one more time so we get the extremely detailed version. It will include the contents of your email so if it is anything you can't post publicly, you can email it to me instead of post it here.
If it is always the same message, we need to look at the original so don't delete it. You may want to increase the time POPFile keeps messages in history in that case until we get it or figure out what is causing it. We have a Download Message link at the bottom of the Message View in POPFile.
These are the lines from your history right before both crashes in long log file:
bayes: 486: Reclassification from unclassified to main
history: 409: Change slot classification of 2161 to main
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for that response. It has not been crashing only when I reclassify messages. For instance, I left it on overnight and this morning, it was DOA when I came to the computer. I did not realize that the logging setting reset itself, so I will change the setting again.
If it is crashing when I reclassify emails, why is it always crashing on 2161? I only recategorize an email once. In other words, I didn't categorize email 2161 more than once, even though the log file seems to say I did.
I'll post another log or email it to you as soon as it crashes again. Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You probably did reclassify it twice because it didn't stick the first time since it died right away.
I don't think logging should reset itself. If you are talking about where I said turn it up again, I meant turn it to the highest level of detail. Looks like it already is though if you followed the prepare a log instructions on the wiki. I forgot what level 2 logs looked like for reclassification. Usually we have problems with POP downloads which show a lot more information.
Have you tried reinstalling POPFile? Maybe you got a corrupt file. It is strange that it is dying during reclassification and when just sitting idle. Do you leave your mail client open overnight so it is checking all the time? Be sure you didn't accidentally turn the trayicon back on, what is happening certainly reminds me of the problems that can sometimes cause.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for the suggestion on checking the database. My database checked out fine. HOwever, during the last 24 hours, I have not had a crash. I did try to reinstall POPFile (without uninstalling the current version) as an upgrade by having it install language support modules that I had opted out of originally. I am not sure if that should make a difference or whether the reinstall repaired damaged files. Whatever the reason, I am good at the moment. Thanks for all your suggestions. Cross your fingers that my problems don't recur.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Talk about jinxing something . . . After posting the last entry, I walked away from my computer. When I returned it had crashed. All detective work appreciated. Here is the log for the last few minutes:
2008/1/22 19:51:55 4840: mq: 377: post UIREG (configuration:windows_trayicon_and_console:windows-configuration.thtml:Platform::MSWin32=HASH(0x2689694)) 2008/1/22 19:51:55 4840: mq: 384: queuing post UIREG (configuration:windows_trayicon_and_console:windows-configuration.thtml:Platform::MSWin32=HASH(0x2689694)) 2008/1/22 19:51:55 4840: mq: 386: UIREG queue length now 0
2008/1/22 19:51:55 4840: bayes: 747: Attempting to connect to dbi:SQLite2:dbname=C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile/popfile.db (1)
2008/1/22 19:51:55 4840: bayes: 753: Using SQLite library version 2.8.15
2008/1/22 19:51:56 4840: bayes: 1919: get_session_key returning key 54P9q9qBrlm3Mguz4pA3 for user XXXXXX
2008/1/22 19:51:56 4840: mq: 377: post RELSE (54P9q9qBrlm3Mguz4pA3)
2008/1/22 19:51:56 4840: mq: 384: queuing post RELSE (54P9q9qBrlm3Mguz4pA3) 2008/1/22 19:51:56 4840: mq: 386: RELSE queue length now 0
2008/1/22 19:51:57 4840: html: 65: Trying to open listening socket on port 8080.
2008/1/22 19:51:57 4840: mq: 377: post UIREG (configuration:pop3_configuration:pop3-configuration-panel.thtml:Proxy::POP3=HASH(0x2a31774)) 2008/1/22 19:51:57 4840: mq: 384: queuing post UIREG (configuration:pop3_configuration:pop3-configuration-panel.thtml:Proxy::POP3=HASH(0x2a31774)) 2008/1/22 19:51:57 4840: mq: 386: UIREG queue length now 1
2008/1/22 19:51:57 4840: mq: 377: post UIREG (security:pop3_security:pop3-security-panel.thtml:Proxy::POP3=HASH(0x2a31774))
2008/1/22 19:51:57 4840: mq: 384: queuing post UIREG (security:pop3_security:pop3-security-panel.thtml:Proxy::POP3=HASH(0x2a31774))
2008/1/22 19:51:57 4840: mq: 386: UIREG queue length now 2
2008/1/22 19:51:57 4840: mq: 377: post UIREG (chain:pop3_chain:pop3-chain-panel.thtml:Proxy::POP3=HASH(0x2a31774))
2008/1/22 19:51:57 4840: mq: 384: queuing post UIREG (chain:pop3_chain:pop3-chain-panel.thtml:Proxy::POP3=HASH(0x2a31774))
2008/1/22 19:51:57 4840: mq: 386: UIREG queue length now 3
2008/1/22 19:51:57 4840: pop3: 130: Opening listening socket on port 110.
2008/1/22 19:51:57 4840: mq: 377: post UIREG (configuration:pop3_socks_configuration:socks-widget.thtml:Proxy::POP3=HASH(0x2a31774)) 2008/1/22 19:51:57 4840: mq: 384: queuing post UIREG (configuration:pop3_socks_configuration:socks-widget.thtml:Proxy::POP3=HASH(0x2a31774)) 2008/1/22 19:51:57 4840: mq: 386: UIREG queue length now 4
2008/1/22 19:51:57 4840: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
2008/1/22 19:51:57 4840: mq: 128: Message RELSE (54P9q9qBrlm3Mguz4pA3) ready for delivery 2008/1/22 19:51:57 4840: mq: 131: Delivering message RELSE (54P9q9qBrlm3Mguz4pA3) to bayes 2008/1/22 19:51:57 4840: bayes: 1817: release_session_key releasing key 54P9q9qBrlm3Mguz4pA3 for user XXXXXX
2008/1/22 19:51:57 4840: mq: 128: Message UIREG (configuration:windows_trayicon_and_console:windows-configuration.thtml:Platform::MSWin32=HASH(0x2689694)) ready for delivery
2008/1/22 19:51:57 4840: mq: 131: Delivering message UIREG (configuration:windows_trayicon_and_console:windows-configuration.thtml:Platform::MSWin32=HASH(0x2689694)) to html
2008/1/22 19:51:57 4840: mq: 128: Message UIREG (configuration:pop3_configuration:pop3-configuration-panel.thtml:Proxy::POP3=HASH(0x2a31774)) ready for delivery 2008/1/22 19:51:57 4840: mq: 131: Delivering message UIREG (configuration:pop3_configuration:pop3-configuration-panel.thtml:Proxy::POP3=HASH(0x2a31774)) to html
2008/1/22 19:51:57 4840: mq: 128: Message UIREG (security:pop3_security:pop3-security-panel.thtml:Proxy::POP3=HASH(0x2a31774)) ready for delivery
2008/1/22 19:51:57 4840: mq: 131: Delivering message UIREG (security:pop3_security:pop3-security-panel.thtml:Proxy::POP3=HASH(0x2a31774)) to html 2008/1/22 19:51:57 4840: mq: 128: Message UIREG (chain:pop3_chain:pop3-chain-panel.thtml:Proxy::POP3=HASH(0x2a31774)) ready for delivery 2008/1/22 19:51:57 4840: mq: 131: Delivering message UIREG (chain:pop3_chain:pop3-chain-panel.thtml:Proxy::POP3=HASH(0x2a31774)) to html
2008/1/22 19:51:57 4840: mq: 128: Message UIREG (configuration:pop3_socks_configuration:socks-widget.thtml:Proxy::POP3=HASH(0x2a31774)) ready for delivery
2008/1/22 19:51:57 4840: mq: 131: Delivering message UIREG (configuration:pop3_socks_configuration:socks-widget.thtml:Proxy::POP3=HASH(0x2a31774)) to html
2008/1/22 19:51:57 4840: html: 658: Read slurp data GET / HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11[0d][0a]Accept: text/xml
2008/1/22 19:51:57 4840: html: 154: GET / HTTP/1.1[0d][0a]
2008/1/22 19:51:57 4840: html: 658: Read slurp data ,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Acc 2008/1/22 19:51:57 4840: html: 658: Read slurp data ept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 300[0d][0a]Connection: keep-alive[0d][0a][0d][0a]
2008/1/22 19:51:58 4840: bayes: 1919: get_session_key returning key ag6v80FRAqM9dLNVn for user XXXXXX
2008/1/22 19:51:58 4840: history: 1012: Base query is select XXX from[0a] history, buckets, magnets where history.userid = 1 and committed = 1 and history.bucketid = buckets.id and magnets.id = magnetid order by inserted desc;
2008/1/22 19:51:58 4840: history: 1100: Request for rows 1 (150), current size 0
2008/1/22 19:51:58 4840: history: 1104: Getting 151 rows from database
2008/1/22 19:51:58 4840: history: 1112: Returning 0..149 2008/1/22 19:51:59 4840: html: 181: HTTP handle_url returned code 1[0a]
2008/1/22 19:51:59 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x2476b90)[0a]
2008/1/22 19:52:00 4840: html: 658: Read slurp data GET /favicon.ico HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11[0d][0a]Accep
2008/1/22 19:52:00 4840: html: 154: GET /favicon.ico HTTP/1.1[0d][0a]
2008/1/22 19:52:00 4840: html: 658: Read slurp data t: image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 300[0d][0a]Connect 2008/1/22 19:52:00 4840: html: 658: Read slurp data ion: keep-alive[0d][0a][0d][0a]
2008/1/22 19:52:00 4840: html: 181: HTTP handle_url returned code 1[0a]
2008/1/22 19:52:00 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x2476bcc)[0a]
2008/1/22 19:52:00 4840: html: 658: Read slurp data GET /skins/smalldefault/style.css HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefo
2008/1/22 19:52:00 4840: html: 154: GET /skins/smalldefault/style.css HTTP/1.1[0d][0a] 2008/1/22 19:52:00 4840: html: 658: Read slurp data x/2.0.0.11[0d][0a]Accept: text/css,*/*;q=0.1[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Ali
2008/1/22 19:52:00 4840: html: 658: Read slurp data ve: 300[0d][0a]Connection: keep-alive[0d][0a]Referer: http://localhost:8080/\[0d][0a][0d][0a]
2008/1/22 19:52:00 4840: html: 181: HTTP handle_url returned code 1[0a]
2008/1/22 19:52:00 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x2476b9c)[0a] 2008/1/22 19:52:01 4840: html: 658: Read slurp data GET /skins/default/magnet.png HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2. 2008/1/22 19:52:01 4840: html: 154: GET /skins/default/magnet.png HTTP/1.1[0d][0a]
2008/1/22 19:52:01 4840: html: 658: Read slurp data 0.0.11[0d][0a]Accept: image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 2008/1/22 19:52:01 4840: html: 658: Read slurp data 300[0d][0a]Connection: keep-alive[0d][0a]Referer: http://localhost:8080/\[0d][0a][0d][0a]
2008/1/22 19:52:01 4840: html: 181: HTTP handle_url returned code 1[0a]
2008/1/22 19:52:01 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x2476938)[0a]
2008/1/22 19:52:02 4840: html: 658: Read slurp data GET /otto.png HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11[0d][0a]Accept:
2008/1/22 19:52:02 4840: html: 154: GET /otto.png HTTP/1.1[0d][0a]
2008/1/22 19:52:02 4840: html: 658: Read slurp data image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 300[0d][0a]Connection
2008/1/22 19:52:02 4840: html: 658: Read slurp data : keep-alive[0d][0a]Referer: http://localhost:8080/\[0d][0a][0d][0a]
2008/1/22 19:52:02 4840: html: 181: HTTP handle_url returned code 1[0a]
2008/1/22 19:52:02 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x2476c14)[0a]
2008/1/22 19:52:07 4840: html: 658: Read slurp data GET /configuration?session=oVi28QID HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Fire
2008/1/22 19:52:07 4840: html: 154: GET /configuration?session=oVi28QID HTTP/1.1[0d][0a] 2008/1/22 19:52:07 4840: html: 658: Read slurp data fox/2.0.0.11[0d][0a]Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Acce 2008/1/22 19:52:07 4840: html: 658: Read slurp data pt-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 300[0d][0a]Connection: keep-alive[0d][0a]Referer: http://localhost:8080/\[0d][0a][0d][0a] 2008/1/22 19:52:07 4840: html: 181: HTTP handle_url returned code 1[0a] 2008/1/22 19:52:07 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x24774fc)[0a]
2008/1/22 19:52:10 4840: html: 658: Read slurp data GET /popfile_current_log.log?session=oVi28QID HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/200 2008/1/22 19:52:10 4840: html: 154: GET /popfile_current_log.log?session=oVi28QID HTTP/1.1[0d][0a]
2008/1/22 19:52:11 4840: html: 658: Read slurp data 71127 Firefox/2.0.0.11[0d][0a]Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q 2008/1/22 19:52:11 4840: html: 658: Read slurp data =0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 300[0d][0a]Connection: keep-alive[0d][0a]Referer: http://localhost:8080/con 2008/1/22 19:52:11 4840: html: 658: Read slurp data figuration?session=oVi28QID[0d][0a][0d][0a]
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> After posting the last entry, I walked away from my computer. When I returned it had crashed. All detective work appreciated. <<
The log file is not the only place where information about crashes can be found. Sometimes POPFile generates some console warnings or error messages when things go wrong. Normally these messages are hidden (i.e. not displayed). The easiest way to see these messages on a Windows system is to use the Message Capture utility.
I'm assuming you have POPFile configured to start automatically when Windows starts up. If POPFile now crashes almost every time you use it I think the easiest thing to do is shutdown POPFile and then use this shortcut:
Start -- All Programs -- POPFile -- Support -- Message Capture utility
This will start POPFile using your normal settings but it will display the console messages in a scrollable window and let you copy these messages to the clipboard. If you see the message
please ignore it - this is a harmless bug in the 1.0.0 release.
Once you see the message "POPFile Engine v1.0.0 running" in the scrollable window POPFile is ready for use.
When POPFile crashes some new messages will appear in the scrollable window, includes the date and time the crash was detected by the utility. This will help identify the relevant parts of the log file.
If you right-click in that scrollable window you can copy all of the messages to the clipboard and save them. If you post all of the messages here it may help us work out what is going wrong.
If POPFile does not crash then you will have to remember to use the Message Capture utility the next time you start POPFile so you can capture the console messages the next time POPFile crashes.
The POPFile wiki has a page explaining how you can use the POPFile UI to enable/disable the Message Capture utility instead of having to remember to use its Start Menu shortcut every time: http://popfile.sourceforge.net/wiki/howtos:messagecapture
>> When I returned it had crashed ... Here is the log for the last few minutes: <<
As you are no doubt aware by now, logger_level 2 generates a _lot_ of information in the log file.
I'm no expert at interpreting these log files but the extract you supplied only seems to show that you started POPFile, accessed the UI, selected the CONFIGURATION page and clicked the "View current log file" link.
I think it would be better to stop using the UI to access the log files, in order to reduce the amount of irrelevant information in the log.
POPFile's log files have names like popfile1201046400.log and are normally kept in the POPFile "User Data" folder. On some systems this folder is not easy to display so the installer creates a shortcut to make this easier:
Start -- All Programs -- POPFile -- Support -- Create 'User Data' shortcut
This shortcut will add a new shortcut to the Start Menu for you. On my system I use an account called "Brian" so that shortcut creates this new Start Menu entry for me:
Start -- All Programs -- POPFile -- Support -- User Data (Brian)
The "User Data (Brian)" shortcut displays the contents of my POPFile User Data folder. At the moment I have 3 log files there (amongst many other files):
Thanks for your suggestions. I ran the Message Capture utility and the result is posted below. This time, POPfile ran for about 18 hours until it completely crashed while I was away from my computer. It seems that it is not crashing as frequently lately. Sorry this post is so long. If there is an easier way to reduce the length of the info, please let me know. I appreciate your (and everyone else's) terrific assistance.
Mitch
------------------------------------------------------------
POPFile Message Capture Utility v0.1.6
------------------------------------------------------------
POPFILE_ROOT = C:\PROGRA~1\POPFile
POPFILE_USER = C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile
Using 'popfilef.exe' to run POPFile
------------------------------------------------------------
(report started 23-Jan-2008 @ 16:23:30)
------------------------------------------------------------
ERROR: POPFile needs Perl module Services::IMAP::Client, please install it.
POPFile Engine v1.0.0 running
DBD::SQLite2::st execute failed: unable to open database file(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3368.
DBD::SQLite2::db do failed: unable to open database file(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN346> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN346> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN346> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN346> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN346> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN346> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN346> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN348> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN348> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN348> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN348> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN348> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN348> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN348> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN352> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN352> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN352> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN352> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN352> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN352> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN352> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN362> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN362> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN362> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN362> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN362> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN362> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN362> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN364> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN364> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN364> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN364> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN364> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN364> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN364> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN364> line 8.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN364> line 8.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN364> line 8.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN364> line 8.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN364> line 8.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN364> line 8.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN364> line 8.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN372> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN372> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN372> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN372> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN372> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN372> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN372> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN374> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN374> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN374> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN374> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN374> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN374> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN374> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN380> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN380> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN380> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN380> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3650, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2107, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2132, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN380> line 7.
Use of uninitialized value in numeric eq (==) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2702, <GEN380> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN380> line 7.
Use of uninitialized value in numeric eq (==) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2755, <GEN380> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN380> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325.
Use of uninitialized value in addition (+) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 413.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3368.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN383> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN383> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN383> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN383> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN383> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 412 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3650, <GEN383> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 412 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2107, <GEN383> line 7.
POPFile Engine v1.0.0 running
DBD::SQLite2::st execute failed: unable to open database file(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3368.
DBD::SQLite2::db do failed: unable to open database file(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN42> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN42> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN42> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN42> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN42> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN42> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN42> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN42> line 8.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN42> line 8.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN42> line 8.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN42> line 8.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN42> line 8.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN42> line 8.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN42> line 8.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN44> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN44> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN44> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN44> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN44> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN44> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN44> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN48> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN48> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN48> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN48> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN48> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN48> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN48> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN50> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN50> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN50> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN50> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN50> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN50> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN50> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN52> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN52> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN52> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2783, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2783, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2807, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2819, <GEN52> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN52> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN54> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN54> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN54> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN54> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3650, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2107, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2132, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN54> line 7.
Use of uninitialized value in numeric eq (==) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2702, <GEN54> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN54> line 7.
Use of uninitialized value in numeric eq (==) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2755, <GEN54> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN54> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325.
Use of uninitialized value in addition (+) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 413.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3368.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN57> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN57> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN57> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN57> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN57> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 412 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3650, <GEN57> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 412 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2107, <GEN57> line 7.
OK. Those captured messages make it pretty obvious, that your POPFile will sometimes have trouble executing database queries. I just have no idea why.
It seem that when it's crashing, you aren't necessarily anywhere near your computer and thus all it can do at that time is classify a message? It will not crash each time a message is classified and when it's not crashing it does what it's supposed to do? What OS are you using? Have you enabled forking/concurrent pop3 access?
Manni
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> I ran the Message Capture utility and the result is posted below ... Sorry this post is so long. If there is an easier way to reduce the length of the info, please let me know. <<
There is no need to apologise. I deliberately asked for the entire Message Capture report because I was interested in more than just whatever warnings or error messages appeared in it. For example it shows that you are not using the system tray icon, so we cannot blame that for your problems!
As Manni says, it seems that POPFile eventually runs into a problem with access to the database, as shown in the very first error message:
DBD::SQLite2::st execute failed: unable to open database file(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3368.
A couple of lines later there is this error:
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN346> line 7.
If I remember correctly one of the things that we changed for this release was to use "transactions" for some operations that could go wrong under high load when concurrent POP3 mode was enabled. By default POPFile does not use concurrent POP3 mode. (It is also possible that this reference to a transaction is simply a side-effect of POPFile's inability to access the database.)
The CONFIGURATION page in POPFile's UI shows the current setting: if it says "Allow concurrent POP3 connections: No" and has a button labelled "Change to Yes" then the mode is disabled.
How many email accounts are being checked by POPFile?
How often is the email client checking for new mail?
How many messages are being processed by POPFile, e.g. is it 100 per day, 1,000 per day, 10,000 per day?
Have you recently experienced an increase in the amount of mail being processed ?
If you have enabled concurrent POP3 connections then I think disabling them should make POPFile less likely to crash, assuming your problem is connected with the high load problem I mentioned earlier.
If POPFile is being used to process more than one email account then disabling concurrent POP3 connections will mean that POPFile will take longer than usual to process all of the mail so you may need to adjust some account timeouts in the email client to stop it from complaining about a lack of response from POPFile.
POPFile automatically deletes old log files. I think it would be a good idea to make a copy of the log files(s) that cover the periods shown in the two Message Capture reports you posted. In an earlier message I explained how to access the folder where the log files are stored. The file timestamps should let you identify the relevant popfile??????????.log files. If you make a copy of these files with names such as savedlog-1.log, savedlog-2.log, etc then it should be possible to get some idea of what POPFile was doing at the time it lost access to the database. These log files will be pretty big (several MB?) and will contain the _entire_ text of every email message processed (if you are still using logger_level set to 2).
I don't know much about the database side of things so I cannot think of anything else to suggest at the moment. Perhaps Naoki or John will have a better idea of how to investigate this further.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> I don't know much about the database side of things so I cannot think of anything else to suggest at the moment. Perhaps Naoki or John will have a better idea of how to investigate this further. <<
We can get more database-related log by setting DBI_TRACE
environment variable. We can see all of the database
accesses when we set DBI_TRACE to '1'.
But I have no idea whether this option gives us any useful
information for us in this case.
>> Anyway, I think it may be useful if the Message Capture utility has an option to set this environment variable. <<
Yes, that sounds like a good idea (and it will be easy to implement it).
>> But I have no idea whether this option gives us any useful information for us in this case. <<
I can easily build a special version of the Message Capture utility which uses DBI_TRACE set to 1 and make it available for download (dbicapture.exe perhaps?). It could then be used instead of the msgcapture.exe program to start POPFile and display all the DBI trace output (and the usual console messages) in a scrollable window.
Brian
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
>> I can easily build a special version of the Message Capture utility which uses DBI_TRACE set to 1 and make it available for download (dbicapture.exe perhaps?). It could then be used instead of the msgcapture.exe program to start POPFile and display all the DBI trace output (and the usual console messages) in a scrollable window. <<
That sounds good.
And I think it is better if we can change the DBI_TRACE variable
by using a command-line parameter (e.g. dbicapture.exe /TRACE_LEVEL=3).
Naoki
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
POPFile has run flawlessly on my computer for years. This past week, however, the program crashes 3-4 times a day while downloading mail. I am running WinVista and get a popup dialog that says "POPFile has stopped running."
Once I restart POPFile, it works fine until it stops running again.
I have not made any significant changes to my computer set up, nor installed any new programs. Any suggestions as to where the problem might lie?
Thanks.
Mitch
Are you using the latest version? We released version 1.0 recently. There have been some fixes in recent versions for strange spam emails that would cause POPFile to crash.
Yes, I installed 1.o shortly after it was released in December.
Is it crashing (the program quits) or freezing (you have to kill the program)? Freezing can be caused by the trayicon.
http://popfile.sourceforge.net/wiki/troubleshooting:freeze
If it is crashing, see if your logfile will give any clue about what is happing. See this page:
http://popfile.sourceforge.net/wiki/troubleshooting:preparelog
I stopped using the tray icon long ago because of the problems it caused. I will enable logging and the next time it crashes, I will post the log. Thanks for your suggestions. Have a good weekend.
Mitch
OK, my log is below. I copied it immediately after POPFile crashed while I was trying to recategorize some emails. What is the diagnosis, doc? Thanks for your help.
2008/1/18 18:04:47 4916: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/18 18:04:47 4916: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/18 18:04:48 4916: pop3: 668: POP3 proxy done
2008/1/18 18:09:58 4916: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/18 18:09:58 4916: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/18 18:09:59 4916: pop3: 668: POP3 proxy done
2008/1/18 18:10:16 4916: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/18 18:10:16 4916: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/18 18:10:17 4916: pop3: 668: POP3 proxy done
2008/1/19 15:16:13 4992: bayes: 747: Attempting to connect to dbi:SQLite2:dbname=C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile/popfile.db (1)
2008/1/19 15:16:15 4992: bayes: 753: Using SQLite library version 2.8.15
2008/1/19 15:18:10 4992: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
2008/1/19 15:36:04 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 15:36:04 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 15:36:27 4992: pop3: 668: POP3 proxy done
2008/1/19 15:40:57 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 15:40:57 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 15:40:58 4992: pop3: 668: POP3 proxy done
2008/1/19 15:46:17 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 15:46:17 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 15:46:18 4992: pop3: 668: POP3 proxy done
2008/1/19 15:51:19 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 15:51:19 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 15:51:23 4992: pop3: 668: POP3 proxy done
2008/1/19 15:56:24 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 15:56:24 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 15:56:25 4992: pop3: 668: POP3 proxy done
2008/1/19 16:01:29 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:01:29 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:01:30 4992: pop3: 668: POP3 proxy done
2008/1/19 16:06:42 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:06:42 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:06:43 4992: pop3: 668: POP3 proxy done
2008/1/19 16:12:02 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:12:02 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:12:03 4992: pop3: 668: POP3 proxy done
2008/1/19 16:17:07 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:17:07 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:17:08 4992: pop3: 668: POP3 proxy done
2008/1/19 16:22:12 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:22:12 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:22:16 4992: pop3: 668: POP3 proxy done
2008/1/19 16:27:21 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:27:21 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:27:22 4992: pop3: 668: POP3 proxy done
2008/1/19 16:32:28 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:32:28 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:32:31 4992: pop3: 668: POP3 proxy done
2008/1/19 16:37:47 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:37:47 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:37:48 4992: pop3: 668: POP3 proxy done
2008/1/19 16:42:57 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:42:57 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:42:58 4992: pop3: 668: POP3 proxy done
2008/1/19 16:48:02 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:48:02 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:48:03 4992: pop3: 668: POP3 proxy done
2008/1/19 16:53:20 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:53:20 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:53:21 4992: pop3: 668: POP3 proxy done
2008/1/19 16:58:25 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 16:58:25 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 16:58:26 4992: pop3: 668: POP3 proxy done
2008/1/19 17:03:30 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 17:03:30 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 17:03:31 4992: pop3: 668: POP3 proxy done
2008/1/19 17:08:31 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 17:08:31 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 17:08:32 4992: pop3: 668: POP3 proxy done
2008/1/19 17:10:50 4992: bayes: 486: Reclassification from spam to info
2008/1/19 17:10:50 4992: history: 409: Change slot classification of 2295 to info
2008/1/19 17:13:34 4992: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 17:13:34 4992: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 17:13:35 4992: pop3: 668: POP3 proxy done
2008/1/19 17:16:15 4992: bayes: 486: Reclassification from unclassified to info
2008/1/19 17:16:15 4992: history: 409: Change slot classification of 2216 to info
2008/1/19 17:17:16 4992: bayes: 486: Reclassification from to main
2008/1/19 17:17:16 4992: history: 409: Change slot classification of 2161 to main
2008/1/19 17:19:11 4440: bayes: 747: Attempting to connect to dbi:SQLite2:dbname=C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile/popfile.db (1)
2008/1/19 17:19:11 4440: bayes: 753: Using SQLite library version 2.8.15
2008/1/19 17:19:16 4440: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
2008/1/19 17:19:49 2612: bayes: 747: Attempting to connect to dbi:SQLite2:dbname=C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile/popfile.db (1)
2008/1/19 17:19:49 2612: bayes: 753: Using SQLite library version 2.8.15
2008/1/19 17:19:52 2612: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
2008/1/19 17:19:59 2612: pop3: 504: Attempting to connect to SSL server at pop.gmail.com:995
2008/1/19 17:19:59 2612: pop3: 521: Connected to pop.gmail.com:995 timeout 60
2008/1/19 17:20:00 2612: pop3: 668: POP3 proxy done
2008/1/19 17:20:22 2612: bayes: 486: Reclassification from unclassified to info
2008/1/19 17:20:23 2612: history: 409: Change slot classification of 2216 to info
2008/1/19 17:20:23 2612: bayes: 486: Reclassification from unclassified to main
2008/1/19 17:20:23 2612: history: 409: Change slot classification of 2161 to main
Here's another log after crash:
2008/1/21 07:40:40 5004: bayes: 747: Attempting to connect to dbi:SQLite2:dbname=C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile/popfile.db (1)
2008/1/21 07:40:40 5004: bayes: 753: Using SQLite library version 2.8.15
2008/1/21 07:40:42 5004: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
Thanks!
As you have no doubt figured out by now, each time it crashes, the same error message appears. It always looks like this:
2008/1/21 11:42:52 596: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
Thoughts and suggestions?? Many thanks!
That part (the warnings) is normal POPFile startup. That is just the warning you get when POPFile starts if you don't have all the optional parts installed. The crash should be just above that. I didn't recognize anything unusual from the longer log you sent. The crash sees to be happening when you reclassify message 2161. Is it always the same message, is there anything unusual about the message? Try turning up the logger level one more time so we get the extremely detailed version. It will include the contents of your email so if it is anything you can't post publicly, you can email it to me instead of post it here.
If it is always the same message, we need to look at the original so don't delete it. You may want to increase the time POPFile keeps messages in history in that case until we get it or figure out what is causing it. We have a Download Message link at the bottom of the Message View in POPFile.
These are the lines from your history right before both crashes in long log file:
bayes: 486: Reclassification from unclassified to main
history: 409: Change slot classification of 2161 to main
Thanks for that response. It has not been crashing only when I reclassify messages. For instance, I left it on overnight and this morning, it was DOA when I came to the computer. I did not realize that the logging setting reset itself, so I will change the setting again.
If it is crashing when I reclassify emails, why is it always crashing on 2161? I only recategorize an email once. In other words, I didn't categorize email 2161 more than once, even though the log file seems to say I did.
I'll post another log or email it to you as soon as it crashes again. Thanks.
You probably did reclassify it twice because it didn't stick the first time since it died right away.
I don't think logging should reset itself. If you are talking about where I said turn it up again, I meant turn it to the highest level of detail. Looks like it already is though if you followed the prepare a log instructions on the wiki. I forgot what level 2 logs looked like for reclassification. Usually we have problems with POP downloads which show a lot more information.
Have you tried reinstalling POPFile? Maybe you got a corrupt file. It is strange that it is dying during reclassification and when just sitting idle. Do you leave your mail client open overnight so it is checking all the time? Be sure you didn't accidentally turn the trayicon back on, what is happening certainly reminds me of the problems that can sometimes cause.
Have you checked POPFile's database? If it gets corrupted strange things can happen.
Shutdown POPFile and use this shortcut created by the installer:
Start -- All Programs -- POPFile -- Support -- Check database status
Brian
Handy tip Brian for the database check. Thanks
Tim
Thanks for the suggestion on checking the database. My database checked out fine. HOwever, during the last 24 hours, I have not had a crash. I did try to reinstall POPFile (without uninstalling the current version) as an upgrade by having it install language support modules that I had opted out of originally. I am not sure if that should make a difference or whether the reinstall repaired damaged files. Whatever the reason, I am good at the moment. Thanks for all your suggestions. Cross your fingers that my problems don't recur.
Talk about jinxing something . . . After posting the last entry, I walked away from my computer. When I returned it had crashed. All detective work appreciated. Here is the log for the last few minutes:
2008/1/22 19:51:55 4840: mq: 377: post UIREG (configuration:windows_trayicon_and_console:windows-configuration.thtml:Platform::MSWin32=HASH(0x2689694)) 2008/1/22 19:51:55 4840: mq: 384: queuing post UIREG (configuration:windows_trayicon_and_console:windows-configuration.thtml:Platform::MSWin32=HASH(0x2689694)) 2008/1/22 19:51:55 4840: mq: 386: UIREG queue length now 0
2008/1/22 19:51:55 4840: bayes: 747: Attempting to connect to dbi:SQLite2:dbname=C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile/popfile.db (1)
2008/1/22 19:51:55 4840: bayes: 753: Using SQLite library version 2.8.15
2008/1/22 19:51:56 4840: bayes: 1919: get_session_key returning key 54P9q9qBrlm3Mguz4pA3 for user XXXXXX
2008/1/22 19:51:56 4840: mq: 377: post RELSE (54P9q9qBrlm3Mguz4pA3)
2008/1/22 19:51:56 4840: mq: 384: queuing post RELSE (54P9q9qBrlm3Mguz4pA3) 2008/1/22 19:51:56 4840: mq: 386: RELSE queue length now 0
2008/1/22 19:51:57 4840: html: 65: Trying to open listening socket on port 8080.
2008/1/22 19:51:57 4840: mq: 377: post UIREG (configuration:pop3_configuration:pop3-configuration-panel.thtml:Proxy::POP3=HASH(0x2a31774)) 2008/1/22 19:51:57 4840: mq: 384: queuing post UIREG (configuration:pop3_configuration:pop3-configuration-panel.thtml:Proxy::POP3=HASH(0x2a31774)) 2008/1/22 19:51:57 4840: mq: 386: UIREG queue length now 1
2008/1/22 19:51:57 4840: mq: 377: post UIREG (security:pop3_security:pop3-security-panel.thtml:Proxy::POP3=HASH(0x2a31774))
2008/1/22 19:51:57 4840: mq: 384: queuing post UIREG (security:pop3_security:pop3-security-panel.thtml:Proxy::POP3=HASH(0x2a31774))
2008/1/22 19:51:57 4840: mq: 386: UIREG queue length now 2
2008/1/22 19:51:57 4840: mq: 377: post UIREG (chain:pop3_chain:pop3-chain-panel.thtml:Proxy::POP3=HASH(0x2a31774))
2008/1/22 19:51:57 4840: mq: 384: queuing post UIREG (chain:pop3_chain:pop3-chain-panel.thtml:Proxy::POP3=HASH(0x2a31774))
2008/1/22 19:51:57 4840: mq: 386: UIREG queue length now 3
2008/1/22 19:51:57 4840: pop3: 130: Opening listening socket on port 110.
2008/1/22 19:51:57 4840: mq: 377: post UIREG (configuration:pop3_socks_configuration:socks-widget.thtml:Proxy::POP3=HASH(0x2a31774)) 2008/1/22 19:51:57 4840: mq: 384: queuing post UIREG (configuration:pop3_socks_configuration:socks-widget.thtml:Proxy::POP3=HASH(0x2a31774)) 2008/1/22 19:51:57 4840: mq: 386: UIREG queue length now 4
2008/1/22 19:51:57 4840: WARNING: POPFile may require Perl module Encode; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module Encode::Guess; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module IO::Socket::Socks; it is needed for "Socks Proxy Support".[0a]WARNING: POPFile may require Perl module Text::Kakasi; it is needed for "Japanese Language Support".[0a]WARNING: POPFile may require Perl module XMLRPC::Transport::HTTP; it is needed for "XML-RPC Server Support".[0a]
2008/1/22 19:51:57 4840: mq: 128: Message RELSE (54P9q9qBrlm3Mguz4pA3) ready for delivery 2008/1/22 19:51:57 4840: mq: 131: Delivering message RELSE (54P9q9qBrlm3Mguz4pA3) to bayes 2008/1/22 19:51:57 4840: bayes: 1817: release_session_key releasing key 54P9q9qBrlm3Mguz4pA3 for user XXXXXX
2008/1/22 19:51:57 4840: mq: 128: Message UIREG (configuration:windows_trayicon_and_console:windows-configuration.thtml:Platform::MSWin32=HASH(0x2689694)) ready for delivery
2008/1/22 19:51:57 4840: mq: 131: Delivering message UIREG (configuration:windows_trayicon_and_console:windows-configuration.thtml:Platform::MSWin32=HASH(0x2689694)) to html
2008/1/22 19:51:57 4840: mq: 128: Message UIREG (configuration:pop3_configuration:pop3-configuration-panel.thtml:Proxy::POP3=HASH(0x2a31774)) ready for delivery 2008/1/22 19:51:57 4840: mq: 131: Delivering message UIREG (configuration:pop3_configuration:pop3-configuration-panel.thtml:Proxy::POP3=HASH(0x2a31774)) to html
2008/1/22 19:51:57 4840: mq: 128: Message UIREG (security:pop3_security:pop3-security-panel.thtml:Proxy::POP3=HASH(0x2a31774)) ready for delivery
2008/1/22 19:51:57 4840: mq: 131: Delivering message UIREG (security:pop3_security:pop3-security-panel.thtml:Proxy::POP3=HASH(0x2a31774)) to html 2008/1/22 19:51:57 4840: mq: 128: Message UIREG (chain:pop3_chain:pop3-chain-panel.thtml:Proxy::POP3=HASH(0x2a31774)) ready for delivery 2008/1/22 19:51:57 4840: mq: 131: Delivering message UIREG (chain:pop3_chain:pop3-chain-panel.thtml:Proxy::POP3=HASH(0x2a31774)) to html
2008/1/22 19:51:57 4840: mq: 128: Message UIREG (configuration:pop3_socks_configuration:socks-widget.thtml:Proxy::POP3=HASH(0x2a31774)) ready for delivery
2008/1/22 19:51:57 4840: mq: 131: Delivering message UIREG (configuration:pop3_socks_configuration:socks-widget.thtml:Proxy::POP3=HASH(0x2a31774)) to html
2008/1/22 19:51:57 4840: html: 658: Read slurp data GET / HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11[0d][0a]Accept: text/xml
2008/1/22 19:51:57 4840: html: 154: GET / HTTP/1.1[0d][0a]
2008/1/22 19:51:57 4840: html: 658: Read slurp data ,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Acc 2008/1/22 19:51:57 4840: html: 658: Read slurp data ept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 300[0d][0a]Connection: keep-alive[0d][0a][0d][0a]
2008/1/22 19:51:58 4840: bayes: 1919: get_session_key returning key ag6v80FRAqM9dLNVn for user XXXXXX
2008/1/22 19:51:58 4840: history: 1012: Base query is select XXX from[0a] history, buckets, magnets where history.userid = 1 and committed = 1 and history.bucketid = buckets.id and magnets.id = magnetid order by inserted desc;
2008/1/22 19:51:58 4840: history: 1100: Request for rows 1 (150), current size 0
2008/1/22 19:51:58 4840: history: 1104: Getting 151 rows from database
2008/1/22 19:51:58 4840: history: 1112: Returning 0..149 2008/1/22 19:51:59 4840: html: 181: HTTP handle_url returned code 1[0a]
2008/1/22 19:51:59 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x2476b90)[0a]
2008/1/22 19:52:00 4840: html: 658: Read slurp data GET /favicon.ico HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11[0d][0a]Accep
2008/1/22 19:52:00 4840: html: 154: GET /favicon.ico HTTP/1.1[0d][0a]
2008/1/22 19:52:00 4840: html: 658: Read slurp data t: image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 300[0d][0a]Connect 2008/1/22 19:52:00 4840: html: 658: Read slurp data ion: keep-alive[0d][0a][0d][0a]
2008/1/22 19:52:00 4840: html: 181: HTTP handle_url returned code 1[0a]
2008/1/22 19:52:00 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x2476bcc)[0a]
2008/1/22 19:52:00 4840: html: 658: Read slurp data GET /skins/smalldefault/style.css HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefo
2008/1/22 19:52:00 4840: html: 154: GET /skins/smalldefault/style.css HTTP/1.1[0d][0a] 2008/1/22 19:52:00 4840: html: 658: Read slurp data x/2.0.0.11[0d][0a]Accept: text/css,*/*;q=0.1[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Ali
2008/1/22 19:52:00 4840: html: 658: Read slurp data ve: 300[0d][0a]Connection: keep-alive[0d][0a]Referer: http://localhost:8080/\[0d][0a][0d][0a]
2008/1/22 19:52:00 4840: html: 181: HTTP handle_url returned code 1[0a]
2008/1/22 19:52:00 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x2476b9c)[0a] 2008/1/22 19:52:01 4840: html: 658: Read slurp data GET /skins/default/magnet.png HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2. 2008/1/22 19:52:01 4840: html: 154: GET /skins/default/magnet.png HTTP/1.1[0d][0a]
2008/1/22 19:52:01 4840: html: 658: Read slurp data 0.0.11[0d][0a]Accept: image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 2008/1/22 19:52:01 4840: html: 658: Read slurp data 300[0d][0a]Connection: keep-alive[0d][0a]Referer: http://localhost:8080/\[0d][0a][0d][0a]
2008/1/22 19:52:01 4840: html: 181: HTTP handle_url returned code 1[0a]
2008/1/22 19:52:01 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x2476938)[0a]
2008/1/22 19:52:02 4840: html: 658: Read slurp data GET /otto.png HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Firefox/2.0.0.11[0d][0a]Accept:
2008/1/22 19:52:02 4840: html: 154: GET /otto.png HTTP/1.1[0d][0a]
2008/1/22 19:52:02 4840: html: 658: Read slurp data image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 300[0d][0a]Connection
2008/1/22 19:52:02 4840: html: 658: Read slurp data : keep-alive[0d][0a]Referer: http://localhost:8080/\[0d][0a][0d][0a]
2008/1/22 19:52:02 4840: html: 181: HTTP handle_url returned code 1[0a]
2008/1/22 19:52:02 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x2476c14)[0a]
2008/1/22 19:52:07 4840: html: 658: Read slurp data GET /configuration?session=oVi28QID HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/20071127 Fire
2008/1/22 19:52:07 4840: html: 154: GET /configuration?session=oVi28QID HTTP/1.1[0d][0a] 2008/1/22 19:52:07 4840: html: 658: Read slurp data fox/2.0.0.11[0d][0a]Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q=0.5[0d][0a]Acce 2008/1/22 19:52:07 4840: html: 658: Read slurp data pt-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 300[0d][0a]Connection: keep-alive[0d][0a]Referer: http://localhost:8080/\[0d][0a][0d][0a] 2008/1/22 19:52:07 4840: html: 181: HTTP handle_url returned code 1[0a] 2008/1/22 19:52:07 4840: html: 189: Close HTTP connection on IO::Socket::INET=GLOB(0x24774fc)[0a]
2008/1/22 19:52:10 4840: html: 658: Read slurp data GET /popfile_current_log.log?session=oVi28QID HTTP/1.1[0d][0a]Host: localhost:8080[0d][0a]User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.11) Gecko/200 2008/1/22 19:52:10 4840: html: 154: GET /popfile_current_log.log?session=oVi28QID HTTP/1.1[0d][0a]
2008/1/22 19:52:11 4840: html: 658: Read slurp data 71127 Firefox/2.0.0.11[0d][0a]Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5[0d][0a]Accept-Language: en-us,en;q 2008/1/22 19:52:11 4840: html: 658: Read slurp data =0.5[0d][0a]Accept-Encoding: gzip,deflate[0d][0a]Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7[0d][0a]Keep-Alive: 300[0d][0a]Connection: keep-alive[0d][0a]Referer: http://localhost:8080/con 2008/1/22 19:52:11 4840: html: 658: Read slurp data figuration?session=oVi28QID[0d][0a][0d][0a]
>> After posting the last entry, I walked away from my computer. When I returned it had crashed. All detective work appreciated. <<
The log file is not the only place where information about crashes can be found. Sometimes POPFile generates some console warnings or error messages when things go wrong. Normally these messages are hidden (i.e. not displayed). The easiest way to see these messages on a Windows system is to use the Message Capture utility.
I'm assuming you have POPFile configured to start automatically when Windows starts up. If POPFile now crashes almost every time you use it I think the easiest thing to do is shutdown POPFile and then use this shortcut:
Start -- All Programs -- POPFile -- Support -- Message Capture utility
This will start POPFile using your normal settings but it will display the console messages in a scrollable window and let you copy these messages to the clipboard. If you see the message
"ERROR: POPFile needs Perl module Services::IMAP::Client, please install it."
please ignore it - this is a harmless bug in the 1.0.0 release.
Once you see the message "POPFile Engine v1.0.0 running" in the scrollable window POPFile is ready for use.
When POPFile crashes some new messages will appear in the scrollable window, includes the date and time the crash was detected by the utility. This will help identify the relevant parts of the log file.
If you right-click in that scrollable window you can copy all of the messages to the clipboard and save them. If you post all of the messages here it may help us work out what is going wrong.
If POPFile does not crash then you will have to remember to use the Message Capture utility the next time you start POPFile so you can capture the console messages the next time POPFile crashes.
The POPFile wiki has a page explaining how you can use the POPFile UI to enable/disable the Message Capture utility instead of having to remember to use its Start Menu shortcut every time: http://popfile.sourceforge.net/wiki/howtos:messagecapture
>> When I returned it had crashed ... Here is the log for the last few minutes: <<
As you are no doubt aware by now, logger_level 2 generates a _lot_ of information in the log file.
I'm no expert at interpreting these log files but the extract you supplied only seems to show that you started POPFile, accessed the UI, selected the CONFIGURATION page and clicked the "View current log file" link.
I think it would be better to stop using the UI to access the log files, in order to reduce the amount of irrelevant information in the log.
POPFile's log files have names like popfile1201046400.log and are normally kept in the POPFile "User Data" folder. On some systems this folder is not easy to display so the installer creates a shortcut to make this easier:
Start -- All Programs -- POPFile -- Support -- Create 'User Data' shortcut
This shortcut will add a new shortcut to the Start Menu for you. On my system I use an account called "Brian" so that shortcut creates this new Start Menu entry for me:
Start -- All Programs -- POPFile -- Support -- User Data (Brian)
The "User Data (Brian)" shortcut displays the contents of my POPFile User Data folder. At the moment I have 3 log files there (amongst many other files):
popfile1200873600.log 21/01/2008 20:46
popfile1200960000.log 22/01/2008 22:36
popfile1201046400.log 23/01/2008 13:01
These log files are simple text files.
Brian
Brian,
Thanks for your suggestions. I ran the Message Capture utility and the result is posted below. This time, POPfile ran for about 18 hours until it completely crashed while I was away from my computer. It seems that it is not crashing as frequently lately. Sorry this post is so long. If there is an easier way to reduce the length of the info, please let me know. I appreciate your (and everyone else's) terrific assistance.
Mitch
------------------------------------------------------------
POPFile Message Capture Utility v0.1.6
------------------------------------------------------------
POPFILE_ROOT = C:\PROGRA~1\POPFile
POPFILE_USER = C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile
Using 'popfilef.exe' to run POPFile
------------------------------------------------------------
(report started 23-Jan-2008 @ 16:23:30)
------------------------------------------------------------
ERROR: POPFile needs Perl module Services::IMAP::Client, please install it.
POPFile Engine loading
Loading...
{core: windows}
{core: config history logger mq}
{classifier: bayes wordmangle}
{interface: html}
{proxy: pop3}
{services:}
POPFile Engine v1.0.0 starting
Initializing...
{core: config history logger mq windows}
{classifier: bayes wordmangle}
{interface: html}
{proxy: pop3
A copy of POPFile appears to be running.
Attempting to signal the previous copy.
Waiting 10 seconds for a reply.
The other POPFile (2484) failed to signal back, starting new copy (3724)
}
{services:}
Starting...
{core: config history logger mq windows}
{classifier: bayes wordmangle}
{interface: html}
{proxy: pop3}
{services:}
POPFile Engine v1.0.0 running
DBD::SQLite2::st execute failed: unable to open database file(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3368.
DBD::SQLite2::db do failed: unable to open database file(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN346> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN346> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN346> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN346> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN346> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN346> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN346> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN348> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN348> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN348> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN348> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN348> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN348> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN348> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN352> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN352> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN352> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN352> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN352> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN352> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN352> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN362> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN362> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN362> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN362> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN362> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN362> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN362> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN364> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN364> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN364> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN364> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN364> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN364> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN364> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN364> line 8.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN364> line 8.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN364> line 8.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN364> line 8.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN364> line 8.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN364> line 8.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN364> line 8.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN372> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN372> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN372> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN372> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN372> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN372> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN372> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN374> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN374> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN374> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN374> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN374> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN374> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN374> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN380> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN380> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN380> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN380> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3650, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2107, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2132, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN380> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN380> line 7.
Use of uninitialized value in numeric eq (==) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2702, <GEN380> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN380> line 7.
Use of uninitialized value in numeric eq (==) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2755, <GEN380> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN380> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325.
Use of uninitialized value in addition (+) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 413.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3368.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN383> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN383> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN383> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN383> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN383> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 412 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3650, <GEN383> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 412 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2107, <GEN383> line 7.
------------------------------------------------------------
Status code: -1073741819
------------------------------------------------------------
(report finished 24-Jan-2008 @ 10:34:36)
------------------------------------------------------------
Another crash . . .another Message Capture Utility log:
------------------------------------------------------------
POPFile Message Capture Utility v0.1.6
------------------------------------------------------------
POPFILE_ROOT = C:\PROGRA~1\POPFile
POPFILE_USER = C:\DOCUME~2\APPLIC~1\POPFIL~1\POPFile
Using 'popfilef.exe' to run POPFile
------------------------------------------------------------
(report started 24-Jan-2008 @ 13:25:28)
------------------------------------------------------------
ERROR: POPFile needs Perl module Services::IMAP::Client, please install it.
POPFile Engine loading
Loading...
{core: windows}
{core: config history logger mq}
{classifier: bayes wordmangle}
{interface: html}
{proxy: pop3}
{services:}
POPFile Engine v1.0.0 starting
Initializing...
{core: config history logger mq windows}
{classifier: bayes wordmangle}
{interface: html}
{proxy: pop3
A copy of POPFile appears to be running.
Attempting to signal the previous copy.
Waiting 10 seconds for a reply.
The other POPFile (3724) failed to signal back, starting new copy (5748)
}
{services:}
Starting...
{core: config history logger mq windows}
{classifier: bayes wordmangle}
{interface: html}
{proxy: pop3}
{services:}
POPFile Engine v1.0.0 running
DBD::SQLite2::st execute failed: unable to open database file(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3368.
DBD::SQLite2::db do failed: unable to open database file(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN42> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN42> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN42> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN42> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN42> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN42> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN42> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN42> line 8.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN42> line 8.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN42> line 8.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN42> line 8.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN42> line 8.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN42> line 8.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN42> line 8.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN44> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN44> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN44> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN44> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN44> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN44> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN44> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN48> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN48> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN48> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN48> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN48> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN48> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN48> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN50> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN50> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN50> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN50> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN50> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN50> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN50> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN52> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN52> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN52> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2783, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2783, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2807, <GEN52> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2819, <GEN52> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN52> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN54> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN54> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN54> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN54> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3650, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2107, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2132, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318, <GEN54> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325, <GEN54> line 7.
Use of uninitialized value in numeric eq (==) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2702, <GEN54> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2733, <GEN54> line 7.
Use of uninitialized value in numeric eq (==) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2755, <GEN54> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 376, <GEN54> line 7.
Use of uninitialized value in join or string at C:\PROGRA~1\POPFile/POPFile/MQ.pm line 126.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3318.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3325.
Use of uninitialized value in addition (+) at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 413.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3368.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 628.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN57> line 7.
DBD::SQLite2::db do failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 305, <GEN57> line 7.
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 310, <GEN57> line 7.
Use of uninitialized value in concatenation (.) or string at C:\PROGRA~1\POPFile/POPFile/History.pm line 316, <GEN57> line 7.
Use of uninitialized value in sprintf at C:\PROGRA~1\POPFile/POPFile/History.pm line 774, <GEN57> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 412 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3650, <GEN57> line 7.
DBD::SQLite2::st execute failed: database is locked(1) at dbdimp.c line 412 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 2107, <GEN57> line 7.
------------------------------------------------------------
Status code: -1073741819
------------------------------------------------------------
(report finished 24-Jan-2008 @ 15:42:22)
------------------------------------------------------------
OK. Those captured messages make it pretty obvious, that your POPFile will sometimes have trouble executing database queries. I just have no idea why.
It seem that when it's crashing, you aren't necessarily anywhere near your computer and thus all it can do at that time is classify a message? It will not crash each time a message is classified and when it's not crashing it does what it's supposed to do? What OS are you using? Have you enabled forking/concurrent pop3 access?
Manni
>> I ran the Message Capture utility and the result is posted below ... Sorry this post is so long. If there is an easier way to reduce the length of the info, please let me know. <<
There is no need to apologise. I deliberately asked for the entire Message Capture report because I was interested in more than just whatever warnings or error messages appeared in it. For example it shows that you are not using the system tray icon, so we cannot blame that for your problems!
As Manni says, it seems that POPFile eventually runs into a problem with access to the database, as shown in the very first error message:
DBD::SQLite2::st execute failed: unable to open database file(1) at dbdimp.c line 419 at C:\PROGRA~1\POPFile/Classifier/Bayes.pm line 3368.
A couple of lines later there is this error:
DBD::SQLite2::db selectrow_arrayref failed: cannot start a transaction within a transaction(1) at dbdimp.c line 402 at C:\PROGRA~1\POPFile/POPFile/History.pm line 292, <GEN346> line 7.
If I remember correctly one of the things that we changed for this release was to use "transactions" for some operations that could go wrong under high load when concurrent POP3 mode was enabled. By default POPFile does not use concurrent POP3 mode. (It is also possible that this reference to a transaction is simply a side-effect of POPFile's inability to access the database.)
The CONFIGURATION page in POPFile's UI shows the current setting: if it says "Allow concurrent POP3 connections: No" and has a button labelled "Change to Yes" then the mode is disabled.
How many email accounts are being checked by POPFile?
How often is the email client checking for new mail?
How many messages are being processed by POPFile, e.g. is it 100 per day, 1,000 per day, 10,000 per day?
Have you recently experienced an increase in the amount of mail being processed ?
If you have enabled concurrent POP3 connections then I think disabling them should make POPFile less likely to crash, assuming your problem is connected with the high load problem I mentioned earlier.
If POPFile is being used to process more than one email account then disabling concurrent POP3 connections will mean that POPFile will take longer than usual to process all of the mail so you may need to adjust some account timeouts in the email client to stop it from complaining about a lack of response from POPFile.
POPFile automatically deletes old log files. I think it would be a good idea to make a copy of the log files(s) that cover the periods shown in the two Message Capture reports you posted. In an earlier message I explained how to access the folder where the log files are stored. The file timestamps should let you identify the relevant popfile??????????.log files. If you make a copy of these files with names such as savedlog-1.log, savedlog-2.log, etc then it should be possible to get some idea of what POPFile was doing at the time it lost access to the database. These log files will be pretty big (several MB?) and will contain the _entire_ text of every email message processed (if you are still using logger_level set to 2).
I don't know much about the database side of things so I cannot think of anything else to suggest at the moment. Perhaps Naoki or John will have a better idea of how to investigate this further.
Brian
Brian,
>> I don't know much about the database side of things so I cannot think of anything else to suggest at the moment. Perhaps Naoki or John will have a better idea of how to investigate this further. <<
We can get more database-related log by setting DBI_TRACE
environment variable. We can see all of the database
accesses when we set DBI_TRACE to '1'.
But I have no idea whether this option gives us any useful
information for us in this case.
For more information, see:
http://search.cpan.org/~timb/DBI-1.601/DBI.pm#DBI_TRACE
http://search.cpan.org/~timb/DBI-1.601/DBI.pm#TRACING
Anyway, I think it may be useful if the Message Capture
utility has an option to set this environment variable.
Naoki
>> Anyway, I think it may be useful if the Message Capture utility has an option to set this environment variable. <<
Yes, that sounds like a good idea (and it will be easy to implement it).
>> But I have no idea whether this option gives us any useful information for us in this case. <<
I can easily build a special version of the Message Capture utility which uses DBI_TRACE set to 1 and make it available for download (dbicapture.exe perhaps?). It could then be used instead of the msgcapture.exe program to start POPFile and display all the DBI trace output (and the usual console messages) in a scrollable window.
Brian
Brian,
>> I can easily build a special version of the Message Capture utility which uses DBI_TRACE set to 1 and make it available for download (dbicapture.exe perhaps?). It could then be used instead of the msgcapture.exe program to start POPFile and display all the DBI trace output (and the usual console messages) in a scrollable window. <<
That sounds good.
And I think it is better if we can change the DBI_TRACE variable
by using a command-line parameter (e.g. dbicapture.exe /TRACE_LEVEL=3).
Naoki
>> And I think it is better if we can change the DBI_TRACE variable
by using a command-line parameter <<
OK, I'll do something like that and maybe also provide a page to select the level (0 to 4?) as an alternative to the command-line.
Brian
>> OK, I'll do something like that and maybe also provide a page to select the level (0 to 4?) as an alternative to the command-line. <<
That's great.
DBI_TRACE can be between 0 and 15 , but I think we need only 0 to 4.
I'll look into the trace log to see what is recorded in it.
Naoki