Attached is the log file. Seems to crash right after starting. (I'm having my share of indexer crashes. Hope these don't continue.) I'd appreciate some guidance on this one.
1256.Logos4Indexer.zip
If you don't have a usable system or it keeps trying to index, then you may have to delete the LibraryIndex folder and start L4 to complete indexing!
But wait for other options to be presented as this is my hunch!
I thought myself lucky as I was not having any of the crash problems lately with L4 but today, went to open L4 to prepare for my sermon tomorrow and as soon as it starts, it crashes and shuts down.
Rebooted my computer, crash and crash and crash.
I see now there is an 881 MB update I am currently downloading, maybe this is the fix, I do not know.
I am running 4.0a on Windows 7 Home Premium, 4 GB Ram and have had no problems until today.
Anyone have the link to the Log File program so I can start creating log files again to upload should I have anymore problems?
http://wiki.logos.com/Diagnostic_Logging
I thought myself lucky as I was not having any of the crash problems lately with L4 but today, went to open L4 to prepare for my sermon tomorrow and as soon as it starts, it crashes and shuts down. Rebooted my computer, crash and crash and crash. I see now there is an 881 MB update I am currently downloading, maybe this is the fix, I do not know. I am running 4.0a on Windows 7 Home Premium, 4 GB Ram and have had no problems until today. Anyone have the link to the Log File program so I can start creating log files again to upload should I have anymore problems?
There is a problem with 4.0a and the date December 31. 4.0a SR-2 was released tonight is supposed to fix this. In the meantime you should be able to start L4 by holding down the CTRL key as Logos4 starts and loading to a blank layout. You won't be able to use the home page until SR2 or Jan 1, 2010.
Are you running 4.0a SR-2? There was an issue with the Home Page crashing on start-up on Dec 31 prior to SR-2. You might try holding down CTRL when you open L4 and chose run with a blank screen.
Attached is the log file. Seems to crash right after starting. (I'm having my share of indexer crashes. Hope these don't continue.) I'd appreciate some guidance on this one. 1256.Logos4Indexer.zip">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/1256.Logos4Indexer.zip:550:0]
1256.Logos4Indexer.zip">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/1256.Logos4Indexer.zip:550:0]
Mark,
It looks to me like a corrupt disk, or a corrupt index. If the latter, then it's probably caused by your previous crashes. If the former, then it would explain your previous crashes! [:)]
I would certainly delete your index and allow Logos to recreate it. I'd probably also run a disk check (including looking for bad sectors), just in case.
I have been having indexer crashes too. I missed the SR-1 update altogether. Last night I read in this forum about the release of both SR-1 and SR-2 before launching Logos 4. When I launched Logos 4, I downloaded 800+ MB of updates, installed them, but when the indexer started it immediately crashed.
I have attempted numerous times, with rebooting the computer in the middle. As soon as I reboot, the indexer begins and crashes (even without starting Logos 4).
I don't know if the best thing to do is to delete the index completely, and then let it rebuild the index, or to just type "rebuild index" from the command line.
1452.Logos4Indexer.log">http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/76/1452.Logos4Indexer.log:550:0]
I did not zip the file before posting. Here is the zipped file:
4812.Logos4Indexer.zip
I'll try to attach the indexer log to this post.
David,
You're getting the same error as Dave, which heightens the possibility that it's a bug with the indexer. I think the only way to proceed will be to delete the index files and reindex from scratch. To do so, make sure the indexer is closed and delete the files in C:\Users\David Fish\AppData\Local\Logos4\Data\3tvz5nph.3sj\LibraryIndex
David, You're getting the same error as Dave, which heightens the possibility that it's a bug with the indexer. I think the only way to proceed will be to delete the index files and reindex from scratch. To do so, make sure the indexer is closed and delete the files in C:\Users\David Fish\AppData\Local\Logos4\Data\3tvz5nph.3sj\LibraryIndex
Mark and David, I believe typing rebuild index into the command bar does virtually the same thing as Mark suggests above. (This is a new command with 4.0a.)
Mark and David, I believe typing rebuild index into the command bar does virtually the same thing as Mark suggests above.
I am running the disk scan Mark suggested. We'll see if it turns up anything. Then I'll do the reindex. Seems since the beta of 4.0a I've had a number of indexing problems, while I had few if any with 4.0 SR-7.
Mark
Are you using Windows Vista or Windows 7? You can try closing the program and opening Logos as Administrator (right-click on the icon, select "Run as Administrator").
Let us know if this helps...
Victor.
Attached is the log file. Seems to crash right after starting. (I'm having my share of indexer crashes. Hope these don't continue.) I'd appreciate some guidance on this one. 1256.Logos4Indexer.zip
Before you rebuild your index, try using the resource checksum program
5353.2100.ResourceChecksum.zip
A ResourceChecksum.txt file will show up in your Logos Log Files folder, upload it here.
Attached is the log file. Seems to crash right after starting. (I'm having my share of indexer crashes. Hope these don't continue.) I'd appreciate some guidance on this one. 1256.Logos4Indexer.zip Before you rebuild your index, try using the resource checksum program 5353.2100.ResourceChecksum.zip A ResourceChecksum.txt file will show up in your Logos Log Files folder, upload it here.
What is a "checksum" file?
Attached is the log file. Seems to crash right after starting. (I'm having my share of indexer crashes. Hope these don't continue.) I'd appreciate some guidance on this one. 1256.Logos4Indexer.zip Before you rebuild your index, try using the resource checksum program 5353.2100.ResourceChecksum.zip A ResourceChecksum.txt file will show up in your Logos Log Files folder, upload it here. What is a "checksum" file?
A checksum is a value created by running a checksum algorithm on a resource, and it used to ensure data integrity. The ResourceChecksum.txt file will contain these values.
Rich, we're not certain we can trust the indexer commands given there is potential corruption. So it's better to delete the LibraryIndex folder with its database and index files.
Doesn't "rebuild index" do precisely that?
We're not talking about merging the index but rebuilding it. I thought that's what "rebuild index" does. If I'm wrong please correct me.
That won't help, Victor. I've run as administrator and it still crashes.
Thank you, George. It is running now.
I checked the disk Logos 4 is on and there is no disk corruption nor are there bad sectors, so that isn't the problem.
8547.ResourceChecksum.txt
A ResourceChecksum.txt file will show up in your Logos Log Files folder, upload it here. 8547.ResourceChecksum.txt
Awesome, this will serve as a quick reference.
You said to do this before I reindexed. Should I try that now or will the checksum report give you help to tell me what to do next?
Awesome, this will serve as a quick reference. You said to do this before I reindexed. Should I try that now or will the checksum report give you help to tell me what to do next?
Assuming George is checking all the checksums, I'd say hold off with reindexing.
The checksum will tell George if you have a corrupt resource file. If there is one, you wouldn't want to index until it was replaced.
If there is one, you wouldn't want to index until it was replaced.
Thanks. I'm in no hurry to reindex anyway. I'm sure George will be working through New Year's Day and the weekend to get the answer, however. [:)]
Doesn't "rebuild index" do precisely that? We're not talking about merging the index but rebuilding it.
We're not talking about merging the index but rebuilding it.
It may return the same result as before as it may perform the same checks! Deleting the index increases the possibility of success if there is a corrupted file or index database.
I was hoping to save you a reindex but it looks like the working day is winding down. Since it was reported to Bradley, he may reply if he gets a chance, otherwise a rebuild over night might do the trick. I'd say if he doesn't post a reply by tomorrow evening go ahead and re-index at your convenience.
Thanks, George. Have a Happy New Year's eve and day.
Awesome, this will serve as a quick reference. You said to do this before I reindexed. Should I try that now or will the checksum report give you help to tell me what to do next? I was hoping to save you a reindex but it looks like the working day is winding down. Since it was reported to Bradley, he may reply if he gets a chance, otherwise a rebuild over night might do the trick. I'd say if he doesn't post a reply by tomorrow evening go ahead and re-index at your convenience.
The exception message attached in the original post doesn't appear to have anything to do with resources (and the checksums for the known resources come out fine).
It sounds like one of the files generated by the indexing process has become corrupted; I'm not sure how this could have happened but since it's in a file created by a third-party component (SQLite) it sounds like either a bug in SQLite (possible, but rare) or a hardware problem (memory or hard disk).
The only thing I can think of doing to fix the problem is "rebuild index". However, before you do that, you may wish to consider running a full hard disk scan overnight, and checking your RAM with a program like http://www.memtest.org/
I did what I thought was a full HD scan today on that drive. At least I checked all the options before I started it. It returned no errors and no bad sectors. That drive is my drive. I have also checked my C: drive in the past week or two. No problems.
I checked RAM a week or so ago using Windows 7 tools, again with no errors. I might try memtest assuming it is more robust than the checker in W7. I'll have to check it out and see how much time I'd have to invest in it. I would like to eliminate the indexing problems I've had again and again of late.
Just an update on my situation.
I followed Richard's suggestion to "rebuild index", and just let my computer do its thing without even checking it, except occasionally to check on how much more time it would take for indexing.
It ran pretty much all day on Dec. 31. When it was less than 2 hours from alleged completion, I got the INDEXER crash notice.
I said "GRRRRRRR", but immediately entered the "rebuild index" command again, and let it run. By evening, I was back to a couple hours before finishing. I said hello to the new year and went to bed. This morning when I got up, I checked on the computer. Evidently, it is finished with no problems.
I did not do anything with a checksum, did not run a memtest. I might do that.
Also, for what it's worth (referring to another post on this forum), I see no change in my list of prioritized resources.
Happy New Year to all! Blessings!
I have used memtest to check my RAM. No problems there. Will try to rebuild the index next.
I rebuilt the index. The log file does not show an early termination. However it is attached because of a large number of errors reported. I am especially interested in the errors reported beginning at 13:31:06 which say that some external problem seems to exist.
5531.Logos4Indexer (2).zip
There is also something else I do not understand. During a search I still show 'New Resources' results from what I assumed would be resources included in the reindexing. They were added recently and did show up in this section before reindexing. I assumed they would be merged when I ran the rebuild index command. There is now no usual 'merge now' option at the top of this list either. I have no idea how to get these indexes merged.
The next strange point is that while the indexer had stopped about 10 hours ago, I have just gotten a tray icon indicating that indexing is going on again with many hours remaining. What would trigger that?
Something definitely seems to be wrong. I've checked my drives and memory. I will wait to see what happens after this round of indexing.
I rebuilt the index. The log file does not show an early termination.However it is attached because of a large number of errors reported. Iam especially interested in the errors reported beginning at 13:31:06which say that some external problem seems to exist. The next strange point is that while the indexer had stopped about 10 hours ago, I have just gotten a tray icon indicating that indexing is going on again with many hours remaining. What would trigger that?
There are many exceptions being thrown - no idea what they are! The log you provided appears to have been done whilst still indexing. Can you ascertain that indexing has started from the beginning (is it the same Indexer log or did a new one get created?).
Because this was done whilst indexing, the search was using your old index structure whilst the new one is being built. You can see this if you look at the \LibraryIndex folder.
The indexer was not running when I zipped that log. It had finished at 2 PM or so on the 1st and I zipped it at about 11 PM. I know what caused the indexer to be relaunched: I closed L4 and opened it again.
Here's the latest:
After the indexer started up as reported last night, it crashed again with just minutes (supposedly) remaining. Log attached. I can still get search results, but the same notice about search results being incomplete while indexing is going on (even though it isn't going on). Still have divided results, still no merge now option. I assume that is due to what you said, the old index is being used.
6888.Logos4Indexer (3).zip
Now I will get a relaunch of the indexer every time I restart Logos. It is just going to crash again.
Something needs to get fixed so I can get a complete indexing finished. I could try eliminating the contents of the LibraryIndex folder (I'd save it somewhere else) and force a reindexing, but I fail to see how this might help. If rebuild index didn't work, why would this?
For indexing, perhaps disabling antivirus and file protection (application control in Kaspersky) will help.
Just 2 cts
Hans
One more crash after the 1.01 GB download.
6011.Logos4Indexer (4).zip
One more crash
Sorry to hear that, Mark.
Ah, well. At this point considering the other problems with SR-2, maybe Bob is ready to start beta testing 5.0 and we can at least keep our attention diverted for awhile. In the meantime I am still able to use 4.0 and I have 3.0 up and running as well.
OK. Now this is weird.
I made a 3 hr trip each way to take my daughter to an airport. All was fine yesterday. When I got home, I could not launch L4. What it does is bring up a cmd window quickly (then it disappears). The Logos 4 Splash Screen appears momentarily, then goes away. And nothing happens.
Occasionally I get a window saying that if the program did not start correctly, I may need to run it as administrator. I issue that command, and it does exactly the same thing: 1) cmd window momentarily; 2) Logos 4 splash screen momentarily, followed by nothing.
I tried to do a system restore to 12/31 at 11:30 PM, but nothing has changed on that.
Can anyone help me?
maybe Bob is ready to start beta testing 5.0
[*][:D][*][8][8][8][8][8][8][8][8][8][*][:D][*]
Besides, look at all the community we've enjoyed while we couldn't work. [:D]
Do any of the suggestions here, help? http://wiki.logos.com/Logos_Not_Starting
I had to do this on one of my machines just to get L4 to open enough to start the download. Then after the download, indexing, more indexing, and still more indexing. Seems curious that a solution of delete the index and rebuild ends up being a fix for so many issues.
Bill,
When I follow the instructions at http://wiki.logos.com/Logos_Not_Starting I get the exact same results.
Bill, When I follow the instructions at http://wiki.logos.com/Logos_Not_Starting I get the exact same results.
Sorry to hear that, David... Will a manual install get to the point that you can at least start? http://downloads.logos.com/LBS4/LDLS4Installer/Logos4Setup.exe
Hopefully one of our MVPs will chime in...
No, it just checked for updates, and told me that the program was up-to-date.
I'm afraid that if I don't get another viable suggestion, I will try to uninstall and reinstall tomorrow.
Just in case you are experiencing problems from the crazy date issue - try and reset your system clock back to a date in December and then run the fixes.
Fred,
I just set the date back to 12/30/09, then rebooted the machine, and tried to launch Logos 4. I got the same result. I set the date back to 1/3/10.
After services, I may go to my office (where I have a 500GB external drive), transfer my Logos 4 files to it, delete the program, and try to reinstall the basic program from scratch, all over again.
I don't know if this is because of some corruption on the index or what.
Thanks for any suggestion. Blessings!
Again this log stopped part way through (12.3%) looking as though it would continue. I'll have to let Logos tech look at this.
No, it just checked for updates, and told me that the program was up-to-date. I'm afraid that if I don't get another viable suggestion, I will try to uninstall and reinstall tomorrow.
I guess you already tried to start L4 using right click "run as administrator"?
If your start icon is on the taskbar, remove it (unpin) and try from the desktop.
I had already tried to start L4 using right click "run as administrator."
I had 4.0a SR-2 on a machine at my office, updated. This afternoon I used the method described here: http://community.logos.com/forums/p/3629/27895.aspx#27895 to uninstall the application on this laptop. All is well now. I DID have to delete the ResourceManager.db file to get L4 to recognize my books.
Thanks for the help.
Well, I don't know if it had to do with the end-of-the-year bug, but after fixing my installation for expired Beta licenses as Bradley suggested, I got a complete indexing finished. So that problem is behind me for now.
I appreciate all the efforts that were made to help me get back up to speed.
