Re: Multiple Crashs on OSX Intel

That's a point !
Let's see ...
In fact I found that with 69 crashs (sic!) , I had only 8 differents
adresses.

But if it's really a currupt-data related problem, could the same base
really works without errors on another platform (PPC G5) ?

Knowing that the crashing database is a clean new install from postgres,
where I then load the base from another machine with a pg_dumpall | psql . I
always do this way cause I never had this kind a problem, but I'm a newb in
the great PG world :-)

Best regards,
Marc Simonin

All the crash look like this one. Some process terminated by signal 10.
****************
Log file

CETLOG: autovacuum: processing database "bozo"
CETLOG: autovacuum process (PID 24305) was terminated by signal 10
CETLOG: terminating any other active server processes
CETWARNING: terminating connection because of crash of another server
process
CETDETAIL: 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.
CETHINT: In a moment you should be able to reconnect to the database and
repeat your command.
CETLOG: all server processes terminated; reinitializing

***************

In fact ... I don't really know where to find this stack trace :-D
But I put here one of the Crash logs and put attached the gzipped entire
Crashlog file (if it pass through the mailing list !).

Hope it can help !

***************

Command: postmaster
Path: /opt/local/lib/pgsql8/bin/postmaster
Parent: postmaster [120]

Version: ??? (???)

PID: 18876
Thread: 0

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x9003b7bc

Thread 0 Crashed:
0 postmaster 0x002635f1 AllocSetAlloc + 1158
1 postmaster 0x0026407d MemoryContextAllocZero + 105
2 postmaster 0x0023b74b InitCatCache + 189
3 postmaster 0x00244110 InitCatalogCache + 281
4 postmaster 0x00256d65 InitPostgres + 710
5 postmaster 0x001ab757 PostgresMain + 4366
6 postmaster 0x00176ca7 BackendRun + 2173
7 postmaster 0x00176141 BackendStartup + 197
8 postmaster 0x00173a1b ServerLoop + 614
9 postmaster 0x001731be PostmasterMain + 4390
10 postmaster 0x0011c96a main + 660
11 postmaster 0x0000196a _start + 216
12 postmaster 0x00001891 start + 41

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x00263179 ecx: 0x0001dfe0 edx: 0x9003b7bc
edi: 0x002efd90 esi: 0x0000000b ebp: 0xbfffedf8 esp: 0xbfffed90
ss: 0x0000001f efl: 0x00010206 eip: 0x002635f1 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037

Binary Images Description:
0x1000 - 0x2f0fff postmaster /opt/local/lib/pgsql8/bin/postmaster
0x387000 - 0x3b9fff libssl.0.9.8.dylib
/opt/local/lib/libssl.0.9.8.dylib
0x3cc000 - 0x3ddfff libz.1.dylib /opt/local/lib/libz.1.dylib
0x505000 - 0x5f4fff libcrypto.0.9.8.dylib
/opt/local/lib/libcrypto.0.9.8.dylib
0x65d000 - 0x67afff libreadline.5.1.dylib
/opt/local/lib/libreadline.5.1.dylib
0x8fe00000 - 0x8fe49fff dyld 46.1 /usr/lib/dyld
0x90000000 - 0x9016ffff libSystem.B.dylib /usr/lib/libSystem.B.dylib
0x901bf000 - 0x901c1fff libmathCommon.A.dylib
/usr/lib/system/libmathCommon.A.dylib
0x90bcf000 - 0x90bd6fff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
0x94960000 - 0x9497dfff libresolv.9.dylib /usr/lib/libresolv.9.dylib
0x95a2e000 - 0x95a5cfff libncurses.5.4.dylib
/usr/lib/libncurses.5.4.dylib

« Tom Lane » <tgl(at)sss(dot)pgh(dot)pa(dot)us> a écrit :

> Marc Simonin <m(dot)simonin(at)allibert-trekking(dot)com> writes:
>> The CrashLog log for every crashes one of this two codes
>> Exception: EXC_BAD_ACCESS (0x0001)
>> Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x9003b7e0
>> Exception: EXC_BAD_ACCESS (0x0001)
>> Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000000
>
> Always those same addresses? If so I'd wonder about a corrupt-data
> problem. Can you get a stack trace from the core files?
>
> regards, tom lane