Stuart,

Well, I think yum needs to keep a list of repos to search and information about the content of these repos in /var/cach/yum. I see all my own repo directories in my corresponding /var/cache/yum. Here is an example of the content of mine:
[root@cobbler1 ~]# ls -al /var/cache/yum/EPEL
total 21664
drwxr-xr-x. 3 root root     4096 Jul  3 10:06 .
drwxr-xr-x. 6 root root     4096 Jun 22 15:57 ..
-rw-r--r--. 1 root root 234887 Jun 30 20:23 00363f350c073727b05d727a7c2556dab7c1d09450b628ab3f75070d897d0e60-comps-el6.xml.gz -rw-r--r--. 1 root root 20734976 Jul 3 09:55 340d89d8a3a02fb9da8502fd5e96afb58243633d2365a02e2ae95cbc2ac6fba0-primary.sqlite
-rw-r--r--. 1 root root        0 Jul  3 09:55 cachecookie
-rw-r--r--. 1 root root 1187212 Jun 30 20:23 fe8d76e72c668fc7e4994c9a57ec7fd76a10b8b8d63bf63787e95635ed004615-comps-el6.xml
drwxr-xr-x. 2 root root     4096 Jul  3 09:55 gen
-rw-r--r--. 1 root root     4118 Jun 30 20:46 repomd.xml

I think you must have created a cobbler repo with the command

'cobbler repo create --name=epelrepo --path=[...]'

...if cobbler is trying to reposync it.

You can check this with

'cobbler repo list' or 'cobbler repo report'

If you do all your work in the bash shell, which is what I do, you can also check the command you issued (as root) by searching the history file:

egrep 'name=epelrepo' ~/.bash_history

 I hope this helps.

Bob Cochran


On 7/13/12 7:18 AM, Newman, Stuart J. (GSFC-444.0)[HONEYWELL TECHNOLOGY SOLUTIONS INC] wrote:

I am running RHEL 6.3 with Cobbler 2.2.3. Trying to run cobbler reposync, I get the following:

Fri Jul 13 07:12:46 2012 - INFO | hello, reposync

Fri Jul 13 07:12:46 2012 - INFO | run, reposync, run!

Fri Jul 13 07:12:46 2012 - DEBUG | creating: /var/www/cobbler/repo_mirror/epelrepo/.origin/epelrepo.repo

Fri Jul 13 07:12:46 2012 - INFO | running: /usr/bin/reposync -l -m -d --config=/var/www/cobbler/repo_mirror/epelrepo/.origin/epelrepo.repo --repoid=epelrepo --download_path=/var/www/cobbler/repo_mirror -a x86_64

Fri Jul 13 07:12:46 2012 - INFO | received on stdout:

Fri Jul 13 07:12:46 2012 - DEBUG | received on stderr: Error setting up repositories: Error making cache directory: /var/cache/yum/epelrepo error was: [Errno 13] Permission denied: '/var/cache/yum/epelrepo'

Fri Jul 13 07:12:46 2012 - INFO | Exception occured: <class 'cobbler.cexceptions.CX'>

Fri Jul 13 07:12:46 2012 - INFO | Exception value: 'cobbler reposync failed'

Fri Jul 13 07:12:46 2012 - INFO | Exception Info:

File "/usr/lib/python2.6/site-packages/cobbler/utils.py", line 126, in die

    raise CX(msg)

Fri Jul 13 07:12:46 2012 - INFO | Exception occured: <class 'cobbler.cexceptions.CX'>

Fri Jul 13 07:12:46 2012 - INFO | Exception value: 'cobbler reposync failed'

Fri Jul 13 07:12:46 2012 - INFO | Exception Info:

File "/usr/lib/python2.6/site-packages/cobbler/action_reposync.py", line 125, in run

    self.sync(repo)

File "/usr/lib/python2.6/site-packages/cobbler/action_reposync.py", line 169, in sync

    return self.yum_sync(repo)

File "/usr/lib/python2.6/site-packages/cobbler/action_reposync.py", line 402, in yum_sync

    utils.die(self.logger,"cobbler reposync failed")

File "/usr/lib/python2.6/site-packages/cobbler/utils.py", line 134, in die

    raise CX(msg)

Fri Jul 13 07:12:46 2012 - WARNING | reposync failed, tries left: 0

Fri Jul 13 07:12:46 2012 - INFO | Exception occured: <class 'cobbler.cexceptions.CX'>

Fri Jul 13 07:12:46 2012 - INFO | Exception value: 'reposync failed, retry limit reached, aborting'

Fri Jul 13 07:12:46 2012 - INFO | Exception Info:

File "/usr/lib/python2.6/site-packages/cobbler/utils.py", line 126, in die

    raise CX(msg)

Fri Jul 13 07:12:46 2012 - INFO | Exception occured: <class 'cobbler.cexceptions.CX'>

Fri Jul 13 07:12:46 2012 - INFO | Exception value: 'reposync failed, retry limit reached, aborting'

Fri Jul 13 07:12:46 2012 - INFO | Exception Info:

File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 89, in run

    rc = self._run(self)

File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 251, in runner

    name=None, nofail=nofail, logger=self.logger)

File "/usr/lib/python2.6/site-packages/cobbler/api.py", line 758, in reposync

    return reposync.run(name)

File "/usr/lib/python2.6/site-packages/cobbler/action_reposync.py", line 147, in run

utils.die(self.logger,"reposync failed, retry limit reached, aborting")

File "/usr/lib/python2.6/site-packages/cobbler/utils.py", line 134, in die

    raise CX(msg)

Fri Jul 13 07:12:46 2012 - ERROR | ### TASK FAILED ###

The immediate error is due to SELinux blocking /var/cache/yum/epelrepo, but I do not understand why this directory is being created.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

*Stuart J. Newman
*Engineer 4; Systems

Solar Dynamics Observatory (SDO)

Honeywell Technology Solutions Inc**

        

NASA/Goddard Space Flight Center

Building 14, Room E222

Mail Stop 428.2

Greenbelt, MD 20771

Office: (301) 286-5145

EMail: [email protected] <mailto:[email protected]>

**

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ NOTICE: This communication, including any attachment, contains information that may be confidential or privileged, and is intended solely for the entity or individual to whom it is addressed. If you are not the intended recipient, please notify the sender at once, and you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message is strictly prohibited. Nothing in this email, including any attachment, is intended to be a legally binding signature.



_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
_______________________________________________
cobbler mailing list
[email protected]
https://fedorahosted.org/mailman/listinfo/cobbler
  • [cobble... Newman, Stuart J. (GSFC-444.0)[HONEYWELL TECHNOLOGY SOLUTIONS INC]
    • Re... Bob Cochran
      • ... Newman, Stuart J. (GSFC-444.0)[HONEYWELL TECHNOLOGY SOLUTIONS INC]

Reply via email to