-
Hello, I started a discussion because rabbitmq started eating memory after the update. We experience this behavior in all clusters we updated from 4.11.0-0.okd-2022-11-19-050030 to 4.11.0-0.okd-2023-01-14-152430. What we know so far:
Are there any changes between 4.11.0-0.okd-2022-11-19-050030 and 4.11.0-0.okd-2023-01-14-152430 that could cause this "problem"/behavior. Maybe some Security Constraints have changed? Anyone an idea why this happens? Do we need to "grant" more rights? Any help/hint is very appreciated! Thanks in advance, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Hi, we did an strace of the network binding:
But there is already a running empd on this port:
We see that the new epmd runs on a different port not on 4369 as from the strace.
We would expect the following behavior:
Any ideas? Regards Philipp |
Beta Was this translation helpful? Give feedback.
-
Hi, any thoughts on this? We really need to find out why we get a random port for: Regards Philipp |
Beta Was this translation helpful? Give feedback.
-
Hi. I think this is a bug in the kernel function bind. If the port is busy it returns success instead of error. spec:
template:
spec:
shareProcessNamespace: true
containers:
- name: watchdog
image: busybox:1.36.1
args:
- sh
- '-c'
- >-
while true; do A=$(netstat -nlp 2>/dev/null | grep epmd | grep -v
4369 | grep -o "[0-9]*/epmd" | grep -o "[0-9]*" | sort | uniq);
C=$(echo $A | wc -w); echo -n $(date "+%F %T"); if [ $C -eq 0
];then echo " Nothing to terminate."; else kill $A; echo "
Terminated $C processes."; fi; sleep 1200; done
resources:
limits:
cpu: 50m
memory: 32Mi
requests:
cpu: 30m
memory: 32Mi |
Beta Was this translation helpful? Give feedback.
Perhaps its https://bugzilla.redhat.com/show_bug.cgi?id=2159802?