Hi all,
We have a customer with B1 HANA system, and we are experiencing the following problem: without notice, the HANA database stops always at 13:30, after running 2 or 3 continuous days.
We searched for any cron jobs but found none. We are new with HANA and can't figure out the reason for this problem.
Based on the HANA logs, we found that a SIGQUIT event is always triggered when this problem occurs. This event is linked to user ndbadm (user id 1001) and the process that triggers is hdbnameserver (pid 31947), and can't figure out the source of this behavior...
Here are the "daemon_xxxx.trc" log file:
[31930]{-1}[-1/-1] 2016-12-26 09:30:51.837818 i Daemon TrexDaemon.cpp(09548) : line up of program group sapwebdisp to instances 0. [31930]{-1}[-1/-1] 2016-12-26 09:30:51.837820 i Daemon TrexDaemon.cpp(09548) : line up of program group compileserver to instances 0. [31930]{-1}[-1/-1] 2016-12-28 13:30:12.622833 i Daemon TrexDaemon.cpp(06717) : signo 3 SIGQUIT from user errno 0 code 0 [31930]{-1}[-1/-1] 2016-12-28 13:30:12.622865 i Daemon TrexDaemon.cpp(06717) : sender pid 31947 real user id 1001 [31930]{-1}[-1/-1] 2016-12-28 13:30:12.622885 i Daemon TrexDaemon.cpp(10751) : got shutdown event (stop) [31930]{-1}[-1/-1] 2016-12-28 13:30:12.622970 i Daemon TrexDaemon.cpp(11147) : comment file contains: nameserver: shared memory lock '/tmp/.hdb_NDB_00_lock'was deleted all instances in runlevel 5 stopped [31930]{-1}[-1/-1] 2016-12-28 13:30:12.651859 i Daemon TrexDaemon.cpp(09342) : stop process sapwebdisp_hdb with pid 33374 [31930]{-1}[-1/-1] 2016-12-28 13:30:16.864655 i Daemon TrexDaemon.cpp(10887) : process sapwebdisp_hdb with pid 33374 exited normally with status 0 [31930]{-1}[-1/-1] 2016-12-28 13:30:16.864672 i Daemon TrexDaemon.cpp(10941) : all instances in runlevel 4 stopped
Any ideas that can justify this HANA db shutdown?
Thanks
mdias