public inbox for [email protected]
help / color / mirror / Atom feedPostgresql database terminates abruptly with too many open files error
6+ messages / 5 participants
[nested] [flat]
* Postgresql database terminates abruptly with too many open files error
@ 2025-01-14 12:58 Sri Mrudula Attili <[email protected]>
2025-01-14 13:39 ` Re: Postgresql database terminates abruptly with too many open files error Ron Johnson <[email protected]>
2025-01-14 14:19 ` Re: Postgresql database terminates abruptly with too many open files error Tom Lane <[email protected]>
0 siblings, 2 replies; 6+ messages in thread
From: Sri Mrudula Attili @ 2025-01-14 12:58 UTC (permalink / raw)
To: pgsql-general
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
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Postgresql database terminates abruptly with too many open files error
2025-01-14 12:58 Postgresql database terminates abruptly with too many open files error Sri Mrudula Attili <[email protected]>
@ 2025-01-14 13:39 ` Ron Johnson <[email protected]>
1 sibling, 0 replies; 6+ messages in thread
From: Ron Johnson @ 2025-01-14 13:39 UTC (permalink / raw)
To: pgsql-general
On Tue, Jan 14, 2025 at 7:58 AM Sri Mrudula Attili <[email protected]> wrote:
> 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.
>
We need more information.
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Postgresql database terminates abruptly with too many open files error
2025-01-14 12:58 Postgresql database terminates abruptly with too many open files error Sri Mrudula Attili <[email protected]>
@ 2025-01-14 14:19 ` Tom Lane <[email protected]>
2025-01-15 11:42 ` Re: Postgresql database terminates abruptly with too many open files error Sri Mrudula Attili <[email protected]>
1 sibling, 1 reply; 6+ messages in thread
From: Tom Lane @ 2025-01-14 14:19 UTC (permalink / raw)
To: Sri Mrudula Attili <[email protected]>; +Cc: pgsql-general
Sri Mrudula Attili <[email protected]> writes:
> We have a postgresql VDB(virtual database- Delphix) that keeps
> terminating due "to too many open files".
What do you have max_connections set to, and how many actually-live
server processes are there typically?
> The number of allowed openfiles at OS level are 65000.
I'm suspecting that you either need to increase that, decrease
max_files_per_process (which defaults to 1000), or decrease
max_connections.
regards, tom lane
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Postgresql database terminates abruptly with too many open files error
2025-01-14 12:58 Postgresql database terminates abruptly with too many open files error Sri Mrudula Attili <[email protected]>
2025-01-14 14:19 ` Re: Postgresql database terminates abruptly with too many open files error Tom Lane <[email protected]>
@ 2025-01-15 11:42 ` Sri Mrudula Attili <[email protected]>
2025-01-19 09:01 ` Re: Postgresql database terminates abruptly with too many open files error Durgamahesh Manne <[email protected]>
2025-01-19 11:06 ` Re: Postgresql database terminates abruptly with too many open files error Peter J. Holzer <[email protected]>
0 siblings, 2 replies; 6+ messages in thread
From: Sri Mrudula Attili @ 2025-01-15 11:42 UTC (permalink / raw)
To: Tom Lane <[email protected]>; +Cc: pgsql-general
Hello Tom,
The max_connections =200 and max_files_per_process =1000 as you mentioned.
So should a max_files_per_process =500 helps?
I could see from the number of connections to the databaseis not
exceeding 20. But still these 20 are causing all the damage or using up
all the openfiles quota.
Thanks,
Sri
On 14/01/2025 14:19, Tom Lane wrote:
> Sri Mrudula Attili <[email protected]> writes:
>> We have a postgresql VDB(virtual database- Delphix) that keeps
>> terminating due "to too many open files".
> What do you have max_connections set to, and how many actually-live
> server processes are there typically?
>
>> The number of allowed openfiles at OS level are 65000.
> I'm suspecting that you either need to increase that, decrease
> max_files_per_process (which defaults to 1000), or decrease
> max_connections.
>
> regards, tom lane
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Postgresql database terminates abruptly with too many open files error
2025-01-14 12:58 Postgresql database terminates abruptly with too many open files error Sri Mrudula Attili <[email protected]>
2025-01-14 14:19 ` Re: Postgresql database terminates abruptly with too many open files error Tom Lane <[email protected]>
2025-01-15 11:42 ` Re: Postgresql database terminates abruptly with too many open files error Sri Mrudula Attili <[email protected]>
@ 2025-01-19 09:01 ` Durgamahesh Manne <[email protected]>
1 sibling, 0 replies; 6+ messages in thread
From: Durgamahesh Manne @ 2025-01-19 09:01 UTC (permalink / raw)
To: Sri Mrudula Attili <[email protected]>; +Cc: Tom Lane <[email protected]>; pgsql-general
---------- Forwarded message ---------
From: Sri Mrudula Attili <[email protected]>
Date: Wed, 15 Jan, 2025, 17:12
Subject: Re: Postgresql database terminates abruptly with too many open
files error
To: Tom Lane <[email protected]>
Cc: <[email protected]>
Hello Tom,
The max_connections =200 and max_files_per_process =1000 as you mentioned.
So should a max_files_per_process =500 helps?
I could see from the number of connections to the databaseis not
exceeding 20. But still these 20 are causing all the damage or using up
all the openfiles quota.
Thanks,
Sri
On 14/01/2025 14:19, Tom Lane wrote:
> Sri Mrudula Attili <[email protected]> writes:
>> We have a postgresql VDB(virtual database- Delphix) that keeps
>> terminating due "to too many open files".
> What do you have max_connections set to, and how many actually-live
> server processes are there typically?
>
>> The number of allowed openfiles at OS level are 65000.
> I'm suspecting that you either need to increase that, decrease
> max_files_per_process (which defaults to 1000), or decrease
> max_connections.
>
> regards, tom lane
Hi Team,
What is the final conclusion for this ?
Regards,
Durga Mahesh
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Postgresql database terminates abruptly with too many open files error
2025-01-14 12:58 Postgresql database terminates abruptly with too many open files error Sri Mrudula Attili <[email protected]>
2025-01-14 14:19 ` Re: Postgresql database terminates abruptly with too many open files error Tom Lane <[email protected]>
2025-01-15 11:42 ` Re: Postgresql database terminates abruptly with too many open files error Sri Mrudula Attili <[email protected]>
@ 2025-01-19 11:06 ` Peter J. Holzer <[email protected]>
1 sibling, 0 replies; 6+ messages in thread
From: Peter J. Holzer @ 2025-01-19 11:06 UTC (permalink / raw)
To: [email protected]
On 2025-01-15 11:42:30 +0000, Sri Mrudula Attili wrote:
> The max_connections =200 and max_files_per_process =1000 as you mentioned.
>
> So should a max_files_per_process =500 helps?
>
>
> I could see from the number of connections to the databaseis not exceeding
> 20. But still these 20 are causing all the damage or using up all the
> openfiles quota.
If there are 20 processes with at most 1000 open files each, that's only
20'000 open files. So where do the other 45'536 files come from?
Use something like
lsof | awk '{print $1, $2}' | uniq -c | sort -n
to find the processes with the most open files (but be aware that lsof
reports file descriptors for each thread, so any multi-threaded programs
will be vastly inflated)
hp
--
_ | Peter J. Holzer | Story must make more sense than reality.
|_|_) | |
| | | [email protected] | -- Charles Stross, "Creative writing
__/ | http://www.hjp.at/ | challenge!"
Attachments:
[application/pgp-signature] signature.asc (833B, 2-signature.asc)
download
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2025-01-19 11:06 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-01-14 12:58 Postgresql database terminates abruptly with too many open files error Sri Mrudula Attili <[email protected]>
2025-01-14 13:39 ` Ron Johnson <[email protected]>
2025-01-14 14:19 ` Tom Lane <[email protected]>
2025-01-15 11:42 ` Sri Mrudula Attili <[email protected]>
2025-01-19 09:01 ` Durgamahesh Manne <[email protected]>
2025-01-19 11:06 ` Peter J. Holzer <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox