# Some problems when deploying kube-apiserver

**URL:** <https://discuss.kubernetes.io/t/some-problems-when-deploying-kube-apiserver/18078>\
**Category:** General Discussions\
**Created:** [November 13, 2021, 10:37am UTC](https://discuss.kubernetes.io/t/some-problems-when-deploying-kube-apiserver/18078 "2021-11-13T10:37:55Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![xiaobin](https://avatars.discourse-cdn.com/v4/letter/x/f04885/32.png) [@xiaobin](https://discuss.kubernetes.io/u/xiaobin)\
**Post date:** [November 13, 2021, 10:37am UTC](https://discuss.kubernetes.io/t/some-problems-when-deploying-kube-apiserver/18078/1 "2021-11-13T10:37:55Z")

</div>

I am following the course `Kubernetes the Hard Way`. Because my arch is riscv64, there are still some problems when deploying kube-apiserver.  
Now, I have succeeded in build k8s source code and get the binary file in `_output/local/bin/linux/riscv64/`.  
My kube-apiserver can not start normally, the failure is time out and get `ccResolverWrapper: sending new addresses to cc: [{` `https://ip:2379` ` 0 <nil>}]` . I search the cause related to etcd(because etcd listen port 2379).

 ![image](https://us1.discourse-cdn.com/flex016/uploads/kubernetes/original/2X/0/089524fb0473142768267a718fb68ab8f83759bd.png)

etcd’s activity is active(running).

```auto
[root@master0 home]# systemctl status etcd
● etcd.service - Etcd Server
   Loaded: loaded (/etc/systemd/system/etcd.service; enabled; vendor preset: disabled)
   Active: active (running) since Sat 2021-11-13 16:44:45 CST; 1h 38min ago
     Docs: https://github.com/coreos
 Main PID: 16892 (etcd)
    Tasks: 7
   Memory: 18.9M
   CGroup: /system.slice/etcd.service
           └─16892 /opt/k8s/bin/etcd --data-dir=/data/k8s/etcd/data --wal-dir=/data/k8s/etcd/wal --name=master0 --cert-file=/etc/etcd/cert/etcd.pem --key-file=/etc/etcd/cert/etc>

Nov 13 16:45:01 master0 etcd[16892]: rejected connection from "192.168.31.195:45724" (error "EOF", ServerName "")
Nov 13 16:45:01 master0 etcd[16892]: rejected connection from "192.168.31.195:45726" (error "EOF", ServerName "")
Nov 13 16:45:01 master0 etcd[16892]: rejected connection from "192.168.31.195:45728" (error "EOF", ServerName "")
Nov 13 16:45:01 master0 etcd[16892]: rejected connection from "192.168.31.195:45730" (error "read tcp 192.168.31.195:2379->192.168.31.195:45730: read: connection reset by peer",>
Nov 13 16:45:01 master0 etcd[16892]: rejected connection from "192.168.31.195:45732" (error "read tcp 192.168.31.195:2379->192.168.31.195:45732: read: connection reset by peer",>
Nov 13 16:45:01 master0 etcd[16892]: rejected connection from "192.168.31.195:45734" (error "EOF", ServerName "")
Nov 13 16:45:01 master0 etcd[16892]: rejected connection from "192.168.31.195:45736" (error "EOF", ServerName "")
Nov 13 16:45:01 master0 etcd[16892]: rejected connection from "192.168.31.195:45738" (error "EOF", ServerName "")
Nov 13 17:44:41 master0 etcd[16892]: Starting auto-compaction at revision 1 (retention: 1h0m0s)
Nov 13 17:44:41 master0 etcd[16892]: Finished auto-compaction at revision 1

```

However etcd seems unnormallly. I changed the source code in `etcdmain/etcd.go` and add the checkSupportArch function for riscv64. Still get the following errors.

```auto
if runtime.GOARCH == "riscv64" {
                return
        }

```

and get

```auto
Nov 12 15:19:48 master0 systemd[1]: Starting Etcd Server...
Nov 12 15:19:48 master0 etcd[4395]: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=riscv64 set
Nov 12 15:19:48 master0 systemd[1]: etcd.service: Main process exited, code=exited, status=1/FAILURE
Nov 12 15:19:48 master0 systemd[1]: etcd.service: Failed with result 'exit-code'.
Nov 12 15:19:49 master0 systemd[1]: Failed to start Etcd Server.
Nov 12 15:19:54 master0 systemd[1]: etcd.service: Service RestartSec=5s expired, scheduling restart.
Nov 12 15:19:54 master0 systemd[1]: etcd.service: Scheduled restart job, restart counter is at 1.
Nov 12 15:19:54 master0 systemd[1]: Stopped Etcd Server.

```

How can i solve these problems.