Re: segmentation violation

Pete, We are having exactly the same problem with 7.23 UC6 running AIX 4.2.1 on an IBM F50, (4 x 166 mhz pentiums, 1GB memory). The Informix people say that it is a known bug that just cropped up in the last couple of months and the fix is to upgrade to 7.24 UC5 which has the bug fix in it. Unfortunately, 7.24 UC5 will not be available for AIX 4.2.1 until mid to late April. Our case number with informix is 716258 if this will help you in working with Informix tech support. HTH ==================================================================== Harold Luse VTH Exten: 120 Applications Programmer Phone: (970) 491-4120 Veterinary Teaching Hospital Fax: (970) 491-1275 Colorado State University Pager: (970) 491-1200 ext 120 Fort Collins, Colorado USA E-mail: hluse@vth.colostate.edu ==================================================================== Be a fundamentalist: That is, make sure the fun comes before the mental. On Fri, 3 Apr 1998, Pete Smith wrote: > help needed > > Informix is crashing on a regular basis, with the following entries in > the online log: > > 03:54:35 Checkpoint Completed: duration was 1 seconds. > 03:54:48 Assert Failed: Internal Error - Segmentation Violation > 03:54:48 Who: Session(2550, testuser@test1, 2356, -1023369440) > Thread(2525, sqlexec, c2fe8758, 1) > 03:54:48 Results: OnLine must abort > 03:54:48 Action: Reinitialize shared memory > 03:54:48 See Also: /tmp/af.9dd4f77, shmem.9dd4f77.0 > 03:55:08 rsinit.c, line 10145, thread 2525, proc id 9884, Segmentation > Violation. > 03:55:08 Assert Failed: Segmentation Violation > 03:55:08 Who: Session(2550, testuser@test1, 2356, 0) > Thread(2525, sqlexec, 0, 1) > 03:55:08 Results: Fatal Internal Error requires system shutdown > 03:55:08 Action: Restart OnLine > 03:55:08 See Also: /tmp/af.9dd4f77, shmem.9dd4f77.1 > 03:55:18 Error writing '/tmp/shmem.9dd4f77.1' errno = 28 > 03:55:18 rsinit.c, line 10145, thread 2525, proc id 9884, Segmentation > Violation. > 03:55:18 PANIC: Attempting to bring system down > 03:55:18 mt.c, line 10177, thread 2525, proc id 9884, Message 16517 not > found. > #####> > and af.9dd4f77: > > 03:54:48 > 03:54:48 Assert Failed: Internal Error - Segmentation Violation > 03:54:48 Who: Session(2550, testuser@test1, 2356, -1023369440) > Thread(2525, sqlexec, c2fe8758, 1) > 03:54:48 Results: OnLine must abort > 03:54:48 Action: Reinitialize shared memory > 03:54:48 See Also: /tmp/af.9dd4f77, shmem.9dd4f77.0 > 03:54:48 Stack for thread: 2525 sqlexec> > base: 0xc34cf018 > len: 36864 > pc: 0x00000000 > tos: 0xc34d0760 > > ( 0) 0x003072a8 afstack + 0xf0 [/home/informix/bin/oninit] > ( 1) 0x00306a78 mt_affail + 0x310 [/home/informix/bin/oninit] > ( 2) 0x001e9568 rsam_affail + 0x18 [/home/informix/bin/oninit] > ( 3) 0x0002aca8 hang_thread + 0xe8 [/home/informix/bin/oninit] > ( 4) 0x0002aad0 afsig_segv + 0x50 [/home/informix/bin/oninit] > ( 5) 0xc0135e08 _sigreturn [/usr/lib/libc.1] > ( 6) 0x002eb1bc mt_lock + 0xc [/home/informix/bin/oninit] > ( 7) 0x001717e4 ha_insrt_hashtab_or_ovrfl_page + 0x7c > [/home/informix/bin/oninit] > ( 8) 0x001685e4 hash_add_group_row + 0xc4 > [/home/informix/bin/oninit] > ( 9) 0x00167cac initgrpcols + 0x11c [/home/informix/bin/oninit] > (10) 0x001683e4 hash_process_all_groups + 0x84 > [/home/informix/bin/oninit] > (11) 0x00166438 group_open + 0x100 [/home/informix/bin/oninit] > (12) 0x00169708 sort_open + 0x70 [/home/informix/bin/oninit] > (13) 0x001436f4 prepselect + 0x42c [/home/informix/bin/oninit] > (14) 0x0015585c open_cursor + 0x33c [/home/informix/bin/oninit] > (15) 0x00155428 sq_open + 0x48 [/home/informix/bin/oninit] > (16) 0x00115cb0 sqmain + 0x98 [/home/informix/bin/oninit] > (17) 0x00307de8 startup + 0xa0 [/home/informix/bin/oninit] > (18) 0x00300b50 mt_swap_threads + 0xdc [/home/informix/bin/oninit] > > > 03:55:08 > ------------------ End of assertion failure 0 ----------------- > > #### > > I think the error writing the shmem file was tmp filling up. > Unix is HP 10.20, Informix is 7.24.UC3 - which I intend to change asap, > but in the meantime if anyone has ANY ideas about what might be causing > this - please mail me > > yours > (completely stumped) > > Pete > > >