(Using cobbler 2.0.11 on RHEL 5.x)
We have a master cobbler server, and two slaves which run a daily cron: cobbler replicate --master=cobbler_master.our.org \ --profiles="*" --systems="*"
In the master we set up a local repo of local RPMs, primarily designed for "yum" to access, but also referenced by cobbler. This was set up: cobbler repo add --name=el5-x86_64-local \ --mirror=http://... --mirror-locally=N --arch=x86_64
But the daily "cobbler replicate" gives an error message:
received on stderr: Rsyncing repos running: rsync -avzH cobbler_master.our.org::repo-el5-x86_64-local /var/www/cobbler/repo_mirror/el5-x86_64-local received on stdout: received on stderr: @ERROR: Unknown module 'repo-el5-x86_64-local' rsync error: error starting client-server protocol (code 5) at main.c(1296) [receiver=2.6.8]
That "unknown module" error message is worrying.
Is this because of the "N" for "mirror-locally"?
Things seem to work OK, and last time we forced an installation from a slave server, it seemed to see this repo.
But I'd like to know whether that error message is genuine and reflects a genuine fault. (Or is it a false alarm on 2.0.11?) Have I missed a step? Is there some "best/recommended practice"?
If it is related to "N" for "mirror-locally", would "Y" fix it? But would that then take an unnecessary (and big!) second copy within each server?
(I tried the "Start Here" on the wiki, but that doesn't really explore the details of this.)
cobbler@lists.fedorahosted.org