Bug 83196 - firstboot had gethostbyaddr() errors
firstboot had gethostbyaddr() errors
Status: CLOSED DUPLICATE of bug 82061
Product: Red Hat Linux
Classification: Retired
Component: firstboot (Show other bugs)
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Brent Fox
Depends On:
  Show dependency treegraph
Reported: 2003-01-30 23:27 EST by Miroslav Krajca
Modified: 2008-05-01 11:38 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:51:31 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Miroslav Krajca 2003-01-30 23:27:25 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030115

Description of problem:
Traceback (most recent call last): 
  File "/usr/share/firstboot/firstbootWindow.py", line 153, in __init__ 
    vbox, eventbox = module.launch() 
  File "/usr/share/firstboot/modules/date.py", line 75, in launch 
  File "/usr/share/firstboot/modules/date.py", line 64, in setupScreen 
    self.datePage = date_gui.datePage(self.dateBackend) 
  File "/usr/share/redhat-config-date/date_gui.py", line 171, in __init__ 
    ntpServer = socket.gethostbyaddr(ntpServerIP)[0] 
TypeError: gethostbyaddr() argument 1 must be string, not None

Machine was booted in SMP kernel.
Type of machine:  Dual AMD Athlon MP
                  Tyan S2466-4M motherboard
                  1 gig Ram

Version-Release number of selected component (if applicable):

How reproducible:
Didn't try

Steps to Reproduce:
1. this only occured during the initial install.

Additional info:

firstboot continued as normal afterwards
Comment 1 Bill Nottingham 2003-01-31 00:10:09 EST

*** This bug has been marked as a duplicate of 82061 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:51:31 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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