Need help ... Urgently ...
by Yogesh Mulay
I have the Cobbler setup ready & esxi5 installed. Is there a way to parse
esxi commands in the host. Like enabling ssh running esxcli. Adding VMKs.
Changing the managament IP address & its Vlan
I need some tips regarding pre & post installation basically
Any help would be highly appreciated. ...
Regards
10 years
<ProtocolError for localhost:25151/cobbler_api: 404 Not Found>
by John Paget Bourke
Hi,
When I run
koan --list=profiles -s localhost
I get the following error
root@Config cobbler]# koan --list=profiles -s localhost
- looking for Cobbler at http://localhost:25151/cobbler_api
Traceback (most recent call last):
File "/usr/lib/python2.6/site-packages/koan/utils.py", line 542, in
__try_connect
xmlrpc_server.ping()
File "/usr/lib64/python2.6/xmlrpclib.py", line 1199, in __call__
return self.__send(self.__name, args)
File "/usr/lib64/python2.6/xmlrpclib.py", line 1489, in __request
verbose=self.__verbose
File "/usr/lib64/python2.6/xmlrpclib.py", line 1243, in request
headers
ProtocolError: <ProtocolError for localhost:25151/cobbler_api: 404 Not
Found>
If I try to see if the server is running and listening, the server is ok
[root@Config cobbler]# netstat -an | grep 25151
tcp 0 0 127.0.0.1:25151 0.0.0.0:*
LISTEN
tcp 0 0 127.0.0.1:25151 127.0.0.1:57483
TIME_WAIT
But returns nothing .
[root@Config cobbler]# curl http://localhost:25151/cobbler_api
curl: (52) Empty reply from server
I am using the web GUI and it works ok, no problems.
When I try to use koan or curl and check the logs
[root@Config cobbler]# curl http://localhost:25151/cobbler_api
curl: (52) Empty reply from server
[root@Config cobbler]# date
Sun Oct 30 05:30:55 UTC 2011
[root@Config cobbler]# ls -l
total 1792
drwxr-xr-x. 2 root root 4096 Oct 6 02:24 anamon
-rw-r--r--. 1 root root 1806499 Oct 30 04:50 cobbler.log
-rw-r--r-- 1 root root 73 Oct 29 00:24 install.log
drwxr-xr-x. 2 root root 4096 Oct 6 02:24 kicklog
drwxr-xr-x. 2 root root 4096 Oct 6 02:24 syslog
drwxr-xr-x. 2 root root 4096 Oct 30 04:40 tasks
[root@Config cobbler]# cd /etc/httpd/logs/
[root@Config logs]# ls -l
total 3172
-rw-r--r-- 1 root root 10904 Oct 30 04:45 access_log
-rw-r--r--. 1 root root 789779 Oct 30 02:43 access_log-20111030
-rw-r--r-- 1 root root 32638 Oct 30 05:20 error_log
-rw-r--r--. 1 root root 2403267 Oct 30 03:06 error_log-20111030
The logs do not seem to be affected.
The versions I am running are
[root@Config cobbler]# rpm -qa | grep cobbler
cobbler-2.2.1-1.el6.noarch
cobbler-web-2.2.1-1.el6.noarch
[root@Config cobbler]# rpm -qa | grep koan
koan-2.2.1-1.el6.noarch
In the modules.conf I have
[authentication]
#module = authn_denyall
module = authn_configfile
[authorization]
module = authz_allowall
So I am a bit lost. Any thoughts ?
Thanks
John
10 years, 2 months
Debian 7.1 import error
by replic4nt0wnz .
Sorry for not responding to the original message posted yesterday but
my original email addy doesn't seem to be working w/the list.
Anyway, I'm getting the same import error when trying to import Debian:
cobbler import --name=wheezy --breed=debian --arch=amd64
--path="rsync://ftp.us.debian.org/debian/dists/wheezy/main/installer-amd64/curren..."
task started: 2013-10-04_164924_import
task started (id=Media import, time=Fri Oct 4 16:49:24 2013)
No signature matched in /var/www/cobbler/ks_mirror/wheezy-amd64
!!! TASK FAILED !!!
I've tried changing the arch from x86_64 to amd64 and back but no
luck. I also grabbed the latest distro_signatures.json with no luck as
well. I did notice in the signatures that the kernel file was set to
"vmlinuz" instead of "linux" like the rest of the Ubuntu sigs and that
the kernel is named "linux" on the Debian ftp site. I changed it back
and forth (restarting Cobbler) with no luck either.
--
I've seen things you people wouldn't believe. Attack ships on fire off
the shoulder of Orion. I watched C-beams glitter in the dark near the
Tannhauser gate. All those moments will be lost in time... like tears
in rain... Time to die.
10 years, 4 months
vmware ESXI support
by Oliver Heinz
Hi all,
I could not find much information about the current state of support for
provisioning VMs in vmware ESXi/vcenter environments. Documentation ist
just talking about vmware server (which is EOL since 2011) and
workstation. Is cobbler/koan supporting ESXi either directly or by
integrating with vMA or other third party software?
TIA,
Oliver
10 years, 5 months
Should I create a Repo to mirror my Distro?
by T Dickinson
I would like my RHEL/CentOS installed servers (provisioned via cobbler) to refer back to the cobbler server for all yum updates/installs.
I understand that is easy for mirrored repos, but how do I configure cobbler so that the distro is used (after the kickstart is over) ?
Im using 2.4 should my installed server's yum repos point at the cobbler server for the base repos? I'm using CentOS-5.9 and /etc/yum.repos.d/CentOS-Base.repo does not point to my server hence any post install yum calls go to internet. Should I create a Repo for the Distro I've installed… this post hints at my dilema http://www.redhat.com/archives/et-mgmt-tools/2007-September/msg00128.html
10 years, 6 months
why My client can't saw the xen on cobbler's menu?
by zhxd
Hi,all!
I installed cobbler on my vmware,to test.
The cobbler server(centos 6.2 i386) was configure complate,the client(centos 5.8 i386) can visit the cobbler's menu,use pxe,and can installed the centos 5.8,also.
But I found a question,the menu only display "(loca)" and "CentOS-5.8-i386",can't display "CentOS-5.8-xen-i386":
(local)
CentOS-5.8-i386
I saw there have anybody installed cobbler,there can display cobbler's menu like this:
(local)
CentOS-5.8-i386
CentOS-5.8-xen-i386
There haven't "CentOS-5.8-xen-i386" option
I executed these command in shell,and find any result:
# cobbler sync
task started: 2013-10-28_223747_sync
task started (id=Sync, time=Mon Oct 28 22:37:47 2013)
running pre-sync triggers
cleaning trees
removing: /var/www/cobbler/images/CentOS-5-xen-i386
removing: /var/www/cobbler/images/CentOS-5-i386
removing: /var/lib/tftpboot/pxelinux.cfg/default
removing: /var/lib/tftpboot/grub/images
removing: /var/lib/tftpboot/grub/grub-x86_64.efi
removing: /var/lib/tftpboot/grub/grub-x86.efi
removing: /var/lib/tftpboot/grub/efidefault
removing: /var/lib/tftpboot/images/CentOS-5-xen-i386
removing: /var/lib/tftpboot/images/CentOS-5-i386
removing: /var/lib/tftpboot/s390x/profile_list
copying bootloaders
copying: /usr/share/syslinux/memdisk -> /var/lib/tftpboot/memdisk
trying hardlink /var/lib/cobbler/loaders/grub-x86_64.efi -> /var/lib/tftpboot/grub/grub-x86_64.efi
trying hardlink /var/lib/cobbler/loaders/grub-x86.efi -> /var/lib/tftpboot/grub/grub-x86.efi
copying distros to tftpboot
copying files for distro: CentOS-5-i386
trying hardlink /var/www/cobbler/ks_mirror/CentOS-5-i386/images/pxeboot/vmlinuz -> /var/lib/tftpboot/images/CentOS-5-i386/vmlinuz
trying hardlink /var/www/cobbler/ks_mirror/CentOS-5-i386/images/pxeboot/initrd.img -> /var/lib/tftpboot/images/CentOS-5-i386/initrd.img
copying files for distro: CentOS-5-xen-i386
trying hardlink /var/www/cobbler/ks_mirror/CentOS-5-i386/images/xen/vmlinuz -> /var/lib/tftpboot/images/CentOS-5-xen-i386/vmlinuz
trying hardlink /var/www/cobbler/ks_mirror/CentOS-5-i386/images/xen/initrd.img -> /var/lib/tftpboot/images/CentOS-5-xen-i386/initrd.img
copying images
generating PXE configuration files
generating PXE menu structure
copying files for distro: CentOS-5-i386
trying hardlink /var/www/cobbler/ks_mirror/CentOS-5-i386/images/pxeboot/vmlinuz -> /var/www/cobbler/images/CentOS-5-i386/vmlinuz
trying hardlink /var/www/cobbler/ks_mirror/CentOS-5-i386/images/pxeboot/initrd.img -> /var/www/cobbler/images/CentOS-5-i386/initrd.img
Writing template files for CentOS-5-i386
copying files for distro: CentOS-5-xen-i386
trying hardlink /var/www/cobbler/ks_mirror/CentOS-5-i386/images/xen/vmlinuz -> /var/www/cobbler/images/CentOS-5-xen-i386/vmlinuz
trying hardlink /var/www/cobbler/ks_mirror/CentOS-5-i386/images/xen/initrd.img -> /var/www/cobbler/images/CentOS-5-xen-i386/initrd.img
Writing template files for CentOS-5-xen-i386
rendering DHCP files
generating /etc/dhcp/dhcpd.conf
rendering TFTPD files
generating /etc/xinetd.d/tftp
cleaning link caches
rendering Rsync files
running post-sync triggers
running python triggers from /var/lib/cobbler/triggers/sync/post/*
running python trigger cobbler.modules.sync_post_restart_services
running: dhcpd -t -q
received on stdout:
received on stderr:
running: service dhcpd restart
received on stdout: Shutting down dhcpd: [ OK ]
Starting dhcpd: [ OK ]
received on stderr:
running shell triggers from /var/lib/cobbler/triggers/sync/post/*
running python triggers from /var/lib/cobbler/triggers/change/*
running python trigger cobbler.modules.scm_track
running shell triggers from /var/lib/cobbler/triggers/change/*
*** TASK COMPLETE ***
(there has any infomation about xen)
# cobbler distro list
CentOS-5-i386
CentOS-5-xen-i386
# cobbler distro report
Name : CentOS-5-i386
Architecture : i386
TFTP Boot Files : {}
Breed : redhat
Comment :
Fetchable Files : {}
Initrd : /var/www/cobbler/ks_mirror/CentOS-5-i386/images/pxeboot/initrd.img
Kernel : /var/www/cobbler/ks_mirror/CentOS-5-i386/images/pxeboot/vmlinuz
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart Metadata : {'tree': 'http://@@http_server@@/cblr/links/CentOS-5-i386'}
Management Classes : []
OS Version : rhel5
Owners : ['admin']
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Template Files : {}
Name : CentOS-5-xen-i386
Architecture : i386
TFTP Boot Files : {}
Breed : redhat
Comment :
Fetchable Files : {}
Initrd : /var/www/cobbler/ks_mirror/CentOS-5-i386/images/xen/initrd.img
Kernel : /var/www/cobbler/ks_mirror/CentOS-5-i386/images/xen/vmlinuz
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart Metadata : {'tree': 'http://@@http_server@@/cblr/links/CentOS-5-xen-i386'}
Management Classes : []
OS Version : rhel5
Owners : ['admin']
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Template Files : {}
(there has any infomation about xen,also.)
# cat /var/lib/tftpboot/pxelinux.cfg/default
DEFAULT menu
PROMPT 0
MENU TITLE Cobbler | http://www.cobblerd.org/
TIMEOUT 200
TOTALTIMEOUT 6000
ONTIMEOUT local
LABEL local
MENU LABEL (local)
MENU DEFAULT
LOCALBOOT -1
LABEL Centos-5-i386
kernel /images/Centos-5-i386/vmlinuz
MENU LABEL Centos-5-i386
append initrd=/images/Centos-5-i386/initrd.img ksdevice=bootif lang= kssendmac text ks=http://192.168.80.151/cblr/svc/op/ks/profile/Centos-5-i386
ipappend 2
MENU end
# cobbler report list
distros:
==========
Name : CentOS-5-i386
Architecture : i386
TFTP Boot Files : {}
Breed : redhat
Comment :
Fetchable Files : {}
Initrd : /var/www/cobbler/ks_mirror/CentOS-5-i386/images/pxeboot/initrd.img
Kernel : /var/www/cobbler/ks_mirror/CentOS-5-i386/images/pxeboot/vmlinuz
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart Metadata : {'tree': 'http://@@http_server@@/cblr/links/CentOS-5-i386'}
Management Classes : []
OS Version : rhel5
Owners : ['admin']
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Template Files : {}
Name : CentOS-5-xen-i386
Architecture : i386
TFTP Boot Files : {}
Breed : redhat
Comment :
Fetchable Files : {}
Initrd : /var/www/cobbler/ks_mirror/CentOS-5-i386/images/xen/initrd.img
Kernel : /var/www/cobbler/ks_mirror/CentOS-5-i386/images/xen/vmlinuz
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart Metadata : {'tree': 'http://@@http_server@@/cblr/links/CentOS-5-xen-i386'}
Management Classes : []
OS Version : rhel5
Owners : ['admin']
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Template Files : {}
profiles:
==========
Name : CentOS-5-i386
TFTP Boot Files : {}
Comment :
DHCP Tag : default
Distribution : CentOS-5-i386
Enable gPXE? : 0
Enable PXE Menu? : 1
Fetchable Files : {}
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart : /var/lib/cobbler/kickstarts/centos5.ks
Kickstart Metadata : {}
Management Classes : []
Management Parameters : <<inherit>>
Name Servers : []
Name Servers Search Path : []
Owners : ['admin']
Parent Profile :
Proxy :
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Repos : []
Server Override : <<inherit>>
Template Files : {}
Virt Auto Boot : 1
Virt Bridge : xenbr0
Virt CPUs : 1
Virt Disk Driver Type : raw
Virt File Size(GB) : 5
Virt Path :
Virt RAM (MB) : 512
Virt Type : kvm
Name : CentOS-5-xen-i386
TFTP Boot Files : {}
Comment :
DHCP Tag : default
Distribution : CentOS-5-xen-i386
Enable gPXE? : 0
Enable PXE Menu? : 1
Fetchable Files : {}
Kernel Options : {}
Kernel Options (Post Install) : {}
Kickstart : /var/lib/cobbler/kickstarts/sample.ks
Kickstart Metadata : {}
Management Classes : []
Management Parameters : <<inherit>>
Name Servers : []
Name Servers Search Path : []
Owners : ['admin']
Parent Profile :
Proxy :
Red Hat Management Key : <<inherit>>
Red Hat Management Server : <<inherit>>
Repos : []
Server Override : <<inherit>>
Template Files : {}
Virt Auto Boot : 1
Virt Bridge : xenbr0
Virt CPUs : 1
Virt Disk Driver Type : raw
Virt File Size(GB) : 5
Virt Path :
Virt RAM (MB) : 512
Virt Type : xenpv
systems:
==========
repos:
==========
Name : CentOS-5-i386
Apt Components (apt only) :
Apt Dist Names (apt only) :
Arch : i386
Breed : yum
Comment :
Createrepo Flags : <<inherit>>
Environment Variables : {}
Keep Updated : True
Mirror : http://mirrors.163.com/centos/5/os/i386/
Mirror locally : True
Owners : ['admin']
Priority : 99
RPM List : []
Yum Options : {}
Name : EPEL-5-i386
Apt Components (apt only) :
Apt Dist Names (apt only) :
Arch : i386
Breed : yum
Comment :
Createrepo Flags : <<inherit>>
Environment Variables : {}
Keep Updated : True
Mirror : http://download.fedoraproject.org/pub/epel/5/i386/
Mirror locally : True
Owners : ['admin']
Priority : 99
RPM List : []
Yum Options : {}
images:
==========
mgmtclasses:
==========
packages:
==========
files:
==========
I don't know where is the mistake.
Can you help me?:(
Waiting for your messages.
Best Regards!
10 years, 6 months
Cobbler & IPv6
by Paco Bernabe
Hi,
Does anyone know where I can find information about IPv6 support in cobbler?
--
Met vriendelijke groeten / Best regards,
*Paco Bernabe*
| Systemsprogrammer | SURFsara | Science Park 140 | 1098XG Amsterdam | T
+31 610 961 785 | paco(a)surfsara.nl | www.surfsara.nl |
10 years, 6 months
pxe files left in tfpboot when netboot is disabled
by Steven Seed
We've been using cobbler for some time and I've noticed that the pxe files
are generated in the /tftpboot/pxe/grub and /tftpboot/pxe/pxelinux.cfg
directories for systems regardless of whether or not netboot is enabled for
a system. I'm assuming this hasn't been a problem for most people who are
letting cobbler manage dhcp. I'm guessing the dhcp config is manipulated so
once netboot is disabled, it removes the boot file from the config. We are
using cobbler in a slightly unconventional way as it pertains to dhcp/pxe.
We use the pxe files generated by cobbler, but they are accessed via a
tfp/dhcp server that is not managed by cobbler. This is done because we
have other systems getting managed outside of cobbler that also generate
pxe configurations.
I'm wondering if there is a reason these pxe files are not removed when the
host has netboot disabled.
As a test, I modified the code (this is 2.2.3-2) in
/usr/lib/python2.6/site-packages/cobbler/pxegen.py line 279 and added (and
system.netboot_enabled):
os.symlink("../yaboot", f3)
else:
continue
>> if system.is_management_supported() and system.netboot_enabled:
if not image_based:
self.write_pxe_file(f2, system, profile, distro,
working_arch)
if grub_path:
self.write_pxe_file(grub_path, system, profile,
distro,
working_arch, format="grub")
else:
self.write_pxe_file(f2, system, None, None,
working_arch, image=profile)
else:
# ensure the file doesn't exist
utils.rmfile(f2)
if grub_path:
utils.rmfile(grub_path)
This change had the desired affect. Is this something that can be patched
into the code, or am I missing something?
--
-
Steven Seed
Sr Systems Engineer
Walt Disney Animation Studios
818-460-9453
10 years, 6 months