Openshift源代码为'；不要启动webconsole

我正在尝试使用以下命令启动Openshift原始群集：

oc cluster up --public-hostname='openshift.xxx.xxx' --http-proxy='http://xx.xx.xx.xx:8080' --https-proxy='http://xx.xx.xx.xx:8080' --no-proxy='0.0.0.0,172.30.1.1,172.17.0.7' --host-data-dir /var/lib/origin/openshift.local.data

（我在公司代理后运行它，所以我必须设置它，并为docker设置一些例外情况）

这是我得到的结果：

Using nsenter mounter for OpenShift volumes
Using 127.0.0.1 as the server IP
Starting OpenShift using openshift/origin:v3.9.0 ...
-- Starting OpenShift container ...
Creating initial OpenShift configuration
Starting OpenShift using container 'origin'
Waiting for API server to start listening
OpenShift server started
-- Adding default OAuthClient redirect URIs ... OK
-- Installing registry ... OK
-- Installing router ... OK
-- Importing image streams ... OK
-- Importing templates ... OK
-- Importing internal templates ... OK
-- Installing web console ... FAIL
Error: failed to start the web console server: timed out waiting for the condition

我只有一个网络控制台吊舱：

oc get pods -n openshift-web-console
NAME                          READY     STATUS             RESTARTS   AGE
webconsole-7dfbffd44d-v5lxw   0/1       CrashLoopBackOff   8          25m

这是我从pod获得的信息：

Events:
Type     Reason                 Age                 From                    Message
----     ------                 ----                ----                    -------
Normal   Scheduled              26m                 default-scheduler       Successfully assigned webconsole-7dfbffd44d-v5lxw to localhost
Normal   SuccessfulMountVolume  26m                 kubelet, localhost       MountVolume.SetUp succeeded for volume "webconsole-config"
Normal   SuccessfulMountVolume  26m                 kubelet, localhost    MountVolume.SetUp succeeded for volume "serving-cert"
Normal   SuccessfulMountVolume  26m                 kubelet, localhost  MountVolume.SetUp succeeded for volume "webconsole-token-qljxd"
Normal   Pulled                 25m (x4 over 26m)   kubelet, localhost   Container image "openshift/origin-web-console:v3.9.0" already present on  machine
Normal   Created                25m (x4 over 26m)   kubelet, localhost  Created container
Normal   Started                25m (x4 over 26m)   kubelet, localhost  Started container
Warning  BackOff                24m (x10 over 26m)  kubelet, localhost  Back-off restarting failed container
Normal   SuccessfulMountVolume  19m                 kubelet, localhost    MountVolume.SetUp succeeded for volume "webconsole-config"
Normal   SuccessfulMountVolume  19m                 kubelet, localhost  MountVolume.SetUp succeeded for volume "webconsole-token-qljxd"
Normal   SuccessfulMountVolume  19m                 kubelet, localhost  MountVolume.SetUp succeeded for volume "serving-cert"
Normal   Pulled                 18m (x4 over 19m)   kubelet, localhost  Container image "openshift/origin-web-console:v3.9.0" already present on   machine
Normal   Created                18m (x4 over 19m)   kubelet, localhost  Created container
Normal   Started                18m (x4 over 19m)   kubelet, localhost  Started container
Warning  BackOff                4m (x74 over 19m)   kubelet, localhost  Back-off restarting failed container

我看不出事件中有任何错误，但pod总是失败

这是Openshift原点的版本：

oc version
oc v3.9.0+191fece
kubernetes v1.9.1+a0ce1bc657
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://127.0.0.1:8443
openshift v3.9.0+191fece
kubernetes v1.9.1+a0ce1bc657

和Redhat版本：

cat /etc/redhat-release
Red Hat Enterprise Linux Server release 7.3 (Maipo)

为了提供更多信息，我将/var文件系统设置为95%，我增加了LV的空间，并尝试重新启动集群，我的问题就从这里开始。目前，/var文件系统的使用率为58%：

df -h /var
Filesystem                  Size  Used Avail Use% Mounted on
/dev/mapper/vg_rhel-lv_var   30G   18G   13G  58% /var

我一直在通过网络阅读信息，但找不到任何结论：我尝试将webconsole serviceaccount添加到特权scc，重新启动docker.service，重新启动虚拟机，等等，但Openshift源webconsole仍然失败。有什么想法吗

---

提前感谢。

像

oc logs openshift web console

、

oc logs origin

和

oc cluster up

这样带有参数

--loglevel=8

的命令是否显示了一些有意义的内容？