Bug 459720
Summary: | [PATCH] fence_xvmd cannot start if default route is not set | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Satoru SATOH <ssato> | ||||
Component: | cman | Assignee: | Lon Hohberger <lhh> | ||||
Status: | CLOSED ERRATA | QA Contact: | Cluster QE <mspqa-list> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 5.2 | CC: | capel, cluster-maint, djansa, edamato, pkennedy, stanislav.polasek, syeghiay | ||||
Target Milestone: | rc | ||||||
Target Release: | --- | ||||||
Hardware: | All | ||||||
OS: | Linux | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2009-01-20 21:50:43 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: | |||||||
Attachments: |
|
Description
Satoru SATOH
2008-08-21 15:26:46 UTC
Created attachment 314709 [details]
A patch for fence_xvmd to add option to select correct network interface explicitly
Here is a log of fence_xvmd with my patch attached: [root@cluster-1 ~]# /var/tmp/cman-2.0.84-2-root-root/sbin/fence_xvmd -LX -fddddd -I virbr0 Debugging threshold is now 5 -- args @ 0xbfc095b8 -- args->addr = 225.0.0.12 args->domain = (null) args->key_file = /etc/cluster/fence_xvm.key args->op = 2 args->hash = 2 args->auth = 2 args->port = 1229 args->ifindex = 5 args->family = 2 args->timeout = 30 args->retr_time = 20 args->flags = 259 args->debug = 5 -- end args -- Reading in key file /etc/cluster/fence_xvm.key into 0xbfc085b8 (4096 max size) Actual key length = 4096 bytesSetting up ipv4 multicast receive (225.0.0.12:1229) Joining multicast group ipv4_recv_sk: success, fd = 3 My Node ID = 1 Domain UUID Owner State ------ ---- ----- ----- Domain-0 00000000-0000-0000-0000-000000000000 00001 00001 [root@cluster-1 ~]# ip route del default via 192.168.122.1 dev eth0 [root@cluster-1 ~]# /var/tmp/cman-2.0.84-2-root-root/sbin/fence_xvmd -LX -fddddd -I virbr0 Debugging threshold is now 5 -- args @ 0xbf95b308 -- args->addr = 225.0.0.12 args->domain = (null) args->key_file = /etc/cluster/fence_xvm.key args->op = 2 args->hash = 2 args->auth = 2 args->port = 1229 args->ifindex = 5 args->family = 2 args->timeout = 30 args->retr_time = 20 args->flags = 259 args->debug = 5 -- end args -- Reading in key file /etc/cluster/fence_xvm.key into 0xbf95a308 (4096 max size) Actual key length = 4096 bytesSetting up ipv4 multicast receive (225.0.0.12:1229) Joining multicast group ipv4_recv_sk: success, fd = 3 My Node ID = 1 Domain UUID Owner State ------ ---- ----- ----- Domain-0 00000000-0000-0000-0000-000000000000 00001 00001 [root@cluster-1 ~]# If no interface is specified with the "-I" option, default interface #0 corresponding to INADDR_ANY in ipv4, will be used. In this case, default route is not set so that fence_xvmd does not start as expected. [root@cluster-1 ~]# /var/tmp/cman-2.0.84-2-root-root/sbin/fence_xvmd -LX -fddddd Debugging threshold is now 5 -- args @ 0xbffea1a8 -- args->addr = 225.0.0.12 args->domain = (null) args->key_file = /etc/cluster/fence_xvm.key args->op = 2 args->hash = 2 args->auth = 2 args->port = 1229 args->ifindex = 0 args->family = 2 args->timeout = 30 args->retr_time = 20 args->flags = 259 args->debug = 5 -- end args -- Reading in key file /etc/cluster/fence_xvm.key into 0xbffe91a8 (4096 max size) Actual key length = 4096 bytesSetting up ipv4 multicast receive (225.0.0.12:1229) Joining multicast group Failed to bind multicast receive socket to 225.0.0.12: No such device Check network configuration. Could not set up multicast listen socket [root@cluster-1 ~]# ip route add default via 192.168.122.1 dev eth0 [root@cluster-1 ~]# (In reply to comment #2) > Here is a log of fence_xvmd with my patch attached: s/attached/applied/ :P Merged to master and RHEL5 branches. Master: http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=5fd95228e8b58a6b42f78a01a480e686e53086c3 RHEL5: http://git.fedorahosted.org/git/?p=cluster.git;a=commit;h=a4f4f109ae329a96632f776d1ce166241f5aa1e1 Is this patch scheduled for inclusion in RHEL5.2? If so, do you have a release date? I'm willing to test this, if required. Kind regards, Jasper Capel An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHBA-2009-0189.html |