tag:blogger.com,1999:blog-35243755.post9053760585466296752..comments2023-09-02T04:51:16.874-07:00Comments on The Linux Juggernaut: Heartbeat ClusteringSurendra Kumar Annehttp://www.blogger.com/profile/12971989109849579563noreply@blogger.comBlogger17125tag:blogger.com,1999:blog-35243755.post-75768599014640954272010-11-03T22:12:53.756-07:002010-11-03T22:12:53.756-07:00@Bharat.. Can you be more info.. I am not able to ...@Bharat.. Can you be more info.. I am not able to understand your question please give as much info as possible so that i can help you in this regard.<br /><br />Thanks,<br />Surendra.Surendra Kumar Annehttps://www.blogger.com/profile/12971989109849579563noreply@blogger.comtag:blogger.com,1999:blog-35243755.post-31464328575941749752010-10-29T04:42:30.450-07:002010-10-29T04:42:30.450-07:00I am having a 4 server private network with one pu...I am having a 4 server private network with one public virtual ip address problem is this ip is not binding to primary server as it is floating to other node first and then binding to primary server as such loosing data <br />using linux suse serverbharathttps://www.blogger.com/profile/18443463131376870813noreply@blogger.comtag:blogger.com,1999:blog-35243755.post-31512305312097266542010-10-29T04:39:27.590-07:002010-10-29T04:39:27.590-07:00my virtual ip address is not stabling in n nodes t...my virtual ip address is not stabling in n nodes to primary server as it first binds to other and then to primary server how can i stop it please tell <br />Thanksbharathttps://www.blogger.com/profile/18443463131376870813noreply@blogger.comtag:blogger.com,1999:blog-35243755.post-14118521017352154572010-09-14T09:00:12.113-07:002010-09-14T09:00:12.113-07:00@anony.. ya thats true.. you can just keep httpd
...@anony.. ya thats true.. you can just keep httpd <br />then check if you have httpd script in /etc/ha.d/resource.d/ then only it will workSurendra Kumar Annehttps://www.blogger.com/profile/12971989109849579563noreply@blogger.comtag:blogger.com,1999:blog-35243755.post-35750631686953113622010-09-14T01:58:29.534-07:002010-09-14T01:58:29.534-07:00How can i setup heartbeat cluster using web servic...How can i setup heartbeat cluster using web service not squid? Do i change this parameter? rp1.linuxnix.com 10.77.225.20 squid to rp1.linuxnix.com 10.77.225.20 httpd? TahnksAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-35243755.post-80897418935663534032010-09-14T01:56:05.030-07:002010-09-14T01:56:05.030-07:00How can i configure Heartbeat cluster web service ...How can i configure Heartbeat cluster web service not squid? Do i change rp1.linuxnix.com 10.77.225.20 squid to rp1.linuxnix.com 10.77.225.20 httpd ? Thanks!Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-35243755.post-89917103725781823232010-02-18T06:54:56.694-08:002010-02-18T06:54:56.694-08:00Thanks Surender for timely response.
I have fixed...Thanks Surender for timely response.<br /><br />I have fixed all the issues. The problem is my crossover cable IP's are not communicating properly. There is some issue with network. So I finished the cluster configuration with single NICs.<br /><br />Regards,<br />UKAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-35243755.post-45018412092402460772010-02-15T21:34:51.170-08:002010-02-15T21:34:51.170-08:00Please see in line..
Regd. issue#1, as you mentio...Please see in line..<br /><br />Regd. issue#1, as you mentioned in your blog-step#7, started heartbeat on both node1 and node2. Somehow both the machines are showing eth0:0 and the last started service (i.e. node2) is active and able to access the server with clusterIP. But when I stop it on node2, though node1 show eth0:0 it is not picking up. looks like it is not switching properly...<br /><br /><br />>> THATS COOL AND YOUR HEARTBEAT CLUSTER IS WORKING VERY WELL.. FOR YOUR ISSUE THINK IN THIS WAY.. I HAVE TWO NODES.. ONE ACTIVE NODE AND OTHER PASIVE.. WHEN PASIVE WILL GET UP?.. PASIVE WILL GET UP WHEN PASIVE IS NOT RECEIVING HEARTBEAT PULSE FROM ACTIVE NODE(THROUGH ETH1). SO WHAT YOUR PASIVE NODE IS THINKING? IT JUST THINKS THAT ACTIVE NODE WENT DOWN, SO I(PASIVE) HAVE TO START SMB SERVICE HERE AND IT(PASIVE NODE) WILL TAKE INITIATING OF CREATING ETH0:0 TOO.. THAT IS THE REASON YOU ARE SEEING ETH0:0 ON BOTH THE NODES..<br />SO HOW TO RESOLVE THIS ISSUE?<br />FROM MY UNDERSTANDING THERE IS NO PROPER COMMUNICATION BETWEEN ETH1 OF BOTH NODES.. PLEASE CHECK THAT CONFIGURATION.. DID YOU USED CROSS CABLE TO CONNECT ETH1 OF BOTH THE NODES?<br />LET ME KNOW..<br /><br />I WILL POST ONE MORE POST ON HOW TO TRUBLESHOOT HEARTBEAT CLUSTER BY THIS WEEKEND.. MAY BE THAT WILL BE MORE USEFULL TO YOU..<br />AND THANKS FOR WRITING TO LINUXNIX.COMSurendra Kumar Annehttps://www.blogger.com/profile/12971989109849579563noreply@blogger.comtag:blogger.com,1999:blog-35243755.post-23347460321861853432010-02-15T21:23:35.386-08:002010-02-15T21:23:35.386-08:00Please see in line..
Please update step 4 (a &...Please see in line..<br /><br />Please update step 4 (a & b). Both are mentioned for node 1. I think 4(b) is for node 2,<br /><br />>>> THE CONFIGURATION SHOULD BE SAME ON BOTH THE NODES.. BECAUSE THIS IS MY MASTER NODE.. lET ME PUT IT IN THIS WAY.. SUPPOSE NODE1(ACTIVE) WENT DOWN, NODE TWO(PACIVE) WILL TAKE CARE OF SERVING SMB.. THIS NODE TWO WILL CONTUNIOUSLY SENDING HERTBEAT PULSE TO MASTER NODE TO CHECK THE STAUS.. ONCE NODE1 IS UP NODE TWO WILL CONSIDER THE CONFIG IN THIS STEP4 TO CHECK TO HOW TO TRANSFER THE CONTROL..Surendra Kumar Annehttps://www.blogger.com/profile/12971989109849579563noreply@blogger.comtag:blogger.com,1999:blog-35243755.post-84512499455315036622010-02-15T15:42:56.460-08:002010-02-15T15:42:56.460-08:00Please update step 4 (a & b). Both are mention...Please update step 4 (a & b). Both are mentioned for node 1. I think 4(b) is for node 2,Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-35243755.post-35385112607063253502010-02-15T10:13:53.175-08:002010-02-15T10:13:53.175-08:00********************************
/var/log/ha-log ...********************************<br />/var/log/ha-log on node2 (next started):<br /> info: Heartbeat generation: 1265931585<br /> info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth1<br /> info: glib: UDP Broadcast heartbeat closed on port 694 interface eth1 - Status: 1<br /> info: glib: ucast: write socket priority set to IPTOS_LOWDELAY on eth1<br /> info: glib: ucast: bound send socket to device: eth1<br /> info: glib: ucast: bound receive socket to device: eth1<br /> info: glib: ucast: started on port 694 interface eth1 to 10.14.2.132<br /> info: G_main_add_TriggerHandler: Added signal manual handler<br /> info: G_main_add_TriggerHandler: Added signal manual handler<br /> info: G_main_add_SignalHandler: Added signal handler for signal 17<br /> info: Local status now set to: 'up'<br /> info: Link nft80fs01b:eth1 up.<br /><b>WARN: node nft80fs01a: is dead</b><br />info: Comm_now_up(): updating status to active<br /> info: Local status now set to: 'active'<br /> WARN: No STONITH device configured.<br /> WARN: Shared disks are not protected.<br /> info: Resources being acquired from nft80fs01a.<br />info: Running /etc/ha.d/rc.d/status status<br />info: No local resources [/usr/share/heartbeat/ResourceManager listkeys nft80fs01b] to acquire.<br />info: Taking over resource group 172.25.41.153<br />ResourceManager[22155]: 2010/02/15_17:56:58 info: Acquiring resource group: nft80fs01a 172.25.41.153 smb<br />IPaddr[22182]: 2010/02/15_17:56:58 INFO: Resource is stopped<br />ResourceManager[22155]: 2010/02/15_17:56:58 info: Running /etc/ha.d/resource.d/IPaddr 172.25.41.153 start<br />IPaddr[22255]: 2010/02/15_17:56:58 INFO: Using calculated nic for 172.25.41.153: eth0<br />IPaddr[22255]: 2010/02/15_17:56:58 INFO: Using calculated netmask for 172.25.41.153: 255.255.255.0<br />IPaddr[22255]: 2010/02/15_17:56:58 INFO: eval ifconfig eth0:0 172.25.41.153 netmask 255.255.255.0 broadcast 172.25.41.255<br />IPaddr[22238]: 2010/02/15_17:56:58 INFO: Success<br />ResourceManager[22155]: 2010/02/15_17:56:58 info: Running /etc/ha.d/resource.d/smb start<br />mach_down[22129]: 2010/02/15_17:56:58 info: /usr/share/heartbeat/mach_down: nice_failback: foreign resources acquired<br />mach_down[22129]: 2010/02/15_17:56:58 info: mach_down takeover complete for node nft80fs01a.<br /> info: mach_down takeover complete.<br /> info: Initial resource acquisition complete (mach_down)<br /> info: Local Resource acquisition completed. (none)<br /> info: local resource transition completed.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-35243755.post-71801003091641902372010-02-15T10:13:35.647-08:002010-02-15T10:13:35.647-08:00see /var/log/ha-log on node1 (1st started):
info...see /var/log/ha-log on node1 (1st started):<br /> info: Heartbeat generation: 1265931455<br /> info: glib: UDP Broadcast heartbeat started on port 694 (694) interface eth1<br /> info: glib: UDP Broadcast heartbeat closed on port 694 interface eth1 - Status: 1<br /> info: glib: ucast: write socket priority set to IPTOS_LOWDELAY on eth1<br /> info: glib: ucast: bound send socket to device: eth1<br /> info: glib: ucast: bound receive socket to device: eth1<br /> info: glib: ucast: started on port 694 interface eth1 to 10.14.2.131<br /> info: G_main_add_TriggerHandler: Added signal manual handler<br /> info: G_main_add_TriggerHandler: Added signal manual handler<br /> info: G_main_add_SignalHandler: Added signal handler for signal 17<br /> info: Local status now set to: 'up'<br /> info: Link nft80fs01a:eth1 up.<br /> WARN: node nft80fs01b: is dead<br /> info: Comm_now_up(): updating status to active<br /> info: Local status now set to: 'active'<br /> WARN: No STONITH device configured.<br /> WARN: Shared disks are not protected.<br /> info: Resources being acquired from nft80fs01b.<br /> info: Running /etc/ha.d/rc.d/status status<br /> info: /usr/share/heartbeat/mach_down: nice_failback: foreign resources acquired<br /> info: mach_down takeover complete for node nft80fs01b.<br /> info: mach_down takeover complete.<br /> info: Initial resource acquisition complete (mach_down)<br />IPaddr[17702]: INFO: Resource is stopped<br />heartbeat[17611]: info: Local Resource acquisition completed.<br />harc[17753]: info: Running /etc/ha.d/rc.d/ip-request-resp ip-request-resp<br />ip-request-resp[17753]: received ip-request-resp 172.25.41.153 OK yes<br />ResourceManager[17774]: info: Acquiring resource group: nft80fs01a 172.25.41.153 smb<br />IPaddr[17801]: INFO: Resource is stopped<br />ResourceManager[17774]: info: Running /etc/ha.d/resource.d/IPaddr 172.25.41.153 start<br />IPaddr[17874]: INFO: Using calculated nic for 172.25.41.153: eth0<br />IPaddr[17874]: INFO: Using calculated netmask for 172.25.41.153: 255.255.255.0<br />IPaddr[17874]: INFO: eval ifconfig eth0:0 172.25.41.153 netmask 255.255.255.0 broadcast 172.25.41.255<br />IPaddr[17857]: INFO: Success<br />ResourceManager[17774]: info: Running /etc/ha.d/resource.d/smb start<br />info: Local Resource acquisition completed. (none)<br />info: local resource transition completed.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-35243755.post-38769208733592292522010-02-15T10:04:12.739-08:002010-02-15T10:04:12.739-08:00Excellent. Thanks for your quick response.
Regd. ...Excellent. Thanks for your quick response.<br /><br />Regd. issue#1, as you mentioned in your blog-step#7, started heartbeat on both node1 and node2. Somehow both the machines are showing eth0:0 and the last started service (i.e. node2) is active and able to access the server with clusterIP. But when I stop it on node2, though node1 show eth0:0 it is not picking up. looks like it is not switching properly...<br /><br />Start heartbeat on node1<br />start heartbeat on node2<br />observation:<br />clusterIP on node2 is active. If I stop it on node2 still the clusterIP not accessible from node1.<br /><br />FYI: I am using heartbeat for smb service.<br /><br />Please let me know if there is any issue in my configs.<br /><br />-UKAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-35243755.post-38478171234019701322010-02-12T08:11:25.098-08:002010-02-12T08:11:25.098-08:00>>PLEASE SEE IN LINE..
I have configured a 2...>>PLEASE SEE IN LINE..<br />I have configured a 2-node cluster as per the steps and everything looks good.<br />But in my setup, both the nodes are giving Floating IP for eth0:0. Is it ok? or Something wrong in my config? Please clarify.<br />>>> IT SHOULD NOT HAPPEN.. AT A GIVEN TIME ONLY ACTIVE NODE SHOULD HAVE eth0:0 CONFIGURED..<br />TO TROUBLESHOOT CLUSTER.. DO AS BELOW..<br />1)STOP THE HEARTBEAT CLUSTER ON ACTIVE NODE.. THE SECONDARY NODE SHOULD TAKE CARE OF STARTING THE DEPENDENT SERVICE..<br />AND eth0:0 SHOULD COME.. IF THIS WORKS FINE I THINK EVERY THING FINE..<br />CHECK THE LOGS OF HEARTBEAT.. MAY BE YOU WILL GET SOME INFO..<br /><br />One more thing how to say the setup is configured as Active-Active OR Active-Passive? Please clarify.<br />>>>LOAD BALANCING CLUSTER IS CALLED ACTIVE-ACTIVE WHERE AS HA IS CALLED ACTIVE-PASSIVE..<br />Regards,<br />UKSurendra Kumar Annehttps://www.blogger.com/profile/12971989109849579563noreply@blogger.comtag:blogger.com,1999:blog-35243755.post-55088928539505810182010-02-12T07:32:43.567-08:002010-02-12T07:32:43.567-08:00Hi Surender,
First of all thank you very much for ...Hi Surender,<br />First of all thank you very much for the detailed steps.<br /><br />I have configured a 2-node cluster as per the steps and everything looks good. <br />But in my setup, both the nodes are giving Floating IP for eth0:0. Is it ok? or Something wrong in my config? Please clarify.<br /><br />One more thing how to say the setup is configured as Active-Active OR Active-Passive? Please clarify.<br /><br />Regards,<br />UKAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-35243755.post-70239210416080159762010-02-08T08:57:47.629-08:002010-02-08T08:57:47.629-08:00Please see in line..
1) wether web server sevi...Please see in line..<br /> 1) wether web server sevice will have to run on both machines or not?<br />>>NO NEED YOU TO RUN THE SERVER SERVICE ON ANY NODE.. HEARTBEAT CLUSTER WILL TAKE CARE OF RUNNING THE SERVICE FOR YOU.. AND ONE MORE THING HEARTBEAT WILL TAKECARE OF RUNNING THE SERVICE ON ACTIVE NODE AND IT WILL TAKE CARE OF STOPING THE SERVICE ON PASIVE NODE.<br /> 2) how would i connect those two ethernet interfaces to each other and to local switch (need a diagram of lan canling between servers and switch)<br />>>>ETH1 ON BOTH THE SYSTEMS ARE DIRECTLY CONNECTED WITH A CROSS CABLE.. AND ETH0 ARE CONNECTED TO A SWITCH DIRECTLY..<br /> 3) configuration realted to squid<br />>>> EDITED THE POST TO POINT TO SQUID CONFIGURATION..<br /> If you provide me this information i think i can setup a cluster with easeSurendra Kumar Annehttps://www.blogger.com/profile/12971989109849579563noreply@blogger.comtag:blogger.com,1999:blog-35243755.post-32916812453139973392010-02-03T00:24:07.509-08:002010-02-03T00:24:07.509-08:00i have gone through your doc, you made it really l...i have gone through your doc, you made it really look simple and now i am all set to make a clusture for a web server but, there are some points to be reach.<br /> 1) wether web server sevice will have to run on both machines or not?<br /> 2) how would i connect those two ethernet interfaces to each other and to local switch (need a diagram of lan canling between servers and switch)<br /> 3) configuration realted to squid<br /> If you provide me this information i think i can setup a cluster with easeUnknownhttps://www.blogger.com/profile/10147462442086552041noreply@blogger.com