On Thu, Jul 16, 2015 at 3:07 PM, Alex Wang wrote:
> Sorry for this very delayed reply,
>
> I think I found the issue, in branch 2.1.*
>
> Will send out a fix soon,
>
>
Sorry I found my theory was wrong, things seem to be trickier~
Want to know if you have modified the source code?
Also, could y
Sorry for this very delayed reply,
I think I found the issue, in branch 2.1.*
Will send out a fix soon,
At the same time, it branch >= 2.3 do not have this issue due to the use of
ovs-rcu... And since branch 2.3 is the LTS branch, I would really recommend
you to switch to 2.3+
Thanks,
Alex Wan
Hi,all
Is anybody know what the problem caused by and how to solve it ?
Look forward for your replying.
At 2015-07-10 18:32:07, "马啸" wrote:
Hi,all
The version is 2.1.2 . openvswitch-2.1.2-26.el6.x86_64
The information as bellow:
===
Hi,all
The version is 2.1.2 . openvswitch-2.1.2-26.el6.x86_64
The information as bellow:
=
Core was generated by `ovs-vswitchd unix:/var/run/openvswitch/db.sock
-vconsole:emer -vsyslog:err -vfi'.
Program term
This could be related to b953042214201e2693a485a8ba8b19f69e5bdf34
("datapath: simplify sample action implementation"). I would check
that you are using OVS 2.3.2 for anything related to sampling.
On Thu, Jul 9, 2015 at 8:43 PM, Alex Wang wrote:
> Hey,
>
> Could you send the core dump info (did no
Hey,
Could you send the core dump info (did not see any attachment)? I assume
you
mean the gdb printout showing what causes the crash. Also, could you
provide
the ovs version you are using?
I'm trying to debug an ipfix related crash, could we related,
Thanks, 谢谢,
Alex Wang,
On Thu, Jul 9, 201
Hi,all
I am one engineer from UnitedStack, one OpenStack Provider.
We are using OpenvSwitch as the software-switch in OpenStack Compute and
Network Node, and we enabled sflow to monitor the traffic.
And one crash happened. The core-dump information is attached, could anybody
help us to sol
