On 02/14/2012 09:33 AM, Dan Barber wrote:
>> Steven,
>>
>> Thanks for the reply, my apologies that my first response was sent
>> directly to you. I am running "/etc/init.d/corosync start" as root, do I
>> need to do something else to make sure that corosync runs as root? I get
>> the same behavior from running "service corosync start" run as root,
>> which is understandable as I believe those are essentially identical
>> operations.
>>
>
>No problem. Also please don't top post - it makes following the threads
>difficult for followup readers of the thread archive.
>
>Which OS are you using? If RHEL/Fedora/centos, do you have selinux enabled?
>
>Can you run corosync-blackbox?
Steve,
Thanks again for the help, both on list protocol and the questions. It looks like it is
a selinux problem, I am running on centos. I'm working with our linux folks to try and
start making progress again, selinux isn't supposed to be enabled.
Thanks!
Dan
>
>> Thanks,
>>
>> Dan
>>
>> ------------------------------------------------------------------------
>> *From:* Steven Dake <sdake@xxxxxxxxxx>
>> *To:* Dan Barber <dandy_dan_1999@xxxxxxxxx>
>> *Cc:* "discuss@xxxxxxxxxxxx" <discuss@xxxxxxxxxxxx>
>> *Sent:* Tuesday, February 14, 2012 9:19 AM
>> *Subject:* Re: [corosync] Problems starting up Corosync
>>
>> On 02/14/2012 09:16 AM, Dan Barber wrote:
>>> I am having problems bringing up Corosync and hoping someone will see
>>> the stupid mistake that I’ve made. I’ve done a lot of searching for the
>>> error that I’m seeing, and haven’t found anything other than a reference
>>> to the line of the code which produces this error, which concerns me a
>>> little.
>>>
>>> Here’s the corosync.conf file that I’m using:
>>> # Please read the corosync.conf.5 manual page
>>> compatibility: whitetank
>>>
>>> totem {
>>> version: 2
>>> secauth: off
>>> threads: 0
>>> interface {
>>> ringnumber: 0
>>> bindnetaddr: 10.47.12.0
>>> mcastaddr: 226.94.1.1
>>> mcastport: 4000
>>> ttl: 1
>>> }
>>> }
>>>
>>> logging {
>>> fileline: off
>>> to_stderr: no
>>> to_logfile: yes
>>> to_syslog: yes
>>> logfile: /var/log/cluster/corosync.log
>>> debug: on
>>> timestamp: on
>>> logger_subsys {
>>> subsys: AMF
>>> debug: off
>>> }
>>> }
>>>
>>> amf {
>>> mode: disabled
>>> }
>>>
>>> And here is corosync.log from start up to the failure lines:
>>> Feb 13 09:45:36 corosync [MAIN ] Corosync Cluster Engine ('1.4.1'):
>>> started and ready to provide service.
>>> Feb 13 09:45:36 corosync [MAIN ] Corosync built-in features: nss dbus
>>> rdma snmp
>>> Feb 13 09:45:36 corosync [MAIN ] Successfully read main configuration
>>> file '/etc/corosync/corosync.conf'.
>>> Feb 13 09:45:36 corosync [TOTEM ] Token Timeout (1000 ms) retransmit
>>> timeout (238 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] token hold (180 ms) retransmits before
>>> loss (4 retrans)
>>> Feb 13 09:45:36 corosync [TOTEM ] join (50 ms) send_join (0 ms)
>>> consensus (1200 ms) merge (200 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] downcheck (1000 ms) fail to recv const
>>> (2500 msgs)
>>> Feb 13 09:45:36 corosync [TOTEM ] seqno unchanged const (30 rotations)
>>> Maximum network MTU 1402
>>> Feb 13 09:45:36 corosync [TOTEM ] window size per rotation (50 messages)
>>> maximum messages per rotation (17 messages)
>>> Feb 13 09:45:36 corosync [TOTEM ] missed count const (5 messages)
>>> Feb 13 09:45:36 corosync [TOTEM ] send threads (0 threads)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP token expired timeout (238 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP token problem counter (2000 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP threshold (10 problem count)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP multicast threshold (100 problem
>>> count)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP automatic recovery check timeout
>>> (1000 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP mode set to none.
>>> Feb 13 09:45:36 corosync [TOTEM ] heartbeat_failures_allowed (0)
>>> Feb 13 09:45:36 corosync [TOTEM ] max_network_delay (50 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] HeartBeat is Disabled. To enable set
>>> heartbeat_failures_allowed > 0
>>> Feb 13 09:45:36 corosync [TOTEM ] Initializing transport (UDP/IP
>> Multicast).
>>> Feb 13 09:45:36 corosync [TOTEM ] Initializing transmit/receive
>>> security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
>>> Feb 13 09:45:36 corosync [IPC ] you are using ipc api v2
>>> Feb 13 09:45:36 corosync [TOTEM ] Unable to bind the socket to receive
>>> multicast packets: Permission denied (13)
>>> Feb 13 09:45:36 corosync [TOTEM ] Could not set traffic priority: Socket
>>> operation on non-socket (88)
>>>
>>> The last two lines are the source of the problem, at least as far as I
>>> can tell. This results in LOTS of these lines as Corosync continues to
>>> try working:
>>> Feb 13 09:45:44 corosync [TOTEM ] sendmsg(mcast) failed (non-critical):
>>> Socket operation on non-socket (88)
>>>
>>> I’m hopeful someone will be able to quickly point out the absolutely
>>> stupid mistake that I’m making.
>>>
>>> Thanks so much!
>>>
>>> Dan Barber
>>>
>>>
>>
>> corosync must be run as root.
>>
>> Regards
>> -steve
>> Steven,
>>
>> Thanks for the reply, my apologies that my first response was sent
>> directly to you. I am running "/etc/init.d/corosync start" as root, do I
>> need to do something else to make sure that corosync runs as root? I get
>> the same behavior from running "service corosync start" run as root,
>> which is understandable as I believe those are essentially identical
>> operations.
>>
>
>No problem. Also please don't top post - it makes following the threads
>difficult for followup readers of the thread archive.
>
>Which OS are you using? If RHEL/Fedora/centos, do you have selinux enabled?
>
>Can you run corosync-blackbox?
Steve,
Thanks again for the help, both on list protocol and the questions. It looks like it is
a selinux problem, I am running on centos. I'm working with our linux folks to try and
start making progress again, selinux isn't supposed to be enabled.
Thanks!
Dan
>
>> Thanks,
>>
>> Dan
>>
>> ------------------------------------------------------------------------
>> *From:* Steven Dake <sdake@xxxxxxxxxx>
>> *To:* Dan Barber <dandy_dan_1999@xxxxxxxxx>
>> *Cc:* "discuss@xxxxxxxxxxxx" <discuss@xxxxxxxxxxxx>
>> *Sent:* Tuesday, February 14, 2012 9:19 AM
>> *Subject:* Re: [corosync] Problems starting up Corosync
>>
>> On 02/14/2012 09:16 AM, Dan Barber wrote:
>>> I am having problems bringing up Corosync and hoping someone will see
>>> the stupid mistake that I’ve made. I’ve done a lot of searching for the
>>> error that I’m seeing, and haven’t found anything other than a reference
>>> to the line of the code which produces this error, which concerns me a
>>> little.
>>>
>>> Here’s the corosync.conf file that I’m using:
>>> # Please read the corosync.conf.5 manual page
>>> compatibility: whitetank
>>>
>>> totem {
>>> version: 2
>>> secauth: off
>>> threads: 0
>>> interface {
>>> ringnumber: 0
>>> bindnetaddr: 10.47.12.0
>>> mcastaddr: 226.94.1.1
>>> mcastport: 4000
>>> ttl: 1
>>> }
>>> }
>>>
>>> logging {
>>> fileline: off
>>> to_stderr: no
>>> to_logfile: yes
>>> to_syslog: yes
>>> logfile: /var/log/cluster/corosync.log
>>> debug: on
>>> timestamp: on
>>> logger_subsys {
>>> subsys: AMF
>>> debug: off
>>> }
>>> }
>>>
>>> amf {
>>> mode: disabled
>>> }
>>>
>>> And here is corosync.log from start up to the failure lines:
>>> Feb 13 09:45:36 corosync [MAIN ] Corosync Cluster Engine ('1.4.1'):
>>> started and ready to provide service.
>>> Feb 13 09:45:36 corosync [MAIN ] Corosync built-in features: nss dbus
>>> rdma snmp
>>> Feb 13 09:45:36 corosync [MAIN ] Successfully read main configuration
>>> file '/etc/corosync/corosync.conf'.
>>> Feb 13 09:45:36 corosync [TOTEM ] Token Timeout (1000 ms) retransmit
>>> timeout (238 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] token hold (180 ms) retransmits before
>>> loss (4 retrans)
>>> Feb 13 09:45:36 corosync [TOTEM ] join (50 ms) send_join (0 ms)
>>> consensus (1200 ms) merge (200 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] downcheck (1000 ms) fail to recv const
>>> (2500 msgs)
>>> Feb 13 09:45:36 corosync [TOTEM ] seqno unchanged const (30 rotations)
>>> Maximum network MTU 1402
>>> Feb 13 09:45:36 corosync [TOTEM ] window size per rotation (50 messages)
>>> maximum messages per rotation (17 messages)
>>> Feb 13 09:45:36 corosync [TOTEM ] missed count const (5 messages)
>>> Feb 13 09:45:36 corosync [TOTEM ] send threads (0 threads)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP token expired timeout (238 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP token problem counter (2000 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP threshold (10 problem count)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP multicast threshold (100 problem
>>> count)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP automatic recovery check timeout
>>> (1000 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] RRP mode set to none.
>>> Feb 13 09:45:36 corosync [TOTEM ] heartbeat_failures_allowed (0)
>>> Feb 13 09:45:36 corosync [TOTEM ] max_network_delay (50 ms)
>>> Feb 13 09:45:36 corosync [TOTEM ] HeartBeat is Disabled. To enable set
>>> heartbeat_failures_allowed > 0
>>> Feb 13 09:45:36 corosync [TOTEM ] Initializing transport (UDP/IP
>> Multicast).
>>> Feb 13 09:45:36 corosync [TOTEM ] Initializing transmit/receive
>>> security: libtomcrypt SOBER128/SHA1HMAC (mode 0).
>>> Feb 13 09:45:36 corosync [IPC ] you are using ipc api v2
>>> Feb 13 09:45:36 corosync [TOTEM ] Unable to bind the socket to receive
>>> multicast packets: Permission denied (13)
>>> Feb 13 09:45:36 corosync [TOTEM ] Could not set traffic priority: Socket
>>> operation on non-socket (88)
>>>
>>> The last two lines are the source of the problem, at least as far as I
>>> can tell. This results in LOTS of these lines as Corosync continues to
>>> try working:
>>> Feb 13 09:45:44 corosync [TOTEM ] sendmsg(mcast) failed (non-critical):
>>> Socket operation on non-socket (88)
>>>
>>> I’m hopeful someone will be able to quickly point out the absolutely
>>> stupid mistake that I’m making.
>>>
>>> Thanks so much!
>>>
>>> Dan Barber
>>>
>>>
>>
>> corosync must be run as root.
>>
>> Regards
>> -steve
_______________________________________________ discuss mailing list discuss@xxxxxxxxxxxx http://lists.corosync.org/mailman/listinfo/discuss
