kubesphere3.0
eks1.15
添加报警通知人出现错误，请帮忙看看

ks-apiserver的log：
E0305 08:36:09.389571 1 authentication.go:60] Unable to authenticate the request due to error: EOF
E0305 08:36:09.397651 1 jwt.go:51] EOF
E0305 08:36:09.397666 1 token.go:57] EOF
E0305 08:36:09.397670 1 jwt_token.go:45] EOF
E0305 08:36:09.397677 1 authentication.go:60] Unable to authenticate the request due to error: EOF
E0305 08:36:09.401144 1 jwt.go:51] EOF
E0305 08:36:09.401156 1 token.go:57] EOF
E0305 08:36:09.401160 1 jwt_token.go:45] EOF
E0305 08:36:09.401166 1 authentication.go:60] Unable to authenticate the request due to error: EOF
E0305 08:37:09.391412 1 jwt.go:51] EOF
E0305 08:37:09.391433 1 token.go:57] EOF
E0305 08:37:09.391438 1 jwt_token.go:45] EOF
E0305 08:37:09.391447 1 authentication.go:60] Unable to authenticate the request due to error: EOF
E0305 08:37:09.399365 1 jwt.go:51] EOF
E0305 08:37:09.399382 1 token.go:57] EOF
E0305 08:37:09.399387 1 jwt_token.go:45] EOF
E0305 08:37:09.399394 1 authentication.go:60] Unable to authenticate the request due to error: EOF
E0305 08:37:09.403333 1 jwt.go:51] EOF
E0305 08:37:09.403344 1 token.go:57] EOF
E0305 08:37:09.403349 1 jwt_token.go:45] EOF
E0305 08:37:09.403355 1 authentication.go:60] Unable to authenticate the request due to error: EOF

    FlywinNing ks-apiserver 的日志跟这个错误没有关系（EOF 是因为有不正确的的请求到 ks-apiserver）。 看提示是有资源冲突了， 刷新一下页面重新编辑一下看看，可以检查一下 kubesphere-monitoring-system 项目下 notification-manager 的日志看看有没有异常

        hongming notification-manager的日志里面没有什么异常，LDAP账号也是可以正常登录的，之前把admin的邮箱admin@kubesphere.io改成我自己的了，后来又改回去了，这个有影响吗？
        [root@wonkubectl ~]# kubectl logs notification-manager-deployment-b8fcb5676-bl52t -n kubesphere-monitoring-system
        level=info ts=2021-02-22T03:14:21.817342843Z caller=main.go:100 msg=“Starting notification manager…” addr=:19093 timeout=5s
        level=info ts=2021-02-22T03:14:24.826524116Z caller=config.go:353 msg=“Setting up informers successfully”
        W0222 03:29:11.725791 1 reflector.go:326] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: watch of *v1alpha1.NotificationManager ended with: too old resource version: 86127585 (86132549)
        W0222 03:40:12.125961 1 reflector.go:326] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: watch of *v1alpha1.NotificationManager ended with: too old resource version: 86132549 (86135472)
        W0222 04:07:35.743110 1 reflector.go:326] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: watch of *v1alpha1.EmailReceiver ended with: too old resource version: 86127744 (86142785)
        W0222 04:21:42.294923 1 reflector.go:326] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: watch of *v1alpha1.NotificationManager ended with: too old resource version: 86135472 (86146524)
        W0222 09:53:15.705576 1 reflector.go:326] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: watch of *v1alpha1.SlackConfig ended with: too old resource version: 86127744 (86236121)
        W0222 12:23:36.084422 1 reflector.go:326] pkg/mod/k8s.io/client-go@v0.17.2/tools/cache/reflector.go:105: watch of *v1alpha1.SlackReceiver ended with: too old resource version: 86127744 (86276060)

        [root@wonkubectl ~]# kubectl logs notification-manager-deployment-b8fcb5676-r45zg -n kubesphere-monitoring-system
        level=info ts=2021-03-05T02:42:31.206173281Z caller=main.go:100 msg=“Starting notification manager…” addr=:19093 timeout=5s
        level=info ts=2021-03-05T02:42:34.322744081Z caller=config.go:353 msg=“Setting up informers successfully”

        [root@wonkubectl ~]# kubectl logs notification-manager-operator-5df57c5b9d-47spk notification-manager-operator -n kubesphere-monitoring-system
        2021-03-05T02:42:49.830Z INFO controller-runtime.metrics metrics server is starting to listen {“addr”: “127.0.0.1:8080”}
        2021-03-05T02:42:49.902Z INFO setup starting manager
        I0305 02:42:49.902380 1 leaderelection.go:242] attempting to acquire leader lease kubesphere-monitoring-system/7b8d27e6.kubesphere.io…
        2021-03-05T02:42:49.902Z INFO controller-runtime.manager starting metrics server {“path”: “/metrics”}
        I0305 02:43:06.844528 1 leaderelection.go:252] successfully acquired lease kubesphere-monitoring-system/7b8d27e6.kubesphere.io
        2021-03-05T02:43:06.844Z INFO controller-runtime.controller Starting EventSource {“controller”: “notificationmanager”, “source”: “kind source: /, Kind=”}
        2021-03-05T02:43:06.844Z DEBUG controller-runtime.manager.events Normal {“object”: {“kind”:“ConfigMap”,“namespace”:“kubesphere-monitoring-system”,“name”:“7b8d27e6.kubesphere.io”,“uid”:“c8c74868-416f-4680-8a26-47fc3f05b2df”,“apiVersion”:“v1”,“resourceVersion”:“90392562”}, “reason”: “LeaderElection”, “message”: “notification-manager-operator-5df57c5b9d-47spk_aef3e882-de0e-4cec-869c-499fe1aba92e became leader”}
        2021-03-05T02:43:06.944Z INFO controller-runtime.controller Starting EventSource {“controller”: “notificationmanager”, “source”: “kind source: /, Kind=”}
        2021-03-05T02:43:06.945Z INFO controller-runtime.controller Starting Controller {“controller”: “notificationmanager”}
        2021-03-05T02:43:06.945Z INFO controller-runtime.controller Starting workers {“controller”: “notificationmanager”, “worker count”: 1}
        2021-03-05T02:43:07.042Z DEBUG controller-runtime.controller Successfully Reconciled {“controller”: “notificationmanager”, “request”: “kubesphere-monitoring-system/notification-manager”}
        2021-03-05T02:43:07.080Z DEBUG controller-runtime.controller Successfully Reconciled {“controller”: “notificationmanager”, “request”: “kubesphere-monitoring-system/notification-manager”}

        [root@wonkubectl ~]# kubectl logs notification-manager-operator-5df57c5b9d-47spk kube-rbac-proxy -n kubesphere-monitoring-system
        I0305 02:42:31.918957 1 main.go:213] Generating self signed cert as no cert is provided
        I0305 02:42:38.607161 1 main.go:243] Starting TCP socket on 0.0.0.0:8443
        I0305 02:42:38.701342 1 main.go:250] Listening securely on 0.0.0.0:8443

            FlywinNing 不是修改邮箱的问题， 应该是编辑的时候冲突了， F12 看看是哪个API的错误

                1.这个要看kubesphere-alerting-system下的notification和alert的日志，不是notification-manager的。
                2.这个对应的邮件服务器也不是通过notification-manager设置的，要在集群管理中的集群设置中设置

                  17 天 后