I just started from scratch on the second serer and reinstalled everything. I am passed that error message. -----Original Message----- From: discuss-bounces@xxxxxxxxxxxx [mailto:discuss-bounces@xxxxxxxxxxxx] On Behalf Of Yount, William D Sent: Thursday, June 07, 2012 4:50 PM To: Jan Friesse Cc: discuss@xxxxxxxxxxxx Subject: Re: Unable to bind the socket to receive multicast packets: Permission denied (13) I checked the /etc/sysconfig/selinux file: # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - No SELinux policy is loaded. SELINUX=disabled # SELINUXTYPE= can take one of these two values: # targeted - Targeted processes are protected, # mls - Multi Level Security protection. SELINUXTYPE=targeted I rebooted the system to be sure. I made sure iptables was off: service iptables stop I ran the command: su root Then I restarted corosync (service corosync restart) Jun 7 16:46:18 KNTCLFS002 corosync[2607]: [TOTEM ] Initializing transport (UDP/IP Multicast). Jun 7 16:46:18 KNTCLFS002 corosync[2607]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0). Jun 7 16:46:18 KNTCLFS002 corosync[2607]: [TOTEM ] Unable to bind the socket to receive multicast packets: Permission denied (13) Jun 7 16:46:18 KNTCLFS002 corosync[2607]: [TOTEM ] Could not set traffic priority: Socket operation on non-socket (88) Jun 7 16:46:18 KNTCLFS002 corosync[2607]: [TOTEM ] The network interface [192.168.1.10] is now up -----Original Message----- From: Jan Friesse [mailto:jfriesse@xxxxxxxxxx] Sent: Thursday, June 07, 2012 3:26 AM To: Yount, William D Cc: discuss@xxxxxxxxxxxx Subject: Re: Unable to bind the socket to receive multicast packets: Permission denied (13) Important message is: > Jun 7 01:06:48 KNTCLFS002 corosync[2452]: [TOTEM ] Unable to bind the socket to receive multicast packets: Permission denied (13) Are you sure you are running corosync on that machine as root AND you really turned of selinux? Honza Yount, William D napsal(a): > I am following the guide posted here: > http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Clusters_from_ > Scratch/ > I have two servers with dual NICS: > Server 1 > NIC-A: 10.89.99.31 > NIC-B: 192.168.1.5 > Server 2 > NIC-A: 10.89.99.32 > NIC-B: 192.168.1.10 > > I want to use NIC-B on both machines to carry corosync traffic. I got down to this section: > > 1. export ais_port=4000 > > 2. export ais_mcast=226.94.1.1 > > 3. export ais_addr=`ip addr | grep "inet" | tail -n 1 | awk '{print $4}' | sed s/255/0/` > > 4. env | grep ais_ais_mcast=226.94.1.1 > > > > The last command did not produce any output, so I edited the corosync.conf file manually. I have attached a copy of the file as it appears on both servers. I am able to start corosync up on Server 1 with no problems. On Server 2, I am getting the errors below: > > Jun 7 01:06:48 KNTCLFS002 corosync[2452]: [TOTEM ] Initializing transport (UDP/IP Multicast). > Jun 7 01:06:48 KNTCLFS002 corosync[2452]: [TOTEM ] Initializing transmit/receive security: libtomcrypt SOBER128/SHA1HMAC (mode 0). > Jun 7 01:06:48 KNTCLFS002 corosync[2452]: [TOTEM ] Unable to bind the socket to receive multicast packets: Permission denied (13) > Jun 7 01:06:48 KNTCLFS002 corosync[2452]: [TOTEM ] Could not set traffic priority: Socket operation on non-socket (88) > Jun 7 01:06:48 KNTCLFS002 corosync[2452]: [TOTEM ] The network interface [192.168.1.10] is now up. > Jun 7 01:07:32 KNTCLFS002 corosync[2452]: [TOTEM ] Totem is unable to form a cluster because of an operating system or network fault. The most common cause of this message is that the local firewall is configured improperly. > > I have made sure that iptables is turned off and selinux is set to permissive. When I run the command 'corosync-blackbox' I get this: > > rec=[1056] Log Message=sendmsg(mcast) failed (non-critical): Socket > operation on non-socket (88) rec=[1057] Log Message=sendmsg(mcast) > failed (non-critical): Socket operation on non-socket (88) rec=[1058] > Log Message=sendmsg(mcast) failed (non-critical): Socket operation on > non-socket (88) rec=[1059] Log Message=sendmsg(mcast) failed > (non-critical): Socket operation on non-socket (88) rec=[1060] Log > Message=sendmsg(mcast) failed (non-critical): Socket operation on > non-socket (88) rec=[1061] Log Message=sendmsg(mcast) failed > (non-critical): Socket operation on non-socket (88) rec=[1062] Log > Message=sendmsg(mcast) failed (non-critical): Socket operation on > non-socket (88) rec=[1063] Log Message=sendmsg(mcast) failed (non-critical): Socket operation on non-socket (88) rec=[1064] Log Message=sendmsg(mcast) failed (non-critical): Socket operation on non-socket (88) rec=[1065] Log Message=sendmsg(mcast) failed (non-critical): Socket operation on non-socket (88) rec=[1066] Log Message=The consensus timeout expired. > rec=[1067] Log Message=sendmsg(mcast) failed (non-critical): Socket > operation on non-socket (88) rec=[1068] Log Message=entering GATHER state from 3. > rec=[1069] Log Message=Totem is unable to form a cluster because of an operating system or network fault. The most common cause of this message is that the local firewall is configured improperly. > > I can ping each machine from the other one. Any help will be greatly appreciated. > > > > > Thanks, > William > > > > > > _______________________________________________ > discuss mailing list > discuss@xxxxxxxxxxxx > http://lists.corosync.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
