SAP Knowledge Base Article - Preview

2920719 - Landscape continuously crashes after being restarted - SAP Data Hub

Symptom

  • Opening Vora Tools shows no tables or schema.

  • The vora-landscape pod shows status 'CrashLoopBackOff' in kubernetes. The vora-landscape log shows the server crashes with return code -9:

Traceback (most recent call last):
File "/dqp/python/dqp_utils.py", line 311, in _stop_process
*args, **kwargs)
File "/dqp/common/elvis_common/process_utils.py", line 267, in _stop_process
dump_debug_information=True)
File "/dqp/common/elvis_common/process_utils.py", line 283, in _error
raise RuntimeError(msg)
RuntimeError: Process /dqp/bin/v2landscape_server ended with return code -9

  • The 'describe' output for the vora-landscape pod shows the is 'OOMKilled':

State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: OOMKilled
Exit Code: 247


Read more...

Environment

SAP Data Hub 2.7

Product

SAP Data Hub 2.0

Keywords

landscape, OOM, out-of-memory, restart, vora-tools , KBA , EIM-DH , SAP Data Hub: Please use CA-DI instead. , Problem

About this page

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

Search for additional results

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