splunk / splunk/docker-splunk

forwarder latest docker image fails to start

Open
#564 16 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
549
Forks
277
Avg merge
3d 9h
Merged PRs (30d)
2

Description

Image:
splunk/universalforwarder:latest

You can reproduce it with:

https://github.com/splunk/docker-splunk/blob/develop/test_scenarios/1uf1so.yaml

or as described here:

https://splunk.github.io/docker-splunk/EXAMPLES.html#create-standalone-and-universal-forwarder

Universal forwarder never starts with the the following error:

[WARNING]: Using world-readable permissions for temporary files Ansible needs to create when becoming an unprivileged user. This may be insecure. For information on securing this, see
https://docs.ansible.com/ansible/user_guide/become.html#risks-of-becoming-an-unprivileged-user
^C [ERROR]: User interrupted execution
Warning: Attempting to revert the SPLUNK_HOME ownership
Warning: Executing "chown -R splunk /opt/splunkforwarder"
Error calling execve(): No such file or directory
Error launching  command: No such file or directory
splunkd is not running.

=> Working fine in 8.2.9.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the failure with test_scenarios/1uf1so.yaml or the standalone and universal forwarder example linked in the issue. Start by comparing the latest image behavior with version 8.2.9 and trace the startup failure around the reported Ansible interruption and /opt/splunkforwarder ownership restoration. Done means the universal forwarder starts successfully and splunkd is running.

Written by the indexing model from the issue text.

Assessment

Tech stack
ansible, docker
Domain
devops, infrastructure
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.