Question
A search on any word in the text of one of my webs will always yield zero results when searching on other webs works fine. Has anyone heard of this?
Environment
--
MichaelMabin - 14 Jan 2008
Answer
If you answer a question - or have a question you asked answered by someone - please remember to edit the page and set the status to answered. The status is in a drop-down list below the edit box.
Can you probably add the SEARCH expressions here? --
OliverKrueger - 15 Jan 2008
For example, I know that the string "db2" is found in the text of many of the pages of the problem web and is also located in the webs that are searchable. If I search on db2 in the other webs I will get results. If I perform the same search in the problem web, I get no results.
--
MichaelMabin - 15 Jan 2008
Just a wild guess: Occasionally there are such observations on Windows, where long installation paths for TWiki can lead to
grep commands which are simply "too long" and aborted. This only happens in webs that had more than a certain number of topics in them. There should be an entry in the error log, though.
If so, there's a constant in one of the modules (which I would have to identify for 4.0.0) how many topics will be fed to
grep in one single command "chunk". The default is 512, probably a simple
grep -R 512 lib will spot the place.
--
HaraldJoerg - 17 Jan 2008
I think you set me on the right direction, Harald. I had been checking grep at the command line before to see if my argument list was too long, but I didn't use the full path to the web. And when I did it again with the full path I did get the argument list too long error. I resolved the search problem by creating a new Archive web and moving 200 of the pages from the problem web to the archive. I forgot to mention that this particular web is one we are using for incident reporting in our developer on-call rotation. After I moved those entries to the archive web, I was able to perform the search on both webs.
Thanks for everyone's imput.
--
MichaelMabin - 05 Feb 2008