![]() ![]() ![]() We have datadog monitoring the DB server and can see at the time of issue an error but not pointing to what it could be.Ĭan see 1 millisecond after: Jul 1 00:36:04 test1 postgres: user=,db=,app=client= PANIC: could not write to file "pg_xlog/xlogtemp.219259": No space left on device I am trying to find the cause but there is nothing in the postgres log file that points to the culprit. Postgres crashed and then recovered, on observing the space where pg_xlog is stored can see the drive fill up, usually 80GB drive with about 10% usage, it happens around the same time every night. Jul 1 00:36:04 test1 postgres: user=,db=,app=client= PANIC: could not write to file "pg_xlog/xlogtemp.219259": No space left on device Jul 1 00:36:05 test1 postgres: user=postgres,db=product,app=psqlclient= HINT: In a moment you should be able to reconnect to the database and repeat your command. Jul 1 00:36:05 test1 postgres: user=postgres,db=product,app=psqlclient= DETAIL: The postmaster has commanded this server process to roll back the current transaction and exit, because another server process exited abnormally and possibly corrupted shared memory. Jul 1 00:36:05 test1 postgres: user=postgres,db=product,app=psqlclient= WARNING: terminating connection because of crash of another server process Jul 1 00:36:05 test1 postgres: user=,db=,app=client= LOG: terminating any other active server processes Jul 1 00:36:05 test1 postgres: user=,db=,app=client= LOG: checkpointer process (PID 219259) was terminated by signal 6: Aborted ![]() We received an outage on our postgres environment relating to the below error: Jul 1 00:36:04 test1 postgres: user=,db=,app=client= CONTEXT: writing block 199237 of relation pg_tblspc/16402/PG_9.6_201608131/7358881/41721132 ![]()
0 Comments
Leave a Reply. |