Hey there again, thanks again for helping with my earlier questions, I got a sync running now and working on the second one. I discovered a problem I can't find a logical explanation for. I observe Bucardo trying to sync a table to a database that should not be a target for that herd nor in that sync:
(1820) [Tue Jun 25 17:15:28 2013] MCP Inspecting source table "public.access_ticket" on database "v_davical" (1820) [Tue Jun 25 17:15:28 2013] MCP Inspecting target table "public.access_ticket" on database "m_davical" (1820) [Tue Jun 25 17:15:28 2013] MCP Inspecting target table "public.access_ticket" on database "v_baculadir" (1820) [Tue Jun 25 17:15:28 2013] MCP Warning: Killed (line 5896): DBD::Pg::st execute failed: ERROR: relation "public.access_ticket" does not exist at /usr/share/perl5/Bucardo.pm line 5896. The probe to the second database v_baculadir should not be happening: I have two servers, one running burcardo both running a psql server each containing several databases. (Maguro is the one running bucardo) Maguro <---> Voodoo ====================== baculadir--->baculadir davical <---davical I have each of them connected to bucardo as v_dbname and m_dbname: Database: m_baculadir Status: active Conn: psql -p 5432 -U bucardo -d baculadir -h localhost Database: m_davical Status: active Conn: psql -p 5432 -U bucardo -d davical -h localhost Database: v_baculadir Status: active Conn: psql -p 5432 -U maguro -d baculadir -h voodoo Database: v_davical Status: active Conn: psql -p 5432 -U maguro -d davical -h voodoo There are two database groups specifying the source and target databases: Database group: maguro Members: m_baculadir:source v_baculadir:target Database group: voodoo Members: m_davical:target v_davical:source For each dbgroup there is a sync-job Sync: maguro_voodoo Herd: maguro [Active] DB group maguro: m_baculadir (source) v_baculadir (target) Sync: voodoo_maguro Herd: voodoo [Active] DB group voodoo: m_davical (target) v_davical (source) The herds specifying the tables that should be synced are the following: Herd: maguro DB: m_baculadir Members: public.basefiles, public.basefiles_baseid_seq, [...] Used in syncs: maguro_voodoo Herd: voodoo DB: v_davical Members: public.access_ticket, public.addressbook_address_adr, [...] Used in syncs: voodoo_maguro So I think bucardo got all the information it should need, I wouldn't expect it needs the tables of the target-db in its herd too would it? Thanks in advance, Olaf Rühenbeck
signature.asc
Description: PGP signature
_______________________________________________ Bucardo-general mailing list Bucardo-general@bucardo.org https://mail.endcrypt.com/mailman/listinfo/bucardo-general