Message-ID: <83e42564-ae78-4876-9525-d1f48843c532@frank.uvena.de>
Date: Tue, 14 Jan 2025 14:39:06 +0100
MIME-Version: 1.0
Subject: Re: Postgresql database terminates abruptly with too many open files
 error
To: pgsql-general@lists.postgresql.org
References: <0af98214-3c2a-43e5-9bbf-ddd79b85ea93@ebi.ac.uk>
 <709d5fa0-85e1-40a2-a6a4-11040f4e5b62@ebi.ac.uk>
Content-Language: en-GB
From: Frank Lanitz <frank@frank.uvena.de>
In-Reply-To: <709d5fa0-85e1-40a2-a6a4-11040f4e5b62@ebi.ac.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://www.postgresql.org/message-id/83e42564-ae78-4876-9525-d1f48843c532%40frank.uvena.de>
Precedence: bulk

Hello,


Have you checked something like lsof to see open file descriptors to see?

Cheers,
frank

Am 14.01.25 um 13:58 schrieb Sri Mrudula Attili:
> Hello Team,
> 
>   We have a postgresql VDB(virtual database- Delphix) that keeps terminating due "to too many open files".
> 
> Below are few alerts that we could see from the postgresql.log
> 
> 
> < 2025-01-14 11:37:20.724 GMT >LOG:  out of file descriptors: Too many open files in system; release and retry
> 
> < 2025-01-14 11:37:20.724 GMT >FATAL:  epoll_create1 failed: Too many open files in system
> 
> 
> The number of allowed openfiles at OS level are 65000. even then we see these all these being utilised and causing the database to terminate.
> 
> 
> Is there a way we could avoid this.
> 
> 
> Thanks,
> 
> Sri
> 
> 
>