K
Q

>>/var/log/kube-apiserver.log not work for kubernetes1.6

6/10/2017

Currently, under kubernetes1.5.3, kube-apiserver.log and kube-controller-manager.log is generated by adding '1>>/var/log/kube-apiserver.log 2>&1' in /etc/kubernetes/kube-apiserver.yaml file. When I upgrade the kubernetes version to 1.6.3, it not work. There is no log file created under /var/log. How to get the kubernetes log file? Thanks, much.

-- zjzhangkui
kubernetes
logging

Similar Questions

error: You must be logged in to the server (the server has asked for the client to provide credentials)
kubetnetes port forward udp
Can we create Multiple databases in Same Persistent Volume in kubernetes ?
Do pods share the filesystems, similar to how they share same network namespace?

2 Answers

6/12/2017
ps -ef | grep kube
tail -f /var/log/message

See the kube* processes's options are configed right ?
And check the /var/log/message to find are there some errors about k8s?

-- sure ruan
Source: StackOverflow
6/12/2017

For kubernetes1.6+, try the following options

kube-apiserver

--audit-log-path=/var/log/kubernetes/kube-apiserver.log --logtostderr=false

and restart kube-apiserver, you can find all logs for kube-apiserver in file /var/log/kubernetes/kube-apiserver.log.

kube-controller-manager

--log-dir=/var/log/kubernetes --logtostderr=false

then restart kube-controller-manager, you will find:

  • ERROR logs in /var/log/kubernetes/kube-controller-manager.ERROR;
  • FATAL logs in /var/log/kubernetes/kube-controller-manager.FATAL;
  • INFO logs in /var/log/kubernetes/kube-controller-manager.INFO;
  • WARNING logs in /var/log/kubernetes/kube-controller-manager.WARNING;

kube-scheduler

 --log-dir=/var/log/kubernetes --logtostderr=false

then restart kube-scheduler, you will find:

  • ERROR logs in /var/log/kubernetes/kube-scheduler.ERROR;
  • FATAL logs in /var/log/kubernetes/kube-scheduler.FATAL;
  • INFO logs in /var/log/kubernetes/kube-scheduler.INFO;
  • WARNING logs in /var/log/kubernetes/kube-scheduler.WARNING;

kubelet

--log-dir=/var/log/kubernetes --logtostderr=false

then restart kubelet, you will find:

  • ERROR logs in /var/log/kubernetes/kubelet.ERROR;
  • FATAL logs in /var/log/kubernetes/kubelet.FATAL;
  • INFO logs in /var/log/kubernetes/kubelet.INFO;
  • WARNING logs in /var/log/kubernetes/kubelet.WARNING;

kube-proxy

--log-dir=/var/log/kubernetes --logtostderr=false

then restart kube-proxy, you will find:

  • ERROR logs in /var/log/kubernetes/kube-proxy.ERROR;
  • FATAL logs in /var/log/kubernetes/kube-proxy.FATAL;
  • INFO logs in /var/log/kubernetes/kube-proxy.INFO;
  • WARNING logs in /var/log/kubernetes/kube-proxy.WARNING;
-- Weike
Source: StackOverflow