SAP HANA indexserver on host was restarted

[former_member247896]

Dear Experts,

I am facing following issues in our HANA database :

on the Alerts tab in HANA studion, I can see following error :

I went through some SAP notes and forums, I can see the following in the trace files :

file: deamon_<hostname>.30000.000.trc

NetworkConnection.cpp(00122) : Connection from 127.0.0.1/28158_tcp over socket 9 handled message of type "started", shall return 6 bytes [737]{-1}[-1/-1] 2017-04-03 13:35:08.781490 i Daemon NetworkListener.cpp(01207) : finishing connection channel 9 [0x00007fc57c1fba48] {refCnt=1} 127.0.0.1/30000_tcp->127.0.0.1/28158_tcp Connected,[----] [737]{-1}[-1/-1] 2017-04-03 13:35:08.781500 i Daemon NetworkListener.cpp(01220) : closing connection finished channel 9 [0x00007fc57c1fba48] {refCnt=1} 127.0.0.1/30000_tcp->127.0.0.1/28158_tcp Connected,[----] [737]{-1}[-1/-1] 2017-04-03 13:35:08.781502 i Daemon NetworkConnection.cpp(00152) : closing connection channel, state FINISHED 9 [0x00007fc57c1fba48] {refCnt=1} 127.0.0.1/30000_tcp->127.0.0.1/28158_tcp Connected,[----] [737]{-1}[-1/-1] 2017-04-03 13:36:51.454891 i Daemon TrexDaemon.cpp(04332) : process hdbindexserver with pid 9855 exited because it caught signal 6

file: indexserver_<hostname>.30003.crashdump.<date>.trc

[CRASH_SHORTINFO] Exception short info: (2017-04-03 13:36:50 277 Local) SIGNAL 6 (SIGABRT) caught, sender PID: 9855, PID: 9855, thread: 2943[thr=9859]: CrashWatchThread, value int: 0, ptr: 0x0000000000000000, time: 2017-04-03 13:36:50 000 Local [OK]

This leads to following shortdumps in st22 in application server :

and

Telnet from application server to 30015 port works fine, this dumps are only created while indexserver restarts.

Also port 30015 listens on the database side.

My HANA version : 1.00.12100

Do you have any idea, or hint why this error in HANA occurs? I am facing the issue for two weeks already without solution.

I will be really thankful for any advise.

Thank you very much in advance,

Cheers,

Jan Masar

[former_member247896 · Accepted solution]

Hi all, update :

Issue fixed with upgrade of database to latest revision - 1.00.122.08.1490178281

Cheers,

JM