PostgreSQL terminated by signal 58
Teraoka Yoshinori
y-teraoka at so-netm3.com
Wed Nov 7 19:17:49 CST 2007
We have no multipath device and no IPMP configuration.
We use single path SCSI RAID (PERC 5/i).
# cat /proc/scsi/scsi
Attached devices:
Host: scsi0 Channel: 00 Id: 08 Lun: 00
Vendor: DP Model: BACKPLANE Rev: 1.00
Type: Enclosure ANSI SCSI revision: 05
Host: scsi0 Channel: 02 Id: 00 Lun: 00
Vendor: DELL Model: PERC 5/i Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 05
Host: scsi0 Channel: 02 Id: 01 Lun: 00
Vendor: DELL Model: PERC 5/i Rev: 1.00
Type: Direct-Access ANSI SCSI revision: 05
-- Teraoka
Anthony_Leatherwood at dell.com wrote:
>
> You running in some type of RHEL MPIO configuration from a SAN or all
> drives local?
>
>
> Ant
>
>
> -----Original Message-----
> From: linux-poweredge-bounces at dell.com
> [mailto:linux-poweredge-bounces at dell.com] On Behalf Of Kuba Ober
> Sent: Tuesday, November 06, 2007 12:58 PM
> To: linux-poweredge-Lists
> Subject: Re: PostgreSQL terminated by signal 58
>
>> I'm running PostgreSQL 8.2.3 on PowerEdge 2950, CentOS 4.4 x86_64.
>> PostgreSQL process had terminated by signal 58 three times in last 6
>> months. What is signal 58 meaning? Which process is sending this
> signal?
>> Hardware problem? Kernel driver problem?
>
> I'd say just add an audit rule for that (into /etc/audit/audit.rules,
> and restart audit daemon)
>
> Say (untested):
>
> -a always -S kill -F a1=58
>
> man auditctl for more info
>
> I don't think it has anything to do with hardware, and I haven't seen
> any driver yet killing applications with odd signals like that.
>
> Cheers, Kuba
More information about the Linux-PowerEdge
mailing list