<p>Somehow, I have 2 versions of fluentd running in my cluster:</p>

<p><a href="https://i.stack.imgur.com/73Lt6.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/73Lt6.png" alt="enter image description here"></a></p>

<p>They end up fighting over the same port, they just keep cranking away, trying to start up on that port, and it saturates all the CPU in the cluster.</p>

<p><code>unexpected error error_class=Errno::EADDRINUSE error="Address already in use - bind(2) for 0.0.0.0:24231</code>
<code>/opt/google-fluentd/embedded/lib/ruby/2.6.0/socket.rb:201:in 'bind'</code></p>

<p>I've tried deleting the daemon sets and deployments, they just keep coming back. Also tried ssh'ing into the machines and killing the process on that port. Nothing seems to work.</p>

<p>Obviously, I only want one version of fluentd to run (and I'm not even sure which one).</p>

Mark
<p>I seem to have fixed it. I went to GCP dashboard cluster edit page, <code>Kubernetes Engine Monitoring</code> dropdown <strong>was blank</strong>. It seems not even the dropdown could decide what to display here.</p>

<p>It seems the automated agent, or whatever, seriously messed up here, and had 2 versions of the logging and monitoring system running, fighting over a port, and crushing the CPU on every machine in the cluster. On top of that, I couldn't delete the daemon sets, pods, or deployments. It seems Google treats these as special somehow, maybe with some kind of automated agent, I don't know.</p>

<p>From the dropdown, I just selected <code>System and workload logging and monitoring</code>, saved, and it applied the changes.</p>

<p>Everything looking good so far, but this whole event has me worried, I didn't do anything. This just....happened.</p>

<p>This is a dev cluster, but if it was a production cluster...</p>
