Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCEAC-0007pY-P7 for pgsql-general@arkaria.postgresql.org; Mon, 02 Jan 2023 06:19:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pCEAB-0007hh-8d for pgsql-general@arkaria.postgresql.org; Mon, 02 Jan 2023 06:19:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCEAA-0007hW-Uc for pgsql-general@lists.postgresql.org; Mon, 02 Jan 2023 06:19:10 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pCEA8-00033g-Jb for pgsql-general@lists.postgresql.org; Mon, 02 Jan 2023 06:19:10 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 3026J2hK1354570; Mon, 2 Jan 2023 01:19:02 -0500 From: Tom Lane To: Antonis Christodoulou cc: Rob Sargent , pgsql-general@lists.postgresql.org Subject: Re: PostgreSQL 12 service failing in Ubuntu 20.04 after a few hours In-reply-to: References: <25d1ff9d-62dd-3124-d6f6-55615ed90d85@aklaver.com> <5cff562f-abf7-b191-c4f6-24409715309e@aklaver.com> <45f03cf0-b93f-f7e2-617c-6381c80ebe2f@gmail.com> Comments: In-reply-to Antonis Christodoulou message dated "Mon, 02 Jan 2023 08:08:37 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-ID: <1354568.1672640342.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Mon, 02 Jan 2023 01:19:02 -0500 Message-ID: <1354569.1672640342@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Antonis Christodoulou writes: > This is a machine in the cloud, I can=E2=80=99t disconnect it. In that case, you need to be taking nonzero security precautions. > And yes the ps looks like this precisely when I do a fresh restart. I ki= ll all postgres processes and restart: > Then this is the output of me ps: That looks fine ... but this doesn't: >>> postgres 3342383 1 0 2022 ? 00:00:00 FzXlkULu = >>> postgres 3344758 1 99 2022 ? 3-14:39:11 OElid7Dp = >>> postgres 3419125 1 18 13:57 ? 01:17:03 tracepath = Somebody is hacking into your system and commandeering it to run something resource-intensive, possibly a bitcoin miner. Whatever it is, it's trying to obscure its process name which is hardly a sign of good intentions. I'd counsel taking a hard look at your pg_hba.conf to be sure it's not allowing non-credentialed logins from anywhere. And for pete's sake don't use a guessable password. regards, tom lane