On Thu, 2013-02-14 at 16:03 -0700, Steven Dake wrote: > Shutdown has been a never-ending source of frustration for corosync, Indeed. > now solved with the 2.x series :) That's good news. > The reason the TERM is not honored immediately is that Corosync wants > to shut down in an orderly fashion on a TERM by quiescing services and > shutting down cleanly with no pending messages. Indeed, which seems reasonable. > Sometimes this is not possible quickly because the network is flaky or > blocked in some way (such as iptables). Hrm. This shouldn't be the case here. Corosync runs successful on this network. Is there anything different done at shutdown than is done during regular run-time in regards to network activity? IOW, if the network is capable of letting corosync work properly during regular runtime, shouldn't it work during shutdown? > I had thought we had sorted all this out for 1.4 series though, so if > you could provide more information on your corosync rpm version, that > might be helpful. EL6: Name : corosync Relocations: (not relocatable) Version : 1.4.1 Vendor: CentOS Release : 7.el6 Build Date: Fri 22 Jun 2012 02:06:53 PM UTC Install Date: Thu 14 Feb 2013 06:51:10 PM UTC Build Host: c6b7.bsys.dev.centos.org Group : System Environment/Base Source RPM: corosync-1.4.1-7.el6.src.rpm Size : 432444 License: BSD Signature : RSA/SHA1, Sun 24 Jun 2012 10:16:17 PM UTC, Key ID 0946fca2c105b9de Packager : CentOS BuildSystem <http://bugs.centos.org> URL : http://ftp.corosync.org Summary : The Corosync Cluster Engine and Application Programming Interfaces Description : This package contains the Corosync Cluster Engine Executive, several default APIs and libraries, default configuration files, and an init script. > sigterm should be honored by the corosync process rather then hacking > around with a sigkill. Indeed. I hate having to use SIGKILL. Cheers, b. _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
