Splunk 9.1.3 Startup Errors
@jmeixensperger ya está trabajando en esto.
Desde el 7/5/2024.
Evaluación
Este issue todavía no se ha evaluado.
Descripción
Hello,
We recently upgraded from 9.0.7 to 9.1.3 for the Universal Forwarder using the image provided here
The errors we see are:
TASK [splunk_universal_forwarder : Debug hec_token] ****************************
ok: [localhost] => {
"hec_token": {
"changed": true,
"excep_str": "No Exception",
"failed": false,
"json": {
"messages": [
{
"text": "Could not find object id=http://splunk_hec_token/",
"type": "ERROR"
}
]
},
"status": 404
}
}
Which looks like it gets resolved with:
TASK [splunk_universal_forwarder : Debug create_hec_token] *********************
ok: [localhost] => {
"create_hec_token": {
"changed": false,
"skip_reason": "Conditional result was False",
"skipped": true
}
}
We're not using HEC in this case so I think this error can be ignored.
We then see this error happen twice:
included: /opt/ansible/roles/splunk_universal_forwarder/tasks/../../../roles/splunk_common/tasks/check_for_required_restarts.yml for localhost
Tuesday 12 March 2024 22:25:58 +0000 (0:00:00.042) 0:00:32.858 *********
TASK [splunk_universal_forwarder : Check for required restarts] ****************
fatal: [localhost]: FAILED! => {}
MSG:
The conditional check 'restart_required.content' failed. The error was: error while evaluating conditional (restart_required.content): 'dict object' has no attribute 'content'
...ignoring
Tuesday 12 March 2024 22:25:58 +0000 (0:00:00.300) 0:00:33.159 *********
TASK [splunk_universal_forwarder : debug] **************************************
ok: [localhost] => (item=failed) => {}
MSG:
Hello World -
ok: [localhost] => (item=msg) => {}
MSG:
Hello World -
Tuesday 12 March 2024 22:25:58 +0000 (0:00:00.071) 0:00:33.230 *********
Tuesday 12 March 2024 22:25:58 +0000 (0:00:00.039) 0:00:33.269 *********
TASK [Check all instances for required restarts] *******************************
included: /opt/ansible/roles/splunk_common/tasks/check_for_required_restarts.yml for localhost
Tuesday 12 March 2024 22:25:58 +0000 (0:00:00.050) 0:00:33.320 *********
TASK [Check for required restarts] *********************************************
fatal: [localhost]: FAILED! => {}
MSG:
The conditional check 'restart_required.content' failed. The error was: error while evaluating conditional (restart_required.content): 'dict object' has no attribute 'content'
...ignoring
Tuesday 12 March 2024 22:25:58 +0000 (0:00:00.305) 0:00:33.625 *********
TASK [debug] *******************************************************************
ok: [localhost] => (item=failed) => {}
MSG:
Hello World -
ok: [localhost] => (item=msg) => {}
MSG:
Hello World -
Tuesday 12 March 2024 22:25:58 +0000 (0:00:00.058) 0:00:33.683 *********
PLAY RECAP *********************************************************************
localhost : ok=108 changed=22 unreachable=0 failed=0 skipped=80 rescued=0 ignored=2
We still see events being forwarded and things appear to look okay. Is there anything else I should check or be concerned about?
- Lenguaje dominante
- Python
- Estrellas
- 551
- Forks
- 279
- Merge medio
- 3 d 9 h
- PR fusionados (30 d)
- 2
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Sin plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de splunk/docker-splunk
-
Dificultad 2/5 Medio día Aptitud para principiantes 78/100
splunk/docker-splunk#730 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 58/100
splunk/docker-splunk#737 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 55/100
splunk/docker-splunk#732 ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 35/100
splunk/docker-splunk#731 · 1 reacción ·
-
Dificultad 3/5 1-2 días Aptitud para principiantes 38/100
splunk/docker-splunk#724 ·
Todos los issues de splunk/docker-splunk
Issues similares
-
`burr` fails to start when the Python path has a space in itPosiblemente ocupada @enekoreto la tomó hoy. Abiertostatus/needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 5 días
-
gemini 出现了新的域名需要加入Abierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
-
Dificultad 2/5 Medio día Aptitud para principiantes 72/100
debpalash/VoiceStudio#2903 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
dagster-io/community-integrations#367 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
aws-samples/sample-per-model-bedrock#243 ·
Los mantenedores suelen responder en 1 día