Bug 17534 - pyton error in the installation script : "bad magic in header"
Summary: pyton error in the installation script : "bad magic in header"
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 6.2
Hardware: i586
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2000-09-15 06:00 UTC by Geert Jordaens
Modified: 2008-05-01 15:37 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2000-10-09 18:53:45 UTC
Embargoed:


Attachments (Terms of Use)

Description Geert Jordaens 2000-09-15 06:00:08 UTC
When trying to install a RH6.2 via bootnet.img + updates 20000419. I get a
pyton error in the installation script : "bad magic in header"

my system : P133
SCSI controler : AHA 2940 UW
SCSI Disk : QUANTUM VIKKING II 4.5GB
Ethernet adapter : NE 2000 compatible


    def readHeaders(self):

        connected = 0
        while not connected:
            try:
                url = urllib.urlopen(self.baseUrl + "/RedHat/base/hdlist")
            except IOError, (errnum, msg):
#                print "IOError occurred, trying again"
                time.sleep(5)
            else:
                connected = 1
                
	raw = url.read(16)
	hl = []
	while (raw):
	    info = struct.unpack("iiii", raw)
	    magic1 = socket.ntohl(info[0]) & 0xffffffff
	    if (magic1 != 0x8eade801 or info[1]):
		raise TypeError, "bad magic in header"

	    il = socket.ntohl(info[2])
	    dl = socket.ntohl(info[3])
	    totalSize = il * 16 + dl;
	    hdrString = raw[8:] + url.read(totalSize)
	    hdr = rpm.headerLoad(hdrString)
	    hl.append(hdr)

	    raw = url.read(16)

	return HeaderList(hl)

Comment 1 Geert Jordaens 2000-09-20 08:28:14 UTC
This error occured as I was trying to install via HTTP. I had to instal via 
HTTP because it doesn't work via FTP. The mirrorsite I've used was :
mirrors.pandora.be/mirrors/ftp.redhat.com. 
It is possible that the mirrors site needs a user name and password and 
responds with on of the folowing codes : HTTP response codes: 301, 302 or 401. 


Comment 2 Michael Fulbright 2000-10-09 18:53:41 UTC
This seems to be related to the mirror site you were attempting to use - we have
not had problems with either FTP or HTTP base installs in our testing.


Note You need to log in before you can comment on or make changes to this bug.