Ingres server crashed with SIGBUS error (and SIGSEGV)

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

ninamarkova@yahoo.ca - 23 Jul 2007 21:58 GMT

After upgrading from Ingres 2.6/0305 to Ingres 2.6/0604 SP5 for
Solaris 9 (after Jul 3 2007)
Ingres started crashing with SIGBUS and once with SIGBUS & SIGSEGV
errors on DMF.

in iicrash.log:
!(dmdcheck.c, 137) ERsend--->'YODA ::[38598 ,
000000010092cec0]: Tue Jul 3 14:32:12 2007 E_DM942B_CRASH_LOG Server
has written dmd_check() information to crash log file: iicrash.log.'
!(dmdcheck.c, 143) ERsend--->'YODA ::[38598 ,
000000010092cec0]: Tue Jul 3 14:32:12 2007 E_DMF015_EVENT_SET
Unexpected error set event wait reason.'
!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
000000010092cec0]: >>>>>Session 000000010092CEC0:11<<<<<'
!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
000000010092cec0]: DB Name: eq
(Owned by:
! )'
!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
000000010092cec0]: User: <Replicator Queue Management>
( <Replicator Queue Management> ) '
!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
000000010092cec0]: User Name at Session Startup: <Replicator
Queue Management> '
!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
000000010092cec0]: Terminal: NONE '
!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
000000010092cec0]: Group Id: '
!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
000000010092cec0]: Role Id: '
!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
000000010092cec0]: Application Code: 00000000 Current
Facili
!ty: DMF (00000003)'
!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
000000010092cec0]: Description: '
!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
000000010092cec0]: Query: '
!

Any help will be appreciated.
I contacted Ingres Tech but they are very slow in their answer.

Some parameters from config.dat:
ii.yoda.dbms.*.*.config.dmf_connect: 32
ii.yoda.dbms.*.dmf_db_cache_size: 40
ii.yoda.dbms.*.dmf_hash_size: 256
ii.yoda.dbms.*.dmf_tbl_cache_size: 40
ii.yoda.dbms.private.*.config.dmf_connect: 64
ii.yoda.dbms.private.*.dmf_cache_size: 384
ii.yoda.dbms.private.*.dmf_free_limit: 12
ii.yoda.dbms.private.*.dmf_group_count: 20
ii.yoda.dbms.private.*.dmf_group_size: 8
ii.yoda.dbms.private.*.dmf_memory: 1114112
ii.yoda.dbms.private.*.dmf_modify_limit: 288
ii.yoda.dbms.private.*.dmf_wb_end: 192
ii.yoda.dbms.private.*.dmf_wb_start: 230
ii.yoda.dbms.private.*.dmf_write_behind: ON
ii.yoda.dbms.private.*.p16k.dmf_cache_size: 384
ii.yoda.dbms.private.*.p16k.dmf_free_limit: 12
ii.yoda.dbms.private.*.p16k.dmf_group_count: 20
ii.yoda.dbms.private.*.p16k.dmf_group_size: 8
ii.yoda.dbms.private.*.p16k.dmf_memory: 8912896
ii.yoda.dbms.private.*.p16k.dmf_modify_limit: 288
ii.yoda.dbms.private.*.p16k.dmf_separate: OFF
ii.yoda.dbms.private.*.p16k.dmf_wb_end: 192
ii.yoda.dbms.private.*.p16k.dmf_wb_start: 230
ii.yoda.dbms.private.*.p16k.dmf_write_behind: ON
ii.yoda.dbms.private.*.p32k.dmf_cache_size: 384
ii.yoda.dbms.private.*.p32k.dmf_free_limit: 12
ii.yoda.dbms.private.*.p32k.dmf_group_count: 20
ii.yoda.dbms.private.*.p32k.dmf_group_size: 8
ii.yoda.dbms.private.*.p32k.dmf_memory: 17825792
ii.yoda.dbms.private.*.p32k.dmf_modify_limit: 288
ii.yoda.dbms.private.*.p32k.dmf_separate: OFF
ii.yoda.dbms.private.*.p32k.dmf_wb_end: 192
ii.yoda.dbms.private.*.p32k.dmf_wb_start: 230
ii.yoda.dbms.private.*.p32k.dmf_write_behind: ON
ii.yoda.dbms.private.*.p4k.dmf_cache_size: 384
ii.yoda.dbms.private.*.p4k.dmf_free_limit: 12
ii.yoda.dbms.private.*.p4k.dmf_group_count: 20
ii.yoda.dbms.private.*.p4k.dmf_group_size: 8
ii.yoda.dbms.private.*.p4k.dmf_memory: 2228224
ii.yoda.dbms.private.*.p4k.dmf_modify_limit: 288
ii.yoda.dbms.private.*.p4k.dmf_separate: OFF
ii.yoda.dbms.private.*.p4k.dmf_wb_end: 192
ii.yoda.dbms.private.*.p4k.dmf_wb_start: 230
ii.yoda.dbms.private.*.p4k.dmf_write_behind: ON
ii.yoda.dbms.private.*.p64k.dmf_cache_size: 384
ii.yoda.dbms.private.*.p64k.dmf_free_limit: 12
ii.yoda.dbms.private.*.p64k.dmf_group_count: 20
ii.yoda.dbms.private.*.p64k.dmf_group_size: 8
ii.yoda.dbms.private.*.p64k.dmf_memory: 35651584
ii.yoda.dbms.private.*.p64k.dmf_modify_limit: 288
ii.yoda.dbms.private.*.p64k.dmf_separate: OFF
ii.yoda.dbms.private.*.p64k.dmf_wb_end: 192
ii.yoda.dbms.private.*.p64k.dmf_wb_start: 230
ii.yoda.dbms.private.*.p64k.dmf_write_behind: ON
ii.yoda.dbms.private.*.p8k.dmf_cache_size: 384
ii.yoda.dbms.private.*.p8k.dmf_free_limit: 12
ii.yoda.dbms.private.*.p8k.dmf_group_count: 20
ii.yoda.dbms.private.*.p8k.dmf_group_size: 8
ii.yoda.dbms.private.*.p8k.dmf_memory: 4456448
ii.yoda.dbms.private.*.p8k.dmf_modify_limit: 288
ii.yoda.dbms.private.*.p8k.dmf_separate: OFF
ii.yoda.dbms.private.*.p8k.dmf_wb_end: 192
ii.yoda.dbms.private.*.p8k.dmf_wb_start: 230
ii.yoda.dbms.private.*.p8k.dmf_write_behind: ON
ii.yoda.rcp.dmf_cache_size: 200
ii.yoda.rcp.dmf_cache_size16k: 0
ii.yoda.rcp.dmf_cache_size32k: 0
ii.yoda.rcp.dmf_cache_size4k: 0
ii.yoda.rcp.dmf_cache_size64k: 0
ii.yoda.rcp.dmf_cache_size8k: 0
ii.yoda.syscheck.dmf_seg_num: 0
ii.yoda.syscheck.dmf_segment: 0
ii.yoda.dbms.*.qsf_memory: 10440000
ii.yoda.star.*.qsf_memory: 460000
ii.yoda.dbms.*.stack_caching: OFF
ii.yoda.dbms.*.stack_size: 131072
ii.yoda.recovery.*.stack_size: 131072

Reply to this Message

Karl & Betty Schendel - 23 Jul 2007 22:58 GMT

>After upgrading from Ingres 2.6/0305 to Ingres 2.6/0604 SP5 for
>Solaris 9 (after Jul 3 2007)
[quoted text clipped - 4 lines]
>!(sc0e.c, 525) ERsend--->'YODA ::[38598 ,
>000000010092cec0]: User: <Replicator Queue Management>

If the session named is the replicator queue management thread
most of the time, try fooling around with the rep_txq_size parameter
to see if you can make the errors go away or reduce their frequency.
(I assume you're using replicator.)

Was there any stack traceback in the errlog.log?

Do you have II_DBMS_LOG set? (ingprenv) If not, try
mkdir $II_SYSTEM/ingres/files/dbmslogs
ingsetenv II_DBMS_LOG $II_SYSTEM/ingres/files/dbmslogs/iidbms_%p.log

and see if you get anything useful in the dbms log the next
time it crashes. (Note: the value of II_DBMS_LOG is just a
full pathname that has to be writable by user ingres.
It can be anywhere convenient. The _%p appends the process
ID so that you don't overwrite the same file over and over.)

I don't know what this error is, but from the sound of it,
I think you'll need a patch to really fix it.

Karl

Reply to this Message