-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Problems with file access through current alias (Elasticsearch 511) #1202
Comments
I don't know how Elasticsearch works or how to replicate this, sorry. Can you provide more info? If I install this manifest replacing If I change The error in the logfile seems to be |
Forgot to mention we install it using the
While running it from the explicit version folder gives the following (normal/successfull output):
Using the explicit version
EDIT: Just to clarify. We have our data folder outside of the scoop install folder (defined in our elasticsearch config), but it fails on the next step when it tries to load .jar file modules from the modules folder with a similar access denied error as the one above. This was just me reproducing the access error on my machine. |
Thanks—that narrows it down, but I'll have to do some more investigation. For now, can you run |
Works great. Thanks :)
|
Having some trouble with file access and the
current
linked folder. Using the following recipe (we have our own repo with recipes) fails when runningelssrv install -> elssrv start
because the JVM doesn't seem to get access to.jar
files through thecurrent
link. When running the same commands from the version specific folder it works.The text was updated successfully, but these errors were encountered: