govau / govau/graylog-boshrelease

elsaticsearch-master Instance getting failed when deploying graylog bosh-release

Open
#13 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Shell
Stars
9
Forks
6
PR merge metrics
No merged PRs in 30d

Description

Hello Team, I am encountering an error when deploying Graylog on our opensource CF platform (Azure IAAS). I am trying to deploy Graylog with Bosh-release.
Graylog project -- https://github.com/govau/graylog-boshrelease
I have deployed latest release graylog v0.2.0
Used below stemcell
stemcells:
- alias: default
os: ubuntu-xenial
version: 621.123
After bosh deploy, The "elasticsearch-master" getting failed with below errors.
It's been 3 days I got stuck with this issue. Can someone please assist me on this. Many thanks!!

/var/vcap/sys/log/elsaticsearch/elasticsearch.stderr.log

**Exception in thread "main" SettingsException[Failed to open stream for url [/var/vcap/packages/elasticsearch/config/elasticsearch.yml]]; nested: AccessDeniedException[/var/vcap/packages/elasticsearch/config/elasticsearch.yml];
Likely root cause: java.nio.file.AccessDeniedException: /var/vcap/packages/elasticsearch/config/elasticsearch.yml
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:84)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102)
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107)
at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:214)
at java.nio.file.Files.newByteChannel(Files.java:361)
at java.nio.file.Files.newByteChannel(Files.java:407)
at java.nio.file.spi.FileSystemProvider.newInputStream(FileSystemProvider.java:384)
at java.nio.file.Files.newInputStream(Files.java:152)
at org.elasticsearch.common.settings.Settings$Builder.loadFromPath(Settings.java:1067)
at org.elasticsearch.node.internal.InternalSettingsPreparer.prepareEnvironment(InternalSettingsPreparer.java:88)
at org.elasticsearch.common.cli.CliTool.(CliTool.java:107)
at org.elasticsearch.common.cli.CliTool.(CliTool.java:100)
at org.elasticsearch.bootstrap.BootstrapCLIParser.(BootstrapCLIParser.java:48)
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:242)
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:45)
Refer to the log for complete error details.**

![image](https://user-images.githubusercontent.com/56149476/120588540-fb755600-c454-11eb-97c6-1eab23acbfa3.png)
![image](https://user-images.githubusercontent.com/56149476/120588577-0af49f00-c455-11eb-8062-441198af9331.png)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the BOSH deployment configuration for the elasticsearch-master instance and the reported /var/vcap/sys/log/elsaticsearch/elasticsearch.stderr.log output. Check how the deployment creates or accesses /var/vcap/packages/elasticsearch/config/elasticsearch.yml under Ubuntu Xenial stemcell 621.123. Done means the elasticsearch-master instance deploys successfully without the reported AccessDeniedException.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure, elasticsearch, ubuntu
Domain
devops, infrastructure, search
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.