Bug 566019 - socket.error: No such file or directory
Summary: socket.error: No such file or directory
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ales Kozumplik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-16 22:13 UTC by John Reiser
Modified: 2014-09-30 23:38 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-23 08:20:53 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John Reiser 2010-02-16 22:13:10 UTC
Description of problem: Install from DVD aborts before graphical splash screen, soon after "Running anconda 13.26, the Fedora system installer - please wait."


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

How reproducible: every time


Steps to Reproduce:
1. Compose DVD from rawhide of 2010-02-16 (Tuesday) using pungi.
2. Boot DVD for install, proceed through text menu questions until "Running anaconda 13.26, ..."
3.
  
Actual results: Traceback (most recent call last):
  File "/usr/bin/anaconda", line 766, in <module>
    import anaconda_log
  File "/usr/lib/anaconda/anaconda_log.py", line 134, in <module>
    logger = AnacondaLog()
  File "/usr/lib/anaconda/anaconda_log.py", line 75, in __init__
    self.forwardToSyslog(self.logger)
  File "/usr/lib/anaconda/anaconda_log.py", line 130, in fowardToSyslog
    logger.name)
  File "/usr/lib/anaconda/anaconda_log.py:, line 58, in __init__
    SysLogHandler.__init__(self, address, facility)
  File "/usr/lib64/python2.6/logging/handlers.py", line 710, in __init__
    self._connect_unixsodket(address)
  File "/usr/lib64/python2.6/logging/handlers.py", line 725, in _connect_unixsocket
    self.socket.connect(address)
  File "<string>", line 1, in connect
socket.error: [Errno 2] No such file or directory
install exited abnormally [1/1]

Expected results: graphical splash screen and rest of install


Additional info:

Comment 1 Chris Lumens 2010-02-16 22:24:15 UTC
There were two problems with rsyslog not starting up:  (1) we were missing a library, resulting in needing to rebuild anaconda.  (2) rsyslog was having its own problems starting.  Did you pull both into your rebuild?

Comment 2 John Reiser 2010-02-16 22:34:33 UTC
Ummm, I didn't do anything special except run pungi (and comment-out all the Language support lines.)  So, I'll run pungi again.  What's the recipe for the workarounds/fixes?

Comment 3 Chris Lumens 2010-02-17 16:11:07 UTC
Make sure you're getting anaconda-13.26 and the latest rsyslog package pulled into your tree.  I don't know which build of rsyslog fixed the problem, but both 4.4.2-5 and 4.4.2-4 look likely (http://koji.fedoraproject.org/koji/buildinfo?buildID=155653)

Comment 4 John Reiser 2010-02-17 20:57:16 UTC
I re-ran the pungi compose today, but the new DVD still gets the same error when booted for install.

The console definitely says "Running anaconda-13.26, the Fedora system installer."

I watched; the compose downloaded rsyslog-4.4.2-6.fc13.x86_64 during the yumdownload portion of buildinstall.

The DVD/isolinux/initrd.img after "gzip -d" and "cpio -i --make-directories" has 
  $ find . -name '*syslog*'
  ./sbin/rsyslogd
  ./etc/rsyslog.conf
  ./lib64/rsyslog
  $ ldd ./sbin/rsyslogd  # not virtualized, but ...
	linux-vdso.so.1 =>  (0x00007fff859ff000)
	libz.so.1 => /lib64/libz.so.1 (0x00000038fcc00000)
	libpthread.so.0 => /lib64/libpthread.so.0 (0x00000038fc000000)
	libdl.so.2 => /lib64/libdl.so.2 (0x00000038fc400000)
	librt.so.1 => /lib64/librt.so.1 (0x00000038fc800000)
	libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x0000003419800000)
	libc.so.6 => /lib64/libc.so.6 (0x00000038fb800000)
	/lib64/ld-linux-x86-64.so.2 (0x00000038fb400000)
and each of those DSOs [except for linux-vdso.so.1] is found in ./lib64.  I don't see where there is a library missing.

Comment 6 Ales Kozumplik 2010-02-18 07:31:35 UTC
Hi John,

you are seeing the exact same error as bug 564213, but with 13.26 this went away for other people. It looks like rsyslogd is still not starting on your machine:

1) Can you please share the failing .iso image with us? If that's too big then at least the initrd.img and install.img files.

2) Are you giving any extra command line parameters to the kernel?

Thank you,
Ales

Comment 7 John Reiser 2010-02-18 16:03:21 UTC
Hi Ales,

wget http://bitwagon.com/initrd.img    #  30380814 bytes
wget http://bitwagon.com/install.img   # 133619712 bytes
It will take about 3 hours of uploading for the full DVD, so please try those two .img first.  I've verified that my DVD still fails in the same way, and that those URLs give the correct files after a round-trip across the net.

Comment 8 John Reiser 2010-02-18 16:05:41 UTC
And 2): I just type <Enter> ["Install or upgrade ..."] at the boot screen, so there are no extra command line parameters to the kernel.

Comment 9 John Reiser 2010-02-22 02:53:31 UTC
anaconda-13.28-1.fc13.x86_64 lists
  
  usr/$LIBDIR/rsyslog

in the $KEEPFILE as a directory to be copied over  (/usr/lib/anaconda-runtime/upd-instroot line 499) but the library actually lives in

  /$LIBDIR/rsyslog

without the "/usr".

Comment 10 Ales Kozumplik 2010-02-22 08:10:22 UTC
Hi John,

You are mentioning the exact error that was fixed with bug #564213 and released in anaconda-13.26.

This is weird, I think your anaconda-13.28 is not the real anaconda-13.28: I used yumdownloader with a rawhide repo like this this morning:

yumdownloader --enablerepo=rawhide anaconda

What it gave me was anaconda-13.28-1.fc14.i686.rpm. I unpacked that and looked at upd-instroot and it is in the fixed version already, of course.

I also downloaded the latest f13 version of anaconda from one of the official fedora mirrors here: 
http://ftp.linux.cz/pub/linux/fedora/linux/development/13/x86_64/os/Packages/

That's also fixed. Maybe you've got a customized anaconda version where somebody forgot to merge the latest patches? (but still release new versions... weird).

Going to close this as not a bug in a couple of days unless something new comes into light.

Ales

Comment 11 John Reiser 2010-02-22 21:47:59 UTC
The problem is caused by bug 567411, "/tmp contaminates the output DVD and CDs of pungi+buildinstall".

Comment 12 Ales Kozumplik 2010-02-23 08:20:53 UTC
Okay, I'm closing this one now.


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