crash help, pgsql 7.2.1 on RH7.3

crash help, pgsql 7.2.1 on RH7.3

Post by Tim Lync » Fri, 22 Nov 2002 05:46:51



running pgsql 7.2.1 on redhat7.3 SMP. installed a hacked glibc to fix the
mktime() timezone problem for dates < 1970
(http://rpms.arvin.dk/glibc/rh73/i686/)

three times now the backend process has unexpectedly quit. what happens is
the postmaster process and the stats processes disappear and only the client
connection processes remain.

i don't see a core file. nothing interesting is mentioned in the logs except
for the usual redo post-mortem on startup, "database system was interrupted
at ...". i'm new to postgres admin, so i'm hoping folks can give some
direction as to where to begin solving this problem. it's happened about 3
times in two months.

now that 7.2.3 is out and fixes the mktime() problem i should probably
upgrade to that and revert to stock redhat glibc stuff. my concern is that i
have no idea what caused these events and i don't know what to do to ensure
that when it happens again i'll be able to determine the cause. what type of
logging and monitoring is recommended to report the health of a running
postgres?

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

http://archives.postgresql.org

 
 
 

1. crash help, pgsql 7.2.1 on RH7.3

Really!?  That would seem to indicate a postmaster crash.  (The stats
processes are designed to quit automatically when the parent postmaster
exits, so it's no surprise they'd exit too.)  This is highly unusual,
and worth looking into more closely.

Check that you are starting the postmaster with "ulimit -c unlimited";
this is not the default on most Linuxen, so you may have to add that to
the start script.  Also note that the postmaster never does a chdir,
so if it drops core it will be in the same directory the start script
was running in.

Probably.  But I do not think the postmaster ever calls mktime(), so the
odds are that your glibc hack is unrelated.

                        regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command

2. Single Quotes converted to 2 single quotes

3. Help: Interrupt key is not working in 4gl RDS 7.31.UC1 on Linux RH7.2

4. XML Technology Preview for SQL Server question

5. RH7.1 setup problem - HELP!

6. onlog fails on tape...

7. Apache with PHP and PGSQL crashing ...

8. How Do I Determine SQL Service Pack

9. pgsql 7.2.3 crash

10. Disabling triggers (was Re: pgsql 7.2.3 crash)

11. backend process crash - PL/pgSQL functions - parsing problem?

12. pgsql 7.2.3 crash

13. Disabling triggers (was Re: pgsql 7.2.3 crash)