<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
Windows install with Cobbler
by Janet.Conkle@afscn.com
Has anyone been successful in installing windows using cobbler? I've
found a few things on the net but nothing definitive. I need a tool
that will install baseline images on lab boxes of both the linux and
Windows flavors.
Janet Conkle
ETG
x5343
11 years, 5 months
[PATCH] support for gPXE and esxi5
by James Cammarata
Two patches, pushed to my github account:
https://github.com/jimi1283/cobbler/commits/esxi-improvements
The ESXI5 patch requires the gpxe patch, since the only sane way to
add the support for it to cobbler was via the gpxe process documented
in the VMware build guide. This allows all of the files to be served
via httpd, otherwise you have to copy the entire ISO contents to a
TFTP directory (which required some ugly hacking in cobbler).
The one caveat about the gpxe process is that you must manually copy
the undionly.kpxe file to your tftp directory. Newer distros package
the etherboot files, otherwise you'll have to download the files from
http://etherboot.org/wiki/download and build the file yourself (it's a
fairly painless process). Another TODO is to make the same setup
changes for DNSMASQ, right now this only supports ISC DHCPD.
There is a new setting called enable_gpxe, which is used currently
only when new items are created. There is also a new field for systems
and profiles by the same name, which sets it on a per-object basis.
This isn't being used for profiles yet, nor will it work on systems
without an interface and MAC specified, but when enabled on a system
with a MAC it will create an entry in dhcpd.conf that is configured to
chain load the undionly.kpxe file. I plan on adding support for
generic profiles and systems without a MAC, but it might be a
some-what convoluted process and I'm trying to work out the best way
to do it (currently it'd involve chain loading gpxe, and then
detecting that you don't want to use gpxe and chain loading back into
the old pxelinux.0 file).
I plan on merging these into master in the near future unless people
have major issues during testing. Enjoy!
12 years, 4 months
Github
by Michael DeHaan
For those that haven't seen the post to cobbler-devel but are
interested in continued access to Cobbler's source, see Scott's post
about moving to github here:
https://fedorahosted.org/pipermail/cobbler-devel/2011-November/002530.html
Oh, and for those that remember me. Hi.
Expect my contributions to be sporadic and mostly community centric --
I definitely should be able to help with some historical knowledge on
"why the heck does that work that way?" and will also be working on
moving documentation into github pages and cleaning that up. There
may be some upgrades to the core as well.
I will say that in the last two years, I've seen Cobbler used in more
and more places. Some I've learned about are exceedingly
impressive. A lot of that momentum comes from how helpful people are
here in helping others. Thank you all for helping make that happen.
I'm also very glad to see things start taking a lot more of a
upstream focus. Github should help with this and allow more people
to find things and collaborate more freely and further accelerate
things. Good times ahead.
--Michael
12 years, 4 months
PXE Booting systems
by Scot Floess
All,
I managed to get PXE booting working with Cobbler (I'm using DHCP outside of Cobbler)...
I notice when I run "cobbler sync," the generated /tftpboot/pxelnux.cfg/default does not contain any system records I have defined. I spent most of yesterday looking through the code and see in pxegen.py only profiles and images are listed. I managed to hack away a little bit to get my system records to emit - and its mostly working now for installations...
Question I have is, were system records purposefully omitted? Or am I missing something? I'm wanting to have all my systems listed in the PXE menu and be able to choose and install just like if I generate the iso file and burn to CD...
Thanks,
Flossy
--
Make It So Number One
12 years, 4 months
help with system pre trigger getting mach address
by bruce bushby
Hi
I've been playing with cobbler triggers in an effort to tie cobbler
into my distributed environment. My cobbler sits on my RHN
Satellite...however I use Infoblox for dhcp & dns.
My initial attempt was the use of a bash script:
/var/lib/cobbler/triggers/add/system/pre/create_dhcp_dns.sh
However I soon discovered that cobbler will ONLY pass $1 to the
script, and does not pass on the MAC address ...which I obviously need
to update the dhcp (Infoblox).
This is my cobbler add system command:
cobbler system add --name=sparta
--profile=uk-mserv-61-puppet:1:MarkitGroup --mac=00:50:56:92:1b:61
--hostname=sparta.mserv.local
I'm guessing a need to change my trigger to a python script, call the
cobbler_api and then parse out the arguments...something like:
/var/lib/cobbler/triggers/add/system/pre/create_dhcp_dns.py
create_dhcp_dns.py would parse the above cobbler command arguments,
extract the mac address and hostname, obtain a new IP from Infoblox,
update the dhcp and then continue the cobbler command...but now with
the additional argument "--ip"
I have working perl scripts to obtain an IP from Infoblox and update
the dhcp etc.....but I'm struggling to build them into my cobbler
trigger. I could probably get away with a wrapper script that calls
cobbler....but I would prefer to use cobbler directly and use triggers
to do the back end work.
Is it possible....any examples?
Thanks
Bruce
12 years, 5 months
buildiso USB ?
by Dan White
Did anyone ever come up with a reliable recipe for making a bootable USB-stick from a generated.iso ?
If so, I could use it.
“Sometimes I think the surest sign that intelligent life exists elsewhere in the universe is that none of it has tried to contact us.”
Bill Waterson (Calvin & Hobbes)
12 years, 5 months
Question about Cobbler on a different port
by Russ Lavoy
I have a question on how I would get cobbler to work on a different port. Is it as easy as changing the listen port?
The reason why i ask, is because the server I am putting this on runs multiple web pages and I noticed that when initially tried to change the port for cobbler it got upset with me.
Thanks!
12 years, 5 months
RE: Re: buildiso with DNS
by Tailpied Stephane
Finally the dns option is coded into the lib python of cobbler (action_buildiso.py). After a new test the dns servers appears into isolinux.cfg. My first test had to have another pb !!!
My buildiso is now ok.
Stéphane
-----Message d'origine-----
De : Tailpied Stephane
Envoyé : mercredi 16 novembre 2011 14:51
À : cobbler(a)lists.fedorahosted.org
Objet : RE: Re: buildiso with DNS
Thank you Christian,
> Hi Stephane,
> On Wed, Nov 16, 2011 at 11:46:15AM +0100, Tailpied Stephane wrote:
> > I use buildiso to deploy with no pxe, and I want to specify a dns server in isolinux.cfg in generated.iso. Is it possible ?
> >
> > I had "Name Server" in my profile.
> > I had an IP/Gateway/Netmask in my system.
> > I used "cobbler buildiso -system=my_system" to generate the iso.
> > My isolinux.cfg looks like :
> > "kernel 3.krn
> > append initrd=3.img ks=<url> ksdevice=bootif lang= kssendmac text ip=<ip> netmask=<netmask> gateway=<gateway>"
> >
> > What to do to specify a DNS server ?
> This question is more PXE/distro specific than cobbler.
Yes, but it's cobbler which builds this iso and the isolinux.cfg. I thought that cobbler could build with a specific DNS like IP, netmask and gateway.
Effectively, after a buildiso, I can open the iso, add a dns into the isolinux.cfg (or replace all names by IP) and rebuild the iso, but it's a supplementary task :-(
> In case you are relating to RHEL or Centos these links will help you:
> http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Install...
> http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Install...
> cheers, Christian
Stéphane
L'integrite de ce message n'etant pas assuree sur internet, Natixis ne peut etre tenu responsable de son contenu. Toute utilisation ou diffusion non autorisee est interdite. Si
vous n'etes pas destinataire de ce message, merci de le detruire et d'avertir l'expediteur. Ensemble, faisons un geste pour l'environnement : n'imprimons nos mails que si
necessaire.
The integrity of this message cannot be guaranteed on the Internet. Natixis can not therefore be considered responsible for the contents. Any unauthorized use or dissemination is
prohibited. If you are not the intended recipient of this message, then please delete it and notify the sender. Let us mind the environment : let's print our mails only when
necessary
12 years, 5 months