Tag Info

New answers tagged

0

It looks like I found out the answer to this. I needed to add the line proxy_set_header Host $host; right under the proxy_pass lines on my load balancer config files.


0

I looked into auto failover, using repmgr, a few months back. It seems repmgr is working as expected. IIRC repmgr doesn't bring an old master up as a new standby, you would need to run a "--force standby clone". You can set other standby nodes to follow a new master, should failover occur (repmgr standby follow). Would you expect your master to recover ...


0

"Remove" the problem website and then add it again along with the virtual directories from IIS Manager may help. It works in my case.


0

It looks like the problem is resolved. Both VMs had idendical MAC-Adresses for there network interfaces. Changed that, rebooted, works.


0

Option 1 is possible with additional servers, but I wouldn't consider using DFS for it. More likely is to use a DAS array / SAN or even some replication to make your application files accessible from both machines. You would then load balance the front end, with a load balancer that itself should be protected from failure by using redundant components or ...


0

It doesn't move because "change node" is not necessarily implied as part of recovering the resource. Apparently the cluster thinks node2 is the best place for them. Use migration-threshold and failure-timeout to control when resources need to be moved away and when they can come back. Also note that a failed start operation is one case where we will ...


1

You're going to have to setup a common storage that both can access at the same time, even when one goes down. I think you can point users' home directory to a network path, in which case you can setup a third system just for broadcasting the storage or a NAS. Otherwise, if they needs to see the storage as local, then you can look into setting up a SAN or ...



Top 50 recent answers are included