[kubernetes-users] Re: Does kube-apiserver set the limitation for "open files" with value 1024 for 'root'?
On Wednesday, November 30, 2016 at 2:23:16 PM UTC-8, kvch...@gmail.com wrote: > Here is why? > root@ovrh0301:/home/envi# ulimit -a > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 772117 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 10 > pipe size(512 bytes, -p) 8 > - > envi@ovrh0301:~$ ps aux | grep kube-apiserver > root 3539 5.5 0.1 300696 252292 ? Ssl 11:09 10:26 > /opt/bin/kube-apiserver --insecure-bind-address=0.0.0.0 --insecure-port=8080 > --etcd-servers=http://127.0.0.1:4001 --logtostderr=true > --service-cluster-ip-range=192.168.3.0/24 > --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,SecurityContextDeny,DefaultStorageClass,ResourceQuota > --service-node-port-range=3-32767 --advertise-address=172.31.0.200 > --allow-privileged=false --client-ca-file=/srv/kubernetes/ca.crt > --tls-cert-file=/srv/kubernetes/server.cert > --tls-private-key-file=/srv/kubernetes/server.key > envi 5546 0.0 0.0 11748 2164 pts/0S+ 14:18 0:00 grep > --color=auto kube-apiserver > envi@ovrh0301:~$ > --- > root@ovrh0301:/home/envi# cat /proc/3539/limits > Limit Soft Limit Hard Limit Units > Max cpu time unlimitedunlimitedseconds > Max file size unlimitedunlimitedbytes > Max data size unlimitedunlimitedbytes > Max stack size8388608 unlimitedbytes > Max core file size0unlimitedbytes > Max resident set unlimitedunlimitedbytes > Max processes 772117 772117 processes > Max open files1024 4096 files > Max locked memory 6553665536bytes > --- > envi@ovrh0301:~$ sudo ls -l /proc/3539/fd > total 0 > lrwx-- 1 root root 64 Nov 30 14:08 0 -> /dev/null > lrwx-- 1 root root 64 Nov 30 14:08 1 -> /dev/pts/7 > lrwx-- 1 root root 64 Nov 30 14:08 10 -> socket:[69672] > lrwx-- 1 root root 64 Nov 30 14:08 100 -> socket:[69680] > lrwx-- 1 root root 64 Nov 30 14:08 1000 -> socket:[43353] > lrwx-- 1 root root 64 Nov 30 14:08 1001 -> socket:[73034] > lrwx-- 1 root root 64 Nov 30 14:08 1002 -> socket:[89431] > lrwx-- 1 root root 64 Nov 30 14:08 1003 -> socket:[86357] > lrwx-- 1 root root 64 Nov 30 14:08 1004 -> socket:[31818] > lrwx-- 1 root root 64 Nov 30 14:08 1005 -> socket:[86359] > lrwx-- 1 root root 64 Nov 30 14:08 1006 -> socket:[76133] > lrwx-- 1 root root 64 Nov 30 14:08 1007 -> socket:[75086] > lrwx-- 1 root root 64 Nov 30 14:08 1008 -> socket:[89433] > lrwx-- 1 root root 64 Nov 30 14:08 1009 -> socket:[73039] > lrwx-- 1 root root 64 Nov 30 14:08 101 -> socket:[11624] > lrwx-- 1 root root 64 Nov 30 14:08 1010 -> socket:[43394] > lrwx-- 1 root root 64 Nov 30 14:08 1011 -> socket:[75091] > lrwx-- 1 root root 64 Nov 30 14:08 1012 -> socket:[43358] > lrwx-- 1 root root 64 Nov 30 14:08 1013 -> socket:[44369] > lrwx-- 1 root root 64 Nov 30 14:08 1014 -> socket:[86361] > lrwx-- 1 root root 64 Nov 30 14:08 1015 -> socket:[73042] > lrwx-- 1 root root 64 Nov 30 14:08 1016 -> socket:[18776] > lrwx-- 1 root root 64 Nov 30 14:08 1017 -> socket:[73045] > lrwx-- 1 root root 64 Nov 30 14:08 1018 -> socket:[76135] > lrwx-- 1 root root 64 Nov 30 14:08 1019 -> socket:[65864] > lrwx-- 1 root root 64 Nov 30 14:08 102 -> socket:[31093] > lrwx-- 1 root root 64 Nov 30 14:08 1020 -> socket:[44371] > lrwx-- 1 root root 64 Nov 30 14:08 1021 -> socket:[89437] > lrwx-- 1 root root 64 Nov 30 14:08 1022 -> socket:[75097] > lrwx-- 1 root root 64 Nov 30 14:08 1023 -> socket:[73048] > lrwx-- 1 root root 64 Nov 30 14:08 103 -> socket:[36939] - My issue is resolved now - here is the link - http://lists.adiscon.net/pipermail/rsyslog/2015-December/041692.html and many thanks to everyone. -- 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.
[kubernetes-users] Re: Does kube-apiserver set the limitation for "open files" with value 1024 for 'root'?
On Wednesday, November 30, 2016 at 2:23:16 PM UTC-8, kvch...@gmail.com wrote: > Here is why? > root@ovrh0301:/home/envi# ulimit -a > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 772117 > max locked memory (kbytes, -l) 64 > max memory size (kbytes, -m) unlimited > open files (-n) 10 > pipe size(512 bytes, -p) 8 > - > envi@ovrh0301:~$ ps aux | grep kube-apiserver > root 3539 5.5 0.1 300696 252292 ? Ssl 11:09 10:26 > /opt/bin/kube-apiserver --insecure-bind-address=0.0.0.0 --insecure-port=8080 > --etcd-servers=http://127.0.0.1:4001 --logtostderr=true > --service-cluster-ip-range=192.168.3.0/24 > --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,SecurityContextDeny,DefaultStorageClass,ResourceQuota > --service-node-port-range=3-32767 --advertise-address=172.31.0.200 > --allow-privileged=false --client-ca-file=/srv/kubernetes/ca.crt > --tls-cert-file=/srv/kubernetes/server.cert > --tls-private-key-file=/srv/kubernetes/server.key > envi 5546 0.0 0.0 11748 2164 pts/0S+ 14:18 0:00 grep > --color=auto kube-apiserver > envi@ovrh0301:~$ > --- > root@ovrh0301:/home/envi# cat /proc/3539/limits > Limit Soft Limit Hard Limit Units > Max cpu time unlimitedunlimitedseconds > Max file size unlimitedunlimitedbytes > Max data size unlimitedunlimitedbytes > Max stack size8388608 unlimitedbytes > Max core file size0unlimitedbytes > Max resident set unlimitedunlimitedbytes > Max processes 772117 772117 processes > Max open files1024 4096 files > Max locked memory 6553665536bytes > --- > envi@ovrh0301:~$ sudo ls -l /proc/3539/fd > total 0 > lrwx-- 1 root root 64 Nov 30 14:08 0 -> /dev/null > lrwx-- 1 root root 64 Nov 30 14:08 1 -> /dev/pts/7 > lrwx-- 1 root root 64 Nov 30 14:08 10 -> socket:[69672] > lrwx-- 1 root root 64 Nov 30 14:08 100 -> socket:[69680] > lrwx-- 1 root root 64 Nov 30 14:08 1000 -> socket:[43353] > lrwx-- 1 root root 64 Nov 30 14:08 1001 -> socket:[73034] > lrwx-- 1 root root 64 Nov 30 14:08 1002 -> socket:[89431] > lrwx-- 1 root root 64 Nov 30 14:08 1003 -> socket:[86357] > lrwx-- 1 root root 64 Nov 30 14:08 1004 -> socket:[31818] > lrwx-- 1 root root 64 Nov 30 14:08 1005 -> socket:[86359] > lrwx-- 1 root root 64 Nov 30 14:08 1006 -> socket:[76133] > lrwx-- 1 root root 64 Nov 30 14:08 1007 -> socket:[75086] > lrwx-- 1 root root 64 Nov 30 14:08 1008 -> socket:[89433] > lrwx-- 1 root root 64 Nov 30 14:08 1009 -> socket:[73039] > lrwx-- 1 root root 64 Nov 30 14:08 101 -> socket:[11624] > lrwx-- 1 root root 64 Nov 30 14:08 1010 -> socket:[43394] > lrwx-- 1 root root 64 Nov 30 14:08 1011 -> socket:[75091] > lrwx-- 1 root root 64 Nov 30 14:08 1012 -> socket:[43358] > lrwx-- 1 root root 64 Nov 30 14:08 1013 -> socket:[44369] > lrwx-- 1 root root 64 Nov 30 14:08 1014 -> socket:[86361] > lrwx-- 1 root root 64 Nov 30 14:08 1015 -> socket:[73042] > lrwx-- 1 root root 64 Nov 30 14:08 1016 -> socket:[18776] > lrwx-- 1 root root 64 Nov 30 14:08 1017 -> socket:[73045] > lrwx-- 1 root root 64 Nov 30 14:08 1018 -> socket:[76135] > lrwx-- 1 root root 64 Nov 30 14:08 1019 -> socket:[65864] > lrwx-- 1 root root 64 Nov 30 14:08 102 -> socket:[31093] > lrwx-- 1 root root 64 Nov 30 14:08 1020 -> socket:[44371] > lrwx-- 1 root root 64 Nov 30 14:08 1021 -> socket:[89437] > lrwx-- 1 root root 64 Nov 30 14:08 1022 -> socket:[75097] > lrwx-- 1 root root 64 Nov 30 14:08 1023 -> socket:[73048] > lrwx-- 1 root root 64 Nov 30 14:08 103 -> socket:[36939] -- This link no longer accessible - You can checkout the full set of limit options at: http://upstart.ubuntu.com/wiki/Stanzas#limit root@ovrh0301:/etc/pam.d# strings /sbin/init | grep limit setrlimit rlimit rlimits state_rlimit_deserialise_all state_rlimit_deserialise state_rlimit_serialise_all state_rlimit_serialise respawn_limit unable to set "%s" resource limit: %s unlimited Illegal limit, expected 'unlimited' or integer stanza_limit root@ovrh0301:/etc/pam.d# --- Which file that need to set for this parameter? The following is an example of increase the maximum number of open files to 4096 for a given upstart job: limit nofile 409
