/etc/rsyncd.conf
by David Lee
(Using cobbler 2.0.11, downloaded from epel, on RHEL 5.6)
I'm trying for the first time to use "cobbler replicate" on a potential
slave machine to fetch files from a cobbler master. It fails quickly
with various "rsync" errors.
Although the server end permits rsync to be spawned as an xinetd daemon,
the server has no "/etc/rsyncd.conf". I've found a file called
"/etc/cobbler/rsync.template", which looks promising, and when I simply
copy that into place as"/etc/rsyncd.conf" things looks much healthier.
Two things:
1. I suggest there is a bug: shouldn't there be something on the
master, either during installation or at each "cobbler sync", that
creates this file?
2. The template file on the master contains:
#for repo in $repos:
[repo-$repo]
path = $webdir/repo_mirror/$repo
comment = Cobbler Repo $repo
#end for
and a similar-looking "distro" clause. These look as though they need
unrolling (as part of the installation or "cobbler sync", as above) into
the final "/etc/rsyncd.conf". Is there a command I can run that will
take the template as input, unpack those loop-looking things, and
produce the final file as output?
--
: David Lee
: ECMWF (Data Handling System)
: Shinfield Park
: Reading RG2 9AX
: Berkshire
:
: tel: +44-118-9499 362
: email: david.lee(a)ecmwf.int
12 years, 7 months
cobbler replicate issues
by Ronald J. Yacketta
Trying to replicate from cobbler 2.0.3.1 to cobbler 2.0.11 and keep
running into the following:
cobbler replicate --master=_MASTER_SERVER_ --distros=* --profiles=*
--systems=* --sync-all
...
Updating Objects Newer On Remote
Linking Distro f14-i386
Exception occured: exceptions.NameError
Exception value: global name 'base' is not defined
Exception Info:
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 95,
in run
rc = self._run(self)
File "/usr/lib/python2.4/site-packages/cobbler/remote.py", line 210,
in runner
self.logger
File "/usr/lib/python2.4/site-packages/cobbler/api.py", line 782, in
replicate
sync_all = sync_all
File "/usr/lib/python2.4/site-packages/cobbler/action_replicate.py",
line 342, in run
self.link_distros()
File "/usr/lib/python2.4/site-packages/cobbler/action_replicate.py",
line 193, in link_distros
print _("- symlink creation failed: %(base)s, %(dest)s") % { "base"
: base, "dest" : dest_link }
!!! TASK FAILED !!!
distro report on the 2.0.3.1 shows
cobbler distro report --name=f14-i386
Name : f14-i386
Architecture : i386
Breed : redhat
Comment :
Initrd : /mnt/iso/f14/images/pxeboot/initrd.img
Kernel : /mnt/iso/f14/images/pxeboot/vmlinuz
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart Metadata : {}
Management Classes : []
OS Version : fedora14
Owners : ['admin']
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Template Files : {}
I had to modify codes.py to add fedora14 and fedora15 and restart cobbler
Thoughts?
-Ron
12 years, 7 months
Cobbler and FOG
by Janet.Conkle＠afscn.com
I've just about given up on getting Cobbler to install my windows boxes.
Has anyone had any experience with Cobbler and FOG coexisting on the
same Linux server?
Are there any special configuration considerations I need to take into
account for DHCP?
Janet Conkle
ETG
x5343
12 years, 7 months
cobblerd
by Christy, Jason E
Hi,
After reading through the documentation, I see that cobbler will keep repos updated, when applicable. On my system, I can see cobblerd running reposync. My question is when does cobbler run reposync? Is it configurable? Thank You!
Take Care!
-Jason
12 years, 7 months
