(XPackPlugin.java:200) ~[?:?]
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) ~[?:?]
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62) ~[?:?]
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) ~[?:?]
at java.lang.reflect.Constructor.newInstance(Constructor.java:423) ~[?:1.8.0_131]
at org.elasticsearch.plugins.PluginsService.loadPlugin(PluginsService.java:383) ~[elasticsearch-5.3.2.jar:5.3.2]
... 18 more
```
I have configured tribe node as below.
```
node.master: false
node.data: false
node.ingest: false
tribe.on_conflict: prefer_tdc1
tribe:
tdc1:
cluster.name: dc1
node.name: ${HOSTNAME}
network.host: 172.16.x.xx
transport.host: 172.16.x.xx
discovery.zen.ping.unicast.hosts: ["172.16.x.xx", "172.16.x.xx", "172.16.x.xx"]
tdc2:
cluster.name: dc2
node.name: ${HOSTNAME}
network.host: 10.xxx.xx.x
transport.host: 10.xxx.xx.x
discovery.zen.ping.unicast.hosts: ["10.xxx.xx.x", "10.xxx.xx.x", "10.xxx.xx.x"]
```
I have installed x-pack from file and there was no error during the installation.
Is there any thing that I have missed with configuration?
---
### Author:  [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)
#### Post date: [April 29, 2017, 10:01am UTC](https://discuss.elastic.co/t/help-tribe-node-startup-fails-if-tribe-on-conflict-option-specified/84080/2 "2017-04-29T10:01:09Z")
Looking at the log , below directory path doesn't even exist when x-pack is installed.
`/usr/share/elasticsearch/config/x-pack`
Is this something that you have to create?
---
### Author:  [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)
#### Post date: [April 29, 2017, 1:12pm UTC](https://discuss.elastic.co/t/help-tribe-node-startup-fails-if-tribe-on-conflict-option-specified/84080/3 "2017-04-29T13:12:27Z")
By following the [document](https://www.elastic.co/guide/en/x-pack/current/security-getting-started.html), error still exists event though I create the **system\_key.**
[sysadmin@xxxx ~]$ sudo ls -ltr /usr/share/elasticsearch/config/x-pack
合計 4
-rw-------. 1 elasticsearch elasticsearch 128 4月 29 21:50 system\_key
---
### Author:  [@TimV](https://discuss.elastic.co/u/TimV)
#### Post date: [May 1, 2017, 1:57am UTC](https://discuss.elastic.co/t/help-tribe-node-startup-fails-if-tribe-on-conflict-option-specified/84080/4 "2017-05-01T01:57:54Z")
> [@YuWatanabe](#):
>
> access denied ("java.io.FilePermission" "/usr/share/elasticsearch/config/x-pack/system\_key" "read")
This sort of error (`FilePermission` on a config file) is generally caused by having mismatch between your `path.conf` setting, and where various files have been put.
The Elasticsearch security manager restricts the process to only being able to read files that are in the specified locations (config dir, data dir, etc), so if your process tries to read files outside of those locations, it will fail.
Because tribe is involved, it could be more complicated than that, but the starting point is to look at things like:
- Does your tribe node have a `path.conf` set?
- What directory is your `elasticsearch.yml` stored in?
- How does that compare to the path in the error message?
---
### Author:  [@YuWatanabe](https://discuss.elastic.co/u/YuWatanabe)
#### Post date: [May 1, 2017, 10:56pm UTC](https://discuss.elastic.co/t/help-tribe-node-startup-fails-if-tribe-on-conflict-option-specified/84080/5 "2017-05-01T22:56:43Z")
> [@TimV](#):
>
> Does your tribe node have a path.conf set?
@TimV
Thank you for the reply. Your first suggestion did the fix. I had to explicitly specify _path.conf_ in elasticsearch.yml for tribe node. (Not in the tribe node stanza)
```
# ----------------------------------- Paths ------------------------------------
#
# Path to directory where to store the data (separate multiple locations by comma):
#
#path.data: /path/to/data
#
# Path to log files:
#
#path.logs: /path/to/logs
path.conf: /etc/elasticsearch
```
Did this behavior changed in 5.3.2?
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [May 29, 2017, 11:05pm UTC](https://discuss.elastic.co/t/help-tribe-node-startup-fails-if-tribe-on-conflict-option-specified/84080/6 "2017-05-29T23:05:17Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.