I now think that 'cobbler reposync' has bugs, at least in the github
version of the code.
Consider these messages which appear in /var/log/messages:
Jul 2 14:01:41 cobbler1 python: abrt: detected unhandled Python
exception in /usr/bin/yum
Jul 2 14:01:41 cobbler1 abrtd: New client connected
Jul 2 14:01:41 cobbler1 abrt-server[1851]: Can't create directory
'/var/spool/abrt/pyhook-2012-07-02-14:01:41-1823.new': No space left on
device
Jul 2 14:01:41 cobbler1 abrt-server[1851]: Error creating crash dump
/var/spool/abrt/pyhook-2012-07-02-14:01:41-1823.new
[not sure if the above are meaningful to this problem, however I started
my 'cobbler reposync' at about this time]
....
....
Jul 2 16:16:34 cobbler1 python: abrt: detected unhandled Python
exception in /usr/bin/cobblerd
I am creating the repo under CentOS 6.2 x86_64:
[root@cobbler1 ~]# uname -a
Linux cobbler1.greenbeltcomputer.biz 2.6.32-220.23.1.el6.x86_64 #1 SMP
Mon Jun 18 18:58:52 BST 2012 x86_64 x86_64 x86_64 GNU/Linux
[root@cobbler1 ~]# cat /etc/centos-release
CentOS release 6.2 (Final)
The cobbler version info:
[root@cobbler1 ~]# cobbler version
Cobbler 2.3.1
source: 9507694, Wed Jun 27 11:28:11 2012 -0700
build time: Thu Jun 28 21:32:47 2012
It appears that the downloading of packages from the first repo shown
below completes fine, then the process stops dead at the first
'createrepo' command. I always see the above 'unhandled Python exception
in /usr/bin/cobblerd' messages. Can anyone give me a clue as to why
these issues are happening?
Name : f17-x86_64-everything
Arch : x86_64
Breed : yum
Comment :
Createrepo Flags : <<inherit>>
Environment Variables : {}
Keep Updated : True
Mirror :
http://fedora.mirrors.tds.net/pub/fedora/releases/17/Everything/x86_64/os/
Mirror locally : True
Owners : ['admin']
Priority : 99
RPM List : []
Yum Options : {}
Name : f17-x86_64-updates
Arch : x86_64
Breed : yum
Comment :
Createrepo Flags : <<inherit>>
Environment Variables : {}
Keep Updated : True
Mirror :
http://mirror.umd.edu/fedora/linux/updates/17/x86_64/
Mirror locally : True
Owners : ['admin']
Priority : 99
RPM List : []
Yum Options : {}
Note: at first I thought that my original 2 Tb hard drive was going bad,
based on kernel messages I was getting, so I cloned this to a brand new
2 Tb drive. The problems I am experiencing with cobblerd persist.
How can I approach tracking down the problem? Does 'createrepo' need
network ports to be opened?
Thanks
Bob Cochran
_______________________________________________
cobbler mailing list
cobbler@lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/cobbler
