Booting over http on a ppc64 machine did not work the error message in VNC is attached. The error message was: "Unable to read package metadata". The logs from the webserber do not show any access to the files except the intial loading of stage2.img: 10.32.5.2 - - [21/Jun/2006:12:07:35 +0200] "GET /fc6test1/Fedora/base/updates.img HTTP/1.0" 404 303 "-" "anaconda/11.1.0.45" 10.32.5.2 - - [21/Jun/2006:12:07:35 +0200] "GET /fc6test1/disc1/Fedora/base/updates.img HTTP/1.0" 404 309 "-" "anaconda/11.1.0.45" 10.32.5.2 - - [21/Jun/2006:12:07:35 +0200] "GET /fc6test1/Fedora/base/product.img HTTP/1.0" 404 303 "-" "anaconda/11.1.0.45" 10.32.5.2 - - [21/Jun/2006:12:07:35 +0200] "GET /fc6test1/disc1/Fedora/base/product.img HTTP/1.0" 404 309 "-" "anaconda/11.1.0.45" 10.32.5.2 - - [21/Jun/2006:12:07:35 +0200] "GET /fc6test1/Fedora/base/stage2.img HTTP/1.0" 200 77934592 "-" "anaconda/11.1.0.45" The same installation works when using NFS.
Created attachment 131288 [details] http installation error message
Can you switch to tty2 and grab /tmp/syslog and /tmp/anaconda.log?
This is a headless install on a Cell based blade. All I have is a serial console. Is there any other way to retrieve the information you need?
If you're doing a vnc install, you should be able to hit enter on the console where you were doing the install and get a shell also.
I cannot reproduce this anymore. Just after entering the hostname and path for the http installation I get a "*** glibc". I booted with the kernel command-line "console=hvc0 vnc debug". I will continue a few more times to see if I can reproduce the earlier described error. Same happens for FTP but NFS still works.
Created attachment 131590 [details] anaconda.log The error with "*** glibc" cannot be seen anymore. I was able to retrieve anaconda log and syslog.
Created attachment 131593 [details] installation syslog
this is fixed with todays rawhide: -rwxr-xr-x 1 ftpadmin ftp 8187840 Jun 29 08:37 ppc64.img