LogLevel not being honored

[rakotak]

Setting LogLevel=notice to /usr/local/lsmcd/conf/node.conf is not honored and the /tmp/lsmcd.log still gets bombarded by ERROR messages such as

2021-11-06 21:54:03.636 [ERROR] [__root] Successful SASL authentication not performed

Relevant conf lines:

LogLevel=notice LogFile=/tmp/lsmcd.log

Restarted lsmcd by

/usr/local/lsmcd/bin/lsmcdctrl stop rm -rf /dev/shm/lsmcd /usr/local/lsmcd/bin/lsmcdctrl start

Can you tell me why are ERROR messages getting included in the log and how to discern what user is trying to run as root

Thanks in advance.

[rperper]

Hi, Actually, there is no way to suppress error messages. LogLevel=notice will include notice, warning and error. However, your point about successful SASL authentication being an error message is fair. That is too high a level for a normal operation message. A fair log level for those messages in my mind would be debug level. So we'll do it that way for the next release.

That is just showing you that the daemon is running as root, which is also normal. The current version of lsmcd (1.4.29) does not log that any more, it logs in brackets the PID of the worker that processes the request, as the user is constant. Its just a message that a login for any user failed. If you'd like we could make the message a notice message and display the failed user name, if you think that would be helpful. That way you could suppress the messages by setting the loglevel for warning.

Thanks,

Bob

[rakotak]

Hello,

I actually managed to pinpoint the actual user generating the messages by stracing the lsmcd pid and the client's site was there just before the error message, however what you are suggesting would be very helpful indeed. Thanks!

[rperper]

If you'll validate it, I'll release it sooner. Just need someone in the field to take a look at it and make sure they're happy. Thanks,

Bob