Hi,
what I understand you want split vhost on separate virtual ip adresses and
join all nodes into one cluster?
I dont think it is a good idea in case of web farm, as you mentioned it
wont scale so good. What if traffic on certain vhost (virtual ip) grow up
and you would need to spread it across
Hi,
it might be historical logs, which appeared during your configuration
process (in case of commit not completed config) . Have you tried to clean
up resource (I mean "crm resource cleanup NGINX_HA") ?
Try then stop|start|migrate resource, are Filed action still present ?
BTW: Try look into /v
Hi,
It seem to be problem with network traffic.
Have you tried to sniff network traffic to be sure that udp traffic reaches
from one node to another ??
Try on server1:
tcpdump -i interface -p udp -s 192.168.100.112
on server2:
tcpdump -i interface -p udp -s 192.168.100.111
if there will be
an the intended recipient's) is
> prohibited. If you receive this e-mail in error, please notify the sender
> by phone or email immediately and delete it!
> --
> *From:* and k [not4...@gmail.com]
> *Sent:* Wednesday, January 23, 2013 7:31 PM
> *To:* The Pacemak
ined herein in any way (including,
>> but not limited to, total or partial disclosure, reproduction, or
>> dissemination) by persons other than the intended recipient's) is
>> prohibited. If you receive this e-mail in error, please notify the sender
>> by phone or
Hello Everybody,
I've got a problem (but I am not quite sure if it is not a feature in
pacemaker ) that's why I decided to write on that mailing list.
It comes about migrate resource with collation in drbd resource.
I've got group including virtual IP and filesystem which is collated with
ms res
