14 Replies Latest reply on Oct 5, 2010 4:00 AM by Javier Herraiz

    Unable to read header list.

    Girish Tapare

      Hello,

       

      I am using BladeLogic 7.6. I am trying to deploy RHL AS4 OS through BladeLogic. While in between of the process I face some problem,

       

      1) I have created the System package for Linux AS4 and in Provisioning manager(Imported console) I am selecting the same. But still I have to manually select the language as well as host, from where I am trying to deploy OS. If I need to fill data manually then what is the use of system package.

       

      2) After I select language and host, it asks for root password. Then it shows a dilogbox saying "Reading Package Information" and finally after some time it show me an error"Unable to read header list. This may be due to a missing file or bad media". If I try to install the OS through the same DVD then it boots properly as well as it successfully install the OS.

       

      Thanks in Advance.

       

      Giri

        • 1. Re: Unable to read header list.
          Bill Robinson

          There is something wrong w/ your system package definition or there is some problem reaching your data store server.

           

          Can you post the kickstart file section of the system package, and give us an idea of your data store configuration (web server config, file server location, location of the redhat files, etc)

          • 2. Re: Unable to read header list.

            It seems you don't even be able to get tje kickstart file thru the network. This may be because your based imaged loaded fromt tftp doesn't contain the right driver for your network card.

            • 3. Re: Unable to read header list.
              Girish Tapare

              Hello Bill,

               

              I found 4 files in kickstart folder(pxelinux.cfg) as below,

               

              filne name=AC100501


              # Perform a local boot by default
              default inst

               

              default64 linux64

               

              # Always prompt
              prompt 1

               

              # Display the bootup message
              display pxeboot.msg

               

              # Boot automatically after 300 seconds
              timeout 1

               

              label local
              localboot 0
              # The rest of this file is machine-generated

               

              label linux64
              kernel Boot_GUI\pxeboot.0
              append initrd=none
              label inst
              kernel Boot_GUI\pxeboot.0
              append initrd=none

               


              filne name=AC100502


              # Perform a local boot by default
              default inst

               

              default64 linux64

               

              # Always prompt
              prompt 1

               

              # Display the bootup message
              display pxeboot.msg

               

              # Boot automatically after 300 seconds
              timeout 1

               

              label local
              localboot 0
              # The rest of this file is machine-generated

               

              label linux64
              kernel Boot_GUI\pxeboot.0
              append initrd=none
              label inst
              kernel Boot_GUI\pxeboot.0
              append initrd=none



              filne name=AC100503


              # Perform a local boot by default
              default inst


              default64 linux64

               

              # Always prompt
              prompt 1

               

              # Display the bootup message
              display pxeboot.msg

               

              # Boot automatically after 300 seconds
              timeout 1

               

              label local
              localboot 0
              # The rest of this file is machine-generated

               

              label linux64
              kernel vmlinuz-4
              append initrd=initrd-4.img lang=en_US devfs=nomount ramdisk_size=16384  ks=http://172.16.5.22/pxestore/00-0C-29-56-85-23 ksdevice=eth0
              label inst
              kernel vmlinuz-4
              append initrd=initrd-4.img lang=en_US devfs=nomount ramdisk_size=16384  ks=http://172.16.5.22/pxestore/00-0C-29-56-85-23 ksdevice=eth0

               

               

              filne name=AC100504


              # Perform a local boot by default
              default inst

               

              default64 linux64

               

              # Always prompt
              prompt 1

               

              # Display the bootup message
              display pxeboot.msg

               

              # Boot automatically after 300 seconds
              timeout 1

               

              label local
              localboot 0
              # The rest of this file is machine-generated

               

              label linux64
              kernel Boot_GUI\pxeboot.0
              append initrd=none
              label inst
              kernel Boot_GUI\pxeboot.0
              append initrd=none

               

              And This is the screen shot for datastore configuration,

              datastore.bmp

              • 4. Re: Unable to read header list.
                Saurabh Kashikar

                Giri,

                 

                Do you see a file getting generated under tftproot/X86PC/pxelinux with name as the mac address of device, during the course of the provisioning process..Thats the kickstart file.

                 

                Remember that this file remains only during the course of the provisioning job and is gone after that..

                • 5. Re: Unable to read header list.
                  Bill Robinson

                  The kickstart file with the name of the mac address will be in ??FULL_PATH??\<MAC> and accessible via http://172.16.5.22/pxestore/00-0C-29-56-85-23

                   

                  for example and not in the tftproot.

                   

                  the files under tftproot/X86PC/pxelinux tell the target system which boot image to pull down.

                   

                  i think based on what you said, tftp is working ok because you are getting into the redhat installer, which is loaded w/ the vmlinuz and initrd.img files under the tftproot directory.

                   

                  so i think your issue is w/ the kickstart file, either the target can't read it, or there's an error in it.

                  • 6. Re: Unable to read header list.
                    Girish Tapare

                    Hi Sourabh,

                     

                    I observer that the file with mac name would be created after selecting the system package and the location of the datastore, in "pxestore" folder but not in  "tftproot/X86PC/pxelinux" folder during the course of the provisioning job.

                     

                    Even I checked the tftp server log it says the same error msg with "File not found : C:\Program Files\BMC BladeLogic\PXE\tftproot\X86PC\pxelinux\pxelinux.cfg\01-00-0c-29-56-85-23". But here I observe that before the filename(mac) "01-" has been added.

                     

                    Thanks.

                    • 7. Re: Unable to read header list.
                      Bill Robinson

                      Read this about how pxelinux works:

                       

                      http://syslinux.zytor.com/wiki/index.php/PXELINUX

                       

                      the error in the tftp log should be normal.  The fact that you are getting an error in the RedHat Linux installer means you are getting past a problem w/ the tftp server.

                      • 8. Re: Unable to read header list.
                        Girish Tapare

                        Hi Bill,

                         

                        As you said in last post, that kickstart file should be accessible via http from this location "http://172.16.5.22/pxestore/00-0C-29-56-85-23". But if I try to access the kickstart file from browser I am not able to download that file, May be this is not an known file format that's why it show an error "unable to read file"

                         

                        And this file contains the information related to system package that I had defined in BladeLogic. But I am not able to download that file that's why I have to select the language, keyboard etc manually.

                         

                         

                        Thanks.

                        • 9. Re: Unable to read header list.
                          Saurabh Kashikar

                          Giri,

                           

                          Can you please confirm whether you are hosting datastore on Windows/Linux and have you accordingly configured http access to the datastore folder or not..In BladeLogic Linux provisioning methodology, the kickstart is downloaded from datastore using wget and so you need to give http access to the folder.

                           

                          Do you have the kickstart file "00-0C-29-56-85-23" created in pxestore folder in the due course of the provisioning job??

                          • 10. Re: Unable to read header list.
                            Girish Tapare

                            Hi Sourabh,

                             

                            My datastore is reside on windows machine. And this datastore folder having windows access as well as http access.

                             

                            My kickstart file "00-0C-29-56-85-23" is reside under pxestore. If I try to download the other file like .img files or other file it will be downloaded.

                             

                            Thanks.

                            • 11. Re: Unable to read header list.

                              With the IIS admin, change the registered MIME types to all file as follow and it should work:

                               

                              4-22-2010 10-01-24 AM.png

                              • 12. Re: Unable to read header list.
                                Girish Tapare

                                Thanks Fred it wored out for "header list reading".

                                But One problem remain same The system package that I had created was not working ie. I have to manually enter the details releted keyboard, disk partition etc.

                                 

                                Once again Thanks.

                                • 13. Re: Unable to read header list.
                                  Bill Robinson

                                  can you get to that kickstart file w/ a web browser?

                                   

                                  if that is working, and you can see in the IIS logs that the file is being set to the target system, then we need to look at the kickstart file itself.

                                  • 14. Re: Unable to read header list.
                                    Javier Herraiz

                                    Thanks!!! It solve my problem!!!!!