I've spent a great deal of time trying to get new (to me) software running on a new distro. In retrospect a bigger bite than I can chew. In any case, I thought I might share some of what I've learned to hopefully help others avoid my situation.
1) Fedora 15 comes with prebuilt packages for all of the common software used here. They are not bugfree, but they generally work well with the right configuration. This is good news. 2) Using default ports, you only need to open tcp ports 4000 and 5404:5405 in your firewall. In fact in my experience you only need one set or the other depending on whether you start corosync directly or with CMAN 3) SELinux *will* cause you problems. If you don't plan on using it just disable it and save yourself a lot of headaches. If you are going to use it, I personally don't see any benefit in delaying the inevitable. Just bite the bullet and fix it. I'm not going to get into all the details on fixing it, but the first thing to do when something doesn't work is to grep "denied" in /var/log/audit/audit.log and fix the denials as they happen. I'm not an SELinux expert by any stretch, but I can give more detailed advice to anyone having an issue here. 3) Fedora 15 uses a new system "systemctl" to start and enable services. This may become a better way to manage services, but it's not yet. The issue that is a problem here, is that it doesn't display the output from the init scripts directly. This is a real problem with pacemaker for example, since it gives a detailed output as it brings up services which is really helpful in debugging. Unfortunately bypassing it with "/etc/rc.d/init.d/(service) start" doesn't help since the bug/feature is in the functions script linked into most init scripts. There's probably a better answer, but my solution was to edit the init script and rem out the line that links to "/etc/rc.d/init.d/functions". This allows the script to display the output it was designed to. 4) Clusters From Scratch gives a pretty brief description of enabling CMAN and describing how it fits into the stack. I'm still pretty unclear on this but it doesn't really matter to me as long as it works. One important thing that is left out though, is that CMAN will not work if NetworkConfig is running or enabled on your system (http://docs.redhat.com/docs/en- US/Red_Hat_Enterprise_Linux/6/html/Cluster_Administration/s1-networkmanager- CA.html). And disabling it with the new "systemctl" tool doesn't help! You *must* use "chkconfig --del NetworkManager". You can only find where the problem is when you look at the output from the init script (which you can't do without a workaround, see above). 5) I once again have a working cluster, now using CMAN. But I still haven't been able to get any of the software based stonith resources to do anything useful. They install, their config checks out, and they are aware of a failure, but nothing ever happens after that. Still working on this one. Jeff _______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
