Обсуждение: could not write to log file: No space left on device -> AWS RDS Aurora postgreql DB

Поиск
Список
Период
Сортировка

could not write to log file: No space left on device -> AWS RDS Aurora postgreql DB

От
dbatoCloud Solution
Дата:
Dear All,

I am facing an issue in AWS Aurora PostgreSQL DB where it shows,

Environment: - AWS RDS PostgreSQL 10.11  

##
ERROR: could not write block 1726445 of temporary file: No space left on device
##

Error#
could not write to log file: No space left on device

 

2021-01-12 01:40:03 UTC::@:[29941]:LOG:  database system is shut downPostgres Shared Memory Value: 46679678976 bytes
2021-01-12 01:40:04.250 GMT [30047] LOG:  skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf"
2021-01-12 01:40:04 UTC::@:[30047]:WARNING:  unrecognized configuration parameter "rds.adaptive_autovacuum"
2021-01-12 01:40:04 UTC::@:[30047]:WARNING:  unrecognized configuration parameter "rds.enable_plan_management"
2021-01-12 01:40:04 UTC::@:[30047]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_calls"
2021-01-12 01:40:04 UTC::@:[30047]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_mean_time_ms"
2021-01-12 01:40:04 UTC::@:[30047]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_stddev_time_ms"
2021-01-12 01:40:04 UTC::@:[30047]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_total_time_ms"
2021-01-12 01:40:04 UTC::@:[30047]:LOG:  listening on IPv4 address "0.0.0.0", port 5432
2021-01-12 01:40:04 UTC::@:[30047]:LOG:  listening on IPv6 address "::", port 5432
2021-01-12 01:40:04 UTC::@:[30047]:LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2021-01-12 01:40:04 UTC::@:[30047]:LOG:  redirecting log output to logging collector process
2021-01-12 01:40:04 UTC::@:[30047]:HINT:  Future log output will appear in directory "/rdsdbdata/log/error".
2021-01-12 02:27:07.156 GMT [1499] LOG:  skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf"
2021-01-12 02:27:07 UTC::@:[1499]:WARNING:  unrecognized configuration parameter "rds.adaptive_autovacuum"
2021-01-12 02:27:07 UTC::@:[1499]:WARNING:  unrecognized configuration parameter "rds.enable_plan_management"
2021-01-12 02:27:07 UTC::@:[1499]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_calls"
2021-01-12 02:27:07 UTC::@:[1499]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_mean_time_ms"
2021-01-12 02:27:07 UTC::@:[1499]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_stddev_time_ms"
2021-01-12 02:27:07 UTC::@:[1499]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_total_time_ms"
2021-01-12 02:27:07 UTC::@:[1499]:LOG:  database system is shut down
Postgres Shared Memory Value: 46679678976 bytes
2021-01-12 02:27:08.128 GMT [1608] LOG:  skipping missing configuration file "/rdsdbdata/db/postgresql.auto.conf"
2021-01-12 02:27:08 UTC::@:[1608]:WARNING:  unrecognized configuration parameter "rds.adaptive_autovacuum"
2021-01-12 02:27:08 UTC::@:[1608]:WARNING:  unrecognized configuration parameter "rds.enable_plan_management"
2021-01-12 02:27:08 UTC::@:[1608]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_calls"
2021-01-12 02:27:08 UTC::@:[1608]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_mean_time_ms"
2021-01-12 02:27:08 UTC::@:[1608]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_stddev_time_ms"
2021-01-12 02:27:08 UTC::@:[1608]:WARNING:  unrecognized configuration parameter "apg_plan_mgmt.pgss_min_total_time_ms"
2021-01-12 02:27:08 UTC::@:[1608]:LOG:  listening on IPv4 address "0.0.0.0", port 5432
2021-01-12 02:27:08 UTC::@:[1608]:LOG:  listening on IPv6 address "::", port 5432
2021-01-12 02:27:08 UTC::@:[1608]:LOG:  listening on Unix socket "/tmp/.s.PGSQL.5432"
2021-01-12 02:27:08 UTC::@:[1608]:LOG:  redirecting log output to logging collector process
2021-01-12 02:27:08 UTC::@:[1608]:HINT:  Future log output will appear in directory "/rdsdbdata/log/error".
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device
could not write to log file: No space left on device

could not write to log file: No space left on device

 

Thanks & Best Wishes,

Ashok

 

---------------------------------------------------------------------------------------------------------------------

Ashokkumar Mani  (OCP12c/11g/10g/9i, AWS SAA, M103)

Dubai , UAE | BLR , INDIA

M: +971 54 723 0075 | +91 90086 70302 | WApp : +91 81975 99922

W: https://dbatocloudsolution.blogspot.in/ | E: dbatocloud17@gmail.com

Re: could not write to log file: No space left on device -> AWS RDS Aurora postgreql DB

От
Michael Banck
Дата:
On Mon, Feb 01, 2021 at 06:49:21PM +0530, dbatoCloud Solution wrote:
> I am facing an issue in AWS Aurora PostgreSQL DB where it shows,

Shouldn't you rather be contacting AWS Aurora PostgreSQL support about
that?


Michael

-- 
Michael Banck
Projektleiter / Senior Berater
Tel.: +49 2166 9901-171
Fax:  +49 2166 9901-100
Email: michael.banck@credativ.de

credativ GmbH, HRB Mönchengladbach 12080
USt-ID-Nummer: DE204566209
Trompeterallee 108, 41189 Mönchengladbach
Geschäftsführung: Dr. Michael Meskes, Jörg Folz, Sascha Heuer

Unser Umgang mit personenbezogenen Daten unterliegt
folgenden Bestimmungen: https://www.credativ.de/datenschutz

Re: could not write to log file: No space left on device -> AWS RDS Aurora postgreql DB

От
naveen goswami
Дата:
Another option if you cannot change the workload,  Free Local storage (temporary files storage), is twice the size of RAM of your Aurora instance. e.g. r5.db24xlarge will provide 1500GB of free local storage. not sure if its possible, but higher instance size may help but that comes with higher cost.

On Mon, Feb 1, 2021 at 6:11 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Mon, 2021-02-01 at 19:27 +0530, dbatoCloud Solution wrote:
> Is there any way to reduce the temporary files which are having huge size .

Cancel the queries that generate them.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com



Re: could not write to log file: No space left on device -> AWS RDS Aurora postgreql DB

От
dbatoCloud Solution
Дата:
at this movement, we don't have the budget to go higher version, we are planning to use temporary_tablespace and make it default and then try to release the space from tempfiles.

 

 

Thanks & Best Wishes,

Ashok

 

---------------------------------------------------------------------------------------------------------------------

Ashokkumar Mani  (OCP12c/11g/10g/9i, AWS SAA, M103)

Dubai , UAE | BLR , INDIA

M: +971 54 723 0075 | +91 90086 70302 | WApp : +91 81975 99922

W: https://dbatocloudsolution.blogspot.in/ | E: dbatocloud17@gmail.com



On Tue, Feb 2, 2021 at 7:57 AM naveen goswami <rilogical@gmail.com> wrote:
Another option if you cannot change the workload,  Free Local storage (temporary files storage), is twice the size of RAM of your Aurora instance. e.g. r5.db24xlarge will provide 1500GB of free local storage. not sure if its possible, but higher instance size may help but that comes with higher cost.

On Mon, Feb 1, 2021 at 6:11 AM Laurenz Albe <laurenz.albe@cybertec.at> wrote:
On Mon, 2021-02-01 at 19:27 +0530, dbatoCloud Solution wrote:
> Is there any way to reduce the temporary files which are having huge size .

Cancel the queries that generate them.

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com