splunk / splunk/docker-splunk

universalforwarder keeps shutting down

Open
#530 0 comments 0 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

Hi

I setup two containers (standalone and universalforwarder) with docker-compose as described in https://splunk.github.io/docker-splunk/EXAMPLES.html#create-standalone-and-universal-forwarder

Splunk standalone runs fine. Universal forwarder however shuts down after a full playbook run. Is it normal?

the docker-compose.yml is just like in the example with added debug env variables:

version: "3.6"

networks:
  splunknet:
    driver: bridge
    attachable: true

services:
  uf1:
    networks:
      splunknet:
        aliases:
          - uf1
    image: ${UF_IMAGE:-splunk/universalforwarder:latest}
    hostname: uf1
    container_name: uf1
    environment:
      - SPLUNK_START_ARGS=--accept-license
      - SPLUNK_STANDALONE_URL=so1
      - SPLUNK_ADD=udp 1514, monitor /var/log/*
      - SPLUNK_PASSWORD=TestSplunk
      - DEBUG=true
      - ANSIBLE_EXTRA_FLAGS=-vv
    ports:
      - 8089

  so1:
    networks:
      splunknet:
        aliases:
          - so1
    image: ${SPLUNK_IMAGE:-splunk/splunk:latest}
    hostname: so1
    container_name: so1
    environment:
      - SPLUNK_START_ARGS=--accept-license
      - SPLUNK_STANDALONE_URL=so1
      - SPLUNK_PASSWORD=TestSplunk
      - DEBUG=true
      - ANSIBLE_EXTRA_FLAGS=-vv
    ports:
      - 8000
      - 8089

I have attached the logs.
uf1_ansible_vv.log
uf1_splunkd.log

Thanks for any insights!

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

Start with docker-compose.yml and the linked universal-forwarder example, then inspect uf1_ansible_vv.log and uf1_splunkd.log to identify why uf1 exits after the full playbook run. Done means establishing whether the shutdown is expected and documenting the evidence or reproducible change needed.

Written by the indexing model from the issue text.

Assessment

Tech stack
docker, docker-compose
Domain
devops, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.