networking - 级别=致命的消息=“ipset [destroy] failed: ipset v6.29: Set cannot be destroyed: it is in use by a kernel component\n: exit status 1”-6ren

networking - 级别=致命的消息=“ipset [destroy] failed: ipset v6.29: Set cannot be destroyed: it is in use by a kernel component\n: exit status 1”

转载作者：行者123 更新时间：2023-12-02 20:17:23

基本信息:

系统:

# cat /proc/version

Linux version 3.10.0-514.2.2.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Tue Dec 6 23:06:41 UTC 2016

Kubeadm版本:

# kubeadm version

kubeadm version: version.Info{Major:"1", Minor:"6+", GitVersion:"v1.6.0-alpha.0.2074+a092d8e0f95f52", GitCommit:"a092d8e0f95f5200f7ae2cba45c75ab42da36537", GitTreeState:"clean", BuildDate:"2016-12-13T17:03:18Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}

Kubectl版本

# kubectl version

Client Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:57:05Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"5", GitVersion:"v1.5.1", GitCommit:"82450d03cb057bab0950214ef122b67c83fb11df", GitTreeState:"clean", BuildDate:"2016-12-14T00:52:01Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}

Docker版本

# docker version

Client:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 02:23:59 2016
 OS/Arch:      linux/amd64

Server:
 Version:      1.12.5
 API version:  1.24
 Go version:   go1.6.4
 Git commit:   7392c3b
 Built:        Fri Dec 16 02:23:59 2016
 OS/Arch:      linux/amd64

编织图像

REPOSITORY                                               TAG                 IMAGE ID            CREATED             SIZE
weaveworks/weave-npc                                     1.8.2               c91ef3f4642b        4 weeks ago         68.77 MB
weaveworks/weave-kube                                    1.8.2               a4740ae55aae        4 weeks ago         166.7 MB

问题

我正在使用kubeadm部署k8s。奇怪的是，在首次时，编织在新VM上的kube-dns可以正常工作，但在重新设置kubeadm并重新初始化后，编织不再起作用。

Kubectl获取 pod

[root@192-168-1-177 pod_network]# kubectl get pods -o wide --all-namespaces
NAMESPACE     NAME                                           READY     STATUS             RESTARTS   AGE       IP              NODE
kube-system   dummy-2088944543-tdxck                         1/1       Running            0          59m       192.168.1.177   192-168-1-177.master
kube-system   etcd-192-168-1-177.master                      1/1       Running            0          59m       192.168.1.177   192-168-1-177.master
kube-system   kube-apiserver-192-168-1-177.master            1/1       Running            0          59m       192.168.1.177   192-168-1-177.master
kube-system   kube-controller-manager-192-168-1-177.master   1/1       Running            0          59m       192.168.1.177   192-168-1-177.master
kube-system   kube-discovery-1769846148-87pgm                1/1       Running            0          59m       192.168.1.177   192-168-1-177.master
kube-system   kube-dns-2924299975-82sb6                      4/4       Running            0          59m       10.32.0.2       192-168-1-177.master
kube-system   kube-proxy-8xprh                               1/1       Running            0          59m       192.168.1.177   192-168-1-177.master
kube-system   kube-scheduler-192-168-1-177.master            1/1       Running            0          59m       192.168.1.177   192-168-1-177.master
kube-system   weave-net-ssqtd                                1/2       CrashLoopBackOff   16         58m       192.168.1.177   192-168-1-177.master

Kubectl日志

  # kubectl logs $(kubectl get pods --all-namespaces | grep weave-net | awk '{print $2}') -n kube-system weave-npc

  time="2017-01-09T11:11:17Z" level=info msg="Starting Weaveworks NPC 1.8.2" 
  time="2017-01-09T11:11:17Z" level=info msg="Serving /metrics on :6781" 
  Mon Jan  9 11:11:17 2017 <5> ulogd.c:843 building new pluginstance stack: 'log1:NFLOG,base1:BASE,pcap1:PCAP'
  time="2017-01-09T11:11:17Z" level=fatal msg="ipset [destroy] failed: ipset v6.29: Set cannot be destroyed: it is in use by a kernel component\n: exit status 1"

基本操作

Kubeadm初始化

kubeadm init --api-advertise-addresses 192.168.1.177 --use-kubernetes-version v1.5.1

应用编织

kubectl apply -f https://git.io/weave-kube

Kubeadm重置

kubeadm reset
docker rm `docker ps -a -q`
find /var/lib/kubelet | xargs -n 1 findmnt -n -t tmpfs -o TARGET -T | uniq | xargs -r umount -v
rm -r -f /etc/kubernetes /var/lib/kubelet /var/lib/etcd

最佳答案

我只是通过我的VM计算机 REBOOT 解决了自己的问题。

重启之前:

Ipset列表

# ipset list

Name: weave-k?Z;25^M}|1s7P3|H9i;*;MhG
Type: hash:ip
Revision: 1
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 16528
References: 0
Members:

Name: weave-iuZcey(5DeXbzgRFs8Szo]<@p
Type: hash:ip
Revision: 1
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 16528
References: 0
Members:

Name: weave-#Of<X6ofOD9U?jkdAmmuY.VL(
Type: hash:ip
Revision: 1
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 16528
References: 0
Members:

Name: felix-calico-hosts-4
Type: hash:ip
Revision: 1
Header: family inet hashsize 1024 maxelem 1048576
Size in memory: 16528
References: 1
Members:

Name: felix-all-ipam-pools
Type: hash:net
Revision: 3
Header: family inet hashsize 1024 maxelem 1048576
Size in memory: 16784
References: 1
Members:

Name: felix-masq-ipam-pools
Type: hash:net
Revision: 3
Header: family inet hashsize 1024 maxelem 1048576
Size in memory: 16784
References: 1
Members:

Ipset销毁

# ipset destroy

ipset v6.19: Set cannot be destroyed: it is in use by a kernel component

重新启动后:

Ipset列表

# ipset list

Name: weave-iuZcey(5DeXbzgRFs8Szo]<@p
Type: hash:ip
Revision: 1
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 16544
References: 1
Members:
10.32.0.2

Name: weave-k?Z;25^M}|1s7P3|H9i;*;MhG
Type: hash:ip
Revision: 1
Header: family inet hashsize 1024 maxelem 65536
Size in memory: 16528
References: 1
Members:

一切都很好。

Kubectl获取 pod

# kubectl get pods -o wide --all-namespaces

NAMESPACE     NAME                                           READY     STATUS    RESTARTS   AGE       IP              NODE
default       busybox                                        1/1       Running   0          6s        10.44.0.1       192-168-1-178.node
kube-system   dummy-2088944543-05kj3                         1/1       Running   0          19m       192.168.1.177   192-168-1-177.master
kube-system   etcd-192-168-1-177.master                      1/1       Running   0          18m       192.168.1.177   192-168-1-177.master
kube-system   kube-apiserver-192-168-1-177.master            1/1       Running   0          18m       192.168.1.177   192-168-1-177.master
kube-system   kube-controller-manager-192-168-1-177.master   1/1       Running   0          17m       192.168.1.177   192-168-1-177.master
kube-system   kube-discovery-1769846148-3t242                1/1       Running   0          19m       192.168.1.177   192-168-1-177.master
kube-system   kube-dns-2924299975-6bv1x                      4/4       Running   0          19m       10.32.0.2       192-168-1-177.master
kube-system   kube-proxy-4jqzb                               1/1       Running   0          19m       192.168.1.177   192-168-1-177.master
kube-system   kube-proxy-kxkxm                               1/1       Running   0          10m       192.168.1.178   192-168-1-178.node
kube-system   kube-scheduler-192-168-1-177.master            1/1       Running   0          18m       192.168.1.177   192-168-1-177.master
kube-system   weave-net-jgwwt                                2/2       Running   0          10m       192.168.1.178   192-168-1-178.node
kube-system   weave-net-s4w7w                                2/2       Running   0          17m       192.168.1.177   192-168-1-177.master

关于networking - 级别=致命的消息=“ipset [destroy] failed: ipset v6.29: Set cannot be destroyed: it is in use by a kernel component\n: exit status 1”，我们在Stack Overflow上找到一个类似的问题： https://stackoverflow.com/questions/41547544/

文章推荐： docker - 我应该在已经具有Cpanel的服务器上安装Docker吗？

ruby-on-rails - rails : how to disable before_destroy callback when it's being destroyed because of the parent is being destroyed (:dependent => :destroy)
我有两个类(class): parent 和 child child : belongs_to :parent 和家长 has_many :children, :dependent => :dest
ruby-on-rails - Has_many 通过关联依赖 : destroy not destroying
我有这个模型 class XmlImport ["text/xml"] end :event_import_records 条目正在被销毁。但是 :events 不是。 has_many throu
terraform - 亚特实验室 CI : terraform destroy doesn't destroy?
我定义了以下简单的管道: image: name: hashicorp/terraform:light entrypoint: - '/usr/bin/env' - 'PATH
terraform - 亚特实验室 CI : terraform destroy doesn't destroy?
我定义了以下简单的管道: image: name: hashicorp/terraform:light entrypoint: - '/usr/bin/env' - 'PATH
ruby-on-rails - 触发依赖 : :destroy with overridden destroy-method
在我们的应用程序中，我们覆盖了 ActiveRecord destroy 方法，以便我们的记录不会被删除(因此用户可以取消删除)。像这样: def destroy self.is_deleted
ruby-on-rails - :dependent => :destroy isn't calling the destroy method before the deletion?
我有一个笔记模型，具有以下关联注意.rb has_many :note_categories, :dependent => :destroy has_many :categories, :throu
python - Tcl 错误 : can't invoke "destroy" command: application has been destroyed
我是一名 Python 初学者。尝试制作一个新按钮来关闭窗口。我收到错误消息: Exception in Tkinter callback Traceback (most recent call la
ruby-on-rails - CommentsController :Class in my destroy comment method 的未定义局部变量或方法 `destroy'
我在我的应用程序中添加了评论功能，到目前为止一切正常，直到出现此错误。我所做的是添加了删除评论功能。当我启动服务器时一切正常，但在我单击“删除”按钮后问题出现了。错误信息 undefined loc
ruby-on-rails - Rails，def destroy，没有响应 destroy.js.erb，为什么？
Rails，def destroy，没有响应 destroy.js.erb 这是我的方法: # DELETE /Groups/1 # DELETE /Groups/1.xml def de
oop - Excel VBA : Does destroying a collection of objects destroy every single object?
假设我有一个 MyClass 对象的集合 MyCollection。 Set MyCollection = Nothing 是否调用每个包含的对象的析构函数，或者我应该单独设置每个对象 = Nothi
javascript - 蒙哥错误: topology was destroyed(when finding the documents) and instance pool was destroyed (when inserting documents)
我正在尝试使用 Node.js、Express 和 Mongodb 构建 REST API。我正在使用 mongodb npm 包连接到数据库，下面是我的 sever.js 文件代码 var expr
ruby-on-rails - ruby rails 3 : after destroy method to destroy object if there is no more related objects in the system?
我有一个小问题，我有以下两个模型: class CriticalProcess :destroy has_many :roles, :through => :authorizations a
Angular 2 错误 : Attempt to use a destroyed view: detectChanges Error: Attempt to use a destroyed view: detectChanges at ViewDestroyedError
我正在使用 ng2-toastr 并收到以下错误 https://www.npmjs.com/package/ng2-toastr Attempt to use a destroyed view: d
networking - 级别=致命的消息=“ipset [destroy] failed: ipset v6.29: Set cannot be destroyed: it is in use by a kernel component\n: exit status 1”
基本信息: 系统: # cat /proc/version Linux version 3.10.0-514.2.2.el7.x86_64 (builder@kbuilder.dev.centos.o
ThreadGroup 的 destroy
一点睛 destroy 用于销毁 ThreadGroup，该方法只是针对一个没有任何 active 线程的 group 进行一次 destroy 标记，调用该方法的直接结果是在父 group 中将自
perl - DESTROY 以意外的顺序调用
我开始注意到 Scope::Guard 的一些奇怪之处。 . 如果我取消定义 $guard变量作为 sub 中的最后一个语句，守卫的 sub 得到比我预期的要晚打电话。如果我不取消它，或者如果我做
AngularJS $destroy 动态插入的组件
我正在构建一个提供打开和关闭它的服务的模式。该模式有一个控制关闭按钮的小 Controller ，以及进入模式内容的模板的 $compile。那个模板就是一个组件，当然，那个组件有一个 Contro
AngularJS:指令范围没有被调用 $destroy
一直在文件馆和网上寻找答案，但没有真正找到答案，只是零零碎碎。似乎有很多建议的帖子，但没有一个有答案。我有一个使用范围的复杂指令:true。它实际上是我正在尝试为其编写清理代码的 ng-grid 最
delphi - 为什么不调用 Destroy？
给定以下 Delphi 代码，Foo 在 FormClose 上是 Free，但 TFoo.Destroy 是没有被调用 - 因此 Bar 没有被 Free'd，导致内存泄漏？我是否在这里错过了一些
AngularJS - $destroy 是否删除事件监听器？
https://docs.angularjs.org/guide/directive By listening to this event, you can remove event listener

行者123

个人简介

我是一名优秀的程序员,十分优秀！

作者热门文章

滴滴打车优惠券免费领取

全站热门文章

首页

博学

6Ren·AI

商城

networking - 级别=致命的消息=“ipset [destroy] failed: ipset v6.29: Set cannot be destroyed: it is in use by a kernel component\n: exit status 1”