SAP Knowledge Base Article - Preview

2416236 - diserver service not starting up

Symptom

After a database restart the Diserver Service is failing with exception "byte buffer type exception" or

FAIL: process hdbdiserver HDB Deployment Infrastructure Server not running

The diserver_xxx.xxx.xxx.trc file shows errors similar to the following:

[17286]{-1}[-1/-1] 2016-12-22 09:48:49.344369 i Basis TraceStream.cpp(00467) : ==== Starting hdbdiserver, version 1.00.122.02.1473345179 (fa/hana1sp12), build linuxx86_64 193a1de893026bf71edc22c2740876969115221c 2016-09-08 16:38:55 ld7272 gcc (SAP release 20151217, based on SUSE gcc48-4.8.5-24.1) 4.8.5
[17286]{-1}[-1/-1] 2016-12-22 09:48:49.344387 i Basis TraceStream.cpp(00469) : MaxOpenFiles: 1048576
[17286]{-1}[-1/-1] 2016-12-22 09:48:49.344392 i Basis TraceStream.cpp(00471) : Server Mode: L2 Delta
[17286]{-1}[-1/-1] 2016-12-22 09:48:49.344417 i Basis ProcessorInfo.cpp(00781) : Using GDT segment limit to determine current CPU ID
[17286]{-1}[-1/-1] 2016-12-22 09:48:49.344418 i Basis Timer.cpp(00642) : Using RDTSC for HR timer
[17286]{-1}[-1/-1] 2016-12-22 09:48:49.344419 i Memory AllocatorImpl.cpp(00481) : Allocators activated
[17286]{-1}[-1/-1] 2016-12-22 09:48:49.344421 i Memory AllocatorImpl.cpp(00497) : Using big block segment size 67108864
[17286]{-1}[-1/-1] 2016-12-22 09:48:50.950756 i HANA_DI_DISERVER HDIServer.cpp(00118) : waitForMasterIndexserver(): Found active master indexserver xxx:xxx
[17286]{-1}[-1/-1] 2016-12-22 09:48:51.095915 i HANA_DI_DISERVER ServerInitialization.cpp(00104) : Initializing HANA DI server...
[17286]{-1}[-1/-1] 2016-12-22 09:48:51.095943 i HANA_DI_DISERVER ServerInitialization.cpp(00106) : Current build version = '1.00.122.02.1473345179'
[17286]{-1}[-1/-1] 2016-12-22 09:48:51.095947 i HANA_DI_DISERVER ServerInitialization.cpp(00107) : Current _SYS_DI version = '5'
[17286]{-1}[-1/-1] 2016-12-22 09:48:51.227154 i HANA_DI_DISERVER ServerInitialization.cpp(00111) : Last installed build version = '1.00.122.02.1473345179'
[17286]{-1}[-1/-1] 2016-12-22 09:48:51.286183 e RemoteEAPI RequestSenderImpl.cpp(00286) : failed to handle request at remote=xxx:xxx: exception 1: no.70012027 (TrexNet/BufferedIO.cpp:5044)
ltt exception in thread 53227: exception 1: no.70000000 (TRexUtils/ByteBuffer.h:380)
byte buffer type exception
exception throw location:
1: 0x00007fee8991eb3f in TRexUtils::TypeException::TypeException(char const*, int)+0x3b at ByteBuffer.h:45 (libhdbbasement.so)
2: 0x00007fee899232ee in TRexUtils::BasicByteBuffer<unsigned char>::operator>>(unsigned long&)+0x2ca at ByteBuffer.h:380 (libhdbbasement.so)
3: 0x00007fee97fef44f in planvizCS::PlanVizContextConfig::PlanVizContextConfig(TRexUtils::Deserializer&)+0x1b at PlanVizContextConfig.cpp:69 (libhdbplanviz.so)
4: 0x00007fee97fda316 in planvizCS::PlanVizContext::PlanVizContext(ltt::allocator&, TRexUtils::Deserializer&, bool, bool)+0x62 at PlanVizContext.cpp:188 (libhdbplanviz.so)
5: 0x00007fee97fda4c2 in planvizCS::PlanVizContext::createFromClient(TRexUtils::Deserializer&, ltt::smartptr_handle<Execution::PlanVizContext>&)+0x60 at PlanVizContext.cpp:115 (libhdbplanviz.so)
6: 0x00007fee89b1e63a in planvizCS::CallbackFunctions::deserializeFromClient(TRexUtils::Deserializer&, ltt::smartptr_handle<Execution::PlanVizContext>&)+0x36 at PlanVizCallback.cpp:125 (libhdbbasement.so)
7: 0x00007fee89ae2974 in TRexUtils::TraceContextSerializer::deserializeFromClient(TRexUtils::Deserializer&, Execution::TraceContext&)+0x900 at TraceContext.cpp:240 (libhdbbasement.so)
8: 0x00007fee89942326 in TrexNet::handleInheritableLocalStorage(TRexUtils::BasicByteBuffer<unsigned char>*, TrexTrace::PerformanceTraceId*, TrexNet::RequestOrigin*)+0x4a2 at Request.cpp:1333 (libhdbbasement.so)
9: 0x00007fee899438dd in TrexNet::Request::readHeader(TrexNet::Channel*, bool)+0xa69 at Request.cpp:1561 (libhdbbasement.so)
10: 0x00007fee89981bf4 in TrexService::WorkerThread::run(void*)+0x350 at Request.h:531 (libhdbbasement.so)
11: 0x00007fee899a03ea in TrexThreads::PoolThread::run()+0x836 at PoolThread.cpp:389 (libhdbbasement.so)
12: 0x00007fee899a1e70 in TrexThreads::PoolThread::run(void*&)+0x10 at PoolThread.cpp:165 (libhdbbasement.so)
13: 0x00007fee88610ce7 in Execution::Thread::staticMainImp(void**)+0x733 at Thread.cpp:462 (libhdbbasis.so)
14: 0x00007fee886122d8 in Execution::Thread::staticMain(void*)+0x34 at ThreadMain.cpp:26 (libhdbbasis.so)

or

[28558]{-1}[-1/-1] 2017-08-09 15:05:47.984140 e HANA_DI_DISERVER HDIServer.cpp(00203) : startup(): Initializing HDIServer in HDIServer::started() failed with exception 'exception  1: no.8201003  (hdi/db/impl/eapidb/EAPIDB.cpp:976)
    Database error 591: : ProtocolException at network layer:
  message: a protocol mismatch occurred


Read more...

Environment

HANA 1.0

Product

SAP HANA 1.0, platform edition

Keywords

diserver, HDI, Deployment Infrastructure, M_TOPOLOGY_TREE, HANA_DI_DISERVER, HDIServer.cpp, 8201003, HDIServer. EAPIDB.cpp , KBA , HAN-DB-DI , SAP HANA DI (HDI): diserver, HDI plugins& client libs , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.