Error Illegal Directive In /etc/ha.d/ha.cf
enabled between nodes, enables or disables certain features, and optionally lists the cluster nodes by host name.This file can safely be made world readable, but should be writable only by root.Global directivesSome directives in ha.cf are global in nature. The order of these global options is important in configuring the ha.cf file, since each directive is interpreted as it is encountered in ha.cf.These directives are use_logd and udpport. It is recommended that these be placed first in the ha.cf file when they are entered.Other directives in this category are baud, logfacility, logfile, and debugfile, but those directives are deprecated and should no longer be used.Supported directivesThe following directives are supported in ha.cf (listed here in alphabetical order): apiauth This directive specifies what users and/or groups are allowed to connect to a specific API group name. The syntax is simple:apiauth apigroupname [uid=uid1,uid2 ...] [gid=gid1,gid2 ...]You can specify either a uid list, or a gid list, or both. However you must specify either a uid list or a gid list. If you include both a uid list and a gid list, then a process is authorized to connect to that API group if if it is either in the uid-list or it is in the gid-list.The API group name default has special meaning. If it is specified, it will be used for authorizing clients without any API group name, and all client groups not identified by any other apiauth directive.Unless you specify otherwise in the ha.cf file, certain services will be provided default authorizations as follows:Table A.1. Default service authorizationsServiceDefault apiauthipfailuid=haclusterccmgid=haclientpinggid=haclientcl_statusgid=haclientlha-snmpagentuid=rootcrmuid=hacluster autojoin The autojoin directive enables nodes to join automatically just by communicating with the cluster, hence not requiring node directives in the ha.cf file. Since our communication is normally strongly authenticated, only nodes which know the cluster key can join (automatically or otherwise).The values you can give for the autojoin directive have the following meanings:none: disables automatic joining.other: allows nodes other than ourself who are not listed in ha.cf to join automatically. In other words, our node has to be listed in ha.cf, but other nodes do not.an
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Heartbeat on Centos linux error message up vote 0 down vote favorite this http://www.linux-ha.org/doc/man-pages/re-hacf.html is the error message I get: heartbeat[22269]: 2012/03/21_07:36:55 ERROR: Illegal directive [unicast] in /etc/ha.d/ha.cf heartbeat[22269]: 2012/03/21_07:36:55 ERROR: Heartbeat not started: configuration error. heartbeat[22269]: 2012/03/21_07:36:55 ERROR: Configuration error, heartbeat not started. this is my ha.cf file: logfile /var/log/ha-log ###logfacility local0 keepalive 1 deadtime 10 initdead 90 udpport 694 unicast eth0 "node02_IP_Address auto_failback on node node01 node node02 ###respawn hacluster /usr/lib/heartbeat/ipfail any idea thanks, E. linux centos heartbeat share|improve this question edited Mar 21 '12 at 8:48 Janne Pikkarainen http://serverfault.com/questions/371863/heartbeat-on-centos-linux-error-message 25.1k23157 asked Mar 21 '12 at 8:42 edotan 62142043 add a comment| 2 Answers 2 active oldest votes up vote 6 down vote accepted The directive for Unicast is 'ucast' not 'unicast: logfile /var/log/ha-log ###logfacility local0 keepalive 1 deadtime 10 initdead 90 udpport 694 ucast eth0 node02_IP_Address auto_failback on node node01 node node02 ###respawn hacluster /usr/lib/heartbeat/ipfail share|improve this answer edited Mar 21 '12 at 11:54 answered Mar 21 '12 at 8:48 JapyDooge 31815 1 Thanks!!!!!!!!1 –edotan Mar 21 '12 at 9:04 add a comment| up vote 2 down vote As the error message you get states, unicast is not a valid configuration option. You should use ucast instead, if my memory serves me right. share|improve this answer answered Mar 21 '12 at 8:50 Janne Pikkarainen 25.1k23157 Thanks!!!!!!!!1 –edotan Mar 21 '12 at 9:04 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Sign up using Facebook Sign up using Email and Password Post as a guest Name Email Post as a guest Name Email discard By posting your answer, you agree to the privacy policy and terms of service. Not the answer you're looking for? Browse other questions tagged linux centos heartbeat or ask your own question. asked 4 years ago viewed 947 times active 4 years ago Blog Stack Overflow Podcast # 90 - Develope
I'm having some problem with configuren load-balanced mysql-cluster setup. I've followed the setps in How to set up A load-balanced Mysql Cluster. The first problem https://www.howtoforge.com/community/threads/problem-with-load-balanced-mysql-cluster.7297/ is with hearbeat. A get te following error: Code: heartbeat: 2006/10/06_16:00:01 ERROR: mcast [eth0] bad addr [255.0.0.1] heartbeat: 2006/10/06_16:00:01 ERROR: Illegal directive [respawm] in /etc/ha.d/ha.cf heartbeat: 2006/10/06_16:00:01 ERROR: Heartbeat not started: http://marc.info/?l=linux-ha-dev&m=108383391324167 configuration error. heartbeat: 2006/10/06_16:00:01 ERROR: Configuration error, heartbeat not started. when I comment these lines out in the ha.cf heartbeat will start and it looks like the load-balancers are running error illegal and all tests in the how-to are showing the right response. But when I want te connect from a other mahine with a mysql-client, I can't connect. After a portscan on the virtual ip of the loadbalancer I see that te mysql port is filtered (I'm not using a firewall). I've really no idea what is wrong? And if the first problem error illegal directive affects the second problem that I can't connect. This is my ha.cf file: Code: logfacility local0 bcast eth0 mcast eth0 255.0.0.1 694 1 0 auto_failback off node loadb1 node loadb2 respawm hacluster /usr/lib/heartbeat/ipfail apiauth ipfail gid=haclient uid=hacluster Some help will be very nice! MvdB, Oct 6, 2006 #1 falko Super Moderator ISPConfig Developer MvdB said: Code: logfacility local0 bcast eth0 mcast eth0 255.0.0.1 694 1 0 auto_failback off node loadb1 node loadb2 respawm hacluster /usr/lib/heartbeat/ipfail apiauth ipfail gid=haclient uid=hacluster Click to expand... You have a typo there. It must be Code: respaw[B][COLOR="Red"]n[/COLOR][/B] hacluster /usr/lib/heartbeat/ipfail falko, Oct 7, 2006 #2 MvdB New Member Aha Tnx! But has the error: Code: heartbeat: 2006/10/06_16:00:01 ERROR: mcast [eth0] bad addr [255.0.0.1] Anything to do with this typo? MvdB, Oct 11, 2006 #3 falko Super Moderator ISPConfig Developer MvdB said: Aha Tnx! But has the error: Code: heartbeat: 2006/10/06_16:00:01 ERROR: mcast [eth0] bad addr [255.0.0.1] Anything to do with this typo?Click to expand... You have another error in your ha.cf. It must be Code: mcast eth0 2[B][COLOR="Red"]2[/COLOR][/B]5.0.0.1 694 1 0 instead of Code: mcast eth0 2[B][COLOR="Red"]5[/COLOR
() verge ! net ! au [Download message RAW] Hi Jeff, thanks for your bug report. It is much appreciated. On Wed, May 05, 2004 at 08:19:55AM -0400, Jeffrey Layton wrote: > Package: heartbeat > Version: 1.2.0-2 > Severity: grave > Justification: renders package unusable > > Perhaps this is a problem with my configuration, but I don't think so. I tried > installing the latest heartbeat packages on some new machines I'm installing, > and got the following errors when trying to start it: > > # /usr/lib/heartbeat/heartbeat > heartbeat: ERROR: Illegal directive [ucast] in /etc/ha.d/ha.cf > heartbeat: ERROR: Invalid user id name [hacluster] > heartbeat: ERROR: Bad uid list [hacluster] in apiauth > heartbeat: ERROR: Invalid apiauth directive [ipfail uid=hacluster] > heartbeat: info: Syntax: apiauth [uid=uidlist] [gid=gidlist] > heartbeat: info: Where uidlist is a comma-separated list of uids, > heartbeat: info: and gidlist is a comma-separated list of gids > heartbeat: info: One or the other must be specified. > heartbeat: ERROR: Invalid user id name [hacluster] > heartbeat: ERROR: Bad uid list [hacluster] in apiauth > heartbeat: ERROR: Invalid apiauth directive [ccm uid=hacluster] > heartbeat: info: Syntax: apiauth [uid=uidlist] [gid=gidlist] > heartbeat: info: Where uidlist is a comma-separated list of uids, > heartbeat: info: and gidlist is a comma-separated list of gids > heartbeat: info: One or the other must be specified. > heartbeat: ERROR: Heartbeat not started: configuration error. > heartbeat: ERROR: Configuration error, heartbeat not started. > > My ha.cf file is very simple. Here it is: > > % grep -v ^# /etc/ha.d/ha.cf > logfacility local5 > ucast eth1 192.168.0.171 > auto_failback on > node angstrom > node zeeman Nice and simple :-) Unfortunately I have been unable to reproduce the behaviour that you describe above. What happens when you invoke heartbeat using /etc/init.d/heartbeat ? /usr/lib/heartbeat/heartbeat genrally isn't run directly. > I also tried the heartbeat 1.2.1 packages at: > > http://www.ultramonkey.org/download/heartbeat/ > > and they worked fine with the above configuration. > > My apologies if this is a prob