On Thu, Oct 05, 2017 at 11:37:09PM +0000, Omar Ramadan wrote: > vswitchd is blocking when I try starting the service on system boot. Can > someone help me make sense of this message: > > > vagrant@magma-dev:~$ sudo tail -f /var/log/openvswitch/ovs-vswitchd.log > 2017-10-05T23:32:07.501Z|00019|ofproto_dpif|INFO|system@ovs-system: Datapath > supports ct_orig_tuple > 2017-10-05T23:32:07.516Z|00001|ofproto_dpif_upcall(handler1)|INFO|received > packet on unassociated datapath port 0 > 2017-10-05T23:32:07.523Z|00020|bridge|INFO|bridge managed_br0: added > interface managed_br0 on port 65534 > 2017-10-05T23:32:08.528Z|00001|ovs_rcu(urcu5)|WARN|blocked 1007 ms waiting > for main to quiesce > 2017-10-05T23:32:09.523Z|00002|ovs_rcu(urcu5)|WARN|blocked 2002 ms waiting > for main to quiesce > ...
Usually this kind of message means that the thread in question (the main thread in this case) is not cycling through the main loop in a reasonable time but blocked somewhere. If you can get a backtrace of the main thread (live or from a core dump), it will probably point to the place it's blocking. _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
