Issues Running `systemctl restart` Command to OpenShift Master Services

Solution Verified - Updated -

Issue

  • atomic-openshift-master.service fails to start or restart with error messages
  • OpenShift master errors in systemctl status or journalctl -xe referring to yaml issues:
Jul 19 16:51:35 master.example.com atomic-openshift-master[69659]: F0719 16:51:35.928627   69659 start_master.go:100] yaml: line 5: did not find expected key
Jul 19 16:51:35 master.example.com systemd[1]: atomic-openshift-master.service: main process exited, code=exited, status=255/n/a
Jul 19 16:51:35 master.example.com systemd[1]: Failed to start Atomic OpenShift Master.
$ systemctl status atomic-openshift-master.service
● atomic-openshift-master.service - Atomic OpenShift Master
   Loaded: loaded (/usr/lib/systemd/system/atomic-openshift-master.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Tue 2016-07-19 16:51:36 EDT; 12s ago
     Docs: https://github.com/openshift/origin
  Process: 69659 ExecStart=/usr/bin/openshift start master --config=${CONFIG_FILE} $OPTIONS (code=exited, status=255)
 Main PID: 69659 (code=exited, status=255)

Environment

  • Red Hat OpenShift Enterprise
    • 3.1
    • 3.2

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content