Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid size of memlock #2020

Open
KmakD opened this issue Jan 29, 2025 · 0 comments
Open

Invalid size of memlock #2020

KmakD opened this issue Jan 29, 2025 · 0 comments
Labels

Comments

@KmakD
Copy link

KmakD commented Jan 29, 2025

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:

  1. Adjust limits in /etc/security/limits.conf
  2. Run controller manager
  3. Warning appears

Expected behavior
No warning, memory locked properly.

Environment:

  • OS: Ubuntu
  • Version: Humble (latest apt release)
  • RPi 4 with custom real-time kernel
@KmakD KmakD added the bug label Jan 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant