No search results
Suddenly, when I do search, I get no results in the basic search. The index has been rebuilt. Even search for "the," "faith," or "Lord" yields nothing. However, I do get search reasults in my content, just not in my library??
Comments
-
Does the search field range setting have "All Text" or has a specific search field or highlighting style been selected?
0 -
I have the exact same problem. It does say all text in entire library and the indexer went off on it's own. There is no indexer crash log either.
0 -
Logos did not state that when you upgrade to 4.0d it will automatically rebuild your indexes (the previous one is deleted).
Dave
===Windows 11 & Android 13
0 -
I did a rebuild index command and still no index...
0 -
And I just updated to the latest RC.
0 -
Michael Lyman said:
I did a rebuild index command and still no index...
Please describe what you did to upgrade, and how you know there is no index. Also, post your logs.
Dave
===Windows 11 & Android 13
0 -
Set update channel to beta...eventually did a rebuild index in the command bar since I didn't have one.I have not crash logs...
0 -
So what is the current status. The indexer file simply looks like indexing is still going on. Is that correct?
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
No it is no longer indexing. It did index My Content and the Topic categories are found. I am using 4.0c (4.03.4.0512)
0 -
The search field has "all text" and I am searching the entire library. I am using 4.0c SR2 (4.03.4.0512). It did index My Content and the Topics show up. It simply will not index my library.
0 -
Joseph,
It would help to see the log files.
To enable diagnostic logging: http://wiki.logos.com/Diagnostic_Logging
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Hi Mark. Here is the log file right after trying to search for Genesis 22:16, basic search, all text, entire library. By the way, this work fine on my other computer.
0 -
Well, there is nothing terribly clear to me in this log except that is seems to have errors when trying to search or open Louw-Nida.
Was Louw-Nida (Greek-English Lexicon of the New Testament Based on Semantic Domains) being used in the search? You were searching the OT so I wonder.
EDIT: Sorry, you were searching your whole library so, yes it was searching for Louw-Nida.
My suggestion at this point is to hide Louw-Nida, close Logos 4, then reopen Logos 4 and unhide Louw-Nida. Use the Program Settings panel to do this. This will force Logos to delete Louw-Nida from your hard drive and then download a new copy. It will need to reindex L-N but you can run the search before it does this to see if you get the same error. Keep the logging going on.
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
I hid Louw-Nida and restarted. However, it still shows up as being in my library. I did a search for "faith" in the entire library and got zero results.attached the logs including one from 6-25, and indexer crash log.
Thanks for your help
Jody (Joseph)
6283.Logos4IndexerCrash_6-25-2010.txt
0 -
Joseph, the indexer crash log is older, from 6/25, so it's not explaining the current problem. But it does have an error in it:
Error ID: 7216
Error detail: SQLiteException: Some kind of disk I/O error occurredError in DeleteA disk I/O error could be caused by a failure on the physical medium of the hard disk (bad sector), a file that is locked/in use by another application or another instance of Logos running which crashed and didn't free up the file handle, or a file on some removable drive that is no longer available, or something along those lines.
However since you've now apparently run the indexer all the way through it's process since that error came up I'm going to assume it resolved itself (possibly by you rebooting?)
Now on to the Indexer4.log. It has no errors in it, but a whole lot of warnings, in two different categories:
1) Lots of the format:
Warn LogosResourceIndexer Ignored 12 invalid references for 'biblio' in LLS:5.10.5 (out of 17 total; 70%).
(and various similar such warnings with different data types instead of 'biblio')
2) Lots of the format:
Warn LogosResourceIndexer Can't load article 'heart' referenced by 'link.pos=heart|res=LLS:40.120.3'; ignoring.
(and various other similar such warnings with different articles and link references)
3) Lots of the format
Warn LogosResourceIndexer No lemma found for 'צַעֲנִים'
(and others with different lemmas)
I'm not sure what to say except something seems very messed up with your index or your library. So let's try to get to the bottom of this. You started this thread off by saying, "Suddenly, when I do search, I get no results in the basic search." So it used to work on this computer, right? Have you upgraded to a new version of Logos between when it last worked and now? Have you purchased/downloaded any new resources between then and when it stopped working? Have you imported any data from Logos 3 into Logos 4 between then and now? Have you had any viruses that you've had to clean up in the interrim? Anything else you can recall out of the ordinary since it last worked on this machine?
First of all, to rule out hardware problems with your hard disk, I would suggest running CHKDSK in a Command window (Start > cmd.exe).
Then I might suggest completely uninstalling Logos and reinstalling it, unless someone from Logos who understands these error messages better can chime in and figure out what specifically is causing them. If you're going to go the uninstall/reinstall route, you can save yourself a lot of the downloading resources (if indeed you're pretty certain you have got an intact Resources folder) by using Method 3 on http://wiki.logos.com/Quick_Installation_onto_multiple_computers.
Michael, sorry no answer to your posts right now. I can only focus on one at a time. If we figure out what's causing Joseph's problems, hopefully whatever it is will help you too.
UPDATE: There are lots of Warnings in the Logos4.log file too, but until we get the Indexing straightened out, it's kind of pointless to waste time on them. Some of them look harmless anyway.
0 -
Michael's Logos4Indexer.log contains the same sorts of Warnings as Joseph's, so I'm convinced it is the same thing causing both of your problems. Thus I'm pretty sure it's not a hardware failure on Joseph's computer.
0 -
JosephDillow said:
I hid Louw-Nida and restarted. However, it still shows up as being in my library.
Something funny is going on. Are you using the Internet to synch automatically with the Logos servers?
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
The most recent log file shows the same problem with Louw-Nida. Are you sure you hid this resource and not another my mistake?
Pastor, North Park Baptist Church
Bridgeport, CT USA
0 -
Mark A. Smith said:
Well, there is nothing terribly clear to me in this log except that is seems to have errors when trying to search or open Louw-Nida.
Was Louw-Nida (Greek-English Lexicon of the New Testament Based on Semantic Domains) being used in the search? You were searching the OT so I wonder.
The logos4 log & any searches attempted were performed whilst indexing was underway (see 6443.Indexer log), and the previous index had been deleted. The LN lexicon has not been indexed.
Dave
===Windows 11 & Android 13
0 -
Yes, I have two instances of L4 open on two different computers so they must be synching. Right?
0 -
Rosie Perera said:
Michael's Logos4Indexer.log contains the same sorts of Warnings as Joseph's, so I'm convinced it is the same thing causing both of your problems. Thus I'm pretty sure it's not a hardware failure on Joseph's computer.
Both Michael's & Joseph's Indexer logs show nothing out of the ordinary - I get the same warnings on the same resources.Both show that:-
- the original index was deleted, and
- indexing has not completed
Michael & Joseph
Please communicate what is happening when indexing has completed (when the warning message in Michael's first post is no longer shown for a Basic Search).
Dave
===Windows 11 & Android 13
0 -
Yes, at least I know it is closed now. Last night I started rebuilding the index. As of 9:00 this morning it says it has 37 hourse to go.
I tried to find "the", "Lord" and "faith" again. It finds them in MyContent, but nothing is found in my library. Is it possible the a library search will never return any results until it is completely rebuilt?
0 -
Last night I started rebuilding the index. As of 9:00 this morning it says it has 37 hourse to go.
I tried to find "the", "Lord" and "faith" again. It finds them in MyContent, but nothing is found in my library. Is it possible the a library search will never return any results until it is completely rebuilt?
0 -
Last night I started rebuilding the index. As of 9:00 this morning it says it has 37 hourse to go.
I tried to find "the", "Lord" and "faith" again. It finds them in MyContent, but nothing is found in my library. Is it possible the a library search will never return any results until it is completely rebuilt?
I am thinking I will let it rebuilt the index and then try again rather than download and resinstall now. Does that make sense?
I tried to run chkdsk and it says I must be admin. I AM admin!
0 -
JosephDillow said:
Last night I started rebuilding the index. As of 9:00 this morning it says it has 37 hourse to go.
I tried to find "the", "Lord" and "faith" again. It finds them in MyContent, but nothing is found in my library. Is it possible the a library search will never return any results until it is completely rebuilt?
I am thinking I will let it rebuilt the index and then try again rather than download and resinstall now. Does that make sense?
I tried to run chkdsk and it says I must be admin. I AM admin!
Joseph,
Is Indexing still at 37 hours left? Do you have any type of backup software running, such as Carbonite or something similar? This has been known to cause errors similar to the one in the Indexer crash log from 6/25, and could be affecting the current indexing process.
Thanks,
Melissa0 -
Hmmmm ... I have Genie Soft Timeline running. It acts like Carbonite but on a local network. It is always running in the background
0 -
JosephDillow said:
Hmmmm ... I have Genie Soft Timeline running. It acts like Carbonite but on a local network. It is always running in the background
To determine whether this is the problem, you might try disabling it temporarily during indexing to see if that allows it to finish successfully. See this support article: http://www.logos.com/L4/Support/carbonite.
0 -
JosephDillow said:
Is it possible the a library search will never return any results until it is completely rebuilt?
Yes, because the previous index has been deleted! Just let the indexing complete before doing anything.
Dave
===Windows 11 & Android 13
0 -
I apologize for not replying more quickly I have been out of town. I got home last night and started my computer. I drove to Ohio for a funeral this morning and since I have returned this evening it has been stuck at 1 hour and 14 minutes. Still no results. I do not have any of the software running that Melissa mentioned.Logging is enabled and this is the only file in the Logos Log file that has a date of today.
0 -
Michael Lyman said:
I apologize for not replying more quickly I have been out of town. I got home last night and started my computer. I drove to Ohio for a funeral this morning and since I have returned this evening it has been stuck at 1 hour and 14 minutes. Still no results. I do not have any of the software running that Melissa mentioned.Logging is enabled and this is the only file in the Logos Log file that has a date of today.
Michael, this latest log file shows indexing still in progress, and it looks normal except for these errors (excerpted out of all the other normal stuff around them):
2010-06-27 23:52:19.0860 9 Error Sinai.SinaiMessage Unable to read run type 65. Returning NULL pointer.
2010-06-27 23:52:19.0880 9 Error Sinai.SinaiMessage Unable to read run type 65. Returning NULL pointer....
2010-06-27 23:52:20.9160 9 Error Sinai.SinaiMessage Unable to read run type 65. Returning NULL pointer.
2010-06-27 23:52:20.9160 9 Error Sinai.SinaiMessage Unable to read run type 65. Returning NULL pointer.
...2010-06-27 23:52:23.1260 7 Error Sinai.SinaiMessage Unable to read run type 65. Returning NULL pointer.
2010-06-27 23:52:23.1280 7 Error Sinai.SinaiMessage Unable to read run type 65. Returning NULL pointer....
2010-06-27 23:52:29.7990 9 Error Sinai.SinaiMessage Unable to read run type 65. Returning NULL pointer.
2010-06-27 23:52:29.7990 9 Error Sinai.SinaiMessage Unable to read run type 65. Returning NULL pointer.After four pairs of occurrences spaced out over a few seconds, these errors stopped happening, and indexing seemed to be proceeding normally. It seems to have been running for just under 2 1/2 hours so far, which is not out of the ordinary. Showing 1 hour and 14 minutes left would still not be out of the ordinary (a total of under 4 hours), but how long has it been stuck at that amount? It might be that the display showing the estimated time left just hasn't been updated in a while, but that the indexing is actually proceeding fine. I'd recommend you keep waiting until it finishes or has been stuck at this point for several more hours.
One important thing to note: if you're doing this on a laptop and it's running off a battery, or if you've got certain power-saving settings (even if plugged in), it will automatically go into hibernate mode after a period of time. This will cancel the indexing which is in progress, and you'll end up having to restart the next time you turn on your computer. You need to temporarily disable the power saving settings, and make sure your laptop is plugged in, in order for indexing to complete.
0 -
I am on a laptop but it is plugged in and set to not hibernate under any conditions. It has been stuck on 1 hour and 14 minutes for about two hours, but I'll it go all night and see what happens. This happened before with a beta and after it finally indexed I hadn't tried a beta again until this RC. Thanks again!
0 -
It is now 8:17 am eastern time 6-29-2010 and the indexer still says 1 hour and 14 minutes to go.
0 -
It is now 1:01 pm eastern time 6-29-2010 and the indexer still says 1
hour and 14 minutes to go...0 -
In Task Manager it is taking up 50% of my cpu and as always making my computer run hot.
0 -
Michael Lyman said:
In Task Manager it is taking up 50% of my cpu and as always making my computer run hot.
For now, go ahead and pause the Indexer by right-clicking on the icon. We'll review your last log.
0 -
I had to kill it in Task Manager, right clicking didn't do anything this time.
0 -
It just started downloading about 40mb of updates maybe it will index correctly this time.
0 -
GenieSoft backup is not the problem. Yesterday it said that it would take another 37 hours to complete the index rebuilt. I just checked, at noon today, and it now says it will take another 71 hours! What is going on?
0 -
JosephDillow said:
GenieSoft backup is not the problem. Yesterday it said that it would take another 37 hours to complete the index rebuilt. I just checked, at noon today, and it now says it will take another 71 hours! What is going on?
This may be due to the 4.0d update this morning, or the large resource update soon after. I've submitted your log to development, too.
0 -
The indexer crashed this time. I have enabled logging, there is no log and I still get 0 results!!!!!!!!! This is why I still use Logos 3 even though I just went to a Camp Logos in Atlanta!!!
0 -
Duplicate post, sorry!
0 -
Actually, the 4.0d update has not been installed, so that is not the reason for the 100 hours to rebuild the index.
0 -
I deleted everything in the bibleindex and libraryindex and restarted Logos. My machine is running very hot and indexing is now stuck at 1 hour and 36 minutes with no results if I try to search for something.
0 -
Indexer just stopped working again!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
0 -
Both of you guys have been suffering with this problem for far too long. I think you need to call Support and get it escalated to one of the advanced support techs. Cite this thread. Sorry I've run out of ideas for helping you.
0 -
Thanks again Rosie. Tech Support knows about it. Melissa has been involved in this thread. I have enabled logging, the indexer isn't working at all and there are no crash logs, just the ones I posted. I don't have time to spend hours on the phone with tech support again.
0 -
Michael Lyman said:
I don't have time to spend hours on the phone with tech support again.
I can only tell you that an error occurred indexing the LogosLXX resource for the main Library Index. The Bible Index was built successfully, including LogosLXX! Can you run a Bible Search on that resource? Check you have plenty of free space on the hard drive and that there are no errors.
You could try deleting LogosLXX which would force a download and a quick index of the Bible Index followed by another (longer) attempt on the Library Index.
Dave
===Windows 11 & Android 13
0 -
The download finished and the indexer finished and still no results!!! C'mon Logos! Dave, I'll try that next.
0 -
Deleting LXX and forcing a re-index did not work either.
0 -
