Following the replacement of puppetdb02 (stretch, old version of puppetdb) with a buster one in T243226: Upgrade puppet in deployment-prep (Puppet agent broken in Beta Cluster)
# service puppetdb status ● puppetdb.service - Puppet data warehouse server Loaded: loaded (/lib/systemd/system/puppetdb.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Wed 2020-03-18 12:15:11 UTC; 11h ago Docs: man:puppetdb(8) file:/usr/share/doc/puppetdb/index.markdown Process: 20795 ExecStart=/usr/bin/java $JAVA_ARGS -Djava.security.egd=/dev/urandom -XX:OnOutOfMemoryError=kill -9 %p -cp /usr/share/puppetdb/puppetdb.jar clojure.main -m puppetlabs.puppetdb.core service Main PID: 20795 (code=killed, signal=KILL) Mar 18 12:15:11 deployment-puppetdb03 systemd: puppetdb.service: Main process exited, code=killed, status=9/KILL Mar 18 12:15:11 deployment-puppetdb03 systemd: puppetdb.service: Failed with result 'signal'. Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
Mar 18 12:15:11 deployment-puppetdb03 kernel: [4838203.377081] [ 20795] 118 20795 1606110 219063 2199552 0 0 java Mar 18 12:15:11 deployment-puppetdb03 kernel: [4838203.377143] Out of memory: Kill process 20795 (java) score 429 or sacrifice child Mar 18 12:15:11 deployment-puppetdb03 kernel: [4838203.378570] Killed process 20795 (java) total-vm:6424440kB, anon-rss:876252kB, file-rss:0kB, shmem-rss:0kB Mar 18 12:15:11 deployment-puppetdb03 kernel: [4838203.394636] oom_reaper: reaped process 20795 (java), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
You can just log into the box, service puppetdb start, and wait a moment, and it'll come back. But this should not be necessary.
Do we really need to increase the size of this box from small? It shouldn't be holding that much data or taking up 2GB RAM. Though a JVM is involved...