Greetings Pawel:
I am having the same problem. However, I discovered that one of the
engineers working in our sandbox/testing environment changed the rDNS (ip
address to hostname lookup) of our non-SCM server prior to my non-SCM
installation testing -- the old hostname works, and the hostname set on the
server and all configuration is still the same, but the rDNS doesn't match.
This may be the issue for us as coda may be pulling in and trying to use
this information "some how". Anyway, we're going to simply flatten and
install from scratch on this new domain (technically arbitrary; selected as
a business decision) and see if that resolves our problem (I love that pun).
Regarding the documentation, it is understood to be not ready for novice
instruction, but it's all we got. Most everything can be updated via here
or via the wiki itself, and any contributions are appreciated.
Regards,
-Don
{void}
pawel eljasz writes:
dear all, have just subscribed, apologies for lame nature of the question.
following the manual (which is by the way quite chaotic from any novice
perspective) I try set up
second server in the cell for replication purposes, right?
first setup on SCM box goes seemingly ok, the second server's vice-setup
results in:
...
....
Enter the update token that matches SCM $_yourserver: $mytoken
Fetching needed files from SCM $_yourserver
09:36:19 Fetch failed with Permission denied
Done.
Now installing things specific to non-SCM machines...
...
..
and it proceeds further, till the end with no more errors nor warnings.
but is this normal?
cheers
