Hi! I did today FTP network installation using boot.iso image from 9th December. Almost everything went fine ;-) After reboot I saw kernel panic:
[snip]
Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys Kernel panic - not syncing: Attempted to kill init! bla bla bla ;]
I looked at /root/install.log → http://pastebin.com/458435 and found that there were problems with installing selinux-policy-targeted [1].
Instalowanie selinux-policy-targeted-2.1.1-1.noarch. /var/tmp/rpm-tmp.77057: line 22: ln: command not found /var/tmp/rpm-tmp.77057: line 34: semodule: command not found /var/tmp/rpm-tmp.77057: line 38: ls: command not found /var/tmp/rpm-tmp.77057: line 39: rm: command not found
I grabbed FC4 CD1, booted system into rescue mode and did `chroot /mnt/sysimage'. I had to reinstall selinux-policy-targeted package with `--noscript' option. I tried to manully execute all commands from {pre,post}install scriplets but some of them failed (for example: `semodule -b /usr/share/selinux/targeted/base.pp -s targeted'). I think that the problem was with too old kernel available in FC4's rescue mode.
I also run `yum update' in chrooted environment but most of the scriptlets failed. Unfortunately, it's not mentioned in /var/log/yum.log :/
After reboot 'kernel panic' problem disappeared :D There were lots of avc messages, though. “Rescue mode” must have screw up security context of system files. `touch /.autorelabel && reboot' fixed this problem...
Two remarks: 1) It would be nice to have newer rescue CD ;-) 2) I miss information about current download speed. For instance, downloading stage2.img file takes some time on my DSL connection. I had to look at NIC's LEDs to make shure that it's really downloading something from the Internet.
That would be all. Now I can die happily ;-)
[1] BTW there are also problems with creating icon cache. Few scriplets failed.
Regards, Dawid
Dawid Gajownik wrote:
Hi! I did today FTP network installation using boot.iso image from 9th December. Almost everything went fine ;-) After reboot I saw kernel panic:
[snip]
Switching to new root and running init. unmounting old /dev unmounting old /proc unmounting old /sys Kernel panic - not syncing: Attempted to kill init! bla bla bla ;]
I looked at /root/install.log → http://pastebin.com/458435 and found that there were problems with installing selinux-policy-targeted [1].
Instalowanie selinux-policy-targeted-2.1.1-1.noarch. /var/tmp/rpm-tmp.77057: line 22: ln: command not found /var/tmp/rpm-tmp.77057: line 34: semodule: command not found /var/tmp/rpm-tmp.77057: line 38: ls: command not found /var/tmp/rpm-tmp.77057: line 39: rm: command not found
I grabbed FC4 CD1, booted system into rescue mode and did `chroot /mnt/sysimage'. I had to reinstall selinux-policy-targeted package with `--noscript' option. I tried to manully execute all commands from {pre,post}install scriplets but some of them failed (for example: `semodule -b /usr/share/selinux/targeted/base.pp -s targeted'). I think that the problem was with too old kernel available in FC4's rescue mode.
I also run `yum update' in chrooted environment but most of the scriptlets failed. Unfortunately, it's not mentioned in /var/log/yum.log :/
After reboot 'kernel panic' problem disappeared :D There were lots of avc messages, though. “Rescue mode” must have screw up security context of system files. `touch /.autorelabel && reboot' fixed this problem...
Two remarks:
- It would be nice to have newer rescue CD ;-)
- I miss information about current download speed. For instance,
downloading stage2.img file takes some time on my DSL connection. I had to look at NIC's LEDs to make shure that it's really downloading something from the Internet.
That would be all. Now I can die happily ;-)
[1] BTW there are also problems with creating icon cache. Few scriplets failed.
Regards, Dawid
You probably could have accessed your system by adding selinux=0 via grub on boot. Regardless, this problem seems to be related to Dec 2nd updates. SELinux policy seems to be effected directly or indrectly by a change somewhere.
I filed a bug that is now closed. The resolution you took resulted in similar results. Using --noscripts probably messed up something on the system though.
Bug hunters for similar failures should round up reports that are currently filed.
My bug report was filed after I resolved the issue. Another reporter is still running through the changes.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174919
The bug above is for reference. You probably want anaconda involved with you particular problem.
*Cannot link, run semodule, list or remove.*
You most likely hit the problem area closer to the cause.
Jim
Dnia 12/10/2005 05:38 PM, Użytkownik Jim Cornette napisał:
You probably could have accessed your system by adding selinux=0 via grub on boot.
Thanks, I completely forgot about this option :)
Using --noscripts probably messed up something on the system though.
I thought that installation with `--noscripts' option only copies files to the disk and adds necessary entries to the RPM database :/
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174919
The bug above is for reference.
Thanks, I've added myself to CC.
Dawid Gajownik wrote:
Dnia 12/10/2005 05:38 PM, Użytkownik Jim Cornette napisał:
You probably could have accessed your system by adding selinux=0 via grub on boot.
Thanks, I completely forgot about this option :)
Using --noscripts probably messed up something on the system though.
I thought that installation with `--noscripts' option only copies files to the disk and adds necessary entries to the RPM database :/
As far as I understand, the post scripts could call programs,set enviromnmental factors or do any other item needed to set things up for the new programs. I know that running noscripts for the kernel is pretty much worthless since it does not add entries for the new kernel and might not have other items that it is supposed to.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=174919
The bug above is for reference.
Thanks, I've added myself to CC.
You might want to include the installation report to the bug report also.
I see what you are referring to the scriptlet error with selinux-policy
This package downloads but aborts being installed either with rpm or yum.
Populating transaction set with selected packages. Please wait. ---> Downloading header for selinux-policy-targeted to pack into transaction set. selinux-policy-targeted-2 100% |=========================| 8.3 kB 00:00 ---> Package selinux-policy-targeted.noarch 0:2.1.1-1 set to be updated --> Running transaction check
Dependencies Resolved
============================================================================= Package Arch Version Repository Size ============================================================================= Updating: selinux-policy-targeted noarch 2.1.1-1 development 221 k
Transaction Summary ============================================================================= Install 0 Package(s) Update 1 Package(s) Remove 0 Package(s) Total download size: 221 k Downloading Packages: (1/1): selinux-policy-tar 100% |=========================| 221 kB 00:00 Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction error: %pre(selinux-policy-targeted-2.1.1-1.noarch) scriptlet failed, exit status 255 error: install: %pre scriptlet failed (2), skipping selinux-policy-targeted-2.1.1-1
Updated: selinux-policy-targeted.noarch 0:2.1.1-1 Complete! [root@cornette-lt ~]# rpm -q selinux-policy-targeted selinux-policy-targeted-2.1.0-1 [root@cornette-lt ~]# cd /var/cache/yum/development/packages/ [root@cornette-lt packages]# ls selinux-policy-targeted-2.1.1-1.noarch.rpm [root@cornette-lt packages]# rpm -Uvh sel*.rpm Preparing... ########################################### [100%] error: %pre(selinux-policy-targeted-2.1.1-1.noarch) scriptlet failed, exit status 255 error: install: %pre scriptlet failed (2), skipping selinux-policy-targeted-2.1.1-1
Downloading Packages: (1/1): selinux-policy-tar 100% |=========================| 221 kB 00:00 Running Transaction Test Finished Transaction Test Transaction Test Succeeded Running Transaction error: %pre(selinux-policy-targeted-2.1.1-1.noarch) scriptlet failed, exit status 255 error: install: %pre scriptlet failed (2), skipping selinux-policy-targeted-2.1.1-1
Updated: selinux-policy-targeted.noarch 0:2.1.1-1 Complete! [root@cornette-lt ~]# rpm -q selinux-policy-targeted selinux-policy-targeted-2.1.0-1 [root@cornette-lt ~]# cd /var/cache/yum/development/packages/ [root@cornette-lt packages]# ls selinux-policy-targeted-2.1.1-1.noarch.rpm [root@cornette-lt packages]# rpm -Uvh sel*.rpm Preparing... ########################################### [100%] error: %pre(selinux-policy-targeted-2.1.1-1.noarch) scriptlet failed, exit status 255 error: install: %pre scriptlet failed (2), skipping selinux-policy-targeted-2.1.1-1
As Jeff commented in another posting, selinux policy could be an influencing factor. Out of curiousity, I booted with selinux=0 and tried to install the yum cached rpm and it installed successfully.
Filing a bug referring to selinux interferring with pre and post scripts is probably a reasonable place to file this bug against.
Jim
ls selinux-policy-targeted-2.1.1-1.noarch.rpm [root@cornette-lt packages]# rpm -Uvh sel*.rpm Preparing... ########################################### [100%] 1:selinux-policy-targeted########################################### [100%] [root@cornette-lt packages]# rpm -q selinux-policy-targeted selinux-policy-targeted-2.1.1-1 [root@cornette-lt packages]# rpm -q --verify selinux-policy-targeted