If you have SELinux enabled, check /var/log/messages for possible security context errors.
For example, you might need to set the context for /var/satellite/jh to something like: system_u:object_r:httpd_sys_content_t Mike -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Jonathan Hoser Sent: Monday, October 11, 2010 8:54 AM To: [email protected] Subject: [Spacewalk-list] Building kickstart distributions Hi all, one issue solved, next problem rises its head: I cannot create kickstart distributions. What do I do? At the webinterface: Systems->Kickstart->Distributions->create new distribution Previously I have copied the entire install DVDs of CentOS 5.5 x86_64 and Fedora13 x86_64 to a local directory called /var/satellite/jh/ ..../centos5.5-x86_64-iso and ..../fedora13-x86_64-iso In the webinterface (https://server/rhn/kickstart/TreeCreate.do) I enter Distribution Label: test1234 Tree Path: /var/satellite/jh/centos5.5-x86_64-iso Base Channel: CentOS-5.5 x86_64 [created a base-channel synced to http://centos.bio.lmu.de/5.5/os/x86_64/ ] Installer Generation: Red Hat Enterprise Linux 5 Kernel Options: [empty] Post Kernel Options: [empty] A click on 'Create Kickstart Distribution' gets me a red warning label located on the page reading: "The kernel could not be found at the specified location: /var/satellite/jh/centos5.5-x86_64-iso/images/pxeboot/vmlinuz" However, the file exists [jonathan.ho...@host ~]$ ls -alZ /var/satellite/jh/centos5.5-x86_64-iso/images/pxeboot/vmlinuz -rwxrwxrwx. tomcat root system_u:object_r:iso9660_t:s0 /var/satellite/jh/centos5.5-x86_64-iso/images/pxeboot/vmlinuz Renaming the vmlinuz file, doesn't change the error message, renaming the initrd.img file, does: "The initrd could not be found at the specified location: /var/satellite/jh/centos5.5-x86_64-iso/images/pxeboot/initrd.img" The contents of my pxeboot-directory are: [jonathan.ho...@host pxeboot]$ ls -alZ drwxrwxrwx. tomcat root system_u:object_r:iso9660_t:s0 . drwxrwxrwx. tomcat root system_u:object_r:iso9660_t:s0 .. -rwxrwxrwx. tomcat root system_u:object_r:iso9660_t:s0 initrd.img -rwxrwxrwx. tomcat root system_u:object_r:iso9660_t:s0 README -rwxrwxrwx. tomcat root system_u:object_r:iso9660_t:s0 TRANS.TBL -rwxrwxrwx. tomcat root system_u:object_r:iso9660_t:s0 vmlinuz with 777-rights only to make sure, I'm not missing anything again. So: Why does initrd.img register as ok, while vmlinuz doesn't? And where would I need to place a modified com.redhat.rhn.domain.kickstart.KickstartableTree class, to test for some scenarios I have in mind? The instructions/scripts with ant install-dev don't work, there's so much stuff missing that the httpd-service won't come up. Best -Jonathan _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
