Ha-cluster Issues with INSSLR

[haridas]

Hi,


It seems that some problems while configuring INSSLR under Fail-over mode. This was happened after I branched the appliance and resized the boot and user volumes to add some softwares from the yum repository.

I noticed this error after starting the application,it seems that both INSSLR activated the public IP on eth0:0 Ethernet interface, But when I ping the public ip from outside there is no collision, and I found which INSSLR hold the public IP by tcpdump. Why this is happening, and I tried to add more public IP's under the INSSLR to support multiple ssl keys, so at this time the problem might be worse. Please helps me to figure out the issues and how we can add and update multiple IP's with HA-cluster or Fail-over mode.


Thanks,
Haridas N,
Sparksupport (http://sparksupport.com)

[PavelGeorgiev]

Haridas,

It would help if you could provide the following info:
1) Did you have this problem before branching the appliances?
2) What changes did you make to the appliance files (you can attach the changed files here)?
3) What is the current configuration for both appliances?
4) Whats in /etc/ha.d/ha.cf and /etc/ha.d/haresources of each appliance after you start them.

Regards,
Pavel

[haridas]

Hi PavelGeorgiev,

Thanks for your reply.

I tested this with out branching, at that time it shows normal functioning. After branching the inconsistency with fail-over were started. What I did on INSSLR appliance is

1) There is no problem with fail-over when the appliances are running without branching.

2) I didn't changed any appliance system files , only installed gcc to compile some c files.

3) After branching I noticed this error.

I couldn't able upload the files with size more than 200B. So I past it here.

--------------
INSSLR1
--------------

ha.cf

keepalive 1
deadtime 10
auto_failback off
logfacility daemon
warntime 5
initdead 60
hbgenmethod time
ucast eth0 192.168.1.9
node 192-168-1-8 192-168-1-9

haresources

192-168-1-8 IPaddr::64.87.40.52/255.255.255.240/eth0 nginx ApplogicNotify


--------------
INSSLR2
--------------

ha.cf

keepalive 1
deadtime 10
auto_failback off
logfacility daemon
warntime 5
initdead 60
hbgenmethod time
ucast eth0 192.168.1.8
node 192-168-1-9 192-168-1-8

haresources

192-168-1-8 IPaddr::64.87.40.52/255.255.255.240/eth0 nginx ApplogicNotify

I hope you can understand the appliance specific configurations from above set of files.

Under this configuration both INSSLR activate the public IP on their eth0:0 interface, but the tcpdump shows that INSSLR1 is currently holding the public IP.

What I'm trying is to add multiple IP's(It's now working for me.) and activate the fail-over feature to them.

Thanks,
Haridas N,
Sparksupport.

[haridas]

Hi everyone,

I resolved the problems with the INSSLR, it seems that if both INSSLR being activating the same public IP means the local IP used by these two INSSLR were under collision. That means some other applications are using the same local IP. Here you have to change the local IP's given for the for INSSLR to another one and try. Hope you will get the problem solved.