1. phenomenon
ifup: waiting for lock on /run/network/ifstate.br-int
2. configurations
/etc/network/interfaces
allow-ovs br-int
iface br-int inet manual
ovs_type OVSBridge
ovs_ports tap111
allow-br-int tap111
iface ngwintp inet manual
ovs_bridge br-int
ovs_type OVSIntPort
3. start ovs
systemctl start openvswitch-switch
now we can see 2 ifup processes, and when use cmd " systemctl status
openvswitch-switch",
we can see error " ifup: waiting for lock on /run/network/ifstate.br-int"
4. I found that in ovs ifupdown.sh scripts, there is such bash cmd:
if /etc/init.d/openvswitch-switch status > /dev/null 2>&1; then :; else
/etc/init.d/openvswitch-switch start
fi
is it means if openvswitch is not running, then start it?
but when use systemd, "/etc/init.d/openvswitch-switch status" this command
always returns value not equal to 0,
hence openvswitch restarted, then ifup will be boot again , that's the reason
caused the LOCK
5. when use the following bash cmd:
if ovs_ctl status > /dev/null 2>&1; then :; else
/etc/init.d/openvswitch-switch start
fi
then we can start and stop openvswitch smoothly
but when we use "ifup --allow=ovs br-int", ifup LOCKED again
6. my question is:
why we need to brought up openvswitch process in ifupdown.sh?
is there a simple way to fix this problem?
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
