安装完进入界面出现
500 Internal Privoxy Error
Privoxy encountered an error while processing your request:
Could not load template file no-server-data or one of its included components.
Please contact your proxy administrator.
If you are the proxy administrator, please put the required file(s)in the (confdir)/templates directory. The location of the (confdir) directory is specified in the main Privoxy config file. (It’s typically the Privoxy install directory).

    zhangyuxiansen2017
    这个要具体看一下 pod 是否都是 Running 状态，我在前二次安装时，k8s-account、k8s-getway 经常不是 Running 状态，导致登录后页面就报500错误，建议先查看一下pod状态，例如：

    [root@k8s-node1 ~]# kubectl get pods --all-namespaces
NAMESPACE                      NAME                                           READY   STATUS    RESTARTS   AGE
kube-system                    coredns-7f9c544f75-2lj7z                       1/1     Running   1          14d
kube-system                    coredns-7f9c544f75-7zwbr                       1/1     Running   1          14d
kube-system                    etcd-k8s-node1                                 1/1     Running   1          14d
kube-system                    kube-apiserver-k8s-node1                       1/1     Running   1          14d
kube-system                    kube-controller-manager-k8s-node1              1/1     Running   5          14d
kube-system                    kube-flannel-ds-amd64-2smws                    1/1     Running   1          14d
kube-system                    kube-flannel-ds-amd64-5k4jk                    1/1     Running   0          14d
kube-system                    kube-flannel-ds-amd64-krmg4                    1/1     Running   0          14d
kube-system                    kube-proxy-5wvhk                               1/1     Running   0          14d
kube-system                    kube-proxy-gvm8b                               1/1     Running   1          14d
kube-system                    kube-proxy-qm6lh                               1/1     Running   0          14d
kube-system                    kube-scheduler-k8s-node1                       1/1     Running   4          14d
kube-system                    tiller-deploy-7b76b656b5-xxz62                 1/1     Running   0          9d
kubesphere-controls-system     default-http-backend-5d464dd566-nbcs5          1/1     Running   4          8d
kubesphere-controls-system     kubectl-admin-6c664db975-qkfxf                 1/1     Running   0          6d16h
kubesphere-monitoring-system   kube-state-metrics-566cdbcb48-xfhbn            4/4     Running   0          6d16h
kubesphere-monitoring-system   node-exporter-ptb8p                            2/2     Running   0          6d16h
kubesphere-monitoring-system   node-exporter-skr7x                            2/2     Running   0          6d16h
kubesphere-monitoring-system   node-exporter-tdmzt                            2/2     Running   0          6d16h
kubesphere-monitoring-system   prometheus-k8s-0                               3/3     Running   1          34h
kubesphere-monitoring-system   prometheus-k8s-system-0                        3/3     Running   1          34h
kubesphere-monitoring-system   prometheus-operator-6b97679cfd-4rhln           1/1     Running   0          6d16h
kubesphere-system              ks-account-794477c45d-n2q6n                    1/1     Running   0          34h
kubesphere-system              ks-apigateway-546d4df545-g4q7c                 1/1     Running   0          34h
kubesphere-system              ks-apiserver-689675d48c-69n67                  1/1     Running   0          34h
kubesphere-system              ks-console-86599887c-g4xwt                     1/1     Running   0          34h
kubesphere-system              ks-controller-manager-6fd9b6d999-nj6cb         1/1     Running   0          34h
kubesphere-system              ks-installer-7557594789-ltkzl                  1/1     Running   0          34h
kubesphere-system              openldap-0                                     1/1     Running   0          8d
kubesphere-system              redis-6fd6c6d6f9-ps5t4                         1/1     Running   0          8d
openebs                        openebs-admission-server-5cf6864fbf-dvlbw      1/1     Running   0          9d
openebs                        openebs-apiserver-bc55cd99b-5rdxh              1/1     Running   4          9d
openebs                        openebs-localpv-provisioner-85ff89dd44-p9td4   1/1     Running   5          9d
openebs                        openebs-ndm-5wnvr                              1/1     Running   0          9d
openebs                        openebs-ndm-operator-87df44d9-482hh            1/1     Running   1          9d
openebs                        openebs-ndm-p89wd                              1/1     Running   0          9d
openebs                        openebs-ndm-swpgb                              1/1     Running   0          9d
openebs                        openebs-provisioner-7f86c6bb64-5xmdd           1/1     Running   5          9d
openebs                        openebs-snapshot-operator-54b9c886bf-s5x9m     2/2     Running   3          9d
        10 天 后

        第一次安装 最后阶段monitoring报错，没有 prometheus-k8s-0 、prometheus-k8s-system-0 和 openldap-0，ks-account 一直 Init:½
        尝试重装（kubectl rollout restart deploy -n kubesphere-system ks-installer），前面两个有了，但是 openldap-0还是没有，而且ks-account 出现两个，两个都是Init:½

        chuanning Feynman

              Feynman 这次操作步骤是没有污点的

              我以前安装试过有污点，能看到openldap-0，但是一直pending，后来才发现要完全安装完才能放开，这次操作就是完全放开的

                11 天 后


                今天yum安装kubelet-1.17.3 kubeadm-1.17.3 kubectl-1.17.3 遇到这个问题，有大佬帮忙看下吗

                Feynman 着急！！！！！ ks-account 安装中 Init:0/2 问题 不管是 dns 问题 还是 其他问题 能不能给个 完整解决方案 七天了 查了所有还是不能解决啊 给个教程啊

                    xinghai ks-account 起不来的原因有很多，不知道具体问题的前提下 我们也没有通用的解决方案。你新建一个帖子，把 ks-account 的 Pod 日志和 events 贴出看看？

                        xinghai kubectl logs 查看 ks-account 的 Pod 日志，describe 看看 Pod 的 events

                            xinghai

                            莫急，按 Feynman 版主的建议：

                            1. 开新帖
                            2. kubectl logs 查看 ks-account 的 Pod 日志，describe 看看 Pod 的 events