Symptom
The SAP HANA indexserver (port 30003) crashed unexpectedly after its self-watchdog detected the PID lock file was missing, triggering an unplanned shutdown and interrupting Hana Startup
Indexserver_xxxx.30003.017.trc
[2983036]{-1}[-1/-1] f self_watchdog SelfWatchdog.cpp(00412) : Could not access /usr/sap/xxxx/HDB00/xxxx/lock/hdbindexserver@30003.pid: 2 (No such file or directory)
[2983036]{-1}[-1/-1] f self_watchdog SelfWatchdog.cpp(00130) : process is terminating, because lockfile '/usr/sap/xxxx/HDB00/xxxx/lock/hdbindexserver@30003.pid' is missing/wrong.
[2983027]{-1}[-1/-1] i Service_Shutdown TrexService.cpp(00623) : Preparing for shutting service down
[2985384]{-1}[-1/-1] i Service_Shutdown TREXIndexServer.cpp(02466) : Preparing to shutdown
[2985384]{-1}[-1/-1] i Service_Shutdown TREXIndexServer.cpp(02529) : Stopping data backup
indexserver_alert_xxxx.trc
[2983036]{-1}[-1/-1] f self_watchdog SelfWatchdog.cpp(00412) : Could not access /usr/sap/xxxx/HDB00/xxxx/lock/hdbindexserver@30003.pid: 2 (No such file or directory)
[2983036]{-1}[-1/-1] f self_watchdog SelfWatchdog.cpp(00130) : process is terminating, because lockfile '/usr/sap/xxxx/HDB00/xxxx/lock/hdbindexserver@30003.pid' is missing/wrong.
Read more...
Environment
SAP Hana Platform Edition 2.0
Product
Keywords
hana not starting, indexserver pid file missing, lock directory missing, trace directory missing, rc=2 no such file or directory, self watchdog termination, disk replacement, empty mount, instance directory structure, /usr/sap, /hana/data, nameserver fails, daemon fails, startup failure, filesystem mount verification , KBA , HAN-LM-INS-SAP , Installation of SAP Systems on HANA , HAN-DB , SAP HANA Database , 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.
SAP Knowledge Base Article - Preview