indexing bug
I had this happen once before and just reindexed the whole thing and everything worked fine but now it has happened again so I am sending you the log files. I'm not sure of all the events that led up to it but at some point the indexer started indexing after a download (just like before) but then at some point it stopped with no warning of an error. Normally I would just assume the indexing was finished exept that whenever I do a search there is a yellow label informing me that my search results may not be complete until indexing is finished. When I exit out of L4 and then reboot the computer then go back into L4 the indexer starts up for a few minutes and then just stops with no error messages- it just stops indexing- and I am still left with the yellow label in search. When I just restart L4 without a reboot the indexer does not start at all. The posts I have looked at have mentioned crashes but this is not quite the same as the indexer just silently exits as if it is finished but leaves me with that label in the search box. Please advise. I am assuming I will need to do another compete reindex tonight.
Comments
-
Sorry, I forgot to attach the logs.5355.Logos4.log2318.Logos4Indexer.log4452.Logos4Crash.txt4784.Logos4IndexerCrash.txt
0 -
Tim,
Both the crash logs are from a much different time (April and late June). The Logos4.log file shows normal operation. The Logos4Indexer.log file shows normal operation but indicates that it is leaving LGNTISBL as WaitingToInstall.
To me this indicates that there is an update to this resource that has been downloaded but for some reason the Indexer cannot process it. This could explain why the indexer restarts all the time.
I would try deleting the file for this resource (The Lexham Greek-Engish Interlinear New Testament:SBL Edition) and reopening Logos to trigger a redownload of the resource. (Delete by going directly to the Resources folder and deleting the file or by hiding the resource under Tools>Program Settings. If you do the latter you'll need to hide it, close Logos and reopen it. Then unhide it, close Logos and reopen it to trigger the download.)
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Thanks for the help. I did do a complete rebuild of the index and everything seems to be fine now. If this same thing happens again I have kept yur instructions and will remove the book and reinstall.
0 -
Mark Smith said:
I would try deleting the file for this resource (The Lexham Greek-Engish Interlinear New Testament:SBL Edition) and reopening Logos to trigger a redownload of the resource. (Delete by going directly to the Resources folder and deleting the file or by hiding the resource under Tools>Program Settings. If you do the latter you'll need to hide it, close Logos and reopen it. Then unhide it, close Logos and reopen it to trigger the download.)
I am trying a new laptop (windows 7 64bit, AMD quadcore processor , 6 gb ram). I reinstalled L4 and downloaded all books and the indexer started and then stopped. I tried your suggestion above (deleted book then closed program then opened) and indeser started then stopped again. Also it has not redownloaded the book I deleted. I tried rebuild index and it did the same things whereas before (on my other computer) it worked. So now I have no index at all. This time though when the indexer stops it pops up an error screen telling me it has stopped. I am sending log file. It seems there is just one file this time, 7713.Logos4IndexerCrash.txt
0 -
This line in your crash file is a bit concerning:
Error detail: IndexingException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
Enable logging (on both machines), as described here and report back: http://wiki.logos.com/Diagnostic_Logging
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
I did an extended memory check and found no problems and also physically removed both modules and put one in at a time and still same problem. I noticed in the log that it seems it is always at the same place in the lineup of resources that it quits. But I did manage to resolve the problem. I reinstalled L4 and transfered my data files, user info and document dirctories from my working installation to the new computer and now it works fine. It even did a resource download and the indexing was extremely fast on the quad core machine and the program itself seems much snapier! Than being said, I plan on exchanging it for an intel core i7 quad core for even more speed and power (at least it seems that the core i7 will be faster than the AMD equivalent from what I read.)
0 -
I'm having the same problem and my log file says the same thing. Just wanted to let you know. I did a complete memory diagnostic and no memory issues were identified. I have an Intel based laptop that works fine. I just built an AMD A8 desktop machine and installed L4, downloaded my resources, and then the indexing issue. It gets to about 3% or so and turns off. Sometimes with a notice and sometimes not.
0 -
Jerry Self said:
I'm having the same problem
Jerry,
Please follow the directions for enabling diagnostic logging, then reproduce the problem, zip all the log files together and attach them to a follow-up post.
You'll find the directions here: http://wiki.logos.com/Diagnostic_Logging
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
We've had a number of reports of this crash from the forums and from Tech Support in the last few days. The common factor is this message (in the log file or the crash file):
Libronix.DigitalLibrary.Logos.IndexingException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. ---> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
At the moment we're not sure what has happened to trigger this bug. Since we haven't released a program update recently, it may be caused by a resource update. However, the full exception message mentions "ReverseInterlinearResourceCore", and the reverse interlinears haven't been updated recently.
At the moment, I don't have any information on why this is happening, or any workarounds for the crash, but we're trying to get a solution as soon as we can.
0 -
We've had some customers with this crash report that before it happens, Norton Internet Security 2011 displays a "Performance Alert" about the indexer. This probably isn't related to the crash, but I would be interested to know if you have a Norton product installed if you're seeing this problem.
We're still trying to reproduce this issue. If you're comfortable with the idea of running unsupported, beta software, you could upgrade to 4.3 Beta 13 to see if it resolves the problem. Some of the indexing code has changed in that release and it's possible it doesn't have the same bug. Instructions on how to upgrade are here: http://community.logos.com/forums/t/8883.aspx. Discussion of any other problems with the beta should move to the beta forum: http://community.logos.com/forums/78.aspx
0 -
Bradley Grainger said:
. . . you could upgrade to 4.3 Beta 13 . . .
So you're releasing Beta 13 soon (the current Beta is 12)? [Keep hitting the update arrows and confronting disappointment. [:(]]
Help links: WIKI; Logos 6 FAQ. (Phil. 2:14, NIV)
0 -
Bradley, I'm not having this problem but on this computer and my previous one Norton Antivirus does report heavy use of the CPU for some indexing functions (not sure it does for some of the small resource updates. It did it more frequently on my last computer which only has a core 2 duo processor running at 2.0 GHz and 4 GB of RAM.
One thought I have is the overheating issue. I got 'strange' crashes with my old computer during long indexing operations. At least once I got a memory error and you directed me to run memtest, and I found no flaws. The advice Dave Hooton gave to run a fan over the computer helped (at least when I had a cold room to run it in, too). I have no problems indexing on my new computer, but it is quad core with 8 GB of RAM. The processor never runs above 50% while indexing. It used to run at 96-99%.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Richard DeRuiter said:Bradley Grainger said:
. . . you could upgrade to 4.3 Beta 13 . . .
So you're releasing Beta 13 soon (the current Beta is 12)? [Keep hitting the update arrows and confronting disappointment.
]Another thread said later today...
Prov. 15:23
0 -
Richard DeRuiter said:
So you're releasing Beta 13 soon
Just shows you Bradley is always way ahead of us. [;)]
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark Smith said:Richard DeRuiter said:
So you're releasing Beta 13 soon
Just shows you Bradley is always way ahead of us.
It was actually a typo; I meant "12" [:S]. Either Beta 12 or Beta 13 (when it's released) could be a possible workaround for this crash.
0 -
Bradley Grainger said:
It was actually a typo; I meant "12"
. Yeah, yeah. Sure, Bradley, we all believe you. [Y]
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark Smith said:
One thought I have is the overheating issue. I got 'strange' crashes with my old computer during long indexing operations.
Thanks, Mark, this is a good suggestion. FWIW, memtest86+ won't tend to find these kind of problems, but Prime95 (or another really CPU-intensive stress test program) can be used to see if there may be some underlying hardware issue.
For anyone who is having an indexing crash: is your computer in a well-ventilated area? Does the computer have good cooling fans, or is it hot to the touch? Is the room temperature normal, or is a hot day (or heatwave) with no A/C?
0 -
I installed the beta and had the same problem. I then uninstalled by security software (Panda) and still had the same problem. I've been through the phone support and provided the logs and as you say no one seems to have an answer yet. Just wanted to let you know what I've tried. I'm on Windows 7 with an AMD A8 processor that came out this year. Just sharing that to see if there are any patterns that can help you guys zoom in on the problem. By the way without my library indexed I don't have the "Search this resource" option in the word study dialog box. This is consistent whether in the beta or not. It still appears in my working version of Logos 4 on my laptop that is indexed. The one I'm having a problem with is on a new install on a new desktop.
I'll keep checking to see if you have any other ideas.
Thanks for the suggestions so far.
0 -
We're still researching this problem; at the moment we're really hampered by being unable to reproduce it on any of our computers. So far the only pattern I've noticed is that it only seems to be reported from Windows 7 SP1 systems--do you also have SP1?
0 -
Yes. SP1 installed immediately on my desktop when I started up the new computer. However, I have SP1 on my laptop where Logos works fine. But SP1 (laptop) was loaded after my library was indexed. Should I try to do the "rebuild index" command on my laptop to see if it will index. I don't mind trying that but if it doesn't work will I lose my old index?
0 -
Yes. I have SP1 on my desktop where I am having the problem. I also have SP1 on my laptop where I don't have a Logos 4 indexing problem. But my laptop logos version was indexed before I downloaded SP1. Is there a pattern of this problem only on new Logos 4 installs after SP1 was installed? Just an idea.
0 -
Jerry Self said:
Is there a pattern of this problem only on new Logos 4 installs after SP1 was installed?
I doubt that is the pattern but indexing can be very intensive on the hardware, either giving similar error messages or switching off the computer. The key has been to have adequate ventilation, whether by fitting an additional fan in the case or by using an external fan.
Dave
===Windows 11 & Android 13
0 -
I have a similar issue.
I installed Logos4 without issue on my desktop (custom-built a few years ago, Win7 32-bit, SP1 with all current patches) about a month ago. Security is Zonealarm Extreme Security. I already had Logos 3 on it.
I have a new Gateway laptop (NV75S03h, just purchased at Futureshop) with Win7 64-bit, SP1 with all current patches and I've hit the indexer bug. Security is Zonealarm Extreme Security with Datalock. After the first failure, I uninstalled Logos 4 and then reinstalled (unfortunate repeat of a 6GB download). This didn't work. After reading the forums a little nore, I deleted the bible and resource index then launched Logos 4 with logging and hit the error again. Logs are attached - I'm open to advice.
Thanks
Mike
0 -
Michael Lemke said:
Logs are attached - I'm open to advice. :
Welcome Michael,
We know it's connected with Reverse interlinears, AV1873 in your case, but removing them hasn't proven to be totally successful! If you haven't tried the external cooling idea do so.
Dave
===Windows 11 & Android 13
0 -
Responding to: "For anyone who is having an indexing crash: is your computer in a
well-ventilated area? Does the computer have good cooling fans, or is it
hot to the touch? Is the room temperature normal, or is a hot day (or
heatwave) with no A/C?"Thanks Dave. The laptop is sitting on my den desk and the temp is around 72F. The laptop isn't excessively hot and there is nothing blocking the fan out-vent. It's also on a flat surface. I ran system diagnostics and nothing showed out of the ordinary. In addition to the Logos4 download/install, I've also downloaded & installed another 30GB worth of programs and updates, while running scans - all without issue. If anything, my desktop should have had this issue a month ago due to its location (but it didn't).
Now, my laptop is AMD-based (A8-3500M). Are all of the reports coming from AMD-based machines or is there a mix?
Thanks
Mike
0 -
I saw the concern about temperature so I took it on this weekend. I live in the Phoenix, AZ area so yes it is hot. I turned down my thermostat to 75 degrees, took the side panel off the computer, aimed two fans at the motherboard, and disconnected everything to the computer that might be making it heat up. I started the indexing and timed it under different heat conditions and it failed everytime. The difference in times was plus or minus thirty seconds with the longest run time of about 3 minutes. I took out the memory and put it in different slots and switched the memory from one slot to another. This did not cause any change in the failure mode. I even left the computer off for hours and it still failed within the same time period. Based on this I would say it is not a temperature issue. I've changed different bios settings (e.g., energy savings mode to performance mode). Still no change in the failure. Right now I am at a loss. I built this computer with Logos as a major consideration and now I can't use it for that purpose. Everything else works fine so far but I don't know of anything I have that requires the indexing that Logos demands. Without indexing Logos loses it most affective attribute.
0 -
Michael Lemke said:
Now, my laptop is AMD-based (A8-3500M). Are all of the reports coming from AMD-based machines or is there a mix?
It doesn't respect brands of CPU!
Michael Lemke said:I've also downloaded & installed another 30GB worth of programs and updates, while running scans
Logos4 indexing can fully (99%+) load the CPU for hours & impose a heavy load on the memory and hard drive. Installing other programs is not as intensive.
Dave
===Windows 11 & Android 13
0 -
Jerry Self said:
Everything else works fine so far but I don't know of anything I have that requires the indexing that Logos demands. Without indexing Logos loses it most affective attribute.
The only thing I can suggest is to hide all your Reverse Interlinear bibles** and resume indexing with the command Rebuild Index
Then unhide the bibles one or two at a time. It's ugly but has method!
** AV1873, Cambridge Paragraph Bible, ESV, KJV1900, LEB, NASB95, NIV (not 2011), NKJV, NLT, NRSV. Restart L4 after you hide them.
Dave
===Windows 11 & Android 13
0 -
Ok - I hid the resources as per the list and then launched with logging. The first-time indexing completed successfully.
Any recommendations regarding in which order to unhide? If I experience a subsequent indexer crash will the indices be messed up such that I need to repeat the process?
Thanks
Mike
0 -
Try two at a time, no particular preference. The Bible Index will be first, so the Library Index should be OK if there is a failure. Keep logging on and upload the indexer log if necessary.
Dave
===Windows 11 & Android 13
0
