[EMAIL PROTECTED] wrote:
On Tue, Dec 12, 2006 at 11:39:13AM -0500, Sean Caron wrote:
# volutil -h clusty2.mytest.de create_rep /vicepa /.1 7f000000
V_BindToServer: binding to host clusty2.mytest.de
RPC2_NewBinding to server clusty2.mytest.de failed with RPC2_NOBINDING (F)
You probably don't want to use the volutil program to create
replicated volumes (it is probably not the proper method anyway).
There is a tool called createvol_rep that will do the job very nicely.
Sean,
you are right of course, but the original problem seemed to be that
volutil could not contact the corresponding server
(which suggests that either the volutil process or the server on clusty2
did not have access to the appropriate token, volutil.tk ?)
As createvol_rep runs volutil, it would fail as well.
Regards,
Rune
Hi,
The createvol_rep did not work either:
# createvol_rep coda.rep clusty1.mytest.de/vicepa clusty2.mytest.de/vicepa
egrep: /tmp/vollist.5037: No such file or directory
egrep: /tmp/vollist.5037: No such file or directory
grep: /tmp/vollist.5037: No such file or directory
Found no partitions for server clusty2.mytest.de.
# cat /vice/db/volutil.tk
test2006
On the slave clusty2:
# cat /vice/db/volutil.tk
test2006
So still no replication :o(
Thanks...
Achim
