Emerging Technologies Management Tools ()

headers Slinky | 1 Jun 19:33 · /tftpboot/

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@...
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
Hi,

I just ran cobbler check (On the latest download) and it told me the following:

[root <at> localhost cobbler]# cobbler check
The following potential problems were detected:
#0: please create directory: -v
#1: directory needs to be created: -v
#2: One or more kickstart templates references default password 'cobbler' and should be changed for
security reasons: /etc/cobbler/sample.ks, /etc/cobbler/legacy.ks, /etc/cobbler/sample_end.ks

#0 and #1 seem a bit odd?  Any thoughts?

Thanks,
- Ole

Slinky,

Awesome - I get lots of information now, such as:

Jun  1 14:11:53 localhost dhcpd: DHCPDISCOVER from 00:16:ec:cc:d1:f6 via eth0
Jun  1 14:11:53 localhost dhcpd: DHCPOFFER on 192.168.1.2 to 00:16:ec:cc:d1:f6 via eth0
Jun  1 14:11:55 localhost dhcpd: DHCPREQUEST for 192.168.1.2 (192.168.1.6) from 00:16:ec:cc:d1:f6 via eth0
Jun  1 14:11:55 localhost dhcpd: DHCPACK on 192.168.1.2 to 00:16:ec:cc:d1:f6 via eth0
Jun  1 14:11:55 localhost xinetd[30107]: START: tftp pid=30114 from=192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30115]: RRQ from 192.168.1.2 filename /pxelinux.0
Jun  1 14:11:55 localhost in.tftpd[30115]: tftp: client does not accept options
Jun  1 14:11:55 localhost in.tftpd[30116]: RRQ from 192.168.1.2 filename /pxelinux.0
Jun  1 14:11:55 localhost in.tftpd[30117]: RRQ from 192.168.1.2 filename /pxelinux.cfg/01-00-16-ec-cc-d1-f6
Jun  1 14:11:55 localhost in.tftpd[30117]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30118]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A80102
Jun  1 14:11:55 localhost in.tftpd[30118]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30119]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A8010
Jun  1 14:11:55 localhost in.tftpd[30119]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30120]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A801
Jun  1 14:11:55 localhost in.tftpd[30120]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30121]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A80
Jun  1 14:11:55 localhost in.tftpd[30121]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30122]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A8
Jun  1 14:11:55 localhost in.tftpd[30122]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30123]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0A
Jun  1 14:11:55 localhost in.tftpd[30123]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30124]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C0
Jun  1 14:11:55 localhost in.tftpd[30124]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30125]: RRQ from 192.168.1.2 filename /pxelinux.cfg/C
Jun  1 14:11:55 localhost in.tftpd[30125]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30126]: RRQ from 192.168.1.2 filename /pxelinux.cfg/default
Jun  1 14:11:55 localhost in.tftpd[30127]: RRQ from 192.168.1.2 filename /menu
Jun  1 14:11:55 localhost in.tftpd[30127]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30128]: RRQ from 192.168.1.2 filename /menu.cbt
Jun  1 14:11:55 localhost in.tftpd[30128]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30129]: RRQ from 192.168.1.2 filename /menu.0
Jun  1 14:11:55 localhost in.tftpd[30129]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30130]: RRQ from 192.168.1.2 filename /menu.com
Jun  1 14:11:55 localhost in.tftpd[30130]: sending NAK (1, File not found) to 192.168.1.2
Jun  1 14:11:55 localhost in.tftpd[30131]: RRQ from 192.168.1.2 filename /menu.c32
Jun  1 14:11:55 localhost in.tftpd[30132]: RRQ from 192.168.1.2 filename /pxelinux.cfg/default

So, I reread the man page, and it says that filename should be set to "pxelinux.0" and I had "/pxelinux.0",
which is what dhcp.template came with (Should I file a ticket?).  So I changed that to "pxelinux.0", and
attempted to run cobbler sync, which tells me:

[root <at> localhost ole]# cobbler sync
cannot find directory: -v

I tried restarting the cobbler daemon and doing cobbler sync and the same message appears.  Thoughts?

Thanks again,
- Ole

Slinky wrote:
> Make sure you have verbose enabled in /etc/xinetd.d/tftp
> 
> ..
>         server_args             = -s -v -v -v /tftpboot
> ...
> 
> You'll then see tftp hits in /var/log/messages. Example:
> 
> /var/log/messages.3:May 13 09:12:47 islinky in.tftpd[3556]: RRQ from 
> 137.138.32.49 <http://137.138.32.49> filename tftpboot/dir/file.cbt
> /var/log/messages.3:May 13 09:12:47 islinky in.tftpd[3556]: sending NAK 
> (1, File not found) to 137.138.32.49 <http://137.138.32.49>
> 
> It could just be some thing simple like you're dhcp points somewhere but 
> your tftp "files" are else where.
> 
> HTH
> Slinky
> 
> 
> 2008/5/31 Ole Ersoy <ole.ersoy@... <mailto:ole.ersoy@...>>:
> 
>     Any trouble shooting tips?  I used to get a "boot" menu prior to
>     adding a system...
> 
>     TIA,
>     - Ole
> 
>     _______________________________________________
>     et-mgmt-tools mailing list
>     et-mgmt-tools@... <mailto:et-mgmt-tools@...>
>     https://www.redhat.com/mailman/listinfo/et-mgmt-tools
> 
> 
> 
> 
> -- 
> Regards
> Dan
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools@...
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@...
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
> pxelinux.0 is the binary pxe loader. dhcp needs to point at pxelinux.0 
> (wherever it is*), as this is what the client needs to boot with.
> 
> default is the default pxe configuration which a request falls down to 
> if the corresponding 01-aa-bb-cc-dd-ee-ff isn't found, and is generally 
> found in pxelinux.cfg/
> 
> A client would expect to find it in /tftpboot/cobbler/loader/pxelinux.0....
> 
> Does that help?

I think so.  Just want to make sure I'm clear.  The file is currently here:

[root <at> localhost ole]# ls /tftpboot/
elilo-3.6-ia64.efi  images  menu.c32  pxelinux.0  pxelinux.cfg

So if I put "pxelinux.0" for the filename option it should resolve correctly right?

>  
> 
>      So I changed that to "pxelinux.0", and attempted to run cobbler
>     sync, which tells me:
> 
>     [root <at> localhost ole]# cobbler sync
>     cannot find directory: -v
> 
>     I tried restarting the cobbler daemon and doing cobbler sync and the
>     same message appears.  Thoughts?
> 
> 
> tbh your cobbler setup sounds a bit FUBAR. Purge and try again perhaps?

I'll try to nuke the system and profile I added to see whether that caused the hiccup.  It was syncing fine
before that.  Otherwise I'll start from scratch.

Thanks!
- Ole

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@...
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
On Wed, May 28, 2008 at 12:22:53PM +0200, Feichtinger Günter wrote:
> > -----Ursprüngliche Nachricht-----
> > Von: Richard W.M. Jones [mailto:rjones@...] 
> > Gesendet: Dienstag, 27. Mai 2008 11:45
> > An: Feichtinger Günter
> > Cc: et-mgmt-tools@...
> > Betreff: Re: ocaml-libvirt-0.4.0.1: Can't connect to Xen- Host
> > 
> > On Tue, May 27, 2008 at 11:37:10AM +0200, Feichtinger Günter wrote:
> > > I intstalled the ocaml-libvirt-0.4.0.1.exe on MS- Vista 
> > without problems.
> > > Also the virt-ctrl.exe starts without problems.
> > > But when I try to connect to a Xen-Host I get the messages: 
> > > libvir: Remote error : Cannot access CA certificate 
> > > 'C:/msys/1.0/local/etc/pki/C
> > > A/cacert.pem': No such file or directory (2)
> > > 
> > > Please be so kind and help.
> > 
> > It's not very clear to me what you are trying to connect to 
> > what, but you'll probably want to read about remote connections, here:
> > 
> > http://libvirt.org/remote.html
> > 
> > Rich.
> 
> Hello Richard,
> thanks for your prompt answer. I see, I have to explain it more excatly.
> I have 3 Xen-Hosts (CentOS 5.1) and use virt-managaer local an this hosts. 
> I'm looking for a possibility to manages xen-hosts from MS-Windows-Clients like VMWareServerConsole.
> So I was looking around and found your port of the virt-manager. 
> I tried to connect with xen://xen-host/ and get the message above. 
> Which possibility to I have for remote connections? I think I read that with your virt-manager port only
support TLS, isn't it?
> So do I have to work with certificates? In my test-envirment a "low" security solution is also fine 

The first thing to say is that this isn't a port of virt-manager.  We
couldn't get that working on Windows because the Python stuff for
Win32 was too complicated.  This is a port of virt-ctrl instead
(http://et.redhat.com/~rjones/virt-ctrl/) which is a far less powerful
virt-manager clone that I wrote in my spare time, just as an
experiment.  (It's also a rather old version of virt-ctrl.  I really
must update that package ...)

Anyway, you should be able to set up your Xen hosts so that TCP
(insecure) connections are possible.  Assuming that libvirtd is
running, there should be a file /etc/libvirt/libvirtd.conf which you
can edit to enable TCP connections:

http://libvirt.org/remote.html#Remote_libvirtd_configuration

  listen_tcp = 1

I believe you also need to edit /etc/sysconfig/libvirtd and uncomment:

  LIBVIRTD_ARGS="--listen"

and of course open firewall port 16509 if necessary.

Then you should be able to connect remotely using this URI:

  xen+tcp://hostname/

TCP connections are totally insecure, so you should only do this on a
private network.

Rich.

--

-- 
Richard Jones, Emerging Technologies, Red Hat  http://et.redhat.com/~rjones
Read my OCaml programming blog: http://camltastic.blogspot.com/
Fedora now supports 59 OCaml packages (the OPEN alternative to F#)
http://cocan.org/getting_started_with_ocaml_on_red_hat_and_fedora

On Mon, Jun 02, 2008 at 10:52:19AM +0100, Richard W.M. Jones wrote:
> http://libvirt.org/remote.html#Remote_libvirtd_configuration
> 
>   listen_tcp = 1
> 
> I believe you also need to edit /etc/sysconfig/libvirtd and uncomment:
> 
>   LIBVIRTD_ARGS="--listen"
> 
> and of course open firewall port 16509 if necessary.
> 
> Then you should be able to connect remotely using this URI:
> 
>   xen+tcp://hostname/
> 
> TCP connections are totally insecure, so you should only do this on a
> private network.

This is no longer true. Recent libvirt will enable SASL authentication on
the TCP socket by default, and the default SASL config for libvirt turns
on digest-md5 which provides by username+password authentication and
subsquent session encryption. You can also switch SASL to use kerberos
which again provides auth & session encryption. With either digest-md5
or Kerberos, the security is on a par with SSL/TLS in terms of encryption
strength

http://libvirt.org/auth.html#ACL_server_username

Regards,
Daniel.
--

-- 
|: Red Hat, Engineering, Boston   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

Ole Ersoy wrote:
> Hi,
>
> I just ran cobbler check (On the latest download) and it told me the 
> following:
>
> [root <at> localhost cobbler]# cobbler check
> The following potential problems were detected:
> #0: please create directory: -v
> #1: directory needs to be created: -v
> #2: One or more kickstart templates references default password 
> 'cobbler' and should be changed for security reasons: 
> /etc/cobbler/sample.ks, /etc/cobbler/legacy.ks, 
> /etc/cobbler/sample_end.ks
>
> #0 and #1 seem a bit odd?  Any thoughts?
>
> Thanks,
> - Ole
>
>
Please post the full contents of your /etc/tftp.d/init.d file as well as 
what OS you are using (rpm -q --what-provides redhat-release).     Since 
the default location in F9 (/var/lib/tftpboot) is different than those 
in previous versions (/tftpboot), Cobbler needs to parse this file to 
find out what location you are using.

It expects to see something like:

        server_args             = -s /tftpboot

Something in your file is confusing the parser.

>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools@...
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools

Slinky wrote:
> Make sure you have verbose enabled in /etc/xinetd.d/tftp
>
> ..
>         server_args             = -s -v -v -v /tftpboot
> ...

Regarding your other post about server locations, here's your problem, 
Mr. Slinky broke you :)

-s /tftpboot -vvv

You just set directory explicitly to "-v" :)

>
> You'll then see tftp hits in /var/log/messages. Example:
>
> /var/log/messages.3:May 13 09:12:47 islinky in.tftpd[3556]: RRQ from 
> 137.138.32.49 <http://137.138.32.49> filename tftpboot/dir/file.cbt
> /var/log/messages.3:May 13 09:12:47 islinky in.tftpd[3556]: sending 
> NAK (1, File not found) to 137.138.32.49 <http://137.138.32.49>
>
> It could just be some thing simple like you're dhcp points somewhere 
> but your tftp "files" are else where.
>
> HTH
> Slinky
>
>
> 2008/5/31 Ole Ersoy <ole.ersoy@... <mailto:ole.ersoy@...>>:
>
>     Any trouble shooting tips?  I used to get a "boot" menu prior to
>     adding a system...
>
>     TIA,
>     - Ole
>
>     _______________________________________________
>     et-mgmt-tools mailing list
>     et-mgmt-tools@... <mailto:et-mgmt-tools@...>
>     https://www.redhat.com/mailman/listinfo/et-mgmt-tools
>
>
>
>
> -- 
> Regards
> Dan
> ------------------------------------------------------------------------
>
> _______________________________________________
> et-mgmt-tools mailing list
> et-mgmt-tools@...
> https://www.redhat.com/mailman/listinfo/et-mgmt-tools

2	August 2009
102	July 2009
76	June 2009
54	May 2009
51	April 2009
100	March 2009
96	February 2009
108	January 2009
156	December 2008
91	November 2008
178	October 2008
124	September 2008
166	August 2008
283	July 2008
261	June 2008
198	May 2008
253	April 2008
208	March 2008
242	February 2008
123	January 2008
126	December 2007
214	November 2007
164	October 2007
212	September 2007
234	August 2007
188	July 2007
251	June 2007
153	May 2007
157	April 2007
257	March 2007
187	February 2007
39	January 2007

Re: Booting Hangs on "Trying to Load: pxelinux.cfg/default"

cobbler check >> #0: please create directory: -v

Re: Booting Hangs on "Trying to Load: pxelinux.cfg/default"

Re: Booting Hangs on "Trying to Load: pxelinux.cfg/default"

Re: Booting Hangs on "Trying to Load: pxelinux.cfg/default"

Re: Booting Hangs on "Trying to Load: pxelinux.cfg/default"

Re: ocaml-libvirt-0.4.0.1: Can't connect to Xen- Host

Re: Re: ocaml-libvirt-0.4.0.1: Can't connect to Xen- Host

Re: cobbler check >> #0: please create directory: -v

Re: Booting Hangs on "Trying to Load: pxelinux.cfg/default"

Mon	Tue	Wed	Thu	Fri	Sat	Sun

						1
2	3	4	5	6	7	8
9	10	11	12	13	14	15
16	17	18	19	20	21	22
23	24	25	26	27	28	29
30