I started with a clean index and the only thing I can think that I done different was to use Collection names as opposed to the standard “user”.
A standard search returns no results (quite quickly)
If I place /date site: etc I get results. I can search images.
So fresh Index, crawled some sites a few hours ago and the only way to return results for normal text based search is to add /date etc otherwise no results.
Strange.
Sometimes, when that happens to me, refresh (sometimes 2x) would help. Reported as an issue, similarexist.
I suspect – in my case – some timeout or something. Happens more probably under load.
Is there something in the log?
No I can not see anything relevant in the log, so far.
I am about to delete and reinstall.
It isn’t a load issue. CPU, Ram and Harddive are basically idle. When I have started indexing, there has been generally less then a load of 1 with 6 cores/ 12 threads.
YACY has 32 gig of ram with no index when I start.
Indexing flies along, results start showing up instantly. Just can not do a standard text search.
I have had the no loading results issue you linked to but seemed to occur when hard drive under to much load. (iostat)
The annoying thing is I have three servers setup the same yacy.conf, yacy.init, network.unit, same ranking settings etc and one with a search issue the others don’t
Hopefully a delete/reinstall fixes it as I have spent so much time trying to troubleshoot.
AFAIK, YaCy searches two indexes by default: RWI (for single word searches only?) and solr. Maybe one way to debug is to try to switch them off and on by debug config option – and try, which one is the culprit.
There is also something like “last search performance analysis” at /PerformanceSearch_p.html (Monitoring > System Status > Search Sequence), but I don’t understand that a much.
Well, with the authors silent, we’re analysing black box
OVH had a deal going on. Still do but not a lot left.
1 server cost $14 the other $16
They still have some of the $14
**Intel Xeon E5-1620v2 - 4 c / 8 t - 3.7 GHz / 3.9 GHz**
**32 GB**
**From 2 x 480 GB to 2 x 2 TB**
Public **300 Mbps**
$14.40
The one I got came with 64gig. I am yet to contact support over this issue. lol
Before deleting I moved the yacy.conf from another server and now its going.
Had me baffled as I had gone right over even using meld (dif gui) in the end
it was
index.maxReferences=
I don’t remember when or why but that was set to 1000 instead of being left empty (After reboot default is 0). Along with memory differences. I think I just ignored that setting when comparing.