[ovs-discuss] failed to put[create][modify]

Federico Iezzi fiezzi at enter.it
Wed Jul 30 09:50:51 UTC 2014


Hi Guys!!

I’m sorry for this huge (!!|) delay but I was in vacation and when I came back I had to manage some trouble situations.
So, this morning I test the latest 2.3 OVS version (commit 5eba2795fc5d4e833e9827ce18f6167e382bf0e1). OS Ubuntu 12.04.4 with Linux Kernel 3.13.0-32 provided by Canonical. Changelog below
http://changelogs.ubuntu.com/changelogs/pool/main/l/linux-lts-trusty/linux-lts-trusty_3.13.0-32.57~precise1/changelog

Unfortunately I have the same issue.

2014-07-30T09:03:09.270Z|00002|dpif(handler65)|WARN|system at ovs-system: failed to put[create][modify] (No such file or directory) dp_hash(0/0),recirc_id(0),skb_priority(0),tunnel(tun_id=0x6e,src=10.19.28.1,dst=10.19.28.2,tos=0x0,ttl=64,flags(key)),in_port(4),skb_mark(0),eth(src=ce:6a:c7:fa:d8:a0/00:00:00:00:00:00,dst=33:33:00:00:00:16/00:00:00:00:00:00),eth_type(0x86dd),ipv6(src=fe80::7c57:98ff:fea7:73e0/::,dst=ff02::16/::,label=0/0,proto=58/0,tclass=0/0,hlimit=1/0,frag=no/0xff),icmpv6(type=143/0,code=0/0), actions:drop
2014-07-30T09:28:15.638Z|00002|dpif(handler66)|WARN|system at ovs-system: failed to put[create][modify] (No such file or directory) dp_hash(0/0),recirc_id(0),skb_priority(0),in_port(1),skb_mark(0/0),eth(src=fa:16:3e:9a:6e:5f,dst=fa:16:3e:4d:38:9d),eth_type(0x0800),ipv4(src=192.168.1.35/0.0.0.0,dst=192.168.1.36/0.0.0.0,proto=6/0,tos=0/0x3,ttl=64/0,frag=no/0xff),tcp(src=5001/0,dst=51344/0),tcp_flags(0x012/0x000), actions:set(tunnel(tun_id=0x67,src=10.19.28.2,dst=10.19.28.3,tos=0x0,ttl=64,flags(df,key))),4
2014-07-30T09:32:39.891Z|00005|dpif(handler62)|WARN|system at ovs-system: failed to put[create][modify] (No such file or directory) dp_hash(0/0),recirc_id(0),skb_priority(0),tunnel(tun_id=0x67,src=10.19.27.1,dst=10.19.28.2,tos=0x0,ttl=64,flags(key)),in_port(4),skb_mark(0),eth(src=fa:16:3e:36:9f:70,dst=fa:16:3e:9a:6e:5f),eth_type(0x0806),arp(sip=192.168.1.4/0.0.0.0,tip=192.168.1.35/0.0.0.0,op=2/0,sha=fa:16:3e:36:9f:70/00:00:00:00:00:00,tha=fa:16:3e:9a:6e:5f/00:00:00:00:00:00), actions:1
2014-07-30T09:36:37.096Z|00001|dpif(handler69)|WARN|system at ovs-system: failed to put[create][modify] (No such file or directory) dp_hash(0/0),recirc_id(0),skb_priority(0),tunnel(tun_id=0x75,src=10.19.27.2,dst=10.19.28.2,tos=0x0,ttl=64,flags(key)),in_port(4),skb_mark(0),eth(src=fa:16:3e:de:fd:2f/00:00:00:00:00:00,dst=fa:16:3e:0b:6a:da/00:00:00:00:00:00),eth_type(0x0800),ipv4(src=80.82.70.148/0.0.0.0,dst=192.168.8.30/0.0.0.0,proto=6/0,tos=0/0,ttl=250/0,frag=no/0xff),tcp(src=60083/0,dst=8088/0),tcp_flags(0x002/0x000), actions:drop
2014-07-30T09:45:09.531Z|00001|dpif(handler68)|WARN|system at ovs-system: failed to put[create][modify] (No such file or directory) dp_hash(0/0),recirc_id(0),skb_priority(0),tunnel(tun_id=0x6e,src=10.19.28.14,dst=10.19.28.2,tos=0x0,ttl=64,flags(key)),in_port(4),skb_mark(0),eth(src=0e:27:1b:49:a9:60/00:00:00:00:00:00,dst=33:33:00:00:00:02/00:00:00:00:00:00),eth_type(0x86dd),ipv6(src=fe80::5801:3ff:fe4d:1345/::,dst=ff02::2/::,label=0/0,proto=58/0,tclass=0/0,hlimit=255/0,frag=no/0xff),icmpv6(type=133/0,code=0/0), actions:drop

ovs-vsctl --version
ovs-vsctl (Open vSwitch) 2.3.0
Compiled Jul 30 2014 07:59:46
DB Schema 7.6.0
ovs-dpctl show
system at ovs-system:
lookups: hit:92901140 missed:2071 lost:0
flows: 7
masks: hit:99027878 total:5 hit/pkt:1.07
port 0: ovs-system (internal)
port 1: qvo15a48b1e-fa
port 2: br-int (internal)
port 3: br-tun (internal)
port 4: vxlan_sys_4789 (vxlan: df_default=false, ttl=0)
ovs-vsctl show
2c653354-38e7-4504-a9c8-2acb88834e41
    Bridge br-tun
        Port "vxlan-10.19.28.3"
            Interface "vxlan-10.19.28.3"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.3"}
        Port br-tun
            Interface br-tun
                type: internal
        Port "vxlan-10.19.28.4"
            Interface "vxlan-10.19.28.4"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.4"}
        Port "vxlan-10.19.28.12"
            Interface "vxlan-10.19.28.12"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.12"}
        Port "vxlan-10.19.27.1"
            Interface "vxlan-10.19.27.1"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.27.1"}
        Port "vxlan-10.19.28.8"
            Interface "vxlan-10.19.28.8"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.8"}
        Port "vxlan-10.19.28.11"
            Interface "vxlan-10.19.28.11"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.11"}
        Port "vxlan-10.19.28.13"
            Interface "vxlan-10.19.28.13"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.13"}
        Port "vxlan-10.19.28.15"
            Interface "vxlan-10.19.28.15"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.15"}
        Port "vxlan-10.19.28.10"
            Interface "vxlan-10.19.28.10"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.10"}
        Port "vxlan-10.19.28.14"
            Interface "vxlan-10.19.28.14"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.14"}
        Port "vxlan-10.19.27.2"
            Interface "vxlan-10.19.27.2"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.27.2"}
        Port "vxlan-10.19.28.6"
            Interface "vxlan-10.19.28.6"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.6"}
        Port "vxlan-10.19.28.9"
            Interface "vxlan-10.19.28.9"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.9"}
        Port "vxlan-10.19.28.5"
            Interface "vxlan-10.19.28.5"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.5"}
        Port "vxlan-10.19.28.7"
            Interface "vxlan-10.19.28.7"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.7"}
        Port patch-int
            Interface patch-int
                type: patch
                options: {peer=patch-tun}
        Port "vxlan-10.19.28.1"
            Interface "vxlan-10.19.28.1"
                type: vxlan
                options: {in_key=flow, local_ip="10.19.28.2", out_key=flow, remote_ip="10.19.28.1"}
    Bridge br-int
        Port patch-tun
            Interface patch-tun
                type: patch
                options: {peer=patch-int}
        Port br-int
            Interface br-int
                type: internal
        Port "qvo15a48b1e-fa"
            tag: 1
            Interface "qvo15a48b1e-fa"
    ovs_version: "2.3.0"

--------------------------------------------
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.

Il giorno 18/lug/2014, alle ore 04:15, Jesse Gross <jesse at nicira.com<mailto:jesse at nicira.com>> ha scritto:

If you are experiencing this problem, can you please test with the
latest master code? It has a fix for one problem and additional
logging in case there are others.

On Tue, Jul 15, 2014 at 8:18 AM, yinpeijun <yinpeijun-joy at 163.com<mailto:yinpeijun-joy at 163.com>> wrote:

Hi Jesse

I want to know is there any conclusion or what is your next plan ?

Thanks for the additional information.

I'm still having a hard time seeing how a flow could be invalid without generating any log messages so I just sent out a patch to hopefully cover the remaining cases (CC'ed to you). The patch is against
master - is it possible for you to try it and report any messages that show up in dmesg?

Also, can you send a copy of what both your kernel and userspace flow tables look like when this happens (ovs-dpctl dump-flows and ovs-ofctl dump-flows <BR> respectively)?

On Mon, Jun 30, 2014 at 1:08 PM, Federico Iezzi <fiezzi at enter.it<mailto:fiezzi at enter.it>> wrote:

Hi Jesse,


Here we go, I’m really sorry for this huge delay but I had some trouble.



_______________________________________________
discuss mailing list
discuss at openvswitch.org<mailto:discuss at openvswitch.org>
http://openvswitch.org/mailman/listinfo/discuss

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://openvswitch.org/pipermail/ovs-discuss/attachments/20140730/d8c053a6/attachment-0002.html>


More information about the discuss mailing list