Replication Error
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-07-2013 05:47 PM
I gave up trying to get replication to work over SSL between two separate servers so I tried to do it on port 8080 and http: I now get this error message:
<blockquote>
Last job failed. Job started: Thu 7 Nov 2013 16:34:30 Ended: Thu 7 Nov 2013 16:34:35
10070603 Error executing transfer - 10070601 Transfer to the same repository not allowed
</blockquote>
How do I change the repository ID's so that they are unique to the server.
I am using Alfresco Community 4.2d ON centos 6.4 with a MySQL 5.1 backend (Percona Server)
We would like to run replication every 30 minutes or 1 hour so we can have a hot back up to fail-over too.
Update
I am getting jobs to run by they are still failing. This is the message I am now getting. Any ideas or help on how to resolve this would be greatly appreciated.
<blockquote>
10081072 Error executing transfer - 10081070 Failed to open stream onto channel:
accessor: ContentAccessor[ contentUrl=store://2013/11/7/11/44/1361f599-e580-4118-b419-d0da5a2e2ecc.bin, mimetype=application/octet-stream, size=0, encoding=UTF-8, locale=en_US]
</blockquote>
I am also going to look at using rsync and MySQL replication to back up the repository.
<blockquote>
Last job failed. Job started: Thu 7 Nov 2013 16:34:30 Ended: Thu 7 Nov 2013 16:34:35
10070603 Error executing transfer - 10070601 Transfer to the same repository not allowed
</blockquote>
How do I change the repository ID's so that they are unique to the server.
I am using Alfresco Community 4.2d ON centos 6.4 with a MySQL 5.1 backend (Percona Server)
We would like to run replication every 30 minutes or 1 hour so we can have a hot back up to fail-over too.
Update
I am getting jobs to run by they are still failing. This is the message I am now getting. Any ideas or help on how to resolve this would be greatly appreciated.
<blockquote>
10081072 Error executing transfer - 10081070 Failed to open stream onto channel:
accessor: ContentAccessor[ contentUrl=store://2013/11/7/11/44/1361f599-e580-4118-b419-d0da5a2e2ecc.bin, mimetype=application/octet-stream, size=0, encoding=UTF-8, locale=en_US]
</blockquote>
I am also going to look at using rsync and MySQL replication to back up the repository.
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-11-2013 12:52 AM
Looking at your log error it has issue with accessing the binary files of contents.
It could be access issue have you verified that permission for alf_data?
It could be access issue have you verified that permission for alf_data?
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-12-2013 03:26 PM
When we created the site that will be the "hot" backup we did a snapshot of the primary server. Because of this both repositories had identical id's. We resolved this by reinstalling alfresco on the "hot" backup and replication now occurs.
At first when we set up the replication job, we were replicating all the folders in the repository, this is when we were getting the replication failed error. We changed this to replicate individual folders in Sites and are now replicating without errors.
At first when we set up the replication job, we were replicating all the folders in the repository, this is when we were getting the replication failed error. We changed this to replicate individual folders in Sites and are now replicating without errors.
