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

pod goes in CrashLoopBackOff. not enough logs for troubleshooting #67

Open
sdputurn opened this issue Jun 3, 2021 · 0 comments
Open

Comments

@sdputurn
Copy link

sdputurn commented Jun 3, 2021

we deployed this app in multiple clusters. it working in most of the cluster except few where the pod is getting into CrashLoopBackOff.

when check the logs where we have issue, we just see 2 lines like below:
I0603 07:49:48.723928 1 secure_serving.go:116] Serving securely on [::]:443
time="2021-06-03T07:49:48Z" level=info msg="Using OpenStack Keystone at https://identity.xxxx.internal.cloud/v3/"

in all working cluster we are seeing logs like:
I0602 06:49:10.671035 1 secure_serving.go:116] Serving securely on [::]:443
time="2021-06-02T06:49:10Z" level=info msg="Using OpenStack Keystone at https://identity.xxxx.internal.cloud/v3/"
time="2021-06-02T06:49:10Z" level=info msg="Found OpenStack Designate service at https://dns.xxx.internal.cloud/"

is there the way to get debug level logs? not able to get for what reason the pod is not progressing in cluster having issues.

thanks,
Sandeep

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

No branches or pull requests

1 participant