Failed to ssh | fork: Cannot allocate memory
This document (000020875) is provided subject to the disclaimer at the end of this document.
bash: fork: Cannot allocate memory
2- Once it is booted, then check the "saptune" status.
This is saptune_check v0.2.2. It verifies if saptune is set up correctly. Please keep in mind: - This tool does not check, if the tuning itself works correctly. - Follow the hints from top to down to minimize side effects. Checking saptune ================ [NOTE] saptune package has version 3.0.2 [WARN] System is in status "degraded". Failed services are: saprouter.service saptune.service -> Check the cause and reset the state with 'systemctl reset-failed'! [FAIL] Configured saptune version is 1 -> Misconfiguration happened or an update went wrong! This needs to be investigated. [ OK ] sapconf.service is inactive [ OK ] sapconf.service is disabled [FAIL] saptune.service is failed -> Run 'systemctl start saptune.service', 'saptune service start' or 'saptune service takeover'. [ OK ] saptune.service is enabled [NOTE] tuned profile is 'missing' [ OK ] tuned.service is inactive [ OK ] tuned.service is disabled 1 warning(s) have been found. 2 error(s) have been found. Saptune will not work properly!
3- reinstall saptune version 3 (ex: the target version is saptune-3.0.2-4.10.1.x86_64)
# zypper install --force saptune-3.0.2-4.10.1
For further information about saptune, kindly, check this link:https://github.com/SUSE/saptune
This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:000020875
- Creation Date: 27-Nov-2022
- Modified Date:12-Dec-2022
- SUSE Linux Enterprise Server for SAP Applications
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com