Enable core dumps for GT.M processes

Bug #693489 reported by Jon Tai
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenVista/GT.M Integration
Fix Released
Medium
Derek_

Bug Description

When a GT.M process segfaults, the following messages are written to syslog (the second message is not always present):

Dec 21 16:30:35 localhost GTM[20999]: %GTM-F-KILLBYSIGSINFO1, GT.M process 20999 has been killed by a signal 11 at address 0x0000000100000028 (vaddr 0x0000000100000028) -- generated from 0x00002B188E41DEDA.
Dec 21 16:30:35 localhost GTM[20999]: %GTM-F-SIGMAPERR, Signal was caused by an address not mapped to an object -- generated from 0x00002B188E41DC85.

To further debug the issue, a core dump file is needed. By default, RedHat (and I believe Ubuntu) disable core dumps. We should enable core dumps in the openvista, ovcc, and ovtied utilities by adding the following line after cd'ing to the instance's tmp directory:

ulimit -S -c unlimited > /dev/null 2>&1

On Ubuntu, we also need to set /proc/sys/kernel/core_pattern to include the pid.

Derek_ (derek-name)
Changed in openvista-gtm-integration:
assignee: nobody → Derek_ (derek-name)
status: New → Confirmed
Derek_ (derek-name)
tags: added: openvista ovcc ovtied
Derek_ (derek-name)
Changed in openvista-gtm-integration:
status: Confirmed → In Progress
status: In Progress → Fix Committed
Derek_ (derek-name)
Changed in openvista-gtm-integration:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.