[SERVER-37435] Improve mlock error log message Created: 03/Oct/18  Updated: 29/Oct/23  Resolved: 24/Oct/18

Status: Closed
Project: Core Server
Component/s: Admin, Logging
Affects Version/s: None
Fix Version/s: 4.1.5

Type: Improvement Priority: Minor - P4
Reporter: Dmitry Agranat Assignee: Patrick Freed
Resolution: Fixed Votes: 1
Labels: neweng
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on DOCS-12119 Create dochub link for unable to mloc... Closed
Related
related to SERVER-28997 Limit SCRAM-SHA-1 Cache's use of Secu... Closed
Backwards Compatibility: Fully Compatible
Sprint: Security 2018-10-22, Security 2018-11-05
Participants:

 Comments   
Comment by Githook User [ 24/Oct/18 ]

Author:

{'name': 'Patrick Freed', 'email': 'patrick.freed@mongodb.com', 'username': 'patrickfreed'}

Message: SERVER-37435 Improve mlock error log message
Branch: master
https://github.com/mongodb/mongo/commit/83f9e4f24a7ad3172d082f733d65b4e7f1295b2f

Comment by Spencer Jackson [ 19/Oct/18 ]

We should use a DocHub link for this, Docs has reserved us: http://dochub.mongodb.org/core/cannot-allocate-locked-memory

Comment by Dmitry Agranat [ 03/Oct/18 ]

Today, we print the following message:

2018-08-11T22:11:18.037+0800 F - [conn1275] Failed to mlock: Unknown error
2018-08-11T22:11:18.037+0800 F - [conn1275] Fatal Assertion 28832 at src/mongo/base/secure_allocator.cpp 246

This error is not very useful for our users as it's not clear and not actionable.

It will be useful to print this instead:

2018-08-11T22:11:18.037+0800 F - [conn1275] Failed to mlock: Cannot allocate locked memory. For more details see: https://docs.mongodb.com/manual/reference/ulimit/index.html#unix-ulimit-settings
2018-08-11T22:11:18.037+0800 F - [conn1275] Fatal Assertion 28832 at src/mongo/base/secure_allocator.cpp 246

Generated at Thu Feb 08 04:45:59 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.