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 1kYWUz-0005zm-Qm for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Oct 2020 15:39:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kYWUx-0001lQ-E3 for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Oct 2020 15:39:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kYWUx-0001lG-6M for pgsql-bugs@lists.postgresql.org; Fri, 30 Oct 2020 15:39:27 +0000 Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kYWUu-0002uJ-Ei for pgsql-bugs@lists.postgresql.org; Fri, 30 Oct 2020 15:39:26 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=depesz.com; s=20170201; h=In-Reply-To:Content-Type:MIME-Version:References:Reply-To: Message-ID:Subject:Cc:To:Sender:From:Date:Content-Transfer-Encoding: Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender: Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=S8jowfkrT4dpdxGpkN14sVx0fJF6vdU6VgkrFhgJWws=; b=R3RTAjMdWwzu5WI5joazB1l4yx PhGqEw5dPKzazaeIRf0IFY6ErF285vRnQMjj+FOWW/SEmGegJQ/PiDhpmgg/R6sz2VSywkV53dJsj 1Yg3887HtfgbZTz1BuIdxNiijxrySMsm3x/pkCMwU4Knb8PqsI7nCL6oD4AtanBFwQS0=; Received: from lana.depesz.com ([88.198.49.178] helo=depesz.com) by depesz.com with esmtpa (Exim 4.92) (envelope-from ) id 1kYWUr-00047V-7Y; Fri, 30 Oct 2020 16:39:21 +0100 Date: Fri, 30 Oct 2020 16:39:21 +0100 From: hubert depesz lubaczewski Sender: depesz@depesz.com To: Magnus Hagander Cc: email2anup14@gmail.com, PostgreSQL mailing lists Subject: Re: BUG #16692: Postgres process using 100 percent CPU Message-ID: <20201030153921.GA2169@depesz.com> Reply-To: depesz@depesz.com References: <16692-84eda90a2c893b12@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Oct 30, 2020 at 03:32:13PM +0100, Magnus Hagander wrote: > On Fri, Oct 30, 2020 at 3:29 PM PG Bug reporting form > wrote: > > > > The following bug has been logged on the website: > > > > Bug reference: 16692 > > Logged by: Anup Maity > > Email address: email2anup14@gmail.com > > PostgreSQL version: 11.0 > > Operating system: UBUNTU 20.4 > > Description: > > > > From last 1 week, this process with user postgres is utilizing entire cpu > > and approx 2.5gb ram. I have tried reinstalling postgres but then too the > > issues persists. please help. No query is being running. this is in idle > > usage > > 37811 postgres 20 0 2442744 2.3g 4 S 399.7 14.8 148:23.87 > > n2cP0Mv4 > > > > That is not a PostgreSQL process. > > It looks very much like malware running on your system, that happens > to be running under the "postgres" user account. > > I'd shut the machine down immediately. And then mount the file system > through some other means (meaning mount the disk from a different > system and absolutely do *NOT* boot off this disk), figuring out where > those binaries are and try to salvage the database from there. Before shutting down it might be good to look at "ls -l /proc/37811", especially "cwd" and "exe" links. depesz