我使用的是AWSEKS1.21和(无服务器)。我试图将Fluentd作为守护进程运行,但是守护进程根本没有运行。
其他所有对象,如角色、角色绑定、serviceaccount、configmap,都已经在集群中了。
NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
aws-node 0 0 0 0 0 <none> 8d
我正在尝试为VMWare的Fluentd operator [1]挂载Kubernetes configmap。我查看了文档,helm图表表明您必须指定一个额外的卷作为名为fluentd.extraVolumeMounts的参数 我用来安装操作员的舵表如下: #!/bin/sh
# helmenv set to helm3
CHART_URL='https://github.com/vmware/kube-fluentd-operator/releases/download/v1.12.0/log-router-0.3.3.tgz'
# Set environment v
我尝试在运行Ubuntu16.04.5LTS的AWS EC2实例上使用google-fluentd stackdriver日志记录代理,但失败了,错误如下。有人能帮上忙吗?
*Job for google-fluentd.service failed because the control process exited with error code. See "systemctl status google-fluentd.service" and "journalctl -xe" for details.
invoke-rc.d: initscript go
我正在尝试创建一个基于fluentd-hec镜像安装了grok-parser的镜像。 这是我正在使用的Dockerfile: FROM splunk/fluentd-hec:1.2.4
USER root
RUN gem install fluent-plugin-grok-parser
RUN chown -R fluent:fluent /usr/local/share/gems/gems/fluent-plugin-grok-parser-*
USER fluent 这是该构建的输出 Step 1/5 : FROM splunk/fluentd-hec:1.2.4
---> a
我有一个fluentd.conf文件,我试图在我的迷你库集群中使用(复制)它(在一个码头容器中工作得很好)。这些步骤如下:
将使用以下命令构建(在我的minikube docker -env中)码头映像:
FROM fluent/fluentd:v1.11-1
# Use root account to use apk
USER root
# below RUN includes plugin as examples elasticsearch is not required
# you may customize including plugins as you wish
R
在EFK设置中,fluentd突然停止向elasticsearch发送,并在日志中显示以下错误:
2020-09-28 18:48:55 +0000 [warn]: #0 Could not communicate to Elasticsearch, resetting connection and trying again. getaddrinfo: Name or service not known (SocketError)
2020-09-28 18:48:55 +0000 [warn]: #0 Remaining retry: 6. Retry to communicate afte