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

chore(logger): Update error message when we dont find any log messages #43

Merged
merged 1 commit into from
Apr 15, 2016

Conversation

jchauncey
Copy link
Member

No description provided.

@arschles
Copy link
Member

Fixes #42 (incidentally)

To get the service ip you can do the following: kubectl get svc deis-logger --namespace=deis`, appID)
2) The application is writing logs to the logger component.
3) Check that an entry in the ring buffer was created by checking the logger pod logs: kubectl logs <logger pod> --namespace=deis
4) Making sure that the container logs were mounted properly into the fluentd pod: kubectl exec <fluentd pod> --namespace=deis ls /var/log/containers`, appID)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is there a simple way to indicate what to look for in the above two sets of logs?

@jchauncey jchauncey force-pushed the update-logger-message branch 3 times, most recently from 0c8d60a to 87e1556 Compare April 15, 2016 18:34
@jchauncey
Copy link
Member Author

Heres what it looks like -

╰─± deis logs
Error: There are currently no log messages. Please check the following things:
1) Logger and fluentd pods are running.
2) The application is writing logs to the logger component by checking that an entry in the ring buffer was created: kubectl logs <logger pod> --namespace=deis
3) Making sure that the container logs were mounted properly into the fluentd pod: kubectl exec <fluentd pod> --namespace=deis ls /var/log/containers

@jchauncey jchauncey merged commit 5e76fc6 into deis:master Apr 15, 2016
@jchauncey jchauncey deleted the update-logger-message branch April 15, 2016 18:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants