[CentOS] CentOS 6.0: iptables stacktrace with named chains > 28 chars

Hi, I'm not sure where to ask this question, you, redhat or netfilter so I'll ask you guys first, hoping you can redirect me where this post belongs. I have an issue with my CentOS 6 box with named chains in iptables. Apparently there is a builtin #define to limit chain names up to 30 chars, but t

[CentOS] CentOS 6: corosync and pacemaker won't stop (patch)

Hi, I cannot 'halt' my CentOS 6 servers while running corosync+pacemaker. I believe the runlevels used to stop corosync and pacemaker are not in the correct order and create the infinite "Waiting for corosync services to unload..." loop thing. This is my first time with this cluster technology bu

Re: [CentOS] CentOS 6.0: iptables stacktrace with named chains > 28 chars

Florian CROUZAT wrote on 2011-09-28: > Hi, > > I'm not sure where to ask this question, you, redhat or netfilter so > I'll ask you guys first, hoping you can redirect me where this post > belongs. I have an issue with my CentOS 6 box with named chains in > iptables. A

Re: [CentOS] CentOS 6: corosync and pacemaker won't stop (patch)

Florian Crouzat wrote on 2011-09-29: > Hi, > > I cannot 'halt' my CentOS 6 servers while running corosync+pacemaker. I > believe the runlevels used to stop corosync and pacemaker are not in the > correct order and create the infinite "Waiting for corosync servi