You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The issue tracker is ONLY used for the bug report(feature request need to follow RIP process). Keep in mind, please check whether there is an existing same report before you raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:
BUG REPORT
Please describe the issue you observed:
What did you do (The steps to reproduce)?
just start a new instance of rocketmq
What did you expect to see?
start success
What did you see instead?
the controller failed to start
root@worker01:~# systemctl status docker
● docker.service - Docker Application Container Engine
Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2024-05-07 16:25:48 CST; 6 days ago
TriggeredBy: ● docker.socket
Docs: https://docs.docker.com
Main PID: 1039 (dockerd)
Tasks: 35
Memory: 514.5M
CPU: 7h 33min 19.623s
CGroup: /system.slice/docker.service
└─1039 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock
kubelet info
root@master01:~# systemctl status kubelet
● kubelet.service - kubelet: The Kubernetes Node Agent
Loaded: loaded (/lib/systemd/system/kubelet.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/kubelet.service.d
└─10-kubeadm.conf
Active: active (running) since Tue 2024-04-16 23:38:54 CST; 3 weeks 6 days ago
Docs: https://kubernetes.io/docs/
Main PID: 2398 (kubelet)
Tasks: 31 (limit: 21440)
Memory: 135.5M
CPU: 1d 20h 16min 49.986s
CGroup: /system.slice/kubelet.service
└─2398 /usr/bin/kubelet --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --container-runtime-endpoint=unix:///var/run/cri-dockerd.sock --pod-infra-container-image=registry.aliyuncs.com/google_containers/pause:3.9
root@master01:~# cat /var/lib/kubelet/config.yaml|grep cgroupDriver
cgroupDriver: systemd
Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
the logs of pod
kubectl logs controller-0
cat: can't open '/sys/fs/cgroup/memory/memory.limit_in_bytes': No such file or directory
/root/rocketmq/controller/bin/runserver.sh: line 58: arithmetic syntax error
FEATURE REQUEST
Please describe the feature you are requesting.
Provide any additional detail on your proposed use case for this feature.
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
The text was updated successfully, but these errors were encountered:
usernameisnull
changed the title
when use cgroups v2,the controller can't start
when use cgroupdriver use systemd,the controller can't start
May 13, 2024
usernameisnull
changed the title
when use cgroupdriver use systemd,the controller can't start
when cgroupdriver use systemd,the controller can't start
May 13, 2024
The issue tracker is ONLY used for the bug report(feature request need to follow RIP process). Keep in mind, please check whether there is an existing same report before you raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our mailing lists. We welcome any friendly suggestions, bug fixes, collaboration and other improvements.
Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following:
BUG REPORT
What did you do (The steps to reproduce)?
just start a new instance of rocketmq
What did you expect to see?
start success
What did you see instead?
the controller failed to start
Please tell us about your environment:
node:
docker version
/etc/docker/daemon.json
docker info
systemctl status docker
kubelet info
Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc):
the logs of pod
FEATURE REQUEST
Please describe the feature you are requesting.
Provide any additional detail on your proposed use case for this feature.
Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue?
If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task:
The text was updated successfully, but these errors were encountered: