I upgraded my old droplet with the new monitoring and the do-agent eats over 40% of the available RAM and spawns a lot of mysqld processes
$ top -b -H -n1 | grep do-agent
9256 do-agent 20 0 496116 5692 0 S 0.0 0.6 0:01.59 do-agent
9276 do-agent 20 0 496116 5692 0 S 0.0 0.6 0:00.74 do-agent
9277 do-agent 20 0 496116 5692 0 S 0.0 0.6 0:02.50 do-agent
9278 do-agent 20 0 496116 5692 0 S 0.0 0.6 0:00.00 do-agent
9285 do-agent 20 0 496116 5692 0 S 0.0 0.6 0:13.49 do-agent
9286 do-agent 20 0 496116 5692 0 S 0.0 0.6 0:06.80 do-agent
10417 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.60 mysqld
10514 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.60 mysqld
10515 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.50 mysqld
10516 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.64 mysqld
10517 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.59 mysqld
10518 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.55 mysqld
10519 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.63 mysqld
10520 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:01.02 mysqld
10521 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.78 mysqld
10522 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:01.22 mysqld
10523 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.58 mysqld
10524 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:02.70 mysqld
10530 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:15.68 mysqld
10531 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:02.79 mysqld
10532 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:01.90 mysqld
10533 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:02.90 mysqld
10534 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:02.06 mysqld
10535 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:06.92 mysqld
10541 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.63 mysqld
10542 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:02.64 mysqld
10543 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.22 mysqld
10544 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.00 mysqld
10545 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:06.34 mysqld
10546 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.00 mysqld
10547 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.08 mysqld
10548 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.20 mysqld
10549 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.01 xpl_worker1
10550 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.01 xpl_worker0
10551 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.00 mysqld
10552 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:03.12 mysqld
10555 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:22.20 mysqld
10556 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.25 mysqld
10557 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.13 mysqld
10558 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.01 mysqld
10559 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.00 mysqld
10560 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.00 mysqld
10561 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.00 mysqld
10562 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:00.00 mysqld
10631 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:23.37 mysqld
10892 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:24.24 mysqld
10893 do-agent 20 0 1399056 424744 0 S 0.0 42.1 0:15.87 mysqld
I tried to uninstall monitoring by purging the do-agent : sudo apt-get purge do-agent and restarting the droplet, but this didn’t help. Is this expected behaviour? This is on Ubuntu 18.04.3 LTS with the smallest droplet.
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
I also seeing something like this in my droplet. I instaled Caprover directly from the marketplace and haven’t done any customization.
I’m seeing MySQL and MongoDB instances run by the do-agent user.
8617 do-agent 20 0 1092028 12680 4656 S 0.0 0.6 0:47.67 do-agent 14191 do-agent 20 0 1117384 266256 5932 S 0.0 13.0 3:01.48 mysqld 29304 do-agent 20 0 1598328 77408 4204 S 0.3 3.8 11:04.09 mongod
do-agent doesn’t spin up MySQL or MySQL services. Did you by chance install MySQL under the do-agent user?
I am seeing the same thing on my DO droplet. Not sure why.
I’m also seeing one MySQL process run by the do-agent user that’s taking up kind of a lot of memory. It looks like do-agent uses a MySQL instance for itself.