数据库在建设备时当掉了, 把错误贴出来高手帮忙看看

lxr_wolf

当时任何用户都无法登陆, 只能将数据库进程杀掉, 重新运行数据库服务, 又恢复正常了。
这个错误信息有点怪, 大家帮忙看看
错误信息如下：
01:00000:00047:2006/07/04 10:05:16.04 kernel  Initializing virtual device 14, '/datadev/posdev/lspsdb.dat' with dsync 'on'.
01:00000:00047:2006/07/04 10:05:16.06 kernel  Virtual device 14 started using asynchronous i/o.
01:00000:00047:2006/07/04 10:05:16.06 kernel  Initializing device /datadev/posdev/lspsdb.dat from offset 0 with zeros.
00:00000:00000:2006/07/04 10:06:30.48 kernel  engine 1, os pid 3400  exited
00:00000:00000:2006/07/04 10:06:30.48 kernel  Process 3400 exited with status 0
00:00000:00000:2006/07/04 10:06:31.06 kernel  Task with kpid 21b00070 running on failed engine
00:00000:00000:2006/07/04 10:06:31.06 kernel  Engine exited with signal 9
00:00000:00000:2006/07/04 10:06:31.06 kernel  current process (0x21dc010a) infected with 11
00:00000:00000:2006/07/04 10:06:31.27 kernel  Address 0x0x0000000e (), siginfo (code, address) = (1, 0x0x00006db4)
00:00000:00000:2006/07/04 10:06:32.27 kernel  pc 0x88055e9 ucbacktrace+0x89(0x0,0x1,0x936e834,0x3aaa4ffc,0x0)
00:00000:00000:2006/07/04 10:06:32.42 kernel  pc 0x81b4869 terminate_process+0x124d(0x0,0xffffffff,0x936e834,0x0,0x3aaa73e
00:00000:00000:2006/07/04 10:06:32.42 kernel  pc 0x8824f49 kisignal+0x1d1(0xb,0x3aaa7010,0x3aaa7090,0xb,0x0)
00:00000:00000:2006/07/04 10:06:32.42 kernel  pc 0xce28b0 (0x393c0058,0x0,0x0,0x0,0x0)
00:00000:00000:2006/07/04 10:06:32.42 kernel  pc 0x826cd95 hk_gc_final_cleanup+0xf5(0x3d72c6b0,0x1,0x936e834,0x0,0x0)
00:00000:00000:2006/07/04 10:06:32.42 kernel  pc 0x81b3b49 terminate_process+0x52d(0x90009,0x0,0x0,0x3aaa75dc,0x8846dec)
00:00000:00000:2006/07/04 10:06:32.42 kernel  pc 0x81b8def terminator+0x1b(0x90009,0x3aaa75e4,0x895eed31,0x0,0x0)
00:00000:00000:2006/07/04 10:06:32.42 kernel  pc 0x8846dec kpexit(0x0,0x0,0x0,0x399f6100,0x10b)
00:00000:00000:2006/07/04 10:06:32.85 kernel  pc 0x895eed31 init_dummy+0x809534c1(0x0,0x399f6100,0x10b,0x1,0x5374616b)
00:00000:00000:2006/07/04 10:06:32.85 kernel  end of stack trace, kernel service process: kpid 568066314
00:00000:00000:2006/07/04 10:06:32.85 kernel  kpenginedied: killed kpid 589833 which was affinitied to engine 1
00:00000:00000:2006/07/04 10:06:32.85 kernel  kpenginedied: killed kpid 563937330 which was affinitied to engine 1
00:00000:00154:2006/07/04 10:06:33.14 kernel  kesetown: engine 1 not online
00:00000:00154:2006/07/04 10:06:33.14 kernel  current process (0x21e000e5) infected with 11
00:00000:00154:2006/07/04 10:06:33.14 kernel  Address 0x0x0000000e (), siginfo (code, address) = (1, 0x0xfffe7961)
00:00000:00154:2006/07/04 10:06:33.15 kernel  ************************************
00:00000:00154:2006/07/04 10:06:33.60 kernel  curdb = 0 tempdb = 0 pstat = 0x0
00:00000:00154:2006/07/04 10:06:33.60 kernel  lasterror = 0 preverror = 0 transtate = 1
00:00000:00154:2006/07/04 10:06:33.60 kernel  curcmd = 0 program =                              
00:00000:00154:2006/07/04 10:06:33.60 kernel  pc 0x88055e9 ucbacktrace+0x89(0x0,0x1,0x936e834,0x3a854c04,0x0)
00:00000:00154:2006/07/04 10:06:33.60 kernel  pc 0x81b41ed terminate_process+0xbd1(0x0,0xffffffff,0x936e834,0x948c060,0x6)
00:00000:00154:2006/07/04 10:06:33.60 kernel  pc 0x8824f49 kisignal+0x1d1(0xb,0x3a856c18,0x3a856c98,0xb,0x0)
00:00000:00154:2006/07/04 10:06:33.60 kernel  pc 0xce28b0 (0x948c060,0x0,0x6,0x936e834,0x3eb0334c)
00:00000:00154:2006/07/04 10:06:33.60 kernel  pc 0x8836146 usctclose+0x1e(0x948c060,0xfffe7961,0x936e834,0x3eb0334c,0x3eb0334c)
00:00000:00154:2006/07/04 10:06:33.60 kernel  pc 0x88927bc omni_ct_close+0x58(0x948c060,0xfffe7961,0x936e834,0x3eb0334c,0x3decd4dc)
00:00000:00154:2006/07/04 10:06:33.91 kernel  pc 0x88b6e3c rdes_free+0x34(0x3eb0334c,0x99e5a094,0x936e834,0x3decd4dc,0x3decd4dc)
00:00000:00154:2006/07/04 10:06:33.91 kernel  pc 0x88b6691 omnipss_free+0x115(0x99e5a094,0x936e834,0x1,0x3a857134,0x81b9baf)
00:00000:00154:2006/07/04 10:06:33.91 kernel  pc 0x889d271 omni_disconnect_handler+0x49(0x3decd4dc,0x3decd4dc,0x936e834,0x393beba0,0x3decd4dc)
00:00000:00154:2006/07/04 10:06:33.91 kernel  pc 0x81b9baf dso_disconnect_handler+0x37(0x3decd4dc,0x3decd4dc,0x0,0x21620033,0x936e834)
00:00000:00154:2006/07/04 10:06:33.91 kernel  pc 0x81b4628 terminate_process+0x100c(0x21620033,0x0,0x0,0x3a8572f8,0x8846dec)
00:00000:00154:2006/07/04 10:06:33.91 kernel  pc 0x81b8def terminator+0x1b(0x21620033,0x3a857300,0x895eed31,0x0,0x0)
00:00000:00154:2006/07/04 10:06:33.91 kernel  pc 0x8846dec kpexit(0x0,0x0,0x0,0x399f6100,0xe6)
00:00000:00154:2006/07/04 10:06:33.91 kernel  pc 0x895eed31 init_dummy+0x809534c1(0x0,0x399f6100,0xe6,0x1,0x5374616b)
00:00000:00154:2006/07/04 10:06:33.91 kernel  end of stack trace, spid 154, kpid 568328421, suid 0
00:00000:00000:2006/07/04 10:06:33.91 kernel  kpenginedied: killed kpid 560070707 which was affinitied to engine 1
00:00000:00184:2006/07/04 10:06:34.09 kernel  current process (0x21e1006 infected with 11
00:00000:00184:2006/07/04 10:06:34.09 kernel  Address 0x0x0000000e (), siginfo (code, address) = (1, 0x0xfffe7961)

1017of

00:00000:00000:2006/07/04 10:06:31.06 kernel  Engine exited with signal 9
---------------------------------------------------------------------------------------------------
someone killed ASE engine process?

lxr_wolf

没有啊，我也觉得奇怪，怎么数据库引擎莫名其妙的被当掉了，但是除了将设备之外，没有其他的人和操作，就算当引擎，那也应该是sybase自我的保护机制之类的吧？反正很怪，以前也没有碰到过这种情况，重启数据库服务后又好了。

1017of

engine 1 process was killed by errorlog at least.signal 9 is obviously clear,which is explained by OS signal description.what means "sybase自我的保护机制之类"?I have no idea about this.

2BeSybPro

"Engine exited with signal 9" means someone or the OS issued a kill -9 for the engine. When the OS issues the kill -9 it is usually because someone issue kill -9 manually, or the OS runs out of memory or had some memory problem and in choosing a process to kill to free up some memory choose engine of ASE. The infected with 11 that followed were a result of those processes on engine not being able to clean up properly due to the kill -9 being issued.