Actually, thats not it either, the iptables firewall was up this time too (deleted the wrong thing in rc5.d... oops...). I have no idea why it wasn't working before, or why it is working now. I am just going to sprinkle some holy water on the console and move on.
On 8/2/07, Michael Edwards <[EMAIL PROTECTED]> wrote: > Apparently this had nothing to do with SELinux. I tried with the > standard SIS kernel (which doesn't have SELinux in it) and I got the > same error. > > I had an IP MASQ setup, which is a sort of firewall I suppose, and > something about it blocked imaging. I don't think it was blocking the > rsync port, it should have been allowing all traffic on 10.0.0.0, but > maybe it was routing the packets to the other interface and > systemimager wasn't looking for them there. I turned it off and its > working now... > > I had forgotten about the IP MASQ bit until earlier today, I had just > checked redhats firewall, which was in fact off :) > > I might try reimaging a node after I turn it on and explicitly open > the rsync port and see if that helps. > > On 8/2/07, Erich Focht <[EMAIL PROTECTED]> wrote: > > Hi Mike, > > > > could you please try modifying the /etc/systemconfig/systemconfig.conf file > > inside your image and add to the [BOOT] section something like: > > > > APPEND = "selinux=0" > > > > before imaging? I'm curious if that helps. > > > > Regards, > > Erich > > > > On Wednesday 01 August 2007 19:36, Michael Edwards wrote: > > > I have imaged this cluster several times, but after updating the image > > > (apparently successfully) to OFED-1.2 it won't image anymore, give an > > > rsync related error. Dumped the imaging log to pastebin. > > > > > > It says something about SELinux, is that normal if the head node has > > > SELinux disabled? > > > > > > This is with RHEL 4, OSCAR 5.0, but I decided to post here ... just cuz. > > > > > > Heres the log. > > > http://pastebin.com/m76526978 > > > > > > To get this far I had to add the path of pxelinux.0 to setup_pxe, > > > which was looking for it in /usr/lib/syslinux and not > > > /usr/lib64/syslinux, if that is meaningful. I have sucessfully rerun > > > the setup networking step with UYOK since then. > > > ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Oscar-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/oscar-devel
