We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
mloginfo should report the host name extracted from the logs
unknown
Run on a log file starting with:
2020-09-07T19:00:36.263+0100 I CONTROL [conn71088] pid=55156 port=27120 64-bit host=xyz10498n01
output starts with:
(base) [nic:~/Downloads/xyz]$ mloginfo --clients xyz/* source: xyz/server_mongosd.log.2020-09-06T08-00-40 host: unknown start: 2020 Sep 05 09:00:17.976 end: 2020 Sep 06 09:00:40.003 date format: iso8601-local
The text was updated successfully, but these errors were encountered:
I think it's this line:
mtools/mtools/util/logfile.py
Line 348 in 59b0233
There's no "starting" in the 3.6 logs. How about
if ln == 0 or "starting :" in line or "starting:" in line: ``
Sorry, something went wrong.
There's no "starting" in the 3.6 logs.
@niccottrell The "starting" match is looking for known restarts, which is still correct for 3.6 (normally from an initandlisten thread).
However, the alternative example you found works as a fall back for finding the host and port details from another thread.
The current match checks even if the hostname is already set, but since only one hostname is reported I'll only check if hostname isn't already set.
Cheers, Stennie
Fix rueckstiess#819: mloginfo reports host name as unknown for 3.6 logs
2649a88
1df4773
stennie
No branches or pull requests
Expected behavior
mloginfo should report the host name extracted from the logs
Actual/current behavior
unknown
Steps to reproduce the actual/current behavior
Run on a log file starting with:
output starts with:
Environment
The text was updated successfully, but these errors were encountered: