Splunk 9.1.3 Startup Errors
@jmeixensperger 已经在做这个了。
开始于 2024年5月7日。
评估
这个 Issue 还没有评估数据。
描述
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?
- 主要语言
- Python
- 星标
- 551
- 派生
- 279
- 平均合并
- 23 小时 25 分钟
- 30 天内合并 PR
- 1
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
splunk/docker-splunk 的其他 Issue
-
难度 2/5 半天 新手友好度 78/100
splunk/docker-splunk#730 ·
-
难度 3/5 1-2 天 新手友好度 35/100
splunk/docker-splunk#738 ·
-
难度 3/5 1-2 天 新手友好度 58/100
splunk/docker-splunk#737 ·
-
难度 3/5 1-2 天 新手友好度 55/100
splunk/docker-splunk#732 ·
-
难度 3/5 1-2 天 新手友好度 35/100
splunk/docker-splunk#731 · 1 个 reaction ·
查看 splunk/docker-splunk 的全部 Issue
相似的 Issue
-
Deferred from #1869: Complete the companion pytest guardrail update noted in the PR description...未关闭
难度 1/5 1 小时以内 新手友好度 95/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
NousResearch/hermes-agent#140958 ·
维护者通常 1 天内回复
-
Bug triage/confirmed
难度 2/5 半天 新手友好度 85/100
agentscope-ai/agentscope#3355 ·
维护者通常 2 天内回复
-
难度 1/5 1 小时以内 新手友好度 95/100
ethereum/execution-specs#3859 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复