How to debug...
by Michael Tiernan
I'm sure I can solve this by hard work but I'm wondering if there's a
way to trigger a debugging so that the steps that cobbler's supposed to
be doing are obvious.
I've got a single system in my cobbler instance and it *should* prepare
the tftp stuff for the pxe boot but I'll be darned if I can see why it's
NOT doing this.
I'm hoping there's a flag one can turn on (or whatever) that will allow
me to see the steps it's attempting to take. I'm sure I'm missing
something obvious and I'd like to find it before I go crazy. :)
Thanks for everyone's time.
task started: 2014-07-22_163236_sync
task started (id=Sync, time=Tue Jul 22 16:32:36 2014)
running pre-sync triggers
cleaning trees
removing: /var/www/cobbler/images/scilinall-x86_64
removing: /var/lib/tftpboot/pxelinux.cfg/default
removing: /var/lib/tftpboot/grub/images
removing: /var/lib/tftpboot/grub/efidefault
removing: /var/lib/tftpboot/grub/grub-x86_64.efi
removing: /var/lib/tftpboot/grub/grub-x86.efi
removing: /var/lib/tftpboot/s390x/profile_list
copying bootloaders
copying: /var/lib/cobbler/loaders/pxelinux.0 -> /var/lib/tftpboot/pxelinux.0
copying: /var/lib/cobbler/loaders/menu.c32 -> /var/lib/tftpboot/menu.c32
copying: /var/lib/cobbler/loaders/yaboot -> /var/lib/tftpboot/yaboot
copying: /var/lib/cobbler/loaders/grub-x86_64.efi -> /var/lib/tftpboot/grub/grub-x86_64.efi
copying: /var/lib/cobbler/loaders/grub-x86.efi -> /var/lib/tftpboot/grub/grub-x86.efi
copying files for distro: scilinall-x86_64
trying hardlink /var/www/cobbler/ks_mirror/scilinall/images/pxeboot/vmlinuz -> /var/www/cobbler/images/scilinall-x86_64/vmlinuz
trying hardlink /var/www/cobbler/ks_mirror/scilinall/images/pxeboot/initrd.img -> /var/www/cobbler/images/scilinall-x86_64/initrd.img
Writing template files for scilinall-x86_64
rendering DHCP files
generating /etc/dhcp/dhcpd.conf
rendering TFTPD files
generating /etc/xinetd.d/tftp
cleaning link caches
running: find /var/lib/tftpboot/images/.link_cache -maxdepth 1 -type f -links 1 -exec rm -f '{}' ';'
received on stdout:
received on stderr:
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 ***
9 years, 8 months
Server still has DHCP address after being built with Ubuntu 14.04
by Justin Lloyd
Hi all,
I'm trying to build an Ubuntu 14.04.1 server from my Cobbler 12.04.4 server
running Cobbler 2.6.3. I'd been successfully building 12.04.4 servers with
Cobbler 2.7.0 out of github, but now that I've added 14.04.1 to my Cobbler
distros, the servers seem to build fine except they're left with the DHCP
address allocated to them by atftpd. The /etc/network/interfaces file
hasn't been updated as expected by the post_install_network_config_deb
snippet specified in the preseed_late_default script.
Any ideas what I might be missing? (I've asked on IRC yesterday and today
but received no replies.)
9 years, 9 months
Re: [cobbler] Anamon
by Michael
Hello Jörgen,
We are using it... Less than 1% of our deployments.
We don't need anamon when everything goes well off course.
But... When something goes bad, when your install has a little thing
wrecked...
The anamon becomes helpful to understand what, and when something goes
wrong.
We use PXE installation massively.
Last time I used it to debug a fresh RHEL install on a brand new physical
server.
As the RAID card was no supported, the anaconda goes to build partitions on
just one disk.
You come back in front of your ILO console, everything looks ok but you
don't have RAID1...
Not easy to detect immediately and even worse easy to understand when and
why it goes bad.
The good reflex was to go see the install log files and I saw that the raid
card was detected
but there was no driver to support it. Fast and rapid detection, brings a
rapid solution.
(a driver disk was used).
So yes, we use anamon. It is quite rare but how helpful !
Off course, if you have an alternative purely based on remote syslog. It
will be welcomed too.
*Michael PATRIS Thales Alenia Space*
2014-07-17 14:30 GMT+02:00 Jörgen Maas <jorgen.maas(a)gmail.com>:
> Hi guys,
>
> Just wondering if there are people out there actually using anamon ?
> Please let me know if you do, or don't.
>
> --
> Grtz,
> Jörgen Maas
>
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
> https://lists.fedorahosted.org/mailman/listinfo/cobbler
>
>
9 years, 9 months
RHEL 5 Update problem
by Dan White
Using EPEL as my source, trying to update this morning :
It wants to update:
cobbler.noarch 2.4.4-1.el5 epel
cobbler-web.noarch 2.4.4-1.el5 epel
koan.noarch 2.4.4-1.el5 epel
And then it says:
Error: Missing Dependency: virt-install is needed by package koan-2.4.4-1.el5.noarch (epel)
A search reveals that there is no such animal anywhere in EPEL or in anything that looks like ot is compatible with RHEL 5
Can I do without koan ? I use Cobbler for bare metal installs. Nothing virtual.
“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)
9 years, 9 months
Help with Exception value: 'dns-name duplicated:
by Neil Watson
Greetings,
I'm using an old version of cobbler that is bundled with Red Hat
Satellite. When I attempt to modify a system, setting hostname and IP I
get this error:
Thu Jul 24 14:09:52 2014 - INFO | find_items; ['system']
Thu Jul 24 14:09:52 2014 - INFO | Exception occured: <class 'cobbler.cexceptions.CX'>
Thu Jul 24 14:09:52 2014 - INFO | Exception value: 'dns-name duplicated: razz0547.example.com'
Thu Jul 24 14:09:52 2014 - INFO | Exception Info:
File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 1759, in _dispatch
return method_handle(*params)
File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 766, in modify_system
return self.modify_item("system",object_id,attribute,arg,token)
File "/usr/lib/python2.6/site-packages/cobbler/remote.py", line 759, in modify_item
return method(arg)
File "/usr/lib/python2.6/site-packages/cobbler/item_system.py", line 582, in modify_interface
if field == "dnsname" : self.set_dns_name(value, interface)
File "/usr/lib/python2.6/site-packages/cobbler/item_system.py", line 264, in set_dns_name
raise CX("dns-name duplicated: %s" % dns_name)
I see no evidence of a duplicate DNS entry in any of the profiles. How can I
debug this?
--
Neil Watson
Linux/UNIX Consultant
http://watson-wilson.ca
9 years, 9 months
Small problem to report.
by Michael Tiernan
When trying to install on a Scientific Linux system using the CentOS6
RPM, I get this error:
Installing : cobbler-2.6.3-7.1.noarch
Non-fatal POSTIN scriptlet failure in rpm package cobbler-2.6.3-7.1.noarch
warning: %post(cobbler-2.6.3-7.1.noarch) scriptlet failed, exit status 1
This is a clean install on a fresh system.
9 years, 9 months
Updating to 2.6.X in stable releases
by Orion Poplawski
Fedora/EPEL currently provides 2.4.X in released branches (F19,F20,EL6). Are
there any concerns about updating to 2.6.4 for any/all of these?
--
Orion Poplawski
Technical Manager 303-415-9701 x222
NWRA, Boulder/CoRA Office FAX: 303-415-9702
3380 Mitchell Lane orion(a)nwra.com
Boulder, CO 80301 http://www.nwra.com
9 years, 9 months