Bug 612752

Summary: clustermon won't start if IPv6 is disabled
Product: Red Hat Enterprise Linux 6 Reporter: Chris Feist <cfeist>
Component: clustermonAssignee: Chris Feist <cfeist>
Status: CLOSED CURRENTRELEASE QA Contact: Cluster QE <mspqa-list>
Severity: medium Docs Contact:
Priority: low    
Version: 6.0CC: cfeist, cluster-maint, djansa, hklein, rmccabe, ssaha, tao
Target Milestone: rc   
Target Release: 6.0   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: clustermon-0.16.2-8.el6 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 612318 Environment:
Last Closed: 2010-11-10 22:06:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 612318    

Comment 1 Lon Hohberger 2010-07-09 15:17:12 UTC
Clustermon does not start if you attempt to start with ipv6 disabled.

To try this, you need to:

1) add the following lines to /etc/modprobe.d/dist.conf:

   alias ipv6 off
   alias net-pf-10 off

2) execute the following command:

   chkconfig --del ip6_tables

3) add the following line to /etc/sysconfig/network:

   NETWORKING_IPV6=no

4) Reboot the system.

You can verify that ipv6 is off by issuing the following command:

   ip addr list | grep inet6

There should be no entries.

5a) When you attempt to start modclusterd in the foreground, you will receive the following error and modclusterd will exit:

   [root@snap ~]# modclusterd -f
   Setting verbosity level to LogBasic
   Fri Jul  9 11:13:05 2010: started
   Fri Jul  9 11:13:05 2010: unhandled exception in main():
     ServerSocket(port=16851): socket() failed: Address family 
     not supported by protocol
   Fri Jul  9 11:13:05 2010: died

5b) When you attempt to start modclusterd normally, it will fail:

   [root@snap ~]# service modclusterd start
   Starting Cluster Module - cluster monitor: Setting verbosity level to LogBasic
                                                           [FAILED]
   [root@snap ~]# service modclusterd status
   modclusterd is stopped



The expected behaviors in 5a is that modclusterd stay running in the foreground.  The expected case in 5b is that modclusterd stays running and returns a positive status when we issue a status command.

Comment 2 Lon Hohberger 2010-07-09 15:20:13 UTC
Oops, (2) should be 'chkconfig --del ip6tables'...

Comment 3 Chris Feist 2010-07-09 19:41:33 UTC
Test output (old version is -7, new version is -8

[root@ask-03 ~]# rpm -Uvh http://porkchop.redhat.com/brewroot/packages/clustermon/0.16.2/7.el6/x86_64/modcluster-0.16.2-7.el6.x86_64.rpm
Retrieving http://porkchop.redhat.com/brewroot/packages/clustermon/0.16.2/7.el6/x86_64/modcluster-0.16.2-7.el6.x86_64.rpm
Preparing...                ########################################### [100%]
   1:modcluster             ########################################### [100%]
[root@ask-03 ~]# modclusterd -f
Setting verbosity level to LogBasic
Fri Jul  9 14:37:49 2010: started
Fri Jul  9 14:37:49 2010: unhandled exception in main(): ServerSocket(port=16851): socket() failed: Address family not supported by protocol
Fri Jul  9 14:37:49 2010: died
[root@ask-03 ~]# rpm -Uvh http://porkchop.redhat.com/brewroot/packages/clustermon/0.16.2/8.el6/x86_64/modcluster-0.16.2-8.el6.x86_64.rpm
Retrieving http://porkchop.redhat.com/brewroot/packages/clustermon/0.16.2/8.el6/x86_64/modcluster-0.16.2-8.el6.x86_64.rpm
Preparing...                ########################################### [100%]
   1:modcluster             ########################################### [100%]
[root@ask-03 ~]# modclusterd -f
Setting verbosity level to LogBasic
Fri Jul  9 14:38:04 2010: started

(Never returns unless you ctrl-c)

Comment 5 Dean Jansa 2010-08-24 21:21:28 UTC
[root@marathon-01 ~]# ip addr list
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:a0:d1:e3:0d:c2 brd ff:ff:ff:ff:ff:ff
    inet 10.15.89.71/24 brd 10.15.89.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN qlen 1000
    link/ether 00:a0:d1:e3:0d:c3 brd ff:ff:ff:ff:ff:ff
[root@marathon-01 ~]# modclusterd -f
Setting verbosity level to LogBasic
Tue Aug 24 16:21:58 2010: started

Verified

Comment 6 releng-rhel@redhat.com 2010-11-10 22:06:54 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.