Fulltext search causes solr error #609 #909
Comments
|
Hi @lopiuh , I need more information :). You said it is a solr error - but the log line doesn't show anything related to solr. Could you paste more logs around the ERROR? The solr-url of Thanks! |
|
it is the provided (docker) setup and search did not work from the beginning. In the meantime I tried a manual installation (debian) but I did not came to a successfull state. I returned to the default docker installation. Maybe now, the local solr installation and docker images of several other tested dms may interfere. The following log is directly after pressing enter in the search box. The second one ofter api call reindex. Both times "docspell-joex | org.http4s.client.UnexpectedStatus: unexpected HTTP status: 404 Not Found and this is giving the command: |
|
It seems that the solr requests are not going to solr. Did you change the docker-compose setup in any way? For example, the config file or the docker-compose file? The solr url must point to the solr container and not localhost. Try the default url: |
|
I did leave everything on default and even installed in a virtualmachine with a vanilla debian buster install. Maybe we should "debug" in that installation because it is a "clean" install. I do the VM way once more and give the logs of that instance... Thanks |
|
Ah, so it's not the docker setup anymore? Using the debian-way you need to install solr via debian and create a solr core (this solr doc might be helpful). |
|
Hi eikek, No, all docker installations, I did a test with fedora (new OS installation in virtualbox) with the same error I got in debian buster (nativly and vitrualbox). The error comes when trying to search. OS, docker and docspell-docker are freshly installed. In debian and fedora I had to manually update docker-compose to a new version (1.29.2) in order to get the container up. I did not configure anything. Any idea? |
|
Really strange! Solr always returns a 404, I don't see why. What I usually do when testing the docker setup is to prune everything (but of course only applicable in testing environments): This removes all containers, images and volumes. Or try to remove the solr volume only. I couldn't see it creating a new core; from the logs it seemed that it found an existing one (see line 5). So there maybe some weird state. If this doesn't work (I suspect it, since you tried from a clean system anyways), try using a different solr version (and always remove the existing solr container and volume, so it can be re-created). Maybe the new version 8.9 changed too much; try 8.4 for example (I'm using this). |
|
Hi eikek, thanks for your thoughts. As far as the docker images are concerned it "should" work shouldn't it? Especially with a clean os Install in a virtual machine, so there is no old solr config.., interestingly would be if someone could reproduce the problem with the actual docker image. What I could do: test an old docker image (with Solr 8.4 e.g.), Is it still downloadable? Thanks lopiuh |
|
It should work :-) I think I tested it when releasing the latest version, but I may have failed or a new solr version is now not compatible anymore (this is my current guess). You can try this by changing the docker-compose file: there is the solr container defined, just replace |
|
Hello, this is reproducible behavior for me as well. Installing via default docker-compose routine, no changes to configs results in: at boot: when uploading a file: when searching: health check: Same issue after downgrading solr to 8.4 and 7 on a pruned docker system. The docspell-solr container is pingable and the webinterface is accessible via its internal address Changing |
|
Thank you @arndto for all these details! Now it is clearly an ordinary bug :/ (easily reproducible by 2 :)) I haven't had time to take a closer look, I'll look more into it in the next days. I can't think of a change that could have caused this right now. Solr is not by default exposed, because it is not necessary. So it is expected that it is not reachable via "localhost" (your host system). Within the docker network, all containers should see each other. The 404 means that at least someone is responding here… really strange. Hope I can figure it out soon. It should work with solr 8.x actually, but I'm myself on solr 8.6 while not using docker (sorry for the wrong info about, but it should also work with 8.4 - I tested these two in the past). |
eikek
added
bug
|
Oh my, I'm very sorry for the confusion! Turns out that I broke the config file - the correct solr url is I really thought I tried it before the release, but it cannot have worked. Edit: I just pushed a fix that hopefully solves this. Running |
|
Works like a charm now ;-) THANK YOU! |
Hi Docspell fans,
I really don't get it trying to search generates a:
ocspell-restserver | [docspell-restserver-blocking-5] ERROR o.h.s.service-errors - Error servicing request: POST /api/v1/sec/item/searchStats from 172.18.0.1
it is a plain docker installation docspell.conf is default:
solr_url="http://localhost:8983/solr/docspell"
I just set the admin PW to regenerate the index with success but no change in search failure.
Anybody?
Thanks
lopiuh
The text was updated successfully, but these errors were encountered: