Thanks Andy,Since i am using OVS 1.4.6,i will try to recreate by swapping
ram again.
I forgot to mention that after the crash system was showing
"parity check 2 system dimm memory"
Thanks for your help.
Regards,
Kev
On Thu, Nov 7, 2013 at 11:09 PM, Andy Zhou wrote:
> This is the sort of err
This is the sort of errors you may need to dig into a bit more at your
end.
We should first try to find out if this caused by hardware issues. I
suppose If you can experiment by swapping RAM back. RAM issues should also
cause crashes that are not OVS related.
If you can rule out RAM change being
Thanks for the reply Andy,
Can you help me identify reason for
this behavior.
I only know that Xenserver was down and hard reset was required to bring it
back.
Recently we changed RAM from 2 Gb x 4 (1333 Mhz) to 8Gb x 1 (1600 MHz).
i have ovs 1.4.2 running on o
It does look like OVS related.
On Wed, Nov 6, 2013 at 3:42 AM, kevin parker wrote:
> Hello All,
>
> One of our xen server server stopped responding after few
> network tests,can some one please help me verify whether it is related to
> ovs.
> In stack trace i can see ovs process id
Hello All,
One of our xen server server stopped responding after few
network tests,can some one please help me verify whether it is related to
ovs.
In stack trace i can see ovs process id.
*ovs-vsctl -V*
ovs-vsctl (Open vSwitch) 1.4.6
Compiled Jun 14 2013 09:23:27
*From log:*
<4>[
