aws / aws/containers-roadmap

[eks][eks-node-monitoring-agent] Establishing dbus connection error

Open
#2,534 1 comment 6 reactions 0 assignees View on GitHub
EKS Nodes
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

When installing eks-node-monitoring-agent addons to EKS cluster onto a Karpenter-provisioned bottle-rocket node, this error message shows up multiple times in pod logs

```shell
{"level":"error","ts":"2025-01-30T11:13:19Z","msg":"error in channel handler","monitor":"container-runtime","error":"establishing dbus connection, dial unix /run/systemd/private: connect: no such file or directory","stacktrace":"golang.a2z.com/EKSNodeMonitoringAgent/internal/monitor/util.(*channelHandler[...]).Start\n\t/local/p4clients/pkgbuild-const/workspace/src/EKSNodeMonitoringAgent/internal/monitor/util/subscription.go:72"}
```

Can you assist in this issue?

Contributor guide

Open the contributing guide

Research direction

Reproduce the installation on an EKS cluster using a Karpenter-provisioned Bottlerocket node and inspect the pod logs. Read internal/monitor/util/subscription.go around line 72, where the reported channel-handler error originates. Done means the repeated dbus connection error is resolved or its expected behavior on Bottlerocket is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, infrastructure, observability-sre
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.