-
Notifications
You must be signed in to change notification settings - Fork 44
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
Prevent log spew when username/password doesn't exist in /etc/passwd #286
Comments
Reading the issue I think it makes sense not to print the error messages since there are valid use cases that triggered them. @AlexGraberTilton would you mind sending a PR against Thanks! |
Signed-off-by: Alexander Graber-Tilton <[email protected]>
Remove no username error messages (#286)
Thanks so much for the PR, @AlexGraberTilton . The change should be propagated to newer branches when we forward port them, usually every some weeks. |
Closed via #291 |
This pull request has been mentioned on Gazebo Community. There might be relevant details there: https://community.gazebosim.org/t/new-ignition-releases-2022-03-25-fortress-edifice-citadel/1343/1 |
Desired behavior
Please stop the spew of "Error getting username: no matching password record.\n"
This occurs in NetUtils.cc
In commit 09723c4, there were changes to username retrieval
In the case of no username in the /etc/passwd, the username is set to "error-" + uuid.ToString()
However the error messages introduced in the change cause log spew when no username exists.
The spew causes the console log to be essentially useless, despite the fact that the system still works fine.
One major use case that this impacts is running with the OSRF gazebo docker containers using --user uid:gid
since /etc/passwd does not have the user in such a scenario, the error message repeats endlessly.
Alternatives considered
Implementation suggestion
remove the error message when getpwuid_r passes but the rule is nullptr
backport to 7+
The text was updated successfully, but these errors were encountered: