Bug 468108 - IOError: [Errno 4] Interrupted system call
IOError: [Errno 4] Interrupted system call
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: anaconda (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Peter Jones
Release Test Team
Depends On:
  Show dependency treegraph
Reported: 2008-10-22 16:44 EDT by Brock Organ
Modified: 2008-10-23 11:53 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-10-23 11:53:47 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
updates.img to test with (100.00 KB, application/octet-stream)
2008-10-22 18:01 EDT, Peter Jones
no flags Details
updates.img to test with (100.00 KB, application/octet-stream)
2008-10-22 18:13 EDT, Peter Jones
no flags Details

  None (edit)
Description Brock Organ 2008-10-22 16:44:03 EDT
* RHEL5.3-Server-20081020.1 s390x
* regression from 5.2
* Anaconda / Arch / Installation using LPAR (native) account
* anaconda- , kernel-2.6.18-120.el5.s390x

During installation, a system call error using vnc occurs and the install aborts:

> The VNC server is now running.
> Please connect to mistymarie.z900.redhat.com:1 to begin the install...
> Press <enter> for a shell
> Starting graphical installation...
> pcilib: Cannot open /proc/bus/pci
> lspci: Cannot find any working access method.
> Traceback (most recent call last):
>   File "/usr/bin/anaconda", line 893, in ?
>     runVNC(vncpassword, vncconnecthost, vncconnectport, doStartupX11Actions)
>   File "/usr/bin/anaconda", line 405, in runVNC
>     sys.stdin.readline()
> IOError: [Errno 4] Interrupted system call
> The application 'anaconda' lost its connection to the display :1.0;
> most likely the X server was shut down or you killed/destroyed
> the application.
> Connection to mistymarie.z900.redhat.com closed.

The error has occurred the first time testing lpar installations on s390x; the error does not occur for the same installation using z/VM guests, I will try to reproduce the error again to see if it is consistent.
Comment 1 Peter Jones 2008-10-22 18:01:45 EDT
Created attachment 321218 [details]
updates.img to test with

Please test with the attached updates.img
Comment 2 Peter Jones 2008-10-22 18:13:42 EDT
Created attachment 321224 [details]
updates.img to test with

Actually, try this one instead.
Comment 3 Peter Jones 2008-10-22 18:21:29 EDT
What I expect is happening here is that vncserver is dying and we're getting a SIGCHILD while we're waiting for the command line input.  If so, the attached image will probably fix the traceback, but you won't be able to connect to vnc afterwards.
Comment 4 Adam Tkac 2008-10-23 11:37:36 EDT
We tried reproduce this bug with Brock but we are not successful. So this doesn't look like beta blocker candidate for me.
Comment 5 Brock Organ 2008-10-23 11:53:47 EDT
I'll re-open this issue if I can reliably reproduce it ...

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