Hey,
for the past while my Logos 4 index has been crashing. I've been trying to fix it by reading the forums here, but nothing has really worked.
Heres my Indexer Crash file:
Thanks and God Bless!
Your crash log doesn't tell us what is causing your issue, but the issue looks like an issue we've seen before.
There is a known problem with some of the reverse interlinears with the latest Logos 4 release. Here's the solution to that issue:
hey richard!
in my ResourceManager folder i only have two files: ResourceSyncManager and ResourceSyncManager.db-journal. Is this what i'm looking for?
thanks again!
hey richard! in my ResourceManager folder i only have two files: ResourceSyncManager and ResourceSyncManager.db-journal. Is this what i'm looking for? thanks again!
No.
That is found in ...Logos4\Documents\[random string]\ResourceManager.
Instead, look in ...Logos4\Data\[random string]\ResourceManager\Resources
sorry richard! Just got back from work and had dinner!
anyways! I've deleted the files and am now looking for them. If they are in the downloaded file, can i continue with the rest of the steps?
thanks for your help!
sorry richard! Just got back from work and had dinner! anyways! I've deleted the files and am now looking for them. If they are in the downloaded file, can i continue with the rest of the steps? thanks for your help!
Restart Logos and they should download automatically (assuming you have Automatically Download Updates set to "Yes."
Once they do, indexing should start immediately and continue without crashing. If it does crash, enable diagnostic logging (see the Wiki for instructions) restart Logos and let and let the indexer crash again. Then, before restarting Logos, post your logs and crash reports here. Hopefully, this won't be necessary.
Thanks Richard! Everything is working great!
God Bless!
I've had the same problem. This has been very frustrating and time consuming. It made my Logos4 unusable, I couldn't even do a search.
Thanks Richard for such clear instructions. I'm back up and working again. I had to implement step 6 and 7 to get it to finally recognize the books I had deleted.
Thanks Richard for such clear instructions.
You're welcome.
The instructions did not originate with me. They have been posted on these forums in several places, as this issue has come up repeatedly since the last program update. Last I read, Logos is still working to resolve the issue.
Can someone tell me if I should follow the same instructions Richard gave Josh to solve the crashing indexer problem? I have attached the indexer crash file.
Thanks!
Can someone tell me if I should follow the same instructions Richard gave Josh to solve the crashing indexer problem? I have attached the indexer crash file. Thanks!
The crash log doesn't tell us the exact cause, but it doesn't look like the same issue.
EDIT: The crash log reports a malformed database. You can try to fix it by typing rebuild index in the command box. Before you do that you may want to enable permanent logging by following the instructions below.
To enable permanent logging follow all the instructions in the link below. Make sure to post all logs here for review (see link below for how to upload logs) before restarting Logos. We'll see if there's anything we can do to help.Here are the URLs:http://wiki.logos.com/Diagnostic_Logginghttp://wiki.logos.com/Uploading_Logs
Thanks, Richard. I have attached all the logs to this post. 77485.Logos4.log
I am not sure which file to include actually. There were three files created when I did the logging:
Logos4IndexerCrashLogos4IndexerLogos4
Not sure which of these I am supposed to attach. I tried to attach all three in my last post, but I am not sure what got posted.
So, I'll try posting all three again. 4505.Logos4IndexerCrash.txt
Well, perhaps the 3rd time will be successful. 8883.Logos4IndexerCrash.zip
I tried to "Rebuild Index" as you noted above. I've attached the latest set of log files to this post6545.Logos4IndexerLatest.zip
I am not sure which file to include actually. There were three files created when I did the logging: Logos4IndexerCrashLogos4IndexerLogos4 Not sure which of these I am supposed to attach. I tried to attach all three in my last post, but I am not sure what got posted. So, I'll try posting all three again. 4505.Logos4IndexerCrash.txt
We need all of them. In this case the most helpful would be the Logos4Index.log. You could zip them all into one file and upload the zip file.
Terry
The problem appears to be with LLS:LEB. So delete the following files from C:\Documents and Settings\Terry Devitt\Local Settings\Application Data\Logos4\Data\2yzcnpps.osw\ResourceManager\Resources:
Restart L4 which should download the missing files and restart indexing.
Thanks, Dave.
Tried that but still get the same error message. Here are the lo files after the latest attempt to "Rebuild Index". 6175.Logos4IndexerMarch 21.zip
Also, it appears the two files above were not downloaded when I restarted L4 and indexed. Should they have been added?
it appears the two files above were not downloaded when I restarted L4 and indexed. Should they have been added?
Yes. So enter Update Resources in the Command box.
Tried that but still get the same error message.
This time the error occurred on the NRSV; another reverse Interlinear. You should contact Technical Support and reference this thread. Please report their recommendation.
Dave,
I called Tech Support. I am no longer getting the crash error each time I index. What seems to have fixed the problem was removing the "Home Page", "Library Index", and "Bible Index" folders located here: C:\Documents and Settings\Terry Devitt\Local Settings\Application Data\Logos4\Data\2yzcnpps.oswI rebuilt the index after this and it crashed again. So then I planned to capture the log files again, expecting it to crash again, but it did not. I closed out the program, and when I loaded it up again, there was no attempt to rebuild the index (i.e., there is no message saying "first-time indexing underway"" as I have been getting). Now, tonight I have been using Logos 4 successfully with no issues whatsoever.
I can't be sure that was the fix, because the technician did a few other things. But if I had to guess this is what seemed to solve the problem.
Hope this helps.
Thanks for the feedback, Terry.
