<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2964" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=132572000-17052007><FONT face=Arial
color=#0000ff size=2>This is exactly what happens when you have a portfast issue
on your switch. It appears your problem was infrastructure after
all.</FONT></SPAN><BR></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> kickstart-list-bounces@redhat.com
[mailto:kickstart-list-bounces@redhat.com] <B>On Behalf Of
</B>SSTinsley@upsfreight.com<BR><B>Sent:</B> Wednesday, May 16, 2007 2:19
PM<BR><B>To:</B> Discussion list about Kickstart<BR><B>Subject:</B> RE: Unable
to get any http requests:Unable toretrieve netstg2.imgfile<BR></FONT><BR></DIV>
<DIV></DIV><BR><FONT face=sans-serif size=2>I finally gave up and copied my
ks.cfg to a CDROM and changed my pxelinux.cfg to load the KS cfg file from CD
the drive. Anaconda could read the ks.cfg. The ks.cfg file pointed to a RedHat
release image on an NFS server. However, Anaconda said it could not read the NFS
release and displayed a screen to input the corrected NFS image information. The
defaults from the KS cfg file where displayed as defaults. I entered nothing
different and hit OK. Anaconda was able to now mount the RHEL image using the
same information as was specified in the KS cfg file. I think Anaconda has a few
bugs in handling network interfaces and protocols. I would love to figure out a
fix, but I got to get some servers installed. </FONT><BR><BR><FONT
face=sans-serif size=2>I'll keep and eye out for your posts to see if you have
any better luck. I still have not heard back from Redhat. So much for paid
support. </FONT><BR><BR><FONT face=sans-serif size=2>Get me back on
Solaris!!</FONT> <BR><BR><FONT size=2><TT>kickstart-list-bounces@redhat.com
wrote on 05/16/2007 11:03:13 AM:<BR><BR>> I feel your pain.<BR>> I'll let
you know if I find anything.<BR>> Thanks<BR>> <BR>> -Mukarram.<BR>>
<BR>> -----Original Message-----<BR>> From:
kickstart-list-bounces@redhat.com<BR>>
[mailto:kickstart-list-bounces@redhat.com] On Behalf Of<BR>>
SSTinsley@upsfreight.com<BR>> Sent: Wednesday, May 16, 2007 6:00 AM<BR>>
To: Discussion list about Kickstart<BR>> Subject: RE: Unable to get any http
requests:Unable toretrieve<BR>> netstg2.imgfile<BR>> <BR>> <BR>> I
have been fighting almost the identical problem. See the thread entitled
<BR>> <BR>> "Re: Kickstart via PXE/NFS" <BR>> <BR>> After the kernel
is loaded via configuration set up in the pxelinux config<BR>> file, the
<BR>> network will not come up and the ks.cfg file can then not be loaded. I
get<BR>> the <BR>> network config screen asking to use DHCP or to enter
static info for setup<BR>> of eth0. It <BR>> has really bee frustrating. I
finally just placed my ks.cfg on CDROM and was<BR>> able <BR>> to get the
rest of the PXE auto install to complete. <BR>> <BR>> If you get a
resolution, I will be very interested. I have had a case open<BR>> with
<BR>> RedHat for 2 days waiting for a response. <BR>> <BR>>
kickstart-list-bounces@redhat.com wrote on 05/16/2007 04:38:30 AM:<BR>>
<BR>> > Nope. Nothing in the error logs.<BR>> > <BR>> > In my
troubleshooting, this is what I've found...<BR>> > <BR>> > When I
remove the ks=http://<ServerIP>/<PATH>/ks.cfg from my
"default"<BR>> file<BR>> > Client PXE boots, shows menu and loads
vmlinuz/initrd.<BR>> > Then it shows up the Language selection. No
luck.<BR>> > However, when I change my default file to read:
ks=/<PATH>/ks.cfg,<BR>> > Client PXE boots, shows menu and loads
vmlinuz/initrd.<BR>> > Then it gives the error "Error opening kickstart
file (null): Bad address"<BR>> > I do some more research (see link
below)<BR>> >
http://linux.derkeiler.com/Mailing-Lists/Fedora/2004-06/5939.html<BR>> >
and modified the ks.cfg file...add more network parameters like so:<BR>> >
network --device=eth0 --bootproto=static --ip=171.67.39.139<BR>> >
--netmask=255.255.255.224 --gateway=171.67.39.129
--nameserver=171.64.7.77<BR>> > --hostname=as-test.stanford.edu<BR>>
> Still no luck.<BR>> > I then changed my --device=eth0 to
--device=link and then to<BR>> > --device=eth1...still no luck. Then
put it back to --device=eth0.<BR>> > Then I change my PATH from:<BR>>
> url --url http://171.67.39.130/ENT_LINUX_64/Enterprise<BR>> >
to<BR>> > url --url http://171.67.39.130/ENT_LINUX_64<BR>> > Still
no luck.<BR>> > Again nothing in the http logs.<BR>> > <BR>> >
It looks like the installer is reading the ks.cfg file silently since it<BR>>
> complained that it couldn't find it from the default file when I
didn't<BR>> > specify the http://<servername>. <BR>> >
Can I figure out what is reading and stopping. Is there a way to look
at<BR>> > the kickstart logs (If there is any...I haven't seen
one).<BR>> > <BR>> > I tried to create logging as well in my ks.cfg
file...no luck...no output:<BR>> > %pre --log=/tmp/my-pre-log<BR>> >
echo 'Hello, World!'<BR>> > <BR>> > Here is my directory/file
setup:<BR>> > <BR>> > TFTP:<BR>> > <BR>> >
/tftpboot/linux-install/pxelinux.cfg<BR>> > [root@as-kickball
pxelinux.cfg]# ls<BR>> > default pxeos.xml<BR>> > <BR>>
> [root@as-kickball linux-install]# ls -lR<BR>> > .:<BR>> > total
32<BR>> > drwxr-xr-x 2 root root 4096 May 14 00:31
ENT_LINUX_32<BR>> > drwxr-xr-x 2 root root 4096 May 16 00:30
ENT_LINUX_64<BR>> > drwxr-xr-x 2 root root 4096 May 14 21:09
msgs<BR>> > -rwxr-xr-x 1 root root 12952 Oct 24 2006
pxelinux.0<BR>> > drwxr-xr-x 2 root root 4096 May 16 00:25
pxelinux.cfg<BR>> > <BR>> > ./ENT_LINUX_32:<BR>> > total
0<BR>> > <BR>> > ./ENT_LINUX_64:<BR>> > total 5984<BR>>
> -rwxr-xr-x 1 root root 4310479 May 14 15:29 initrd.img<BR>> >
-rwxr-xr-x 1 root root 85 May 16 00:30 ks.cfg<BR>>
> -rwxr-xr-x 1 root root 1792835 May 14 15:29 vmlinuz<BR>> >
<BR>> > ./msgs:<BR>> > total 24<BR>> > -rwxr-xr-x 1 root
root 534 May 14 21:00 boot.msg<BR>> > -rwxr-xr-x 1 root root 668 Oct
24 2006 expert.msg<BR>> > -rwxr-xr-x 1 root root 871 Oct 24
2006 general.msg<BR>> > -rwxr-xr-x 1 root root 860 Oct 24
2006 param.msg<BR>> > -rwxr-xr-x 1 root root 530 Oct 24
2006 rescue.msg<BR>> > -rwxr-xr-x 1 root root 545 Oct 24
2006 snake.msg<BR>> > <BR>> > ./pxelinux.cfg:<BR>> >
total 20<BR>> > -rwxr-xr-x 1 root root 511 May 16 00:25
default<BR>> > -rwxr-xr-x 1 root root 511 May 15 23:34
default.bak<BR>> > -rwxr-xr-x 1 root root 461 May 15 14:44
default.dhcp<BR>> > -rwxr-xr-x 1 root root 573 May 15 13:30
default.staticIP<BR>> > -rwxr-xr-x 1 root root 42 May 14 16:28
pxeos.xml<BR>> > <BR>> > My HTTP directory:<BR>> > <BR>>
> [root@as-kickball /]# ls -lart /var/www/html<BR>> > total 24<BR>>
> drwxr-xr-x 8 root root 4096 Mar 21 19:17 ..<BR>> > drwxr-xr-x
4 root root 4096 May 14 00:35 .<BR>> > drwxr-xr-x 3 root root
4096 May 14 00:40 ENT_LINUX_32<BR>> > drwxr-xr-x 3 root root 4096
May 15 15:49 ENT_LINUX_64<BR>> > <BR>> > [root@as-kickball /]# ls
-lart /var/www/html/ENT_LINUX_64/Enterprise/<BR>> > total 136<BR>> >
drwxr-xr-x 2 root root 114688 Feb 24 13:15 RPMS<BR>> > drwxr-xr-x
2 root root 4096 May 14 15:53 base<BR>> > -rwxr-xr-x 1
root root 1386 May 15 15:05 ks_ent_linux_64.cfg<BR>> > drwxr-xr-x
3 root root 4096 May 15 15:49 ..<BR>> > -rw-r--r-- 1
root root 1242 May 16 01:08 ks.cfg<BR>> > drwxr-xr-x 4 root
root 4096 May 16 01:08 .<BR>> > <BR>> > I am at a loss now.
I am sure it's something simple as it mostly is.<BR>> > Help is
appreciated.<BR>> > <BR>> > Tomorrow, I'll tell my networking guy to
enable "spanning tree" so I could<BR>> > use dhcp and get the static crap
out of my way.<BR>> > Will let you know more.<BR>> > <BR>> >
-Mukarram.<BR>> > <BR>> > <BR>> > -----Original
Message-----<BR>> > From: kickstart-list-bounces@redhat.com<BR>> >
[mailto:kickstart-list-bounces@redhat.com] On Behalf Of Mike Jennings<BR>>
> Sent: Tuesday, May 15, 2007 8:47 PM<BR>> > To: Discussion list about
Kickstart<BR>> > Subject: Re: Unable to get any http requests:Unable to
retreive<BR>> > netstg2.imgfile<BR>> > <BR>> > Is the apache
log showing any 404 errors? My stupid screwups are <BR>> >
always shown in the error log when I typo something.<BR>> > <BR>> >
Mike<BR>> > <BR>> > <BR>> > <BR>> > On May 15, 2007, at
10:39 PM, Mukarram Syed wrote:<BR>> > <BR>> > ><BR>> > >
Colin,<BR>> > > I changed it from ksdevice=eth0 to
ksdevice=link<BR>> > ><BR>> > > Sorry, that didn't
help.<BR>> > ><BR>> > > Wonder what else could it be, why is
it not connecting to the http <BR>> > > server?<BR>> > >
I don't see any traffic in tcpdump after pxeboot.<BR>> > ><BR>> >
> -Mukarram.<BR>> > ><BR>> > > -----Original
Message-----<BR>> > > From: kickstart-list-bounces@redhat.com<BR>>
> > [mailto:kickstart-list-bounces@redhat.com] On Behalf Of Coe, Colin
<BR>> > > C. (Unix<BR>> > > Engineer)<BR>> > >
Sent: Tuesday, May 15, 2007 5:56 PM<BR>> > > To: Discussion list about
Kickstart<BR>> > > Subject: RE: Unable to get any http
requests:Unabletoretreive<BR>> > > netstg2.imgfile<BR>> >
><BR>> > ><BR>> > > Try changing 'ksdevice=eth0' to
'ksdevice=link'. With 2.6 kernels, <BR>> > > the<BR>>
> > kernel's idea of what eth0 and eth1 are often differs from the BIOS/
<BR>> > > PXE<BR>> > > stack.<BR>> > ><BR>> >
> CC<BR>> > ><BR>> > >> -----Original
Message-----<BR>> > >> From:
kickstart-list-bounces@redhat.com<BR>> > >>
[mailto:kickstart-list-bounces@redhat.com] On Behalf Of Mukarram Syed<BR>>
> >> Sent: Wednesday, 16 May 2007 8:42 AM<BR>> > >> To:
'Discussion list about Kickstart'<BR>> > >> Subject: RE: Unable to
get any http requests:<BR>> > >> Unabletoretreive
netstg2.imgfile<BR>> > >><BR>> > >> John,<BR>> >
>> Sorry...just to make things clear.<BR>> > >> eth0 works to
get the dhcp/tftp request and eth1 does not.<BR>> > >> However, I
tried using both is what I meant.<BR>> > >><BR>> > >> We
have a problem with dhcp, the networking folks here did<BR>> > >>
not enable "spanning tree" on the switch ports, until that<BR>> > >>
happens I am using static<BR>> > >> ip. I double checked the
syntax etc.<BR>> > >><BR>> > >> Thanks<BR>> >
>> -Mukarram.<BR>> > >><BR>> > >> -----Original
Message-----<BR>> > >> From:
kickstart-list-bounces@redhat.com<BR>> > >>
[mailto:kickstart-list-bounces@redhat.com] On Behalf Of John<BR>> >
>> Summerfield<BR>> > >> Sent: Tuesday, May 15, 2007 5:32
PM<BR>> > >> To: Discussion list about Kickstart<BR>> >
>> Subject: Re: Unable to get any http requests: Unable<BR>> >
>> toretreive netstg2.imgfile<BR>> > >><BR>> > >>
Mukarram Syed wrote:<BR>> > >>> Thanks Colin for the quick
response<BR>> > >>><BR>> > >>><BR>> >
>>><BR>> > >>> Yes. It does have. It's a
Dell PE2950.<BR>> > >>><BR>> > >>><BR>> >
>>><BR>> > >>> I have already tried that option as
well.<BR>> > >>><BR>> > >>> I tried both
ksdevice=eth0 and ksdevice=eth1 and they don't work.<BR>> >
>>><BR>> > >><BR>> > >> If you can connect all
network interfaces, that might help,<BR>> > >> because it then
doesn't matter whether either one or both is used.<BR>> > >><BR>>
> >> If you run arpwatch that will report on which interfaces
are<BR>> > >> used (by mac address and IP).<BR>> >
>><BR>> > >> More below...<BR>> > >><BR>> >
>>><BR>> > >>><BR>> > >>>
-Mukarram.<BR>> > >>><BR>> > >>><BR>> >
>>><BR>> > >>><BR>> > >>><BR>> >
>>> _____<BR>> > >>><BR>> > >>>
From: kickstart-list-bounces@redhat.com<BR>> > >>>
[mailto:kickstart-list-bounces@redhat.com] On Behalf Of<BR>> > >>
Coe, Colin C.<BR>> > >> (Unix<BR>> > >>>
Engineer)<BR>> > >>> Sent: Tuesday, May 15, 2007 4:52 PM<BR>>
> >>> To: Discussion list about Kickstart<BR>> > >>>
Subject: RE: Unable to get any http requests: Unable to retreive<BR>> >
>>> netstg2.imgfile<BR>> > >>><BR>> >
>>><BR>> > >>><BR>> > >>> Does the
machine you're on have multiple Ethernet<BR>> > >> interfaces?
If so,<BR>> > >>> what you may find is adding
'ksdevice=link' will assist.<BR>> > >>><BR>> >
>>><BR>> > >>><BR>> > >>> CC<BR>> >
>>><BR>> > >>><BR>> > >>><BR>> >
>>><BR>> > >>> _____<BR>> >
>>><BR>> > >>><BR>> > >>> From:
kickstart-list-bounces@redhat.com<BR>> > >>>
[mailto:kickstart-list-bounces@redhat.com] On Behalf Of<BR>> > >>
Mukarram Syed<BR>> > >>> Sent: Wednesday, 16 May 2007 7:50
AM<BR>> > >>> To: kickstart-list@redhat.com<BR>> >
>>> Subject: Unable to get any http requests: Unable to
retreive<BR>> > >>> netstg2.img file<BR>> >
>>><BR>> > >>> Hi<BR>> > >>><BR>> >
>>> I am sure there is some information regarding my request, but I
am<BR>> > >>> unable<BR>> > >> to<BR>> >
>>> find it, hence the post.<BR>> > >>><BR>> >
>>><BR>> > >>><BR>> > >>> I configured my
kickstart server using http.<BR>> > >>><BR>> > >>>
I am able to pxeboot the client, but my client is not able<BR>> > >>
to get the<BR>> > >>> netstg2.img file from the server.<BR>>
> >>><BR>> > >>> I am able to http into my
netstg2.img directory from a web browser<BR>> > >>> from another
server in the same subnet successfully.<BR>> > >>><BR>> >
>>><BR>> > >>><BR>> > >>> Also I tried to
put in a boot cdrom and run the following:<BR>> > >>><BR>>
> >>> Linux
ks=http://<ServerIP>/ENT_LINUX_64/Enterprise/ks.cfg<BR>> >
>>> ip=<ClientIP><BR>> > >>>
netmask=255.255.255.224 gateway=<GatewayIP><BR>> > >><BR>>
> >><BR>> > >> I have never used static IP for ks, I alway
configure<BR>> > >> everything I can with dhcp. However, I do know
that that's<BR>> > >> not the format the kernel expects for the ip
parameter. Check<BR>> > >> your documentation, if I were writing a
script tp parse ip=<BR>> > >> then I'd conform to the existing
standards (that is, the way<BR>> > >> the kernel expects it), and
that's what works with Ubuntu.<BR>> > >><BR>> >
>><BR>> > >><BR>> > >>><BR>> >
>>><BR>> > >>><BR>> > >>> Still no luck.
It goes straight to the cd installer.<BR>> > >>><BR>> >
>>><BR>> > >>><BR>> > >>> I tried to
tcpdump the traffic on the MAC address of the client, it<BR>> > >>
outputs<BR>> > >>> the tftp information and after that it
stops.<BR>> > >>><BR>> > >>> I don't see any http
traffic coming from the client.<BR>> > >><BR>> > >>
That's fairly consistent with you specifying ip= incorrectly.<BR>> >
>><BR>> > >> btw, if you're using PXE, the why are you trying
to spectify<BR>> > >> static IP info?<BR>> > >><BR>>
> >> btw, as I recall, pxelinux has an option to pass on the IP<BR>>
> >> address info it gets in the proper format for the kernel to
parse.<BR>> > >><BR>> > >><BR>> >
>>><BR>> > >>><BR>> > >>><BR>> >
>>> I'd appreciate some help in this regard.<BR>> >
>>><BR>> > >>> I've spent all day trying to troubleshoot
this but no luck.<BR>> > >>><BR>> > >>><BR>>
> >>><BR>> > >>> Thanks Much<BR>> >
>>><BR>> > >>><BR>> > >>><BR>> >
>>><BR>> > >>><BR>> > >>> Mukarram
Syed<BR>> > >>><BR>> > >>> Unix Systems
Administrator,<BR>> > >>><BR>> > >>> Stanford
University.<BR>> > >>><BR>> > >>><BR>> >
>>><BR>> > >>><BR>> > >>> NOTICE: This
email and any attachments are confidential.<BR>> > >>> They may
contain legally privileged information or<BR>> > >>> copyright
material. You must not read, copy, use or<BR>> > >>> disclose
them without authorisation. If you are not an<BR>> > >>> intended
recipient, please contact us at once by return<BR>> > >>> email
and then delete both messages and all attachments.<BR>> >
>>><BR>> > >>><BR>> > >>><BR>> >
>>><BR>> > >>
--------------------------------------------------------------<BR>> >
>> ----------<BR>> > >>><BR>> > >>>
_______________________________________________<BR>> > >>>
Kickstart-list mailing list<BR>> > >>>
Kickstart-list@redhat.com<BR>> > >>>
https://www.redhat.com/mailman/listinfo/kickstart-list<BR>> >
>><BR>> > >><BR>> > >> -- <BR>> >
>><BR>> > >> Cheers<BR>> > >> John<BR>> >
>><BR>> > >> -- spambait<BR>> > >>
1aaaaaaa@coco.merseine.nu Z1aaaaaaa@coco.merseine.nu<BR>> >
>><BR>> > >> Please do not reply off-list<BR>> >
>><BR>> > >>
_______________________________________________<BR>> > >>
Kickstart-list mailing list<BR>> > >>
Kickstart-list@redhat.com<BR>> > >>
https://www.redhat.com/mailman/listinfo/kickstart-list<BR>> >
>><BR>> > >>
_______________________________________________<BR>> > >>
Kickstart-list mailing list<BR>> > >>
Kickstart-list@redhat.com<BR>> > >>
https://www.redhat.com/mailman/listinfo/kickstart-list<BR>> >
>><BR>> > ><BR>> > > NOTICE: This email and any
attachments are confidential.<BR>> > > They may contain legally
privileged information or<BR>> > > copyright material. You must not
read, copy, use or<BR>> > > disclose them without authorisation. If you
are not an<BR>> > > intended recipient, please contact us at once by
return<BR>> > > email and then delete both messages and all
attachments.<BR>> > ><BR>> > >
_______________________________________________<BR>> > > Kickstart-list
mailing list<BR>> > > Kickstart-list@redhat.com<BR>> > >
https://www.redhat.com/mailman/listinfo/kickstart-list<BR>> > ><BR>>
> > _______________________________________________<BR>> > >
Kickstart-list mailing list<BR>> > > Kickstart-list@redhat.com<BR>>
> > https://www.redhat.com/mailman/listinfo/kickstart-list<BR>> >
<BR>> > _______________________________________________<BR>> >
Kickstart-list mailing list<BR>> > Kickstart-list@redhat.com<BR>> >
https://www.redhat.com/mailman/listinfo/kickstart-list<BR>> > <BR>>
> _______________________________________________<BR>> > Kickstart-list
mailing list<BR>> > Kickstart-list@redhat.com<BR>> >
https://www.redhat.com/mailman/listinfo/kickstart-list<BR>> <BR>> NOTE:
THIS DOCUMENT MAY CONTAIN CONFIDENTIAL AND NONPUBLIC INFORMATION. IT<BR>> IS
INTENDED ONLY FOR THE USE OF THE INDIVIDUAL(S) OR ENTITY(IES) NAMED<BR>>
ABOVE, AND OTHERS SPECIFICALLY AUTHORIZED TO RECEIVE IT. If you are not
the<BR>> intended recipient of this document, you are notified that any
review,<BR>> dissemination, distribution or copying of this communication is
prohibited.<BR>> If you have received this communication in error, please
notify me<BR>> immediately by return email, delete the electronic message and
destroy any<BR>> printed copies. Thank you for your cooperation.<BR>>
<BR>> <BR>> _______________________________________________<BR>>
Kickstart-list mailing list<BR>> Kickstart-list@redhat.com<BR>>
https://www.redhat.com/mailman/listinfo/kickstart-list<BR></TT></FONT>
<DIV>NOTE: THIS DOCUMENT MAY CONTAIN CONFIDENTIAL AND NONPUBLIC INFORMATION. IT
IS INTENDED ONLY FOR THE USE OF THE INDIVIDUAL(S) OR ENTITY(IES) NAMED ABOVE,
AND OTHERS SPECIFICALLY AUTHORIZED TO RECEIVE IT. If you are not the intended
recipient of this document, you are notified that any review, dissemination,
distribution or copying of this communication is prohibited. If you have
received this communication in error, please notify me immediately by return
email, delete the electronic message and destroy any printed copies. Thank you
for your cooperation.<BR></DIV></BODY></HTML>