Skip to content

Instantly share code, notes, and snippets.

@vmpjdc
Created August 26, 2024 23:33
Show Gist options
  • Save vmpjdc/06913c8125814eb98f8ebda3fd356ab2 to your computer and use it in GitHub Desktop.
Save vmpjdc/06913c8125814eb98f8ebda3fd356ab2 to your computer and use it in GitHub Desktop.
journalctl -xe -u snap.k8s.kube-proxy.service | cat
-- Boot 4d2db5cba2684d18ba240fd88b6f3e31 --
Aug 24 00:32:16 juju-bd78f7-stg-netbox-30 systemd[1]: Started Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A start job for unit snap.k8s.kube-proxy.service has finished successfully
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A start job for unit snap.k8s.kube-proxy.service has finished successfully.
â–‘â–‘
â–‘â–‘ The job identifier is 129.
Aug 24 00:33:03 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[971]: The connection to the server 127.0.0.1:6443 was refused - did you specify the right host or port?
Aug 24 00:33:03 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:06 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1209]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:06 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:09 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1225]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:09 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:12 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1301]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:12 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:16 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1356]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:16 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:19 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1394]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:19 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:22 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1495]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:22 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:25 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1512]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:25 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:28 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1622]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:28 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:31 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1639]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:31 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:34 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1651]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:34 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:37 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1670]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:37 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:41 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1687]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:41 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:44 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1717]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:44 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:47 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1738]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:47 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:50 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1758]: error: You must be logged in to the server (Unauthorized)
Aug 24 00:33:50 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: Waiting for kube-apiserver to start
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: + exec /snap/k8s/313/bin/kube-proxy --cluster-cidr=10.1.0.0/16 --healthz-bind-address=127.0.0.1 --hostname-override=juju-bd78f7-stg-netbox-30 --kubeconfig=/etc/kubernetes/proxy.conf --profiling=false
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: I0824 00:33:53.621814 611 server_linux.go:69] "Using iptables proxy"
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: I0824 00:33:53.651253 611 server.go:1062] "Successfully retrieved node IP(s)" IPs=["10.142.102.91"]
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: I0824 00:33:53.652936 611 conntrack.go:119] "Set sysctl" entry="net/netfilter/nf_conntrack_max" value=131072
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: E0824 00:33:53.653060 611 server.go:558] "Error running ProxyServer" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[611]: E0824 00:33:53.653169 611 run.go:74] "command failed" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Main process exited, code=exited, status=1/FAILURE
â–‘â–‘ Subject: Unit process exited
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ An ExecStart= process belonging to unit snap.k8s.kube-proxy.service has exited.
â–‘â–‘
â–‘â–‘ The process' exit code is 'exited' and its exit status is 1.
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Failed with result 'exit-code'.
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ The unit snap.k8s.kube-proxy.service has entered the 'failed' state with result 'exit-code'.
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Consumed 3.354s CPU time.
â–‘â–‘ Subject: Resources consumed by unit runtime
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ The unit snap.k8s.kube-proxy.service completed and consumed the indicated resources.
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Scheduled restart job, restart counter is at 1.
â–‘â–‘ Subject: Automatic restarting of a unit has been scheduled
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ Automatic restarting of the unit snap.k8s.kube-proxy.service has been scheduled, as the result for
â–‘â–‘ the configured Restart= setting for the unit.
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 systemd[1]: Stopped Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A stop job for unit snap.k8s.kube-proxy.service has finished
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A stop job for unit snap.k8s.kube-proxy.service has finished.
â–‘â–‘
â–‘â–‘ The job identifier is 303 and the job result is done.
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Consumed 3.354s CPU time.
â–‘â–‘ Subject: Resources consumed by unit runtime
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ The unit snap.k8s.kube-proxy.service completed and consumed the indicated resources.
Aug 24 00:33:53 juju-bd78f7-stg-netbox-30 systemd[1]: Started Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A start job for unit snap.k8s.kube-proxy.service has finished successfully
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A start job for unit snap.k8s.kube-proxy.service has finished successfully.
â–‘â–‘
â–‘â–‘ The job identifier is 303.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1835]: + exec /snap/k8s/313/bin/kube-proxy --cluster-cidr=10.1.0.0/16 --healthz-bind-address=127.0.0.1 --hostname-override=juju-bd78f7-stg-netbox-30 --kubeconfig=/etc/kubernetes/proxy.conf --profiling=false
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1835]: I0824 00:33:54.077225 1835 server_linux.go:69] "Using iptables proxy"
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1835]: I0824 00:33:54.084432 1835 server.go:1062] "Successfully retrieved node IP(s)" IPs=["10.142.102.91"]
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1835]: I0824 00:33:54.085283 1835 conntrack.go:119] "Set sysctl" entry="net/netfilter/nf_conntrack_max" value=131072
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1835]: E0824 00:33:54.085315 1835 server.go:558] "Error running ProxyServer" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1835]: E0824 00:33:54.085332 1835 run.go:74] "command failed" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Main process exited, code=exited, status=1/FAILURE
â–‘â–‘ Subject: Unit process exited
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ An ExecStart= process belonging to unit snap.k8s.kube-proxy.service has exited.
â–‘â–‘
â–‘â–‘ The process' exit code is 'exited' and its exit status is 1.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Failed with result 'exit-code'.
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ The unit snap.k8s.kube-proxy.service has entered the 'failed' state with result 'exit-code'.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Scheduled restart job, restart counter is at 2.
â–‘â–‘ Subject: Automatic restarting of a unit has been scheduled
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ Automatic restarting of the unit snap.k8s.kube-proxy.service has been scheduled, as the result for
â–‘â–‘ the configured Restart= setting for the unit.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 systemd[1]: Stopped Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A stop job for unit snap.k8s.kube-proxy.service has finished
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A stop job for unit snap.k8s.kube-proxy.service has finished.
â–‘â–‘
â–‘â–‘ The job identifier is 390 and the job result is done.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 systemd[1]: Started Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A start job for unit snap.k8s.kube-proxy.service has finished successfully
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A start job for unit snap.k8s.kube-proxy.service has finished successfully.
â–‘â–‘
â–‘â–‘ The job identifier is 390.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1864]: + exec /snap/k8s/313/bin/kube-proxy --cluster-cidr=10.1.0.0/16 --healthz-bind-address=127.0.0.1 --hostname-override=juju-bd78f7-stg-netbox-30 --kubeconfig=/etc/kubernetes/proxy.conf --profiling=false
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1864]: I0824 00:33:54.543162 1864 server_linux.go:69] "Using iptables proxy"
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1864]: I0824 00:33:54.550029 1864 server.go:1062] "Successfully retrieved node IP(s)" IPs=["10.142.102.91"]
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1864]: I0824 00:33:54.551180 1864 conntrack.go:119] "Set sysctl" entry="net/netfilter/nf_conntrack_max" value=131072
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1864]: E0824 00:33:54.551299 1864 server.go:558] "Error running ProxyServer" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1864]: E0824 00:33:54.551404 1864 run.go:74] "command failed" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Main process exited, code=exited, status=1/FAILURE
â–‘â–‘ Subject: Unit process exited
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ An ExecStart= process belonging to unit snap.k8s.kube-proxy.service has exited.
â–‘â–‘
â–‘â–‘ The process' exit code is 'exited' and its exit status is 1.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Failed with result 'exit-code'.
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ The unit snap.k8s.kube-proxy.service has entered the 'failed' state with result 'exit-code'.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Scheduled restart job, restart counter is at 3.
â–‘â–‘ Subject: Automatic restarting of a unit has been scheduled
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ Automatic restarting of the unit snap.k8s.kube-proxy.service has been scheduled, as the result for
â–‘â–‘ the configured Restart= setting for the unit.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 systemd[1]: Stopped Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A stop job for unit snap.k8s.kube-proxy.service has finished
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A stop job for unit snap.k8s.kube-proxy.service has finished.
â–‘â–‘
â–‘â–‘ The job identifier is 477 and the job result is done.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 systemd[1]: Started Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A start job for unit snap.k8s.kube-proxy.service has finished successfully
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A start job for unit snap.k8s.kube-proxy.service has finished successfully.
â–‘â–‘
â–‘â–‘ The job identifier is 477.
Aug 24 00:33:54 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1891]: + exec /snap/k8s/313/bin/kube-proxy --cluster-cidr=10.1.0.0/16 --healthz-bind-address=127.0.0.1 --hostname-override=juju-bd78f7-stg-netbox-30 --kubeconfig=/etc/kubernetes/proxy.conf --profiling=false
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1891]: I0824 00:33:55.037960 1891 server_linux.go:69] "Using iptables proxy"
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1891]: I0824 00:33:55.046984 1891 server.go:1062] "Successfully retrieved node IP(s)" IPs=["10.142.102.91"]
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1891]: I0824 00:33:55.048323 1891 conntrack.go:119] "Set sysctl" entry="net/netfilter/nf_conntrack_max" value=131072
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1891]: E0824 00:33:55.048491 1891 server.go:558] "Error running ProxyServer" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1891]: E0824 00:33:55.048613 1891 run.go:74] "command failed" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Main process exited, code=exited, status=1/FAILURE
â–‘â–‘ Subject: Unit process exited
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ An ExecStart= process belonging to unit snap.k8s.kube-proxy.service has exited.
â–‘â–‘
â–‘â–‘ The process' exit code is 'exited' and its exit status is 1.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Failed with result 'exit-code'.
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ The unit snap.k8s.kube-proxy.service has entered the 'failed' state with result 'exit-code'.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Scheduled restart job, restart counter is at 4.
â–‘â–‘ Subject: Automatic restarting of a unit has been scheduled
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ Automatic restarting of the unit snap.k8s.kube-proxy.service has been scheduled, as the result for
â–‘â–‘ the configured Restart= setting for the unit.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: Stopped Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A stop job for unit snap.k8s.kube-proxy.service has finished
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A stop job for unit snap.k8s.kube-proxy.service has finished.
â–‘â–‘
â–‘â–‘ The job identifier is 564 and the job result is done.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: Started Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A start job for unit snap.k8s.kube-proxy.service has finished successfully
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A start job for unit snap.k8s.kube-proxy.service has finished successfully.
â–‘â–‘
â–‘â–‘ The job identifier is 564.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1918]: + exec /snap/k8s/313/bin/kube-proxy --cluster-cidr=10.1.0.0/16 --healthz-bind-address=127.0.0.1 --hostname-override=juju-bd78f7-stg-netbox-30 --kubeconfig=/etc/kubernetes/proxy.conf --profiling=false
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1918]: I0824 00:33:55.520570 1918 server_linux.go:69] "Using iptables proxy"
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1918]: I0824 00:33:55.527419 1918 server.go:1062] "Successfully retrieved node IP(s)" IPs=["10.142.102.91"]
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1918]: I0824 00:33:55.528587 1918 conntrack.go:119] "Set sysctl" entry="net/netfilter/nf_conntrack_max" value=131072
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1918]: E0824 00:33:55.528733 1918 server.go:558] "Error running ProxyServer" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1918]: E0824 00:33:55.528856 1918 run.go:74] "command failed" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Main process exited, code=exited, status=1/FAILURE
â–‘â–‘ Subject: Unit process exited
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ An ExecStart= process belonging to unit snap.k8s.kube-proxy.service has exited.
â–‘â–‘
â–‘â–‘ The process' exit code is 'exited' and its exit status is 1.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Failed with result 'exit-code'.
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ The unit snap.k8s.kube-proxy.service has entered the 'failed' state with result 'exit-code'.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Scheduled restart job, restart counter is at 5.
â–‘â–‘ Subject: Automatic restarting of a unit has been scheduled
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ Automatic restarting of the unit snap.k8s.kube-proxy.service has been scheduled, as the result for
â–‘â–‘ the configured Restart= setting for the unit.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: Stopped Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A stop job for unit snap.k8s.kube-proxy.service has finished
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A stop job for unit snap.k8s.kube-proxy.service has finished.
â–‘â–‘
â–‘â–‘ The job identifier is 651 and the job result is done.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: Started Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A start job for unit snap.k8s.kube-proxy.service has finished successfully
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A start job for unit snap.k8s.kube-proxy.service has finished successfully.
â–‘â–‘
â–‘â–‘ The job identifier is 651.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1942]: + exec /snap/k8s/313/bin/kube-proxy --cluster-cidr=10.1.0.0/16 --healthz-bind-address=127.0.0.1 --hostname-override=juju-bd78f7-stg-netbox-30 --kubeconfig=/etc/kubernetes/proxy.conf --profiling=false
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1942]: I0824 00:33:55.789754 1942 server_linux.go:69] "Using iptables proxy"
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1942]: I0824 00:33:55.797132 1942 server.go:1062] "Successfully retrieved node IP(s)" IPs=["10.142.102.91"]
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1942]: I0824 00:33:55.798099 1942 conntrack.go:119] "Set sysctl" entry="net/netfilter/nf_conntrack_max" value=131072
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1942]: E0824 00:33:55.798130 1942 server.go:558] "Error running ProxyServer" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[1942]: E0824 00:33:55.798153 1942 run.go:74] "command failed" err="open /proc/sys/net/netfilter/nf_conntrack_max: no such file or directory"
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Main process exited, code=exited, status=1/FAILURE
â–‘â–‘ Subject: Unit process exited
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ An ExecStart= process belonging to unit snap.k8s.kube-proxy.service has exited.
â–‘â–‘
â–‘â–‘ The process' exit code is 'exited' and its exit status is 1.
Aug 24 00:33:55 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Failed with result 'exit-code'.
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ The unit snap.k8s.kube-proxy.service has entered the 'failed' state with result 'exit-code'.
Aug 24 00:33:56 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Scheduled restart job, restart counter is at 6.
â–‘â–‘ Subject: Automatic restarting of a unit has been scheduled
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ Automatic restarting of the unit snap.k8s.kube-proxy.service has been scheduled, as the result for
â–‘â–‘ the configured Restart= setting for the unit.
Aug 24 00:33:56 juju-bd78f7-stg-netbox-30 systemd[1]: Stopped Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A stop job for unit snap.k8s.kube-proxy.service has finished
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A stop job for unit snap.k8s.kube-proxy.service has finished.
â–‘â–‘
â–‘â–‘ The job identifier is 738 and the job result is done.
Aug 24 00:33:56 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Start request repeated too quickly.
Aug 24 00:33:56 juju-bd78f7-stg-netbox-30 systemd[1]: snap.k8s.kube-proxy.service: Failed with result 'exit-code'.
â–‘â–‘ Subject: Unit failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ The unit snap.k8s.kube-proxy.service has entered the 'failed' state with result 'exit-code'.
Aug 24 00:33:56 juju-bd78f7-stg-netbox-30 systemd[1]: Failed to start Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A start job for unit snap.k8s.kube-proxy.service has failed
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A start job for unit snap.k8s.kube-proxy.service has finished with a failure.
â–‘â–‘
â–‘â–‘ The job identifier is 738 and the job result is failed.
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 systemd[1]: Started Service for snap application k8s.kube-proxy.
â–‘â–‘ Subject: A start job for unit snap.k8s.kube-proxy.service has finished successfully
â–‘â–‘ Defined-By: systemd
â–‘â–‘ Support: http://www.ubuntu.com/support
â–‘â–‘
â–‘â–‘ A start job for unit snap.k8s.kube-proxy.service has finished successfully.
â–‘â–‘
â–‘â–‘ The job identifier is 4890.
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: + exec /snap/k8s/313/bin/kube-proxy --cluster-cidr=10.1.0.0/16 --healthz-bind-address=127.0.0.1 --hostname-override=juju-bd78f7-stg-netbox-30 --kubeconfig=/etc/kubernetes/proxy.conf --profiling=false
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.655472 482082 server_linux.go:69] "Using iptables proxy"
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.664188 482082 server.go:1062] "Successfully retrieved node IP(s)" IPs=["10.142.102.91"]
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.665534 482082 conntrack.go:119] "Set sysctl" entry="net/netfilter/nf_conntrack_max" value=131072
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.665685 482082 conntrack.go:59] "Setting nf_conntrack_max" nfConntrackMax=131072
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.665839 482082 conntrack.go:119] "Set sysctl" entry="net/netfilter/nf_conntrack_tcp_timeout_established" value=86400
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.665973 482082 conntrack.go:119] "Set sysctl" entry="net/netfilter/nf_conntrack_tcp_timeout_close_wait" value=3600
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.669824 482082 server.go:659] "kube-proxy running in dual-stack mode" primary ipFamily="IPv4"
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.669939 482082 server_linux.go:165] "Using iptables Proxier"
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.671425 482082 server_linux.go:511] "Detect-local-mode set to ClusterCIDR, but no cluster CIDR for family" ipFamily="IPv6"
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.671530 482082 server_linux.go:528] "Defaulting to no-op detect-local"
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.671680 482082 proxier.go:243] "Setting route_localnet=1 to allow node-ports on localhost; to change this either disable iptables.localhostNodePorts (--iptables-localhost-nodeports) or set nodePortAddresses (--nodeport-addresses) to filter loopback addresses"
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.671923 482082 server.go:872] "Version info" version="v1.30.0"
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.672023 482082 server.go:874] "Golang settings" GOGC="" GOMAXPROCS="" GOTRACEBACK=""
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.674225 482082 config.go:192] "Starting service config controller"
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.674266 482082 shared_informer.go:313] Waiting for caches to sync for service config
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.674714 482082 config.go:101] "Starting endpoint slice config controller"
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.674727 482082 shared_informer.go:313] Waiting for caches to sync for endpoint slice config
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.675008 482082 config.go:319] "Starting node config controller"
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.675015 482082 shared_informer.go:313] Waiting for caches to sync for node config
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.774433 482082 shared_informer.go:320] Caches are synced for service config
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.774789 482082 shared_informer.go:320] Caches are synced for endpoint slice config
Aug 26 22:50:10 juju-bd78f7-stg-netbox-30 k8s.kube-proxy[482082]: I0826 22:50:10.775231 482082 shared_informer.go:320] Caches are synced for node config
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment