On Tuesday, January 31, 2017 at 6:17:04 PM UTC+5:30, Andrew Smith wrote: > You should be able to use journalctl to dig in to the logs and find out why > kube-apiserver didn't download (it looks from the config like it should get > downloaded as part of that unit). > > > On 31 January 2017 at 12:45, <selv...@gmail.com> wrote: > On Tuesday, January 31, 2017 at 5:59:25 PM UTC+5:30, Andrew Smith wrote: > > > That error generally means that the kubernetes API server is not running > > (or not listening on port 8080). > > > > > > > > > From the looks of the cloud-config > > (https://gist.githubusercontent.com/ryancurrah/ab320ea6ce65587e2706/raw/cloud-config-master.yaml) > > the API server should be running under systemd. > > > > > > > > > So you should be able to run the following command to see why it isn't > > there: > > > > > > > > > sudo systemctl status kube-apiserver > > > > > > > > > > > > > > > > > > > > > On 31 January 2017 at 12:20, <selv...@gmail.com> wrote: > > > Hi, > > > > > > > > > > > > I am trying to setup one master server and 3 nodes server using the below > > tutorial. > > > > > > "CoreOS w/ Kubernetes Install Guide for VirtualBox" > > > > > > http://www.currah.ca/tech/2015/10/08/kubernetes-coreos.html > > > > > > > > > > > > But I got struck in the below step. > > > > > > "To start the kubectl client" > > > > > > > > > > > > 1.What are the changes need to be added in the config.yml file? > > > > > > 2.I got the below error when I ran the command > > > > > > "kubectl get nodes" > > > > > > > > > > > > core@master01 /opt/bin $ kubectl get nodes > > > > > > error: couldn't read version from server: Get http://localhost:8080/api: > > dial tcp 127.0.0.1:8080: connection refused > > > > > > > > > > > > Could you please help in resolving the issue. > > > > > > > > > > > > Thanks in advance > > > > > > > > > > > > -- > > > > > > You received this message because you are subscribed to the Google Groups > > "Kubernetes user discussion and Q&A" group. > > > > > > To unsubscribe from this group and stop receiving emails from it, send an > > email to kubernetes-use...@googlegroups.com. > > > > > > To post to this group, send email to kubernet...@googlegroups.com. > > > > > > Visit this group at https://groups.google.com/group/kubernetes-users. > > > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > > > > > > > > > > > -- > > > > > > > > > Andy Smith > > > > > > > > > http://andrewmichaelsmith.com | @bingleybeep > > > > When I ran the command, I got the below output > > > > core@master01 /opt/bin $ sudo systemctl status kube-apiserver > > ● kube-apiserver.service - Kubernetes API Server > > Loaded: loaded (/etc/systemd/system/kube-apiserver.service; static; vendor > preset: disabled) > > Active: inactive (dead) > > Docs: https://github.com/GoogleCloudPlatform/kubernetes > > > > Jan 31 12:15:35 master01 systemd[1]: Dependency failed for Kubernetes API > Server. > > Jan 31 12:15:35 master01 systemd[1]: kube-apiserver.service: Job > kube-apiserver.service/start failed with result 'dependency'. > > Jan 31 12:15:45 master01 systemd[1]: Dependency failed for Kubernetes API > Server. > > Jan 31 12:15:45 master01 systemd[1]: kube-apiserver.service: Job > kube-apiserver.service/start failed with result 'dependency'. > > Jan 31 12:15:55 master01 systemd[1]: Dependency failed for Kubernetes API > Server. > > Jan 31 12:15:55 master01 systemd[1]: kube-apiserver.service: Job > kube-apiserver.service/start failed with result 'dependency'. > > core@master01 /opt/bin $ > > > > Then I checked my bin directory "/opt/bin" I was not able to find the > kube-apiserver listed > > > > core@master01 /opt/bin $ ls -ailh /opt/bin > > total 22M > > 1042434 drwxr-xr-x. 2 root root 4.0K Jan 31 12:15 . > > 1042433 drwxr-xr-x. 3 root root 4.0K Jan 31 09:56 .. > > 1042436 -rw-r--r--. 1 root root 1.7K Jan 31 12:15 kube-serviceaccount.key > > 1042438 -rwxr-xr-x. 1 root root 20M Jan 31 10:00 kubectl > > 1042437 -rwxrwxrwx. 1 root root 2.0M Jan 31 09:57 setup-network-environment > > 1042435 -rwxr-xr-x. 1 root root 164 Jan 31 12:15 wupiao > > > > Could you please suggest any ways to get the kube-apiserver? I tried running > the installer again. But I was not able to find the same. > > > > Thanks in advance! > > Selva > > > > > > -- > > You received this message because you are subscribed to the Google Groups > "Kubernetes user discussion and Q&A" group. > > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-use...@googlegroups.com. > > To post to this group, send email to kubernet...@googlegroups.com. > > Visit this group at https://groups.google.com/group/kubernetes-users. > > For more options, visit https://groups.google.com/d/optout. > > > > > > -- > > > Andy Smith > > > http://andrewmichaelsmith.com | @bingleybeep
>From the journalctl log I found this Feb 01 06:04:49 master01 etcd2[1416]: etcd Version: 2.3.7 Feb 01 06:04:49 master01 etcd2[1416]: Git SHA: fd17c91 Feb 01 06:04:49 master01 etcd2[1416]: Go Version: go1.7.3 Feb 01 06:04:49 master01 etcd2[1416]: Go OS/Arch: linux/amd64 Feb 01 06:04:49 master01 etcd2[1416]: setting maximum number of CPUs to 1, total number of available CPUs is 1 Feb 01 06:04:49 master01 etcd2[1416]: listen tcp 192.168.122.10:2380: bind: cannot assign requested address Feb 01 06:04:49 master01 systemd[1]: etcd2.service: Main process exited, code=exited, status=1/FAILURE Feb 01 06:04:49 master01 systemd[1]: Failed to start etcd2. Feb 01 06:04:49 master01 coreos-cloudinit[826]: 2017/02/01 06:04:49 Result of "start" on "kube-apiserver.service": dependency Feb 01 06:04:49 master01 coreos-cloudinit[826]: 2017/02/01 06:04:49 Calling unit command "start" on "kube-controller-manager.service"' Feb 01 06:04:49 master01 systemd[1]: Dependency failed for Kubernetes API Server. Feb 01 06:04:49 master01 systemd[1]: kube-apiserver.service: Job kube-apiserver.service/start failed with result 'dependency'. Feb 01 06:04:49 master01 systemd[1]: etcd2.service: Unit entered failed state. Feb 01 06:04:49 master01 systemd[1]: etcd2.service: Failed with result 'exit-code'. Feb 01 06:04:59 master01 systemd[1]: etcd2.service: Service hold-off time over, scheduling restart. Feb 01 06:04:59 master01 systemd[1]: Stopped etcd2. Feb 01 06:04:59 master01 systemd[1]: Starting etcd2... Feb 01 06:04:59 master01 etcd2[1439]: recognized and used environment variable ETCD_ADVERTISE_CLIENT_URLS=http://192.168.122.10:2379,http://192.168.122.10:4001 Feb 01 06:04:59 master01 etcd2[1439]: recognized and used environment variable ETCD_DATA_DIR=/var/lib/etcd2 Feb 01 06:04:59 master01 etcd2[1439]: recognized and used environment variable ETCD_INITIAL_ADVERTISE_PEER_URLS=http://192.168.122.10:2380 Feb 01 06:04:59 master01 etcd2[1439]: recognized and used environment variable ETCD_INITIAL_CLUSTER=master=http://192.168.122.10:2380 Feb 01 06:04:59 master01 etcd2[1439]: recognized and used environment variable ETCD_INITIAL_CLUSTER_STATE=new Feb 01 06:04:59 master01 etcd2[1439]: recognized and used environment variable ETCD_INITIAL_CLUSTER_TOKEN=k8s_etcd Feb 01 06:04:59 master01 etcd2[1439]: recognized and used environment variable ETCD_LISTEN_CLIENT_URLS=http://0.0.0.0:2379,http://0.0.0.0:4001 Feb 01 06:04:59 master01 etcd2[1439]: recognized and used environment variable ETCD_LISTEN_PEER_URLS=http://192.168.122.10:2380,http://192.168.122.10:7001 Feb 01 06:04:59 master01 etcd2[1439]: recognized and used environment variable ETCD_NAME=master Feb 01 06:04:59 master01 etcd2[1439]: etcd Version: 2.3.7 Feb 01 06:04:59 master01 etcd2[1439]: Git SHA: fd17c91 Feb 01 06:04:59 master01 etcd2[1439]: Go Version: go1.7.3 Feb 01 06:04:59 master01 etcd2[1439]: Go OS/Arch: linux/amd64 Feb 01 06:04:59 master01 etcd2[1439]: setting maximum number of CPUs to 1, total number of available CPUs is 1 Feb 01 06:04:59 master01 etcd2[1439]: listen tcp 192.168.122.10:2380: bind: cannot assign requested address Feb 01 06:04:59 master01 systemd[1]: etcd2.service: Main process exited, code=exited, status=1/FAILURE Feb 01 06:04:59 master01 systemd[1]: Failed to start etcd2. -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
