-
Notifications
You must be signed in to change notification settings - Fork 286
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Photon compilation #427
Comments
Hi, i have a similar problem. Sometimes the same error as yours accour, sometimes it starts but doesnt find any queryterm. It always results in an 500 "no such index". Something seems to be wrong with this version |
Glad to see that I'm not alone. I suspect we need to re-create the photon_data dir with the latest version if we want to use it. I no longer have my Nominatim around, so I gave up for now. Anyway if someone from Photon could confirm that this is the cause of the problem or not it would be great :) |
I tried the latest version of the Database with the latest version of the jar. Both, self-compiled und the downloaded jar results in the no index exception. I red that it could be a file-right problem, so i tried chmod 777 to photon_data dir. This ended up, that non of the jars started anymore. After reunpacking the whole downloaded photon_data it worked again but with still the error "noSuchIndex" occuring. when getting the error, this line makes me curious: org.elasticsearch.cluster.metadata.IndexNameExpressionResolver$WildcardExpressionResolver.infe(IndexNameExpressionResolver.java:676) If i find a solution i will tell you. :) |
Thanks! It is not urgent for me as I managed to make it work as I want with the current release, so I'll wait an answer from someone at Photon. |
Ok found the Issue for the problem with the jar hell Caused by: java.lang.IllegalStateException: jar hell! you only need to delete the files in /photon_data/elasticsearch/modules/lang-painless/ which are duplicate. I deleted all files with version ending. This seems to work :) VG |
Awesome, thanks! I can confirm that it solved the problem. |
As a general rule, the dumps we provide must always be used with the latest released photon. We do not guarantee compatibility with former or future versions. If you want to to use the development version from master, you need to create your own extracts. That said, I think the dependency change is currently the only breaking change. So at the time of writing this, you might get away with deleting these files. |
@lonvia Thanks for the explanation! |
There is still something wrong! I have downloaded the photon-0.3.2.jar and latest photon_data from 'http://download1.graphhopper.com/public/photon-db-latest.tar.bz2' Then I ran the jar As you can see below, it ran and I was able to make API requests
Later I stopped the jar, and wanted to run from my local code repo. I'm unable to run it. Below is the error
Now when I go back to just running the jar which I downloaded
To add to the above, I also checked /photon_data/elasticsearch/modules/lang-painless/ for duplicates. Which don't exist. Below screenshot for reference The photon_data is broken now.
When do we get the above errors? This is not my first attempt at running this application. I was able to run it previously. To investigate, I set up the entire project again today. Now, still running into same issue. I just need a why |
Hello,
I'm trying to compile Photon to get the latest features (mostly the bbox). I simply cloned the master branch and ran the following comands:
When going to http://locahost:2322/api/?q=berlin, I get a 500 error: org.elasticsearch.index.IndexNotFoundException: no such index
I guess that it is normal since I didn't download the photon_data folder on my dev machine. But then when I upload my jar to my server (with the worldwide photon_data) and start Photon, it fails to start with the following error:
Worse, after that it broke my photon_data and I can't start photon using the old jar either (error is the same). I ran a diff between my saved photon_data and the corrupted one, here's the result:
Did I do something wrong, or is it a bug?
The text was updated successfully, but these errors were encountered: