I am running an older version 2.1.4 for the prototype, but will update everything to the latest stable when launching. Also I am going through the list of error and warnings, and googling... Please be patient with me, this is my first time with LVS.
Cheers, Nicholas. On Mon, Sep 5, 2011 at 1:13 PM, Nick Khamis <[email protected]> wrote: > Hello, > > Thank you so much for your response. Basically what I am trying to do > is setup a mysql cluster via direct routing: > > lb1 > Heartbeat + ldirectord > IP Address: 192.168.2.101 eth0 > > lb2 > Heartbeat + ldirectord > IP Address: 192.168.2.102 eth0 > > lb1 + lb2 Configureation Files > > <ldirectord.cf> > > #Global Directives > #checktimeout=10 > checkinterval=2 > autoreload=no > logfile="/var/log/ldirectord.log" > quiescent=yes > virtual = 192.168.2.100:3306 > service = mysql > real = 192.168.2.104:3306 gate > real = 192.168.2.105:3306 gate > checktype = negotiate > login = "ldirector" > passwd = "Shlemon1" > database = "ldirectordb" > request = "SELECT * FROM connectioncheck" > scheduler = wrr > > <ha.cf> > crm respawn > logfacility local0 > bcast eth0 > mcast eth0 225.0.0.1 694 1 0 > auto_failback off > node lb1 > node lb2 > respawn hacluster /usr/local/heartbeat/lib/heartbeat/ipfail > apiauth ipfail gid=haclient uid=hacluster > keepalive 2 > deadtime 11 > debugfile /var/log/ha-debug > logfile /var/log/ha-log > logfacility daemon > > <haresources> > > lb1 \ > ldirectord::ldirectord.cf \ > LVSSyncDaemonSwap::master \ > IPaddr2::192.168.2.100/24/eth2/192.168.2.255 > > > > mysq1 > IP Address 192.168.2.104 eth0 > > mysql2 > IP Address 192.168.2.105 eth0 > > >>What you should do is use several links, like >>bcast ethx >>mcast eth2 ... >>ucast eth3 ... > > > My questions are: > > 1) The machine only has one interface. Am I still able to set bcast, > mcast, and ucast to ethx, eth2, and eth3? I was following the > directions from > "http://www.howtoforge.com/loadbalanced_mysql_cluster_debian_p6";, and > they specified bcast and mcast on the same interface. > 2) When I get this working smoothly, am I able to add another virtual > and service to ldirector? Say for eample pgsql? > 3) Will the load balancers ever act as a bottleneck to the cluster, > and if so how do we handle such an issue. > > In respect to the warnings, and errors that I am seeing in the log file: > > heartbeat[9193]: 2011/09/05_17:04:08 ERROR: api_process_request: bad > request [getrsc] > heartbeat[9193]: 2011/09/05_17:04:08 ERROR: MSG: Dumping message with 5 fields > heartbeat[9193]: 2011/09/05_17:04:08 ERROR: MSG[0] : [t=hbapi-req] > heartbeat[9193]: 2011/09/05_17:04:08 ERROR: MSG[1] : [reqtype=getrsc] > heartbeat[9193]: 2011/09/05_17:04:08 ERROR: MSG[2] : [dest=lb1] > heartbeat[9193]: 2011/09/05_17:04:08 ERROR: MSG[3] : [pid=9210] > heartbeat[9193]: 2011/09/05_17:04:08 ERROR: MSG[4] : [from_id=ipfail] > heartbeat[9193]: 2011/09/05_17:04:08 WARN: Managed > /usr/local/heartbeat/lib/heartbeat/ipfail process 9210 exited with > return code 100. > > cib[9204]: 2011/09/05_17:04:08 ERROR: socket_wait_conn_new: unlink > failure(/var/run/heartbeat/crm/cib_callback): Permission denied > cib[9204]: 2011/09/05_17:04:08 ERROR: socket_wait_conn_new: trying to > create in /var/run/heartbeat/crm/cib_callback bind:: Permission denied > cib[9204]: 2011/09/05_17:04:08 ERROR: Can't create wait channel of > type uds: Permission denied > heartbeat[9193]: 2011/09/05_17:04:08 WARN: Managed > /usr/local/heartbeat/lib/heartbeat/cib process 9204 exited with return > code 1. > heartbeat[9193]: 2011/09/05_17:04:08 ERROR: Respawning client > "/usr/local/heartbeat/lib/heartbeat/cib": > heartbeat[9193]: 2011/09/05_17:04:08 info: Starting child client > "/usr/local/heartbeat/lib/heartbeat/cib" (1000,1002) > heartbeat[9193]: 2011/09/05_17:04:09 info: Status update for node lb2: > status active > mgmtd[9209]: 2011/09/05_17:04:09 info: login to cib: 1, ret:-10 > crmd[9208]: 2011/09/05_17:04:09 WARN: do_cib_control: Couldn't > complete CIB registration 1 times... pause and retry > crmd[9208]: 2011/09/05_17:04:09 info: crmd_init: Starting crmd's mainloop > heartbeat[9213]: 2011/09/05_17:04:09 info: Starting > "/usr/local/heartbeat/lib/heartbeat/cib" as uid 1000 gid 1002 (pid > 9213) > cib[9213]: 2011/09/05_17:04:09 info: G_main_add_SignalHandler: Added > signal handler for signal 15 > cib[9213]: 2011/09/05_17:04:09 info: G_main_add_TriggerHandler: Added > signal manual handler > cib[9213]: 2011/09/05_17:04:09 info: G_main_add_SignalHandler: Added > signal handler for signal 17 > cib[9213]: 2011/09/05_17:04:09 info: main: Retrieval of a per-action > CIB: disabled > cib[9213]: 2011/09/05_17:04:09 ERROR: crm_is_writable: > /var/lib/heartbeat/crm must be owned and r/w by user cluster > cib[9213]: 2011/09/05_17:04:09 info: retrieveCib: Reading cluster > configuration from: /var/lib/heartbeat/crm/cib.xml (digest: > /var/lib/heartbeat/crm/cib.xml.sig) > cib[9213]: 2011/09/05_17:04:09 WARN: retrieveCib: Cluster > configuration not found: /var/lib/heartbeat/crm/cib.xml > cib[9213]: 2011/09/05_17:04:09 WARN: readCibXmlFile: Primary > configuration corrupt or unusable, trying backup... > cib[9213]: 2011/09/05_17:04:09 info: retrieveCib: Reading cluster > configuration from: /var/lib/heartbeat/crm/cib.xml.last (digest: > /var/lib/heartbeat/crm/cib.xml.sig.last) > cib[9213]: 2011/09/05_17:04:09 WARN: retrieveCib: Cluster > configuration not found: /var/lib/heartbeat/crm/cib.xml.last > cib[9213]: 2011/09/05_17:04:09 WARN: readCibXmlFile: Continuing with > an empty configuration. > cib[9213]: 2011/09/05_17:04:09 WARN: readCibXmlFile: No value for > admin_epoch was specified in the configuration. > cib[9213]: 2011/09/05_17:04:09 WARN: readCibXmlFile: The reccomended > course of action is to shutdown, run crm_verify and fix any errors it > reports. > cib[9213]: 2011/09/05_17:04:09 WARN: readCibXmlFile: We will default > to zero and continue but may get confused about which configuration to > use if multiple nodes are powered up at the same time. > > cib[9213]: 2011/09/05_17:04:09 ERROR: socket_wait_conn_new: unlink > failure(/var/run/heartbeat/crm/cib_callback): Permission denied > cib[9213]: 2011/09/05_17:04:09 ERROR: socket_wait_conn_new: trying to > create in /var/run/heartbeat/crm/cib_callback bind:: Permission denied > cib[9213]: 2011/09/05_17:04:09 ERROR: Can't create wait channel of > type uds: Permission denied > > > ccm[9203]: 2011/09/05_17:04:08 ERROR: Cannot chdir to > [/var/lib/heartbeat/cores/cluster]: Permission denied > > cib[9204]: 2011/09/05_17:04:08 WARN: readCibXmlFile: No value for > admin_epoch was specified in the configuration. > cib[9204]: 2011/09/05_17:04:08 WARN: readCibXmlFile: The reccomended > course of action is to shutdown, run crm_verify and fix any errors it > reports. > cib[9204]: 2011/09/05_17:04:08 WARN: readCibXmlFile: We will default > to zero and continue but may get confused about which configuration to > use if multiple nodes are powered up at the same time. > > heartbeat[3857]: 2011/09/05_15:38:05 WARN: Logging daemon is disabled > --enabling logging daemon is recommended > > mgmtd[9209]: 2011/09/05_17:04:08 WARN: Core dumps could be lost if > multiple dumps occur. > mgmtd[9209]: 2011/09/05_17:04:08 WARN: Consider setting non-default > value in /proc/sys/kernel/core_pattern (or equivalent) for maximum > supportability > mgmtd[9209]: 2011/09/05_17:04:08 WARN: Consider setting > /proc/sys/kernel/core_uses_pid (or equivalent) to 1 for maximum > supportability > > > Your help is greatly appreciated, > > Nick. > _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
