SAP Knowledge Base Article - Preview

3793375 - Microsoft Azure: saptune fails to start after reboot due to cloud-init 25.1.3

Symptom

  • saptune.service is inactive or fails to start after a system reboot.
  • SAP kernel and operating system tuning parameters managed by saptune are not reapplied during boot. As a result, vm.max_map_count reverts to the default value of 65530 instead of the previously configured value.
  • Applications or databases that require a higher vm.max_map_count value may fail to start or experience startup issues after the reboot.
  • The issue is typically observed after rebooting an Azure virtual machine.


Read more...

Environment

  • SUSE Linux Enterprise Server for SAP Applications 12 SP5
  • SUSE Linux Enterprise Server for SAP Applications 15 SP4
  • SUSE Linux Enterprise Server for SAP Applications 15 SP5
  • SUSE Linux Enterprise Server for SAP Applications 15 SP6
  • SUSE Linux Enterprise Server for SAP Applications 15 SP7
  • SUSE Linux Enterprise Server for SAP Applications 16.0
  • SUSE Linux Enterprise Server 16.0

Product

SAP NetWeaver all versions

Keywords

dependency loop, boot ordering, sysctl persistence, Linux VM, SUSE for SAP, HANA prerequisites, unit dependency, VM resize, post-boot configuration, daemon order, service orchestration, parameter persistence, init sequence, target conflicts, boot remediation , KBA , BC-OP-LNX-SUSE , SUSE Linux , Known Error

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.