RE: Segmentation Violation
Michael
Its a problem with KAIO. The OS and Informix Version is essential here for
anyone to assist.
For Assert Fails, logging a call imediately with Informix Support is the
best option for fastest resolution. They can quickly match the stack trace
with known issues.
MW
-----Original Message-----
From: owner-informix-list@iiug.iiug.org
[mailto:owner-informix-list@iiug.iiug.org]On Behalf Of Michael Hoffman
Sent: Tuesday, December 12, 2000 6:19 AM
To: informix-list@iiug.org
Subject: Segmentation Violation
Hi all,
Well, my first real major crisis and I had no idea what was going
on. :-( Informix crashed early Saturday AM, but no one noticed until Monday
AM. I got Informix up and running, but have no idea what caused the problem
(other than what was in the online.log file). All I can see is that a
Segmentation Violation forced Informix to Shut-down.
Can anyone make heads or tails out of the following log excerpt? I've
also included the /tmp/af.fe941 file. (I know for the future to get a
Shared
Memory dump, but it's too late now, huh?)
Thanks,
Michael Hoffman
===========================
online.log
----------
03:10:05 Checkpoint Completed: duration was 2 seconds.
03:11:46 Assert Failed: Internal Error - Segmentation Violation
03:11:46 Who: Thread(15, kaio, bae0898, 1)
03:11:46 Results: OnLine must abort
03:11:46 Action: Reinitialize shared memory
03:11:46 See Also: /tmp/af.fe941
03:11:46 rsinit.c, line 9968, thread 15, proc id 371, Segmentation
Violation.
03:11:46 PANIC: Attempting to bring system down
Mon Dec 11 07:42:51 2000
07:42:51 Event alarms enabled. ALARMPROG = '/home/informix/log_full.sh'
07:42:56 DR: DRAUTO is 0 (Off)
07:42:57 INFORMIX-OnLine Initialized -- Shared Memory Initialized.
07:42:57 Physical Recovery Started.
=============================================
/tmp/af.fe941
--------------
03:11:46
03:11:46 Assert Failed: Internal Error - Segmentation Violation
03:11:46 Who: Thread(15, kaio, bae0898, 1)
03:11:46 Results: OnLine must abort
03:11:46 Action: Reinitialize shared memory
03:11:46 See Also: /tmp/af.fe941
03:11:46 Stack for thread: 15 kaio
base: 0x0bcf4018
len: 33280
pc: 0x00385610
tos: 0x0bcfae20
0x00384fac mt_affail (0x0, 0x0, 0x4e38d8, 0xbb04260, 0x4e38d4, 0x0)
0x00280464 rsam_affail (0xbf5c018, 0xbb37208, 0xbdbdfe0, 0xbae0898,
0xbb04260, 0x0)
0x0007bf90 hang_thread (0x4e27c8, 0x2400, 0xb, 0x0, 0x0, 0x0)
0xff195ec4 ***unknown*** (0xb, 0x0, 0xbcfb6f0, 0xffffffff, 0x0, 0x1)
0x0be1a000 ***unknown*** (0xbb32018, 0xbe1a000, 0x0, 0x0, 0x0, 0x0)
0x0037a67c morecore (0xbb32018, 0x8818, 0xffffffff, 0xbaa8000,
0xbb6c948, 0x5801800)
0x00379f5c mt_shm_malloc_segid(0xbb32018, 0x8800, 0x1b, 0xffffffff,
0xbcc2800, 0xff3468b8)
0x00379bf4 mt_shm_malloc (0xbb32018, 0x8800, 0x1b, 0xfffffff8, 0x0,
0xbb6c945)
0x00370a9c mt_aio_malloc (0x8800, 0x0, 0x0, 0x28, 0x0, 0x580a800)
0x00383d64 kaio_bb_get (0xbb96b50, 0x0, 0x580a800, 0x0, 0x0, 0xbcc2800)
0x00383104 kaio_workon (0x0, 0xbc46330, 0x2, 0xbc46364, 0xbb97530,
0xbb97208)
0x003827b8 kaiothread (0xbb97500, 0x3a107f52, 0xbbff808, 0x7, 0x0,
0xbb97504)
0x0036b404 startup (0xffffffff, 0x2, 0x4, 0x3, 0x0, 0x0)
0x00371da4 mt_aio_wait (0x0, 0x0, 0x0, 0x0, 0x0, 0x0)
0x00000000 ***unknown***
03:11:46
------------------ End of assertion failure 0 -----------------
You are correct, my bad. I should have known better. (Bad Mike, Bad Mike) OS --> Sun SOlaris 5.7 Informix 7.23.UC7 Michael In <913g4u$j59$1@news.xmission.com> article, Murray Wood mentioned that: : Michael : Its a problem with KAIO. The OS and Informix Version is essential here for : anyone to assist. : For Assert Fails, logging a call imediately with Informix Support is the : best option for fastest resolution. They can quickly match the stack trace : with known issues. : MW : -----Original Message----- : From: owner-informix-list@iiug.iiug.org : [mailto:owner-informix-list@iiug.iiug.org]On Behalf Of Michael Hoffman : Sent: Tuesday, December 12, 2000 6:19 AM : To: informix-list@iiug.org : Subject: Segmentation Violation : Hi all, : Well, my first real major crisis and I had no idea what was going : on. :-( Informix crashed early Saturday AM, but no one noticed until Monday : AM. I got Informix up and running, but have no idea what caused the problem : (other than what was in the online.log file). All I can see is that a : Segmentation Violation forced Informix to Shut-down. : Can anyone make heads or tails out of the following log excerpt? I've : also included the /tmp/af.fe941 file. (I know for the future to get a : Shared : Memory dump, but it's too late now, huh?) : Thanks, : Michael Hoffman : =========================== : online.log : ---------- : 03:10:05 Checkpoint Completed: duration was 2 seconds. : 03:11:46 Assert Failed: Internal Error - Segmentation Violation : 03:11:46 Who: Thread(15, kaio, bae0898, 1) : 03:11:46 Results: OnLine must abort : 03:11:46 Action: Reinitialize shared memory : 03:11:46 See Also: /tmp/af.fe941 : 03:11:46 rsinit.c, line 9968, thread 15, proc id 371, Segmentation : Violation. : 03:11:46 PANIC: Attempting to bring system down : Mon Dec 11 07:42:51 2000 : 07:42:51 Event alarms enabled. ALARMPROG = '/home/informix/log_full.sh' : 07:42:56 DR: DRAUTO is 0 (Off) : 07:42:57 INFORMIX-OnLine Initialized -- Shared Memory Initialized. : 07:42:57 Physical Recovery Started. : ============================================= : /tmp/af.fe941 : -------------- : 03:11:46 : 03:11:46 Assert Failed: Internal Error - Segmentation Violation : 03:11:46 Who: Thread(15, kaio, bae0898, 1) : 03:11:46 Results: OnLine must abort : 03:11:46 Action: Reinitialize shared memory : 03:11:46 See Also: /tmp/af.fe941 : 03:11:46 Stack for thread: 15 kaio : base: 0x0bcf4018 : len: 33280 : pc: 0x00385610 : tos: 0x0bcfae20 : 0x00384fac mt_affail (0x0, 0x0, 0x4e38d8, 0xbb04260, 0x4e38d4, 0x0) : 0x00280464 rsam_affail (0xbf5c018, 0xbb37208, 0xbdbdfe0, 0xbae0898, : 0xbb04260, 0x0) : 0x0007bf90 hang_thread (0x4e27c8, 0x2400, 0xb, 0x0, 0x0, 0x0) : 0xff195ec4 ***unknown*** (0xb, 0x0, 0xbcfb6f0, 0xffffffff, 0x0, 0x1) : 0x0be1a000 ***unknown*** (0xbb32018, 0xbe1a000, 0x0, 0x0, 0x0, 0x0) : 0x0037a67c morecore (0xbb32018, 0x8818, 0xffffffff, 0xbaa8000, : 0xbb6c948, 0x5801800) : 0x00379f5c mt_shm_malloc_segid(0xbb32018, 0x8800, 0x1b, 0xffffffff, : 0xbcc2800, 0xff3468b8) : 0x00379bf4 mt_shm_malloc (0xbb32018, 0x8800, 0x1b, 0xfffffff8, 0x0, : 0xbb6c945) : 0x00370a9c mt_aio_malloc (0x8800, 0x0, 0x0, 0x28, 0x0, 0x580a800) : 0x00383d64 kaio_bb_get (0xbb96b50, 0x0, 0x580a800, 0x0, 0x0, 0xbcc2800) : 0x00383104 kaio_workon (0x0, 0xbc46330, 0x2, 0xbc46364, 0xbb97530, : 0xbb97208) : 0x003827b8 kaiothread (0xbb97500, 0x3a107f52, 0xbbff808, 0x7, 0x0, : 0xbb97504) : 0x0036b404 startup (0xffffffff, 0x2, 0x4, 0x3, 0x0, 0x0) : 0x00371da4 mt_aio_wait (0x0, 0x0, 0x0, 0x0, 0x0, 0x0) : 0x00000000 ***unknown*** : 03:11:46 : ------------------ End of assertion failure 0 -----------------