Always check for bad memory when you see sig 11 first.
There are bugs that can throw a sig11, but if you see them at random
places, with random queries, it's usually bad memory.
On Tue, 17 Jun 2003, Taranjit Singh Lamba wrote:
> Hi All ,
>
> H/W Configuration - Dell 7150 Quad Itanium 1 ( 733 MHz) with 4G RAM
>
> OS - Red Hat 7.2
> - Postgresql ver 7.3.3 compiled from raw hide red hat rpms.
>
>
> Problem : We were able to install postgreSQL 7.3.3 successfully on this enviornment , but server crashes randomly and
throwsfollowing error :
> *************************************************************************************
> LOG: server process (pid 11220) was terminated by signal 11
> LOG: terminating any other active server processes
> LOG: all server processes terminated; reinitializing shared memory and semaphores
> LOG: database system was interrupted at 2003-06-17 10:29:08 PDT
> LOG: checkpoint record is at 0/83CEC8
> LOG: redo record is at 0/83CEC8; undo record is at 0/0; shutdown TRUE
> LOG: next transaction id: 480; next oid: 16976
> LOG: database system was not properly shut down; automatic recovery in progress
> LOG: ReadRecord: record with zero length at 0/83CF10
> LOG: redo is not required
> LOG: database system is ready
> FATAL: Database "template0" is not currently accepting connections
> FATAL: IDENT authentication failed for user "zippool1"
> LOG: fast shutdown request
> LOG: shutting down
> LOG: database system is shut down
> ***********************************************************************************************
>
> Any help would be highly appreciated !
>
>
> Thanks in Advance !
>
> Regards
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
>