exiting - failed to create process due to low system resources, errno(11)
Article ID: 100054512
Updated On:
Description
Error Message
One or more of the following errors will be reported in the applicable resource log. i.e. DiskGroup_A.l.og, NIC_A.log etc.
2022/11/07 21:43:37 VCS ERROR V-16-2-13469 Thread(139941547460352) Agent(Application) exiting - failed to create process due to low system resources, errno(11)
2022/11/15 13:26:06 VCS WARNING V-16-1-13162 Could not create thread
2022/11/12 18:18:03 VCS INFO V-16-2-13716 Thread(140700412692224) Resource(dg_xxxxx): Output of the completed operation (monitor)
==============================================
/opt/VRTSvcs/bin/ag_i18n_inc.sh: fork: retry: No child processes
==============================================
==============================================
2022/11/12 18:23:17 VCS INFO V-16-2-13716 Thread(140700412692224) Resource(dg_xxxxx): Output of the completed operation (monitor)
==============================================
/opt/VRTSvcs/bin/ag_i18n_inc.sh: fork: retry: Resource temporarily unavailable
Cause
Suse 12 SP2 appears to have changed the default value for the parameter DefaultTasksMax to 512. This can be verified with the following command:
systemctl show --property DefaultTasksMax
This is insufficient to start anything other than a small number VCS agents and resources simultaneously. This behaviour has not been observed in Suse 15 where the default setting is much higher.
Resolution
Increase the value for the parameter DefaultTasksMax.
Please consult the following Suse knowledge article for the steps to modify this value:
How to modify systemd DefaultTasksMax / TasksMax / UserTasksMax settings
Although Veritas does not have a specific recommendation, no issues have been reported with the default value in Suse 15 of 4915.
Issue/Introduction
