Community mailing list archives
RE: Bacurdo Replicationby
We’re getting these kind of errors no matter what we do on one of the servers. Not just for that key.
duplicate key value violates unique constraint "ir_property_pkey"
DETAIL: Key (id)=(152498) already exists.
It only happens on one, and if we shutdown the other server, we still get them.
I’m at a real loss here.
From: Carlos Paz [mailto:email@example.com]
Sent: Wednesday, February 24, 2016 10:23 PM
To: Community <firstname.lastname@example.org>
Subject: Re: Bacurdo Replication
Welcome to the 'The Replication Twilight Zone' , this issues are common, daily, nightware.
In your case, the partner was created in one replica, but when syncing, there is another registry with the same id on the other side, computer CANT solve this as this is human criteria, you either delete the conflictive one, or assign other ID, etc.
On Wed, Feb 24, 2016 at 10:22 AM, The Geek Meister <email@example.com> wrote:
I had followed these directions to create a replicated OpenERP environment. What I’m finding is that if I create an entry in the server with Bacurdo installed, it creates it in our other server. However, when I try to create another item in the server without bacurdo, it gives an error similar to the following:
duplicate key value violates unique constraint "res_partner_pkey"
DETAIL: Key (id)=(104405) already exists.
This particular error was found when creating a contact, however it seems to be happening with any item created. Any ideas on how to fix this?
This is a test environment with two local servers, no firewalls. 192.168.1.231 and 192.168.1.232 both running the same code, same PostgreSQL version, and same Ubuntu 14.04 LTS.