Hello,
thanks for answer, here are results from \d on source/target:
rcubex1 sync:
roundcubemail=> \d
List of relations
Schema | Name | Type | Owner
--------+---------------------+----------+-----------
public | cache | table | roundcube
public | cache_index | table | roundcube
public | cache_messages | table | roundcube
public | cache_thread | table | roundcube
public | contact_ids | sequence | roundcube
public | contactgroupmembers | table | roundcube
public | contactgroups | table | roundcube
public | contactgroups_ids | sequence | roundcube
public | contacts | table | roundcube
public | dictionary | table | roundcube
public | identities | table | roundcube
public | identity_ids | sequence | roundcube
public | search_ids | sequence | roundcube
public | searches | table | roundcube
public | session | table | roundcube
public | system | table | roundcube
public | user_ids | sequence | roundcube
public | users | table | roundcube
(18 rows)
both are identical on source/target and here is for mxsync:
List of relations
Schema | Name | Type | Owner
--------+---------+-------+------------
public | aliases | table | mailreader
public | users | table | mailreader
same here, both target/source are the same.
Thing is that this error is correct as on mx2 there is no table public.cache -
it is on “rcubex2” but bucardo try that table on wrong db… please see the logs,
it do not have sense for me…
about starting bucardo, i use stock init scripts, also i simply do "bucardo
start”
thanks!
__
Zbyszek Żółkiewski
On 24 Feb 2014, at 13:05, Mitchell Perilstein
<[email protected]> wrote:
> Well, that message is coming from Postgres on your target. You can get it
> from your psql shell like this:
>
> mydb=> select * from foo;
> ERROR: relation "foo" does not exist
>
> Can you go into your target db, go into psql, and do a "\d" to let us see the
> tables there? Maybe better a \d on the source as well. Also, posting your
> init script you start bucardo with would be helpful.
>
> Thanks.
>
>
> On 02/24/14 05:32, Zbyszek Żółkiewski wrote:
>> Hello,
>>
>> so no one have any idea what is going on?
>>
>> __
>> Zbyszek Żółkiewski
>>
>> On 20 Feb 2014, at 21:27, Zbyszek Żółkiewski <[email protected]> wrote:
>>
>>> Hello
>>>
>>> I am using bucardo to synchronise one database - and it works great.
>>> However today i wanted to add additional database for replication and it
>>> seems there is some bug, or me doing something wrong, please see my config:
>>>
>>> bucardo list all
>>>
>>> -- customcodes:
>>> There are no entries in the 'customcode' table.
>>> -- customnames:
>>> No customnames have been added yet
>>> -- customcols:
>>> No customcols have been added yet
>>> -- dbgroups:
>>> Database group: mxsync Members: mx1:source mx2:target
>>> Database group: rcubesync Members: rcubex1:source rcubex2:target
>>> -- databases:
>>> Database: mx1 Status: active Conn: psql -p -U mailreader -d mail
>>> Database: mx2 Status: active Conn: psql -p -U mailreader -d mail -h
>>> mx-2.somehost.com
>>> Database: rcubex1 Status: active Conn: psql -p -U roundcube -d
>>> roundcubemail
>>> Database: rcubex2 Status: active Conn: psql -p -U roundcube -d
>>> roundcubemail -h mx-2.somehost.com
>>> -- herds:
>>> Herd: mxherd DB: mx1 Members: public.aliases, public.users
>>> Used in syncs: mxsync
>>> Herd: rcubeherd DB: rcubex1 Members: public.cache_index,
>>> public.cache_messages, public.cache_thread, public.contact_ids,
>>> public.contactgroupmembers, public.contactgroups, public.contactgroups_ids,
>>> public.contacts, public.dictionary, public.identities, public.identity_ids,
>>> public.search_ids, public.searches, public.session, public.system,
>>> public.user_ids, public.users
>>> Used in syncs: rcubesync
>>> -- syncs:
>>> Sync: mxsync Herd: mxherd [Active]
>>> DB group mxsync: mx1 (source) mx2 (target)
>>> Sync: rcubesync Herd: rcubeherd [Active]
>>> DB group rcubesync: rcubex1 (source) rcubex2 (target)
>>> -- tables:
>>> 44. Table: public.aliases DB: mx1 PK: alias|email
>>> (text|text) Syncs: mxsync
>>> 46. Table: public.cache_index DB: rcubex1 PK: user_id|mailbox
>>> (int4|varchar) Syncs: rcubesync
>>> 48. Table: public.cache_messages DB: rcubex1 PK: user_id|mailbox|uid
>>> (int4|varchar|int4) Syncs: rcubesync
>>> 49. Table: public.cache_thread DB: rcubex1 PK: user_id|mailbox
>>> (int4|varchar) Syncs: rcubesync
>>> 50. Table: public.contactgroupmembers DB: rcubex1 PK:
>>> contactgroup_id|contact_id (int4|int4) Syncs: rcubesync
>>> 51. Table: public.contactgroups DB: rcubex1 PK: contactgroup_id
>>> (int4) Syncs: rcubesync
>>> 52. Table: public.contacts DB: rcubex1 PK: contact_id (int4)
>>> Syncs: rcubesync
>>> 53. Table: public.dictionary DB: rcubex1 PK: user_id|language
>>> (int4|varchar) Syncs: rcubesync
>>> 54. Table: public.identities DB: rcubex1 PK: identity_id (int4)
>>> Syncs: rcubesync
>>> 55. Table: public.searches DB: rcubex1 PK: search_id (int4)
>>> Syncs: rcubesync
>>> 56. Table: public.session DB: rcubex1 PK: sess_id (varchar)
>>> Syncs: rcubesync
>>> 57. Table: public.system DB: rcubex1 PK: name (varchar)
>>> Syncs: rcubesync
>>> 58. Table: public.users DB: rcubex1 PK: user_id (int4)
>>> 45. Table: public.users DB: mx1 PK: email (text)
>>> Syncs: mxsync,rcubesync
>>> -- sequences:
>>> Sequence: public.contactgroups_ids DB: rcubex1
>>> Sequence: public.contact_ids DB: rcubex1
>>> Sequence: public.identity_ids DB: rcubex1
>>> Sequence: public.search_ids DB: rcubex1
>>> Sequence: public.user_ids DB: rcubex1
>>>
>>> from this config all seems fine (to me) and correct, until i have added
>>> “rcubesync” all was working fine, but now when bucardo start i got
>>> following error:
>>>
>>> (25464) [Thu Feb 20 21:13:22 2014] MCP Activating sync "mxsync"
>>> (25464) [Thu Feb 20 21:13:22 2014] MCP Running validate_sync on "mxsync"
>>> (25464) [Thu Feb 20 21:13:22 2014] MCP Connecting to database "mx1" (source)
>>> (25464) [Thu Feb 20 21:13:22 2014] MCP DB "mx1" Local epoch:
>>> 1392927202.36905 DB epoch: 1392927202.36907
>>> (25464) [Thu Feb 20 21:13:22 2014] MCP DB "mx1" Local time: Thu Feb 20
>>> 21:13:22 2014 DB time: 2014-02-20 21:13:22.369068+01
>>> (25464) [Thu Feb 20 21:13:22 2014] MCP DB "mx1" Local timezone: CET (+0100)
>>> DB timezone: localtime
>>> (25464) [Thu Feb 20 21:13:22 2014] MCP DB "mx1" Postgres version: 90111
>>> (25464) [Thu Feb 20 21:13:22 2014] MCP DB "mx1" Database port: 5432
>>> (25464) [Thu Feb 20 21:13:22 2014] MCP Connecting to database "mx2" (target)
>>> (25464) [Thu Feb 20 21:13:23 2014] MCP DB "mx2" Local epoch:
>>> 1392927203.41941 DB epoch: 1392927203.45948
>>> (25464) [Thu Feb 20 21:13:23 2014] MCP DB "mx2" Local time: Thu Feb 20
>>> 21:13:23 2014 DB time: 2014-02-20 21:13:23.459475+01
>>> (25464) [Thu Feb 20 21:13:23 2014] MCP DB "mx2" Local timezone: CET (+0100)
>>> DB timezone: localtime
>>> (25464) [Thu Feb 20 21:13:23 2014] MCP DB "mx2" Postgres version: 90111
>>> (25464) [Thu Feb 20 21:13:23 2014] MCP DB "mx2" Database port: 5432
>>> (25464) [Thu Feb 20 21:13:25 2014] MCP Inspecting source table
>>> "public.aliases" on database "mx1"
>>> (25464) [Thu Feb 20 21:13:25 2014] MCP Inspecting target table
>>> "public.aliases" on database "mx2"
>>> (25464) [Thu Feb 20 21:13:25 2014] MCP Inspecting source table
>>> "public.users" on database "mx1"
>>> (25464) [Thu Feb 20 21:13:26 2014] MCP Inspecting target table
>>> "public.users" on database "mx2"
>>> (25464) [Thu Feb 20 21:13:26 2014] MCP Activating sync "rcubesync"
>>> (25464) [Thu Feb 20 21:13:26 2014] MCP Running validate_sync on "rcubesync"
>>> (25464) [Thu Feb 20 21:13:26 2014] MCP Connecting to database "rcubex1"
>>> (source)
>>> (25464) [Thu Feb 20 21:13:26 2014] MCP DB "rcubex1" Local epoch:
>>> 1392927206.43815 DB epoch: 1392927206.43817
>>> (25464) [Thu Feb 20 21:13:26 2014] MCP DB "rcubex1" Local time: Thu Feb 20
>>> 21:13:26 2014 DB time: 2014-02-20 21:13:26.438167+01
>>> (25464) [Thu Feb 20 21:13:26 2014] MCP DB "rcubex1" Local timezone: CET
>>> (+0100) DB timezone: localtime
>>> (25464) [Thu Feb 20 21:13:26 2014] MCP DB "rcubex1" Postgres version: 90111
>>> (25464) [Thu Feb 20 21:13:26 2014] MCP DB "rcubex1" Database port: 5432
>>> (25464) [Thu Feb 20 21:13:26 2014] MCP Connecting to database "rcubex2"
>>> (target)
>>> (25464) [Thu Feb 20 21:13:28 2014] MCP DB "rcubex2" Local epoch:
>>> 1392927207.81976 DB epoch: 1392927207.86042
>>> (25464) [Thu Feb 20 21:13:28 2014] MCP DB "rcubex2" Local time: Thu Feb 20
>>> 21:13:27 2014 DB time: 2014-02-20 21:13:27.860423+01
>>> (25464) [Thu Feb 20 21:13:28 2014] MCP DB "rcubex2" Local timezone: CET
>>> (+0100) DB timezone: localtime
>>> (25464) [Thu Feb 20 21:13:28 2014] MCP DB "rcubex2" Postgres version: 90111
>>> (25464) [Thu Feb 20 21:13:28 2014] MCP DB "rcubex2" Database port: 5432
>>> (25464) [Thu Feb 20 21:13:32 2014] MCP Inspecting source table
>>> "public.cache_index" on database "rcubex1"
>>> (25464) [Thu Feb 20 21:13:32 2014] MCP Inspecting target table
>>> "public.cache_index" on database "mx2"
>>> (25464) [Thu Feb 20 21:13:33 2014] MCP Warning: Killed (line 5896):
>>> DBD::Pg::st execute failed: ERROR: relation "public.cache_index" does not
>>> exist at /usr/share/perl5/Bucardo.pm line 5896.
>>> (25464) [Thu Feb 20 21:13:34 2014] MCP End of cleanup_mcp. Sys time: Thu
>>> Feb 20 21:13:34 2014. Database time: 2014-02-20 21:13:34.602085+01
>>>
>>> at the and you can see that somehow bucardo tries to check table
>>> “public.cache_index” on database mx2 - which is not in correct herd! This
>>> seems like bug.
>>>
>>> Any help is greatly appreciated!
>>>
>>> Thanks!
>>>
>>> __
>>> Zbyszek Żółkiewski
>>>
>>> _______________________________________________
>>> Bucardo-general mailing list
>>> [email protected]
>>> https://mail.endcrypt.com/mailman/listinfo/bucardo-general
>> _______________________________________________
>> Bucardo-general mailing list
>> [email protected]
>> https://mail.endcrypt.com/mailman/listinfo/bucardo-general
>
>
> Confidentiality Notice: This e-mail (including any attachments) is intended
> only for the recipients named above. It may contain confidential or
> privileged information and should not be read, copied or otherwise used by
> any other person. If you are not a named recipient, please notify the sender
> of that fact and delete the e-mail from your system.
>
>
_______________________________________________
Bucardo-general mailing list
[email protected]
https://mail.endcrypt.com/mailman/listinfo/bucardo-general
