Skip to Content
avatar image
Former Member

maxdb 7.8 going offline without any information while users are logged in

Hello All

maxdb 7.8 going offline without any information while users are logged in the system. we have maxdb7.8 in sles11. i looked int he log files KLNMSGARC & KLNMSGOLD.

Anybody faced this issue, Could you please look into the log & help to resolve this.

Thanks in advance

KLNMSGARC:

Thread 0x4229 Task - 2013-01-11 11:09:52 ERR RTEKernel 102: Kernel exited without core and exit status 0x9,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=68 3

Thread 0x4229 Task - 2013-01-11 11:09:52 ERR RTEKernel 98: Kernel exited due to signal 9 (SIGKILL),_FILE=RTEKernel_Termination+noPIC.cpp,_LI NE=729

Thread 0x4229 Task - 2013-01-11 11:09:52 MsgOutput 28: ___ Stopping GMT 2013-01-11 05:39:52 7.8.01 Build 014-121-233-288

Thread - Task - 2013-01-11 11:11:18 MsgOutput 27: --- Starting GMT 2013-01-11 05:41:18 7.8.01 Build 014-121-233-288

Thread 0x327D Task 80 2013-01-11 11:11:32 AdminMsg 0: 50EFA60C001A 0000 RST RESTART

Thread 0x3280 Task 80 2013-01-11 11:12:14 AdminMsg 0: 50EFA636006B 0000 RST RETURNCODE 0;RESTART

Thread 0x325B Task - 2013-01-11 12:39:09 ERR RTEKernel 102: Kernel exited without core and exit status 0x9,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=68 3

Thread 0x325B Task - 2013-01-11 12:39:09 ERR RTEKernel 98: Kernel exited due to signal 9 (SIGKILL),_FILE=RTEKernel_Termination+noPIC.cpp,_LI NE=729

Thread 0x325B Task - 2013-01-11 12:39:10 MsgOutput 28: ___ Stopping GMT 2013-01-11 07:09:10 7.8.01 Build 014-121-233-288

Thread - Task - 2013-01-11 12:40:04 MsgOutput 27: --- Starting GMT 2013-01-11 07:10:04 7.8.01 Build 014-121-233-288

Thread 0x453E Task 81 2013-01-11 12:40:17 AdminMsg 0: 50EFBAD90018 0000 RST RESTART

Thread 0x453F Task 81 2013-01-11 12:41:07 AdminMsg 0: 50EFBB0B00BF 0000 RST RETURNCODE 0;RESTART

Thread 0x451B Task - 2013-01-11 13:14:57 ERR RTEKernel 102: Kernel exited without core and exit status 0x9,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=68 3

Thread 0x451B Task - 2013-01-11 13:14:57 ERR RTEKernel 98: Kernel exited due to signal 9 (SIGKILL),_FILE=RTEKernel_Termination+noPIC.cpp,_LI NE=729

Thread 0x451B Task - 2013-01-11 13:14:57 MsgOutput 28: ___ Stopping GMT 2013-01-11 07:44:57 7.8.01 Build 014-121-233-288

Thread - Task - 2013-01-11 13:20:08 MsgOutput 27: --- Starting GMT 2013-01-11 07:50:08 7.8.01 Build 014-121-233-288

Thread 0x4E7F Task 81 2013-01-11 13:20:22 AdminMsg 0: 50EFC43E0006 0000 RST RESTART

Thread 0x4E80 Task 81 2013-01-11 13:20:27 AdminMsg 0: 50EFC443000D 0000 RST RETURNCODE 0;RESTART

Thread 0x4E5D Task - 2013-01-11 16:28:07 ERR RTEKernel 102: Kernel exited without core and exit status 0x9,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=68 3

Thread 0x4E5D Task - 2013-01-11 16:28:07 ERR RTEKernel 98: Kernel exited due to signal 9 (SIGKILL),_FILE=RTEKernel_Termination+noPIC.cpp,_LI NE=729

Thread 0x4E5D Task - 2013-01-11 16:28:07 MsgOutput 28: ___ Stopping GMT 2013-01-11 10:58:07 7.8.01 Build 014-121-233-288

Thread - Task - 2013-01-11 16:29:34 MsgOutput 27: --- Starting GMT 2013-01-11 10:59:34 7.8.01 Build 014-121-233-288

Thread 0x7809 Task 80 2013-01-11 16:29:47 AdminMsg 0: 50EFF0A30022 0000 RST RESTART

Thread 0x780B Task 80 2013-01-11 16:30:19 AdminMsg 0: 50EFF0C3007B 0000 RST RETURNCODE 0;RESTART

Thread 0x77C9 Task - 2013-01-11 18:05:37 ERR RTEKernel 102: Kernel exited without core and exit status 0x9,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=68 3

Thread 0x77C9 Task - 2013-01-11 18:05:37 ERR RTEKernel 98: Kernel exited due to signal 9 (SIGKILL),_FILE=RTEKernel_Termination+noPIC.cpp,_LI NE=729

Thread 0x77C9 Task - 2013-01-11 18:05:37 MsgOutput 28: ___ Stopping GMT 2013-01-11 12:35:37 7.8.01 Build 014-121-233-288

Thread - Task - 2013-01-11 18:06:00 MsgOutput 27: --- Starting GMT 2013-01-11 12:36:00 7.8.01 Build 014-121-233-288

Thread 0xE37 Task 81 2013-01-11 18:06:14 AdminMsg 0: 50F0073E0010 0000 RST RESTART

Thread 0xE3A Task 81 2013-01-11 18:06:47 AdminMsg 0: 50F0075F008F 0000 RST RETURNCODE 0;RESTART

Thread 0xE14 Task - 2013-01-11 18:48:57 ERR RTEKernel 102: Kernel exited without core and exit status 0x9,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=68 3

Thread 0xE14 Task - 2013-01-11 18:48:57 ERR RTEKernel 98: Kernel exited due to signal 9 (SIGKILL),_FILE=RTEKernel_Termination+noPIC.cpp,_LI NE=729

Thread 0xE14 Task - 2013-01-11 18:48:57 MsgOutput 28: ___ Stopping GMT 2013-01-11 13:18:57 7.8.01 Build 014-121-233-288

Thread - Task - 2013-01-11 18:54:11 MsgOutput 27: --- Starting GMT 2013-01-11 13:24:11 7.8.01 Build 014-121-233-288

Thread 0x1852 Task 81 2013-01-11 18:54:26 AdminMsg 0: 50F0128A0004 0000 RST RESTART

Thread 0x1852 Task 81 2013-01-11 18:54:33 AdminMsg 0: 50F012910005 0000 RST RETURNCODE 0;RESTART

Thread 0x181D Task - 2013-01-15 21:47:40 ERR RTEKernel 102: Kernel exited without core and exit status 0x9,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=68 3

Thread 0x181D Task - 2013-01-15 21:47:40 ERR RTEKernel 98: Kernel exited due to signal 9 (SIGKILL),_FILE=RTEKernel_Termination+noPIC.cpp,_LI NE=729

Thread 0x181D Task - 2013-01-15 21:47:40 MsgOutput 28: ___ Stopping GMT 2013-01-15 16:17:40 7.8.01 Build 014-121-233-288

Thread - Task - 2013-01-15 22:34:26 MsgOutput 27: --- Starting GMT 2013-01-15 17:04:26 7.8.01 Build 014-121-233-288

Thread 0x6FE8 Task 81 2013-01-15 22:34:39 AdminMsg 0: 50F58C270004 0000 RST RESTART

Thread 0x6FEB Task 81 2013-01-15 22:35:22 AdminMsg 0: 50F58C520027 0000 RST RETURNCODE 0;RESTART

Thread 0x6FC6 Task - 2013-01-16 09:50:15 ERR RTEKernel 102: Kernel exited without core and exit status 0x9,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=68 3

Thread 0x6FC6 Task - 2013-01-16 09:50:15 ERR RTEKernel 98: Kernel exited due to signal 9 (SIGKILL),_FILE=RTEKernel_Termination+noPIC.cpp,_LI NE=729

Thread - Task - 2013-01-16 10:03:18 MsgOutput 27: --- Starting GMT 2013-01-16 04:33:18 7.8.01 Build 014-121-233-288

Thread 0x1844 Task 81 2013-01-16 10:03:35 AdminMsg 0: 50F62D9F0004 0000 RST RESTART

Thread 0x1845 Task 81 2013-01-16 10:04:17 AdminMsg 0: 50F62DC90005 0000 RST RETURNCODE 0;RESTART



KNLMSGOLD

---

Thread 0x6FE7 Task 1 2013-01-16 09:47:18 Savepoint 1: Savepoint (Time) started by T1

Thread 0x6FE4 Task 181 2013-01-16 09:47:18 Pager 20003: SVP(1) Start Write Data

Thread 0x6FE4 Task 181 2013-01-16 09:47:19 Pager 20004: SVP(1) Stop Data IO, Pages: 361 IO: 260

Thread 0x6FE4 Task 181 2013-01-16 09:47:19 Pager 20005: SVP(2) Wait for last synchronizing task: 181

Thread 0x6FE4 Task 181 2013-01-16 09:47:19 Pager 20006: SVP(2) Stop Wait for last synchronizing task, Pages: 0 IO: 0

Thread 0x6FE4 Task 181 2013-01-16 09:47:19 DataCache 4: Mark data pages for savepoint (prepare phase)

Thread 0x6FE4 Task 181 2013-01-16 09:47:19 Pager 20007: SVP(3) Start Write Data

Thread 0x6FE4 Task 181 2013-01-16 09:47:19 Pager 20008: SVP(3) Stop Data IO, Pages: 3 IO: 3

Thread 0x6FE4 Task 181 2013-01-16 09:47:19 Pager 20009: SVP(3) Start Write Converter

Thread 0x6FE4 Task 181 2013-01-16 09:47:19 Pager 20011: SVP(3) Stop Converter IO, Pages: 258 IO: 258

Thread 0x6FE4 Task 181 2013-01-16 09:47:19 DataCache 3: Savepoint with ID 13430 completed

Thread 0x6FC6 Task - 2013-01-16 09:50:15 RTEKernel 61: rtedump written to file 'rtedump'

Thread 0x6FC6 Task - 2013-01-16 09:50:15 ERR RTEKernel 102: Kernel exited without core and exit status 0x9,_FILE=RTEKernel_Termination+noPIC.cpp,_LINE=68 3

Thread 0x6FC6 Task - 2013-01-16 09:50:15 ERR RTEKernel 98: Kernel exited due to signal 9 (SIGKILL),_FILE=RTEKernel_Termination+noPIC.cpp,_LI NE=729

Thread 0x6FC6 Task - 2013-01-16 09:50:15 RTEKernel 58: Backup of diagnostic files will be forced at next restart

Thread 0x6FC6 Task - 2013-01-16 09:50:15 RTEKernel 107: Flushing knltrace pages (emergency)

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • Best Answer
    Jan 18, 2013 at 09:43 AM

    Hi,

    please check as root '/var/log/messages', if the database kernel was killed by the Linux operating system. This can happen, if the Linux OS runs out of memory - it then starts a so called 'oom killer' program which identifies suitable processes to kill. As the MaxDB kernel usually allocates a lot of memory (depends on the CACHE_SIZE setting), it is a likely candidate for termination.

    If this was indeed the oom killer, you should find some hint in the 'messages' file like:

    /var/log/messages

    kernel: [33872.707196] Out of memory: kill process 17092 (kernel)
    score 958925227 or a child

    kernel: [33872.707199] Killed process 17095 (kernel)

    If you are an SAP customer, you can find further info in note 1647204.

    Thorsten

    Add comment
    10|10000 characters needed characters exceeded

    • Hi,

      the database is killed by the Linux 'oom-killer' process when Linux runs out of memory - looking at the database call stacks verifies this.

      In your system the cachememorysize is set to 107264 pages. Each MaxDB page has a size of 8 KB, so the database will use 838 MB memory plus maybe 200-300 MB on top (depending on how many user tasks are configured...). I do not know how much memory the other applications are using on that server, but you need to check the total memory consumption of all applications against how much ram you have allowed for your VM. Has there been a 'sizing check' for that system? Was the hardware/software changed lately?

      Thorsten