question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

statsd socat beats the DNS to death

See original GitHub issue

When deploying kubernetes on single node cluster using kubeadm, coredns services shows high cpu usage (30-40% per process) if ambassador was deployed.

How to reproduce:

  1. Install kubeadm on single node.
  2. Set net.bridge.bridge-nf-call-iptables=1
  3. Allow master to run pods kubectl taint nodes --all node-role.kubernetes.io/master-
  4. Install network plugins, flannel or romana (reproduced on both).
  5. Deploy ambassador.

Versions:

  • Ambassador 0.34.3 or 0.35.0
  • kubeadm v1.11.0 on vds
  • kubectl v1.11.0

Ambassador with no connected services, without ingress. High kube-dns and dnsmasq cpu usage (cannot attach a screenshot, since I have already updated k8s). After upgrade, kube-dns was replaced with coredns, but cpu usage is identical. After deleting ambassador CPU usage reduced to normal value (1-3% in my case). Ambassador 0.30.1 doesn’t have this issue.

top screenshot: image

Issue Analytics

  • State:closed
  • Created 5 years ago
  • Reactions:2
  • Comments:11 (6 by maintainers)

github_iconTop GitHub Comments

2reactions
jar3bcommented, Jun 28, 2018

@kflynn No, I’m not in the channel. For configuration i use this manual with RBAC enabled. Statsd isn’t separately configured. I looked at the logs, there is a repeated message

2018/06/28 15:25:11 socat[6173] E getaddrinfo("statsd-sink", "NULL", {1,0,2,17}, {}): Name does not resolve

about 100 times per second. Then found the solution in a similar issue - https://github.com/datawire/ambassador/issues/465

Tested with statsd container disabled - all is ok. Thanks for the right questions 😉 this is my inattention.

1reaction
concafcommented, Aug 14, 2018

Sorry for the delay, loooong weekend 😐 The fix is at #725, if someone wants to try it out. Container image for the PR: quay.io/datawire/ambassador:concaf-fix-socat-5d30875 Do read the instructions at https://github.com/datawire/ambassador/pull/725#issue-208206832

This might take a couple of days to merge because it’s sort of a backwards incompatible change.

Read more comments on GitHub >

github_iconTop Results From Across the Web

statsd socat beats the DNS to death · Issue #568 · emissary-ingress ...
When deploying kubernetes on single node cluster using kubeadm, coredns services shows high cpu usage (30-40% per process) if ambassador was deployed.
Read more >
Metasploit - OutRunSec
Notice our meterpreter session died, approximately 30 seconds after starting. We have a error message indicating a problem starting the service, and mostly ......
Read more >
uWSGI Documentation - Read the Docs
This will spawn 4 processes (each with 2 threads), a master process (will respawn your processes when they die) and.
Read more >
format string - CVE - Search Results
Multiple format string vulnerabilities in (a) OpenBOR 2.0046 and earlier, (b) Beats of Rage (BOR) 1.0029 and earlier, and (c) Horizontal Shooter BOR...
Read more >
Untitled
Snellire, A quoi sert beats audio, 1989 aerobics championship, ... Beantown brewery terminal hack, Sutcliffe jugend death mask, Palabras en idioma warao, ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found