SAP Knowledge Base Article - Preview

2863626 - vsystem pod failed to start with error 'start-di failed with ResourceRequest timed out|vsystem-xxx-xxx'


  • The problem happens after SAP Data Hub is upgraded to 2.7.
  • Vsystem is down with following error message:
    |+0000|INFO |Starting app in direct exec mode|vsystem-xxx-xxx
    |+0000|INFO |Get HANA credentials from environment for direct execution|vsystem-xxx-xxx
    |+0000|INFO |Got hana-credentials from environment|vsystem-xxx-xxx
    |+0000|INFO |Starting the diserver on the HANA database...|vsystem-xxx-xxx
    |+0000|ERROR|start-di failed with ResourceRequest timed out|vsystem-xxx-xxx, just checking it
  • Restart hana-0 pod and it's failed with error below (log of hana-0 pod):
    Finished execution of hook /hana/hooks/pre_start/330_custom_afls (exit code 0)
    Finished execution of hooks in folder /hana/hooks/pre_start
    Finished pre start sequence
    Starting up HANA ...
    Waiting for HANA to finish start up ...
    ERROR: Unexpected shutdown of hdbdaemon detected. HANA did not come up :-/ ...
  • check hana-0 filesystem with the following command: 'kubectl exec -it hana-0 -n <DataHubNamespace> -c hana -- df -h /hana/mounts/trace', it shows trace disk got full.
    df -h /hana/mounts/trace
    Filesystem      Size  Used Avail Use% Mounted on
    /dev/xxx        xx G  xx G     0 100% /hana/mounts/trace



  • SAP Data Hub 2.7 


SAP Data Hub 2.0


start-di, hana-0, hdbdaemon , 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.