Bug 3274 - Make MaxStartup errors/warnings appear at the INFO log level
Summary: Make MaxStartup errors/warnings appear at the INFO log level
Status: CLOSED FIXED
Alias: None
Product: Portable OpenSSH
Classification: Unclassified
Component: sshd (show other bugs)
Version: -current
Hardware: All All
: P5 enhancement
Assignee: Assigned to nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-03-10 00:00 AEDT by John Devitofranceschi
Modified: 2021-04-23 15:00 AEST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Devitofranceschi 2021-03-10 00:00:11 AEDT 
In a recent debugging session with one of my users on a very busy server, we only discovered that we needed to tune MaxStatups after increasing the LogLevel setting to VERBOSE.

I would think that this kind of condition warrants reporting at the default LogLevel (INFO).  It would have shaved a few days off of the debugging process in our case if this had been the case.

Thank you for your consideration in this matter.
Comment 1 Darren Tucker 2021-03-10 00:29:35 AEDT 
What version did you see that with?  There was a change to improve the logging that shipped in 8.4 (bug#3055, commithttps://github.com/openssh/openssh-portable/commit/9c5f64b6c)
Comment 2 Damien Miller 2021-03-12 14:50:44 AEDT 
Yes, there is ample MaxStartups logging at info/error level now, specifically whenever MaxStartups starts or stops throttling and periodically while in this condition.

see https://github.com/openssh/openssh-portable/commit/9c5f64b6c
Comment 3 Damien Miller 2021-04-23 15:00:26 AEST 
closing resolved bugs as of 8.6p1 release