ResourceWatcherService Exception even on changing the permissions

I have changed permission for the scripts directory to "drwxrwxr-x". But still getting the following exception:

failed to run scheduled task [org.elasticsearch.watcher.ResourceWatcherService$ResourceMonitor@3f813572] on thread pool [same] access denied ("" "" "read")
at ~[?:1.8.0_66]
at ~[?:1.8.0_66]
at java.lang.SecurityManager.checkPermission( ~[?:1.8.0_66]
at java.lang.SecurityManager.checkRead( ~[?:1.8.0_66]
at sun.nio.fs.UnixPath.checkRead( ~[?:?]
at sun.nio.fs.UnixFileSystemProvider.checkAccess( ~[?:?]
at java.nio.file.Files.exists( ~[?:1.8.0_66]
at org.elasticsearch.watcher.FileWatcher$FileObserver.checkAndNotify( ~[elasticsearch-5.6.8.jar:5.6.8]
at org.elasticsearch.watcher.FileWatcher.doCheckAndNotify( ~[elasticsearch-5.6.8.jar:5.6.8]
at org.elasticsearch.watcher.AbstractResourceWatcher.checkAndNotify( ~[elasticsearch-5.6.8.jar:5.6.8]
at org.elasticsearch.watcher.ResourceWatcherService$ ~[elasticsearch-5.6.8.jar:5.6.8]
at org.elasticsearch.threadpool.ThreadPool$ReschedulingRunnable.doRun( [elasticsearch-5.6.8.jar:5.6.8]
at [elasticsearch-5.6.8.jar:5.6.8]
at org.elasticsearch.threadpool.ThreadPool$ [elasticsearch-5.6.8.jar:5.6.8]
at java.util.concurrent.Executors$ [?:1.8.0_66]
at [?:1.8.0_66]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201( [?:1.8.0_66]
at java.util.concurrent.ScheduledThreadPoolExecutor$ [?:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:1.8.0_66]
at java.util.concurrent.ThreadPoolExecutor$ [?:1.8.0_66]
at [?:1.8.0_66]

If you are going to open duplicate issues in the forums and github (but really, please don't), then can you at least link them so we don't try and answer them twice.

What do the permissions look like on the hierachy of that scripts directory?




while [ -n "$Dir" -a "$Dir" != "/" -a -d "$Dir" ]
    ls -ld $Dir
    Dir=$(dirname $Dir)

Apologies for not linking the issue....but my intention was to get help from where ever I could.
Yes the issue is resolved now as I updated the scripts location to be within the config directory.
Just one question why path.scripts variable is provided if we have to keep scripts inside the CONFIG DIRECTORY?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.