-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
regular/sshserver.go errors after v2.4.2 -> v2.5.1 upgrade #1785
Milestone
Comments
This is a not a real error, although it's being reported as one, we will suppress it, but it's not an indication of a problem. |
klizhentas
added a commit
that referenced
this issue
Mar 18, 2018
fixes #1785, fixes #1776 This commit fixes several issues with output: First teleport start now prints output matching quickstart guide and sets default console logging to ERROR. SIGCHLD handler now only collects processes PID forked during live restart to avoid confusing other wait calls that have no process status to collect any more.
klizhentas
added a commit
that referenced
this issue
Mar 19, 2018
fixes #1785, fixes #1776 This commit fixes several issues with output: First teleport start now prints output matching quickstart guide and sets default console logging to ERROR. SIGCHLD handler now only collects processes PID forked during live restart to avoid confusing other wait calls that have no process status to collect any more.
klizhentas
added a commit
that referenced
this issue
Mar 20, 2018
fixes #1785, fixes #1776 This commit fixes several issues with output: First teleport start now prints output matching quickstart guide and sets default console logging to ERROR. SIGCHLD handler now only collects processes PID forked during live restart to avoid confusing other wait calls that have no process status to collect any more.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened:
Stream of errors every few minutes in systemd logs for teleport:
Using teleport config file:
What you expected to happen:
Didn't expect these errors.
How to reproduce it (as minimally and precisely as possible):
Upgraded cluster from v2.4.2 -> v2.5.1
Environment:
teleport version
): Teleport v2.5.1tsh version
): N/ABrowser environment
Relevant Debug Logs If Applicable
The text was updated successfully, but these errors were encountered: