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

cluster up: print last 10 lines of logs on errors after container started #9256

Merged
merged 1 commit into from
Jun 10, 2016

Conversation

csrwng
Copy link
Contributor

@csrwng csrwng commented Jun 9, 2016

improves logging for unexplained errors after server has started

@csrwng
Copy link
Contributor Author

csrwng commented Jun 9, 2016

@gabemontero ptal

@smarterclayton
Copy link
Contributor

Sample output?

@csrwng
Copy link
Contributor Author

csrwng commented Jun 9, 2016

Sample output:

$ oc cluster up
-- Checking Docker client ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:latest image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ...
   Using nsenter mounter for OpenShift volumes
-- Checking Docker version ... OK
-- Creating volume share ... OK
-- Finding server IP ...
   Using 192.168.64.27 as the server IP
-- Starting OpenShift container ...
   Creating initial OpenShift configuration
   Starting OpenShift using container 'origin'
   Waiting for API server to start listening
FAIL
   Error: cannot access master readiness URL https://192.168.64.27:8443/healthz/ready
   Details:
     Last 10 lines of "origin" container log:
     I0609 17:51:32.204655   23441 master.go:269] Started Web Console 0.0.0.0:8443/console/
     I0609 17:51:32.204662   23441 master.go:269] Started Swagger Schema API at 0.0.0.0:8443/swaggerapi/
     I0609 17:51:32.314069   23441 ensure.go:224] No cluster policy found.  Creating bootstrap policy based on: /var/lib/origin/openshift.local.config/master/policy.json
     I0609 17:51:33.618001   23441 ensure.go:209] Created default security context constraint privileged
     I0609 17:51:33.621442   23441 ensure.go:209] Created default security context constraint nonroot
     I0609 17:51:33.625630   23441 ensure.go:209] Created default security context constraint hostmount-anyuid
     I0609 17:51:33.628949   23441 ensure.go:209] Created default security context constraint hostaccess
     I0609 17:51:33.631646   23441 ensure.go:209] Created default security context constraint restricted
     I0609 17:51:33.634807   23441 ensure.go:209] Created default security context constraint anyuid
     I0609 17:51:33.637186   23441 ensure.go:209] Created default security context constraint hostnetwork

@smarterclayton
Copy link
Contributor

Is that an actual error or just synthetic?

On Thu, Jun 9, 2016 at 2:16 PM, Cesar Wong [email protected] wrote:

Sample output:

$ oc cluster up
-- Checking Docker client ... OK
-- Checking for existing OpenShift container ... OK
-- Checking for openshift/origin:latest image ... OK
-- Checking Docker daemon configuration ... OK
-- Checking for available ports ... OK
-- Checking type of volume mount ...
Using nsenter mounter for OpenShift volumes
-- Checking Docker version ... OK
-- Creating volume share ... OK
-- Finding server IP ...
Using 192.168.64.27 as the server IP
-- Starting OpenShift container ...
Creating initial OpenShift configuration
Starting OpenShift using container 'origin'
Waiting for API server to start listening
FAIL
Error: cannot access master readiness URL https://192.168.64.27:8443/healthz/ready
Details:
Last 10 lines of "origin" container log:
I0609 17:51:32.204655 23441 master.go:269] Started Web Console 0.0.0.0:8443/console/
I0609 17:51:32.204662 23441 master.go:269] Started Swagger Schema API at 0.0.0.0:8443/swaggerapi/
I0609 17:51:32.314069 23441 ensure.go:224] No cluster policy found. Creating bootstrap policy based on: /var/lib/origin/openshift.local.config/master/policy.json
I0609 17:51:33.618001 23441 ensure.go:209] Created default security context constraint privileged
I0609 17:51:33.621442 23441 ensure.go:209] Created default security context constraint nonroot
I0609 17:51:33.625630 23441 ensure.go:209] Created default security context constraint hostmount-anyuid
I0609 17:51:33.628949 23441 ensure.go:209] Created default security context constraint hostaccess
I0609 17:51:33.631646 23441 ensure.go:209] Created default security context constraint restricted
I0609 17:51:33.634807 23441 ensure.go:209] Created default security context constraint anyuid
I0609 17:51:33.637186 23441 ensure.go:209] Created default security context constraint hostnetwork


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#9256 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/ABG_p32jUYDLquEh9hCQPVTUZH7hgb2-ks5qKFiSgaJpZM4IyPHa
.

@csrwng
Copy link
Contributor Author

csrwng commented Jun 9, 2016

Just synthetic, to get an actual error is not easy :)

@smarterclayton
Copy link
Contributor

LGTM [merge]

@openshift-bot
Copy link
Contributor

openshift-bot commented Jun 9, 2016

continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/4695/) (Image: devenv-rhel7_4347)

@openshift-bot
Copy link
Contributor

Evaluated for origin merge up to da05de1

@openshift-bot
Copy link
Contributor

[Test]ing while waiting on the merge queue

@openshift-bot
Copy link
Contributor

Evaluated for origin test up to da05de1

@openshift-bot
Copy link
Contributor

continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pr_origin/4678/)

@openshift-bot openshift-bot merged commit f31d127 into openshift:master Jun 10, 2016
@csrwng csrwng deleted the cluster_up_log branch July 19, 2016 15:34
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 this pull request may close these issues.

3 participants