| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Markus Bertheau <twanger(at)bluetwanger(dot)de> |
| Cc: | PostgreSQL-Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: stuck spinlock. Aborting. What does this mean? |
| Date: | 2001-12-14 22:31:02 |
| Message-ID: | 5216.1008369062@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Markus Bertheau <twanger(at)bluetwanger(dot)de> writes:
> I looked and found several postgres processes with parent process init
> and *no* postmaster process.
It looks to me like your postmaster crashed because there were no free
file descriptors left in the system:
FATAL 1: ReleaseLruFile: No open files available to be closed
I believe this would lead to the subsequent errors shown in the log,
because the postmaster would delete the semaphores it owns before
exiting.
The same hypothesis probably explains the peculiar backend-startup
failures earlier in your log:
FATAL 1: File '/var/lib/pgsql/PG_VERSION' does not exist or no read permission.
Consider increasing your kernel file table size. An update to PG 7.1
also seems in order...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-12-15 16:12:33 | Re: Unable to compare _bpchar for similarity in WHERE-clause |
| Previous Message | Markus Bertheau | 2001-12-14 16:35:19 | stuck spinlock. Aborting. What does this mean? |