473,856 Members | 2,162 Online
Bytes | Software Development & Data Engineering Community
+ Post

Home Posts Topics Members FAQ

no space left on device

I'm running Postgres 7.1.3, and just started having a problem where my
dynamic site is going down (read-only DB, with no writes happening to the
DB) regularly (every other day). I have no idea whay this is happening,
and my search of the FAQ's and mail list don't bring up anything. i've
attached the error from the log file, at the end of this message.

Here's an output of the disk usage from within the DB dir

[postgres - DB]$ du -k .
1716 ./base/1
1716 ./base/16555
5192 ./base/56048
8628 ./base
116 ./global
32812 ./pg_xlog
11380 ./pg_clog
53192 .

Note that the pg_xlog dir is huge! Here's its contents:

[postgres - DB/pg_xlog]$ ls -al
total 32816
drwx------ 2 postgres admin 4096 Mar 29 2003 .
drwx------ 6 postgres admin 4096 Jan 9 15:04 ..
-rwx------ 1 postgres admin 16777216 Jan 9 15:09 000000000000000 1
-rwx------ 1 postgres admin 16777216 Mar 29 2003 000000000000000 2

What are these files, and what can I do to resolve this issue?

Thx,

Zeb
--
DEBUG: statistics collector process (pid 2523) exited with exit code 1
PGSTAT: Error closing temp stats file
PGSTAT: /usr/local/G101/App/DB/./global/pgstat.tmp.7823 : No space left on
device
PGSTAT: AbDEBUG: statistics collector process (pid 2979) exited with exit
code
1
FATAL 2: write of clog file 43, offset 188416 failed: No space left on
device
DEBUG: server process (pid 3741) exited with exit code 2
DEBUG: terminating any other active server processes
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
DEBUG: all server processes terminated; reinitializing shared memory and
semaph
ores
DEBUG: database system was interrupted at 2004-01-09 05:22:52 EST
DEBUG: checkpoint record is at 0/138CFD4
DEBUG: redo record is at 0/138CFD4; undo record is at 0/0; shutdown FALSE
DEBUG: next transaction id: 45811837; next oid: 65205
DEBUG: database system was not properly shut down; automatic recovery in
progre
ss
DEBUG: redo starts at 0/138D014
FATAL 2: write of clog file 43, offset 188416 failed: No space left on
device
DEBUG: startup process (pid 3785) exited with exit code 2
DEBUG: aborting startup due to startup process failure

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Nov 12 '05 #1
27 20072

Note that the pg_xlog dir is huge! Here's its contents:

[postgres - DB/pg_xlog]$ ls -al
total 32816
drwx------ 2 postgres admin 4096 Mar 29 2003 .
drwx------ 6 postgres admin 4096 Jan 9 15:04 ..
-rwx------ 1 postgres admin 16777216 Jan 9 15:09 000000000000000 1
-rwx------ 1 postgres admin 16777216 Mar 29 2003 000000000000000 2

What are these files, and what can I do to resolve this issue?

The are check_point files. You need them. Have you ran a vacuum recently?

Sincerely,

Joshua D. Drake
Thx,

Zeb
--
DEBUG: statistics collector process (pid 2523) exited with exit code 1
PGSTAT: Error closing temp stats file
PGSTAT: /usr/local/G101/App/DB/./global/pgstat.tmp.7823 : No space left on
device
PGSTAT: AbDEBUG: statistics collector process (pid 2979) exited with exit
code
1
FATAL 2: write of clog file 43, offset 188416 failed: No space left on
device
DEBUG: server process (pid 3741) exited with exit code 2
DEBUG: terminating any other active server processes
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
NOTICE: Message from PostgreSQL backend:
The Postmaster has informed me that some other backend
died abnormally and possibly corrupted shared memory.
I have rolled back the current transaction and am
going to terminate your database system connection and exit.
Please reconnect to the database system and repeat your query.
DEBUG: all server processes terminated; reinitializing shared memory and
semaph
ores
DEBUG: database system was interrupted at 2004-01-09 05:22:52 EST
DEBUG: checkpoint record is at 0/138CFD4
DEBUG: redo record is at 0/138CFD4; undo record is at 0/0; shutdown FALSE
DEBUG: next transaction id: 45811837; next oid: 65205
DEBUG: database system was not properly shut down; automatic recovery in
progre
ss
DEBUG: redo starts at 0/138D014
FATAL 2: write of clog file 43, offset 188416 failed: No space left on
device
DEBUG: startup process (pid 3785) exited with exit code 2
DEBUG: aborting startup due to startup process failure

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandpromp t.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postg resql.org

Nov 12 '05 #2
On Friday 09 January 2004 20:31, Aurangzeb M. Agha wrote:
I'm running Postgres 7.1.3, and just started having a problem where my
dynamic site is going down (read-only DB, with no writes happening to the
DB) regularly (every other day). I have no idea whay this is happening,
and my search of the FAQ's and mail list don't bring up anything. i've
attached the error from the log file, at the end of this message.

Here's an output of the disk usage from within the DB dir

[postgres - DB]$ du -k .
1716 ./base/1
1716 ./base/16555
5192 ./base/56048
8628 ./base
116 ./global
32812 ./pg_xlog
11380 ./pg_clog
53192 .
OK, and what does "df -m" show? That will display disk sizes and free space
remaining. Your error is that you have run out of disk space.
Note that the pg_xlog dir is huge! Here's its contents:
Well - it's 32MB (2 x 16MB as you show below).
-rwx------ 1 postgres admin 16777216 Jan 9 15:09 000000000000000 1
-rwx------ 1 postgres admin 16777216 Mar 29 2003 000000000000000 2

What are these files, and what can I do to resolve this issue?


They're transaction logs (see the section on WAL). You can probably reduce
them from their default size of 16MB, I'm guessing by changing some constant
in the source and re-compiling.

--
Richard Huxton
Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to ma*******@postg resql.org

Nov 12 '05 #3
I've not run a vacuum in quite some time, and that's because I've only
been doing reads from this DB. I was under the impression that I should
run vacuum when tables are heavily modified:

http://www.postgresql.org/docs/aw_pg...k/node110.html

I guess I must have been mistaken?

I'm looking through the docs now, but am having trouble finding this: how
can I vacuum the entire DB at once?

Thx,

Zeb

On Fri, 9 Jan 2004, Joshua D. Drake wrote:

:
:>
:>Note that the pg_xlog dir is huge! Here's its contents:
:>
:>[postgres - DB/pg_xlog]$ ls -al
:>total 32816
:>drwx------ 2 postgres admin 4096 Mar 29 2003 .
:>drwx------ 6 postgres admin 4096 Jan 9 15:04 ..
:>-rwx------ 1 postgres admin 16777216 Jan 9 15:09 000000000000000 1
:>-rwx------ 1 postgres admin 16777216 Mar 29 2003 000000000000000 2
:>
:>What are these files, and what can I do to resolve this issue?
:>
:>
:The are check_point files. You need them. Have you ran a vacuum recently?
:
:Sincerely,
:
:Joshua D. Drake
:
:
:
:>Thx,
:>
:>Zeb
:>
:>
:>--
:>DEBUG: statistics collector process (pid 2523) exited with exit code 1
:>PGSTAT: Error closing temp stats file
:>PGSTAT: /usr/local/G101/App/DB/./global/pgstat.tmp.7823 : No space left on
:>device
:>PGSTAT: AbDEBUG: statistics collector process (pid 2979) exited with exit
:>code
:>1
:>FATAL 2: write of clog file 43, offset 188416 failed: No space left on
:>device
:>DEBUG: server process (pid 3741) exited with exit code 2
:>DEBUG: terminating any other active server processes
:>NOTICE: Message from PostgreSQL backend:
:> The Postmaster has informed me that some other backend
:> died abnormally and possibly corrupted shared memory.
:> I have rolled back the current transaction and am
:> going to terminate your database system connection and exit.
:> Please reconnect to the database system and repeat your query.
:>NOTICE: Message from PostgreSQL backend:
:> The Postmaster has informed me that some other backend
:> died abnormally and possibly corrupted shared memory.
:> I have rolled back the current transaction and am
:> going to terminate your database system connection and exit.
:> Please reconnect to the database system and repeat your query.
:>NOTICE: Message from PostgreSQL backend:
:> The Postmaster has informed me that some other backend
:> died abnormally and possibly corrupted shared memory.
:> I have rolled back the current transaction and am
:> going to terminate your database system connection and exit.
:> Please reconnect to the database system and repeat your query.
:>DEBUG: all server processes terminated; reinitializing shared memory and
:>semaph
:>ores
:>DEBUG: database system was interrupted at 2004-01-09 05:22:52 EST
:>DEBUG: checkpoint record is at 0/138CFD4
:>DEBUG: redo record is at 0/138CFD4; undo record is at 0/0; shutdown FALSE
:>DEBUG: next transaction id: 45811837; next oid: 65205
:>DEBUG: database system was not properly shut down; automatic recovery in
:>progre
:>ss
:>DEBUG: redo starts at 0/138D014
:>FATAL 2: write of clog file 43, offset 188416 failed: No space left on
:>device
:>DEBUG: startup process (pid 3785) exited with exit code 2
:>DEBUG: aborting startup due to startup process failure
:>
:>---------------------------(end of broadcast)---------------------------
:>TIP 6: Have you searched our list archives?
:>
:> http://archives.postgresql.org
:>
:>
:
:
:

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Nov 12 '05 #4
Aurangzeb M. Agha wrote:
I've not run a vacuum in quite some time, and that's because I've only
been doing reads from this DB. I was under the impression that I should
run vacuum when tables are heavily modified:


That would be accurate. Did you recently add a second database?

Sincerely,

Joshua D. Drake

http://www.postgresql.org/docs/aw_pg...k/node110.html

I guess I must have been mistaken?

I'm looking through the docs now, but am having trouble finding this: how
can I vacuum the entire DB at once?

Thx,

Zeb

On Fri, 9 Jan 2004, Joshua D. Drake wrote:

:
:>
:>Note that the pg_xlog dir is huge! Here's its contents:
:>
:>[postgres - DB/pg_xlog]$ ls -al
:>total 32816
:>drwx------ 2 postgres admin 4096 Mar 29 2003 .
:>drwx------ 6 postgres admin 4096 Jan 9 15:04 ..
:>-rwx------ 1 postgres admin 16777216 Jan 9 15:09 000000000000000 1
:>-rwx------ 1 postgres admin 16777216 Mar 29 2003 000000000000000 2
:>
:>What are these files, and what can I do to resolve this issue?
:>
:>
:The are check_point files. You need them. Have you ran a vacuum recently?
:
:Sincerely,
:
:Joshua D. Drake
:
:
:
:>Thx,
:>
:>Zeb
:>
:>
:>--
:>DEBUG: statistics collector process (pid 2523) exited with exit code 1
:>PGSTAT: Error closing temp stats file
:>PGSTAT: /usr/local/G101/App/DB/./global/pgstat.tmp.7823 : No space left on
:>device
:>PGSTAT: AbDEBUG: statistics collector process (pid 2979) exited with exit
:>code
:>1
:>FATAL 2: write of clog file 43, offset 188416 failed: No space left on
:>device
:>DEBUG: server process (pid 3741) exited with exit code 2
:>DEBUG: terminating any other active server processes
:>NOTICE: Message from PostgreSQL backend:
:> The Postmaster has informed me that some other backend
:> died abnormally and possibly corrupted shared memory.
:> I have rolled back the current transaction and am
:> going to terminate your database system connection and exit.
:> Please reconnect to the database system and repeat your query.
:>NOTICE: Message from PostgreSQL backend:
:> The Postmaster has informed me that some other backend
:> died abnormally and possibly corrupted shared memory.
:> I have rolled back the current transaction and am
:> going to terminate your database system connection and exit.
:> Please reconnect to the database system and repeat your query.
:>NOTICE: Message from PostgreSQL backend:
:> The Postmaster has informed me that some other backend
:> died abnormally and possibly corrupted shared memory.
:> I have rolled back the current transaction and am
:> going to terminate your database system connection and exit.
:> Please reconnect to the database system and repeat your query.
:>DEBUG: all server processes terminated; reinitializing shared memory and
:>semaph
:>ores
:>DEBUG: database system was interrupted at 2004-01-09 05:22:52 EST
:>DEBUG: checkpoint record is at 0/138CFD4
:>DEBUG: redo record is at 0/138CFD4; undo record is at 0/0; shutdown FALSE
:>DEBUG: next transaction id: 45811837; next oid: 65205
:>DEBUG: database system was not properly shut down; automatic recovery in
:>progre
:>ss
:>DEBUG: redo starts at 0/138D014
:>FATAL 2: write of clog file 43, offset 188416 failed: No space left on
:>device
:>DEBUG: startup process (pid 3785) exited with exit code 2
:>DEBUG: aborting startup due to startup process failure
:>
:>---------------------------(end of broadcast)---------------------------
:>TIP 6: Have you searched our list archives?
:>
:> http://archives.postgresql.org
:>
:>
:
:
:

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandpromp t.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

Nov 12 '05 #5
Here's the output of "df -m":

[postgres - DB]$ df -m .
Filesystem 1M-blocks Used Available Use% Mounted on
- 63328 55308 4803 93% /

Thx for the info.
Rgs,

Aurangzeb
On Fri, 9 Jan 2004, Richard Huxton wrote:

:On Friday 09 January 2004 20:31, Aurangzeb M. Agha wrote:
:> I'm running Postgres 7.1.3, and just started having a problem where my
:> dynamic site is going down (read-only DB, with no writes happening to the
:> DB) regularly (every other day). I have no idea whay this is happening,
:> and my search of the FAQ's and mail list don't bring up anything. i've
:> attached the error from the log file, at the end of this message.
:>
:> Here's an output of the disk usage from within the DB dir
:>
:> [postgres - DB]$ du -k .
:> 1716 ./base/1
:> 1716 ./base/16555
:> 5192 ./base/56048
:> 8628 ./base
:> 116 ./global
:> 32812 ./pg_xlog
:> 11380 ./pg_clog
:> 53192 .
:
:OK, and what does "df -m" show? That will display disk sizes and free space
:remaining. Your error is that you have run out of disk space.
:
:> Note that the pg_xlog dir is huge! Here's its contents:
:
:Well - it's 32MB (2 x 16MB as you show below).
:
:> -rwx------ 1 postgres admin 16777216 Jan 9 15:09 000000000000000 1
:> -rwx------ 1 postgres admin 16777216 Mar 29 2003 000000000000000 2
:>
:> What are these files, and what can I do to resolve this issue?
:
:They're transaction logs (see the section on WAL). You can probably reduce
:them from their default size of 16MB, I'm guessing by changing some constant
:in the source and re-compiling.
:
:

--
Aurangzeb M. Agha | Email : am*@mltp.com
| Home : +1 413 586.4863
| Pager : +1 413 785.7568
| : 41********@myai rmail.com
73 Bridge St. #15 | Mobile: <coming soon>
Northampton, MA 01060 | e-Fax : +1 978 246.0770
USA | PGP id: <coming soon>
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Nov 12 '05 #6
No, I've not added any new DB's. In fact, what's puzzling is that this DB
has been running without issue (except for one server restart) for the
last nine months. Now, all of a sudden, with no DB changes, additions,
etc... I'm getting this problem.

Do you suggest that I still run a vacuumdb?

Rgs,

Zeb

On Fri, 9 Jan 2004, Joshua D. Drake wrote:

:Aurangzeb M. Agha wrote:
:
:>I've not run a vacuum in quite some time, and that's because I've only
:>been doing reads from this DB. I was under the impression that I should
:>run vacuum when tables are heavily modified:
:>
:>
:
:That would be accurate. Did you recently add a second database?
:
:Sincerely,
:
:Joshua D. Drake
:
:
:>http://www.postgresql.org/docs/aw_pg...k/node110.html
:>
:>I guess I must have been mistaken?
:>
:>I'm looking through the docs now, but am having trouble finding this: how
:>can I vacuum the entire DB at once?
:>
:>Thx,
:>
:>Zeb
:>
:>On Fri, 9 Jan 2004, Joshua D. Drake wrote:
:>
:>:
:>:>
:>:>Note that the pg_xlog dir is huge! Here's its contents:
:>:>
:>:>[postgres - DB/pg_xlog]$ ls -al
:>:>total 32816
:>:>drwx------ 2 postgres admin 4096 Mar 29 2003 .
:>:>drwx------ 6 postgres admin 4096 Jan 9 15:04 ..
:>:>-rwx------ 1 postgres admin 16777216 Jan 9 15:09 000000000000000 1
:>:>-rwx------ 1 postgres admin 16777216 Mar 29 2003 000000000000000 2
:>:>
:>:>What are these files, and what can I do to resolve this issue?
:>:>
:>:>
:>:The are check_point files. You need them. Have you ran a vacuum recently?
:>:
:>:Sincerely,
:>:
:>:Joshua D. Drake
:>:
:>:
:>:
:>:>Thx,
:>:>
:>:>Zeb
:>:>
:>:>
:>:>--
:>:>DEBUG: statistics collector process (pid 2523) exited with exit code 1
:>:>PGSTAT: Error closing temp stats file
:>:>PGSTAT: /usr/local/G101/App/DB/./global/pgstat.tmp.7823 : No space left on
:>:>device
:>:>PGSTAT: AbDEBUG: statistics collector process (pid 2979) exited with exit
:>:>code
:>:>1
:>:>FATAL 2: write of clog file 43, offset 188416 failed: No space left on
:>:>device
:>:>DEBUG: server process (pid 3741) exited with exit code 2
:>:>DEBUG: terminating any other active server processes
:>:>NOTICE: Message from PostgreSQL backend:
:>:> The Postmaster has informed me that some other backend
:>:> died abnormally and possibly corrupted shared memory.
:>:> I have rolled back the current transaction and am
:>:> going to terminate your database system connection and exit.
:>:> Please reconnect to the database system and repeat your query.
:>:>NOTICE: Message from PostgreSQL backend:
:>:> The Postmaster has informed me that some other backend
:>:> died abnormally and possibly corrupted shared memory.
:>:> I have rolled back the current transaction and am
:>:> going to terminate your database system connection and exit.
:>:> Please reconnect to the database system and repeat your query.
:>:>NOTICE: Message from PostgreSQL backend:
:>:> The Postmaster has informed me that some other backend
:>:> died abnormally and possibly corrupted shared memory.
:>:> I have rolled back the current transaction and am
:>:> going to terminate your database system connection and exit.
:>:> Please reconnect to the database system and repeat your query.
:>:>DEBUG: all server processes terminated; reinitializing shared memory and
:>:>semaph
:>:>ores
:>:>DEBUG: database system was interrupted at 2004-01-09 05:22:52 EST
:>:>DEBUG: checkpoint record is at 0/138CFD4
:>:>DEBUG: redo record is at 0/138CFD4; undo record is at 0/0; shutdown FALSE
:>:>DEBUG: next transaction id: 45811837; next oid: 65205
:>:>DEBUG: database system was not properly shut down; automatic recovery in
:>:>progre
:>:>ss
:>:>DEBUG: redo starts at 0/138D014
:>:>FATAL 2: write of clog file 43, offset 188416 failed: No space left on
:>:>device
:>:>DEBUG: startup process (pid 3785) exited with exit code 2
:>:>DEBUG: aborting startup due to startup process failure
:>:>
:>:>---------------------------(end of broadcast)---------------------------
:>:>TIP 6: Have you searched our list archives?
:>:>
:>:> http://archives.postgresql.org
:>:>
:>:>
:>:
:>:
:>:
:>
:>
:
:
:

--
Aurangzeb M. Agha | Email : am*@mltp.com
| Home : +1 413 586.4863
| Pager : +1 413 785.7568
| : 41********@myai rmail.com
73 Bridge St. #15 | Mobile: <coming soon>
Northampton, MA 01060 | e-Fax : +1 978 246.0770
USA | PGP id: <coming soon>
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nov 12 '05 #7
Hello,

Wait... from the df you provided you have space left on the device:

postgres - DB]$ df -m .
Filesystem 1M-blocks Used Available Use% Mounted on
- 63328 55308 4803 93% /

Perhaps you are out of inodes?

Sincerely,

Josuha D. Drake


Aurangzeb M. Agha wrote:
No, I've not added any new DB's. In fact, what's puzzling is that this DB
has been running without issue (except for one server restart) for the
last nine months. Now, all of a sudden, with no DB changes, additions,
etc... I'm getting this problem.

Do you suggest that I still run a vacuumdb?

Rgs,

Zeb

On Fri, 9 Jan 2004, Joshua D. Drake wrote:

:Aurangzeb M. Agha wrote:
:
:>I've not run a vacuum in quite some time, and that's because I've only
:>been doing reads from this DB. I was under the impression that I should
:>run vacuum when tables are heavily modified:
:>
:>
:
:That would be accurate. Did you recently add a second database?
:
:Sincerely,
:
:Joshua D. Drake
:
:
:>http://www.postgresql.org/docs/aw_pg...k/node110.html
:>
:>I guess I must have been mistaken?
:>
:>I'm looking through the docs now, but am having trouble finding this: how
:>can I vacuum the entire DB at once?
:>
:>Thx,
:>
:>Zeb
:>
:>On Fri, 9 Jan 2004, Joshua D. Drake wrote:
:>
:>:
:>:>
:>:>Note that the pg_xlog dir is huge! Here's its contents:
:>:>
:>:>[postgres - DB/pg_xlog]$ ls -al
:>:>total 32816
:>:>drwx------ 2 postgres admin 4096 Mar 29 2003 .
:>:>drwx------ 6 postgres admin 4096 Jan 9 15:04 ..
:>:>-rwx------ 1 postgres admin 16777216 Jan 9 15:09 000000000000000 1
:>:>-rwx------ 1 postgres admin 16777216 Mar 29 2003 000000000000000 2
:>:>
:>:>What are these files, and what can I do to resolve this issue?
:>:>
:>:>
:>:The are check_point files. You need them. Have you ran a vacuum recently?
:>:
:>:Sincerely ,
:>:
:>:Joshua D. Drake
:>:
:>:
:>:
:>:>Thx,
:>:>
:>:>Zeb
:>:>
:>:>
:>:>--
:>:>DEBUG: statistics collector process (pid 2523) exited with exit code 1
:>:>PGSTAT: Error closing temp stats file
:>:>PGSTAT: /usr/local/G101/App/DB/./global/pgstat.tmp.7823 : No space left on
:>:>device
:>:>PGSTAT: AbDEBUG: statistics collector process (pid 2979) exited with exit
:>:>code
:>:>1
:>:>FATAL 2: write of clog file 43, offset 188416 failed: No space left on
:>:>device
:>:>DEBUG: server process (pid 3741) exited with exit code 2
:>:>DEBUG: terminating any other active server processes
:>:>NOTICE: Message from PostgreSQL backend:
:>:> The Postmaster has informed me that some other backend
:>:> died abnormally and possibly corrupted shared memory.
:>:> I have rolled back the current transaction and am
:>:> going to terminate your database system connection and exit.
:>:> Please reconnect to the database system and repeat your query.
:>:>NOTICE: Message from PostgreSQL backend:
:>:> The Postmaster has informed me that some other backend
:>:> died abnormally and possibly corrupted shared memory.
:>:> I have rolled back the current transaction and am
:>:> going to terminate your database system connection and exit.
:>:> Please reconnect to the database system and repeat your query.
:>:>NOTICE: Message from PostgreSQL backend:
:>:> The Postmaster has informed me that some other backend
:>:> died abnormally and possibly corrupted shared memory.
:>:> I have rolled back the current transaction and am
:>:> going to terminate your database system connection and exit.
:>:> Please reconnect to the database system and repeat your query.
:>:>DEBUG: all server processes terminated; reinitializing shared memory and
:>:>semaph
:>:>ores
:>:>DEBUG: database system was interrupted at 2004-01-09 05:22:52 EST
:>:>DEBUG: checkpoint record is at 0/138CFD4
:>:>DEBUG: redo record is at 0/138CFD4; undo record is at 0/0; shutdown FALSE
:>:>DEBUG: next transaction id: 45811837; next oid: 65205
:>:>DEBUG: database system was not properly shut down; automatic recovery in
:>:>progre
:>:>ss
:>:>DEBUG: redo starts at 0/138D014
:>:>FATAL 2: write of clog file 43, offset 188416 failed: No space left on
:>:>device
:>:>DEBUG: startup process (pid 3785) exited with exit code 2
:>:>DEBUG: aborting startup due to startup process failure
:>:>
:>:>---------------------------(end of broadcast)---------------------------
:>:>TIP 6: Have you searched our list archives?
:>:>
:>:> http://archives.postgresql.org
:>:>
:>:>
:>:
:>:
:>:
:>
:>
:
:
:

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandpromp t.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Nov 12 '05 #8
On Fri, 9 Jan 2004, Aurangzeb M. Agha wrote:
I'm running Postgres 7.1.3, and just started having a problem where my
dynamic site is going down (read-only DB, with no writes happening to the
DB) regularly (every other day). I have no idea whay this is happening,
and my search of the FAQ's and mail list don't bring up anything. i've
attached the error from the log file, at the end of this message.

Here's an output of the disk usage from within the DB dir

[postgres - DB]$ du -k .
1716 ./base/1
1716 ./base/16555
5192 ./base/56048
8628 ./base
116 ./global
32812 ./pg_xlog
11380 ./pg_clog
53192 .

Note that the pg_xlog dir is huge! Here's its contents:


That's normal. 32 meg isn't really that big. How big of a partition do
you have this database on? Your best bet is to put it on a bigger
partition. the pg_xlog directory is gonna be at least 16 megs for most
installations.

Do you have any transactions sitting at idle keeping postgresql from
recycling the xlogs?

Normally when you run out of space it's a lack of vacuuming, but here it
just sounds like either the partition is too small or the postgres user is
living under a quota on that partition.
---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

Nov 12 '05 #9
:That's normal. 32 meg isn't really that big. How big of a partition do
:you have this database on? Your best bet is to put it on a bigger
:partition. the pg_xlog directory is gonna be at least 16 megs for most
:installations.
:
:Do you have any transactions sitting at idle keeping postgresql from
:recycling the xlogs?
:
:Normally when you run out of space it's a lack of vacuuming, but here it
:just sounds like either the partition is too small or the postgres user is
:living under a quota on that partition.

Scott -- I'm at 93% disk usage:

[postgres - DB]$ df -m .
Filesystem 1M-blocks Used Available Use% Mounted on
- 63328 55308 4803 93% /

I don't know about transactions sitting idle--like I mentioned this DB is
read-only, and there's no writes taking place. Would I still need to
worry about transactions? How can I check to see if there are any?

Re vacuuming, I haven't run vacuum for the same reason as above. This is
only a read-only DB, and I didn't think a vacuum was necessary if there's
no writes happening to the DB.

My concern is why this problem is happening now (on a read-only DB). The
DB has had nothing written to it, no new DB's have been created, and the
disk usage has stayed constant. I'm stumped as to why this problem has
started all of a sudden.

Rgs,

Zeb

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Nov 12 '05 #10

This thread has been closed and replies have been disabled. Please start a new discussion.

Similar topics

5
7593
by: Yasaswi Pulavarti | last post by:
does a command like, db2 drop table tabschema.tabname when run from the Aix prompt reclaim the disk space? Are there any other options? How can we make sure the disk space is reclaimed? Thanks, Yasaswi
9
1423
by: James Harris | last post by:
I'm wanting to write in C some code in which it is necessary to address a device as I/O space rather than as part of memory. I would like the code to be as standard - and hence as portable - as possible. It's intended to be later ported to other hardware. Options? 1) Set up some inline assembler in a header file. I believe I'd need to use the asm keyword but that this isn't ansi C. Is that correct? 2) Write a separate routine in...
1
2169
by: sir_alex | last post by:
Is there any function to see how much space is left on a device (such as a usb key)? I'm trying to fill in an mp3 reader in a little script, and this information could be very useful! Thanks!
28
1924
by: Alan Silver | last post by:
Hello, Here I am again with another "why does IE do that" question!! Please have a look at http://www.kidsinaction.org.uk/fd/homepage.html and see if you can work out why IE adds a one pixel white space on the left and right side of the links with the light-green backgrounds. It doesn't do it on the header links, which have darker green backgrounds. FF and Opera don't add the pixel at all, which is what I would expect as
8
15019
by: maroger | last post by:
I'm sure this is a common issue, but I haven't come across anything that works for me thusfar. I am trying to fix my header, which works fine in firefox but has extra space in IE. Here are example html and css files that illustrate my problem: http://torch.cs.dal.ca/~mroger/css/ietest.html http://torch.cs.dal.ca/~mroger/css/styles.css I would like to get both browsers to display the page as firefox does. That is, with no space...
4
2347
by: bill_nirl | last post by:
Hi all, can anyone help. i have a spreasheet (set up by a looney) they have in the surname field, the surname then forename. What sort of code would i need to use to sort this out. It looks like this: |Smith Bill |14 Any Street| |Doe John |19 High Stree| and so on (there are 7891 of them). Would make life a lot easier to
12
7231
by: JA | last post by:
Is there a way to remove all the white space in the fields? I have been using Find-and-replace - looking for 2 or 3 or 4 or 10 spaces and replacing them with none. I don't want to replace single spaces, those are the spaces between the words. But most of what is in the fields has been cut-n-pasted from online forms, and the results can be VERY spread out. I could probably save 80% of the space if I could get rid of the extra white space....
5
6238
by: mostro713 | last post by:
Hello all, I would like to write a script in Python to email me when disk space gets below a certain value. My first question (I'm sure of many) is how do get this output into a dictionary or list to index the values? import os os.system("df -x cifs -x iso9660 | grep -E ^/dev | awk '{ print
1
2291
by: ismailc | last post by:
Hi, I've changed an existing xslt file, i found this css file but now the css object is not aligned with the other objects - i checked the other objects they are calling templates. I have added the code in <td align-'left'> but the objects are out by a space to the css object i added: How do i add a space/move the select box up by a space!, not the text of the selectbox but the entire object The CSS File
0
9903
marktang
by: marktang | last post by:
ONU (Optical Network Unit) is one of the key components for providing high-speed Internet services. Its primary function is to act as an endpoint device located at the user's premises. However, people are often confused as to whether an ONU can Work As a Router. In this blog post, we’ll explore What is ONU, What Is Router, ONU & Router’s main usage, and What is the difference between ONU and Router. Let’s take a closer look ! Part I. Meaning of...
0
10692
jinu1996
by: jinu1996 | last post by:
In today's digital age, having a compelling online presence is paramount for businesses aiming to thrive in a competitive landscape. At the heart of this digital strategy lies an intricately woven tapestry of website design and digital marketing. It's not merely about having a website; it's about crafting an immersive digital experience that captivates audiences and drives business growth. The Art of Business Website Design Your website is...
1
10769
by: Hystou | last post by:
Overview: Windows 11 and 10 have less user interface control over operating system update behaviour than previous versions of Windows. In Windows 11 and 10, there is no way to turn off the Windows Update option using the Control Panel or Settings app; it automatically checks for updates and installs any it finds, whether you like it or not. For most users, this new feature is actually very convenient. If you want to control the update process,...
0
10375
tracyyun
by: tracyyun | last post by:
Dear forum friends, With the development of smart home technology, a variety of wireless communication protocols have appeared on the market, such as Zigbee, Z-Wave, Wi-Fi, Bluetooth, etc. Each protocol has its own unique characteristics and advantages, but as a user who is planning to build a smart home system, I am a bit confused by the choice of these technologies. I'm particularly interested in Zigbee because I've heard it does some...
0
9526
agi2029
by: agi2029 | last post by:
Let's talk about the concept of autonomous AI software engineers and no-code agents. These AIs are designed to manage the entire lifecycle of a software development project—planning, coding, testing, and deployment—without human intervention. Imagine an AI that can take a project description, break it down, write the code, debug it, and then launch it, all on its own.... Now, this would greatly impact the work of software developers. The idea...
1
7927
isladogs
by: isladogs | last post by:
The next Access Europe User Group meeting will be on Wednesday 1 May 2024 starting at 18:00 UK time (6PM UTC+1) and finishing by 19:30 (7.30PM). In this session, we are pleased to welcome a new presenter, Adolph Dupré who will be discussing some powerful techniques for using class modules. He will explain when you may want to use classes instead of User Defined Types (UDT). For example, to manage the data in unbound forms. Adolph will...
0
7084
by: conductexam | last post by:
I have .net C# application in which I am extracting data from word file and save it in database particularly. To store word all data as it is I am converting the whole word file firstly in HTML and then checking html paragraph one by one. At the time of converting from word file to html my equations which are in the word document file was convert into image. Globals.ThisAddIn.Application.ActiveDocument.Select();...
0
5754
by: TSSRALBI | last post by:
Hello I'm a network technician in training and I need your help. I am currently learning how to create and manage the different types of VPNs and I have a question about LAN-to-LAN VPNs. The last exercise I practiced was to create a LAN-to-LAN VPN between two Pfsense firewalls, by using IPSEC protocols. I succeeded, with both firewalls in the same network. But I'm wondering if it's possible to do the same thing, with 2 Pfsense firewalls...
2
4168
muto222
by: muto222 | last post by:
How can i add a mobile payment intergratation into php mysql website.

By using Bytes.com and it's services, you agree to our Privacy Policy and Terms of Use.

To disable or enable advertisements and analytics tracking please visit the manage ads & tracking page.