On Wed, Oct 03, 2018 at 04:40:12PM +0300, Andrey Trushin wrote: > ovs-vsctl (Open vSwitch) 2.10.0 > DB Schema 7.16.1 > FreeBSD free-test 11.2-RELEASE FreeBSD 11.2-RELEASE #0 r335510: Fri Jun 22 > 04:32:14 UTC 2018 > [email protected]:/usr/obj/usr/src/sys/GENERIC > amd64 > > I am having some problems using openvswitch on freeBSD 11.2 > When I restart ovsdb-server again, settings are not saving. > error in log: > Code: > > 2018-09-28T13:33:24Z|00003|ovsdb_server|INFO|referential integrity > violation: Table Port column interfaces row > 00a824c6-0000-0008-ffff-e53000007fff references nonexistent row > 93337f30-ce0c-40f4-81e4-f6c4c72d8548 in table Interface. > 2018-09-28T13:33:24Z|00004|ovsdb_server|INFO|constraint violation: > transaction causes "Open_vSwitch" table to contain 2 rows, greater > than the schema-defined limit of 1 row(s) > 2018-09-28T13:33:24Z|00005|ovsdb_server|INFO|constraint violation: > transaction causes "Open_vSwitch" table to contain 2 rows, greater > than the schema-defined limit of 1 row(s)
Wow, this is really strange. For one thing, these UUIDs are essentially impossible. OVSDB generates random UUIDs and there's no way that you'd get 0000, ffff, and 000007fff in a random UUID. When ovsdb-server encounters this kind of issue at startup, it deletes the invalid transactions and rolls back the database to before that point. That means that the conf.db that you sent doesn't have the invalid transactions in it. Instead of restarting ovsdb-server, would you mind just stopping it (in the same context you were previously restarting it), then passing along the conf.db *before* restart? _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
