Question
Nationale Nederlanden
NL
Last activity: 6 Jul 2018 6:59 EDT
Path Lucene index
Hello,
we got a lot of Acces denied errors cause by the Lucene search or ElasticSearch.
Errors like:
Hello,
we got a lot of Acces denied errors cause by the Lucene search or ElasticSearch.
Errors like:
[[18-6-18 11:41:20:656 CEST] 0000014d SecurityManag W SECJ0314W: Current Java 2 Security policy reported a potential violation of Java 2 Security Permission. Refer to the InfoCenter for further information.
Permission:
/sys : Access denied ("java.io.FilePermission" "/sys" "read")
Code:
org.apache.lucene.util.IOUtils in {pegajdbc://691737468:0/lucene-core-5.5.2.jar}
Stack Trace:
java.security.AccessControlException: Access denied ("java.io.FilePermission" "/sys" "read")
at java.security.AccessController.throwACE(AccessController.java:176)
at java.security.AccessController.checkPermissionHelper(AccessController.java:236)
at java.security.AccessController.checkPermission(AccessController.java:371)
at java.lang.SecurityManager.checkPermission(SecurityManager.java:562)
at com.ibm.ws.security.core.SecurityManager.checkPermission(SecurityManager.java:208)
at java.lang.SecurityManager.checkRead(SecurityManager.java:901)
at sun.nio.fs.UnixFileSystem$FileStoreIterator.readNext(UnixFileSystem.java:220)
at sun.nio.fs.UnixFileSystem$FileStoreIterator.hasNext(UnixFileSystem.java:237)
at org.apache.lucene.util.IOUtils.getFileStore(IOUtils.java:515)
at org.apache.lucene.util.IOUtils.spinsLinux(IOUtils.java:459)
at org.apache.lucene.util.IOUtils.spins(IOUtils.java:448)
at org.elasticsearch.env.ESFileStore.<init>(ESFileStore.java:62)
at org.elasticsearch.env.ESFileStore.getFileStores(ESFileStore.java:192)
at org.elasticsearch.env.ESFileStore.getMatchingFileStore(ESFileStore.java:108)
at org.elasticsearch.env.Environment.getFileStore(Environment.java:303)
at org.elasticsearch.env.NodeEnvironment$NodePath.<init>(NodeEnvironment.java:93)
at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:175)
at org.elasticsearch.node.Node.<init>(Node.java:165)
at com.pega.pegarules.search.internal.es.ElasticSearchNode$ESNode.<init>(ElasticSearchNode.java:177)
at com.pega.pegarules.search.internal.es.ElasticSearchNode.createESNode(ElasticSearchNode.java:52)
at com.pega.pegarules.search.internal.PRSearchProviderImpl._initializeFTS(PRSearchProviderImpl.java:618)
at com.pega.pegarules.search.internal.PRSearchProviderImpl.initializeFTS(PRSearchProviderImpl.java:230)
at com.pega.pegarules.search.internal.PRSearchProviderImpl.initializeFTS(PRSearchProviderImpl.java:193)
at com.pega.pegarules.session.internal.async.startup.SearchInitializationTask.runTask(SearchInitializationTask.java:38)
at com.pega.pegarules.session.internal.async.startup.StartupTask$1.run(StartupTask.java:35)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock(PRSessionProviderImpl.java:1286)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:1034)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:843)
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(PRSessionProviderImpl.java:810)
at com.pega.pegarules.session.internal.async.startup.StartupTask.run(StartupTask.java:30)
at java.lang.Thread.run(Thread.java:811)
Code Base Location:
We are running on the Websphere platform 8.5.5 / Pega 7.2.2. and have on each machine multiple JVMs. The error is because of it looks like Lucene search tries to access some root directories (like /sys in this example) and not only the directories defined on a JVM. Is there a way to restrict this? Tried to find documentation on this, but no luck so far.
Regards,
Maurice Boer
***Edited by Moderator Marissa to update platform capability tags***
Pegasystems Inc.
IN
Hi,
I am little confused here, have you checked your search landing page ? What is the path mentioned there? And if the user has the access to the location ? Correct me if I got something wrong here
Nationale Nederlanden
NL
Maurice
Wipro
IN
Hi Maurice
What I understand that even though the Index directory for Lucene is NOT set to /sys directory, lucene is trying to read it and failing because it does not have permission to read it . I am not sure but I found below post from IBM support taking about similar issue, please check this, this might help.
http://www-01.ibm.com/support/docview.wss?uid=swg1PK67415
-Rajesh
Nationale Nederlanden
NL
Hello Rajesh,
thanks for the response. I will forward it to our Websphere department. And yes it doesn't have the rights to read it. But we don't like to give read access to all libraries. I will give the result back as soons as the Websphere team have look to it.
Regards,
Maurice