litespeedtech / litespeedtech/lsmcd
LogLevel not being honored
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 39
- Forks
- 18
- PR merge metrics
- No merged PRs in 30d
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with /usr/local/lsmcd/conf/node.conf and the LogLevel=notice and LogFile=/tmp/lsmcd.log settings. Reproduce the behavior using the reported lsmcdctrl stop, cleanup, and start commands, then trace why the ERROR message is emitted and how the attempted root user can be identified. Done means the log-level behavior and user identity are explained or corrected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- authentication, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100