When RHEL installs heartbeat, the following error occurs: heartbeat: udpport setting must precede media statements.

Source: Internet
Author: User

The environment is as follows:

[root@master ~]# cat /etc/redhat-release Red Hat Enterprise Linux Server release 5.5 (Tikanga)[root@master ~]# uname -aLinux master 2.6.18-194.el5 #1 SMP Tue Mar 16 21:52:39 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux[root@master ~]# 

Install Heartbeat-2.1.3 with the following error:

logd is already runningStarting High-Availability services: 2013/07/15_16:31:45 INFO:  Resource is stopped2013/07/15_16:31:45 INFO:  Resource is stopped                                                           [FAILED]heartbeat: udpport setting must precede media statementsheartbeat[4742]: 2013/07/15_16:31:45 ERROR: Invalid user id name [hacluster]heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Bad uid list [hacluster]heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Invalid apiauth directive [ipfail uid=hacluster]heartbeat[4742]: 2013/07/15_16:31:45 info: Syntax: apiauth client [uid=uidlist] [gid=gidlist]heartbeat[4742]: 2013/07/15_16:31:45 info: Where uidlist is a comma-separated list of uids,heartbeat[4742]: 2013/07/15_16:31:45 info: and gidlist is a comma-separated list of gidsheartbeat[4742]: 2013/07/15_16:31:45 info: One or the other must be specified.heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Invalid user id name [hacluster]heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Bad uid list [hacluster]heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Invalid apiauth directive [ccm uid=hacluster]heartbeat[4742]: 2013/07/15_16:31:45 info: Syntax: apiauth client [uid=uidlist] [gid=gidlist]heartbeat[4742]: 2013/07/15_16:31:45 info: Where uidlist is a comma-separated list of uids,heartbeat[4742]: 2013/07/15_16:31:45 info: and gidlist is a comma-separated list of gidsheartbeat[4742]: 2013/07/15_16:31:45 info: One or the other must be specified.heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Invalid group name [haclient]heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Bad gid list [haclient]heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Invalid apiauth directive [ping gid=haclient]heartbeat[4742]: 2013/07/15_16:31:45 info: Syntax: apiauth client [uid=uidlist] [gid=gidlist]heartbeat[4742]: 2013/07/15_16:31:45 info: Where uidlist is a comma-separated list of uids,heartbeat[4742]: 2013/07/15_16:31:45 info: and gidlist is a comma-separated list of gidsheartbeat[4742]: 2013/07/15_16:31:45 info: One or the other must be specified.heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Invalid group name [haclient]heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Bad gid list [haclient]heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Invalid apiauth directive [anon gid=haclient]heartbeat[4742]: 2013/07/15_16:31:45 info: Syntax: apiauth client [uid=uidlist] [gid=gidlist]heartbeat[4742]: 2013/07/15_16:31:45 info: Where uidlist is a comma-separated list of uids,heartbeat[4742]: 2013/07/15_16:31:45 info: and gidlist is a comma-separated list of gidsheartbeat[4742]: 2013/07/15_16:31:45 info: One or the other must be specified.heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Bad permissions on keyfile [/opt/heartbeat-2.1.3/etc/ha.d/authkeys], 600 recommended.heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Authentication configuration error.heartbeat[4742]: 2013/07/15_16:31:45 ERROR: Configuration error, heartbeat not started.


I couldn't understand what it meant, And then I checked it by google. I checked the original Installation Guide carefully and found that the authkeys Configuration File Permission must be 600,

Flash: Is it because of this? But it doesn't look like it ......


Despite the doubt, I tried it with the idea of taking care of the dead horse. oh my god, it really solved it!

[root@master ha.d]# service heartbeat start       logd is already runningStarting High-Availability services: 2013/07/15_16:33:41 INFO:  Resource is stopped2013/07/15_16:33:41 INFO:  Resource is stopped                                                           [  OK  ]

As for the reason, there is no time to study it in detail. If you are interested, try it.


Related Article

Contact Us

The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion; products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the content of the page makes you feel confusing, please write us an email, we will handle the problem within 5 days after receiving your email.

If you find any instances of plagiarism from the community, please send an email to: info-contact@alibabacloud.com and provide relevant evidence. A staff member will contact you within 5 working days.

A Free Trial That Lets You Build Big!

Start building with 50+ products and up to 12 months usage for Elastic Compute Service

  • Sales Support

    1 on 1 presale consultation

  • After-Sales Support

    24/7 Technical Support 6 Free Tickets per Quarter Faster Response

  • Alibaba Cloud offers highly flexible support services tailored to meet your exact needs.