You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
According to documentation the memlock should be set to 102400 bytes:
@realtime soft memlock 102400
@realtime hard memlock 102400
With such settings however, when starting controller manager following warning appears:
[controller_manager]: Unable to lock the memory: 'No proper privileges to lock the memory!'
If I change the limits to "unlimited", then the warning doesn't appear. Looks like the controller_manager is trying to lock memory with a greater value than 102400 bytes (higher than "hard" memlock value).
I've tested it also in docker with "docker way" of setting ulimits and the result is the same. Warning appears for value 102400 and not when "unlimited".
To Reproduce
Steps to reproduce the behavior:
Adjust limits in /etc/security/limits.conf
Run controller manager
Warning appears
Expected behavior
No warning, memory locked properly.
Environment:
OS: Ubuntu
Version: Humble (latest apt release)
RPi 4 with custom real-time kernel
The text was updated successfully, but these errors were encountered:
Describe the bug
According to documentation the memlock should be set to 102400 bytes:
With such settings however, when starting controller manager following warning appears:
If I change the limits to "unlimited", then the warning doesn't appear. Looks like the controller_manager is trying to lock memory with a greater value than 102400 bytes (higher than "hard" memlock value).
I've tested it also in docker with "docker way" of setting ulimits and the result is the same. Warning appears for value 102400 and not when "unlimited".
To Reproduce
Steps to reproduce the behavior:
/etc/security/limits.conf
Expected behavior
No warning, memory locked properly.
Environment:
The text was updated successfully, but these errors were encountered: