Skip to content
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

teleport start default output #1776

Closed
kontsevoy opened this issue Mar 14, 2018 · 2 comments · Fixed by #1790
Closed

teleport start default output #1776

kontsevoy opened this issue Mar 14, 2018 · 2 comments · Fixed by #1790
Assignees

Comments

@kontsevoy
Copy link
Contributor

kontsevoy commented Mar 14, 2018

Problem 1

Our quickstart promises this output:

$ mkdir -p /var/lib/teleport
$ sudo teleport start

[AUTH]  Auth service is starting on 0.0.0.0:3025
[PROXY] Reverse tunnel service is starting on 0.0.0.0:3024
[PROXY] Web proxy service is starting on 0.0.0.0:3080
[PROXY] SSH proxy service is starting on 0.0.0.0:3023
[SSH]   Service is starting on 0.0.0.0:3022

Notice the absence of --debug flag.
2.5 is giving this:

WARN [PROCESS]   No TLS Keys provided, using self signed certificate. service/service.go:1474
WARN [AUTH]      Parameter advertise_ip is not set for this auth server. Trying to guess the IP this server can be reached at: 192.168.122.1:3025. service/service.go:684

Problem 2

$ tctl users add ekontsevoy
user "User(name=ekontsevoy, roles=[], identities=[])" already exists

Should be "user ekontsevoy already exists"

Proposal

  • When in "zero-configuration mode" (i.e. no YAML config provided) Teleport should start with ERROR log level (so those warnings won't confuse first-timers).
  • Default stderr output should be as before.
  • Make the warning more readable / less verbose for advertise_ip (Ev: I'll update the text myself)
@kontsevoy kontsevoy self-assigned this Mar 14, 2018
@kontsevoy kontsevoy added this to the 2.5.1 "Portland" milestone Mar 14, 2018
@klizhentas
Copy link
Contributor

Also provide more progress during migrations of the sessions, to let admins know about what's actually going on.

@kontsevoy
Copy link
Contributor Author

@klizhentas I've fixed "problem 2", removing myself from assigness.

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
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants