Re: [users@httpd] Second apache as fallback server

2016-02-15 Thread Bob

Hello Yehuda,

Thanks for your response.

I'm still confused with log files. Say load balancer now put us on hot 
standby node. We already have some logs ( both access and error) at 
master node. How can we get all those logs as soon as we are on hot 
standby ?  We need unique log files for production clusters.


I wonder how cloud cluster address this issue !!



On Monday 15 February 2016 02:34 PM, Yehuda Katz wrote:
On Mon, Feb 15, 2016 at 9:24 AM, Bob > wrote:


The challenge is to maintain unique web server log across the
nodes. Any clue about that ?
Again for pages which send emails, all nodes must have running
postfix with same domain.
I'm also wondering how to do that.


To keep the configuration the same, look at Puppet 
(https://puppetlabs.com/puppet/puppet-open-source) or Chef (chef.io 
).
For log files, we use rsync to put all the logs on one machine after 
they are rotated. That means it may take 24 hours before the logs are 
received, but on servers that don't have shared storage, that it 
probably the easiest way.


- Y




Re: [users@httpd] Second apache as fallback server

2016-02-15 Thread Yehuda Katz
On Mon, Feb 15, 2016 at 9:24 AM, Bob  wrote:

> The challenge is to maintain unique web server log across the nodes. Any
> clue about that ?
> Again for pages which send emails, all nodes must have running postfix
> with same domain.
> I'm also wondering how to do that.
>

To keep the configuration the same, look at Puppet (
https://puppetlabs.com/puppet/puppet-open-source) or Chef (chef.io).
For log files, we use rsync to put all the logs on one machine after they
are rotated. That means it may take 24 hours before the logs are received,
but on servers that don't have shared storage, that it probably the easiest
way.

- Y


Re: [users@httpd] Second apache as fallback server

2016-02-15 Thread Bob

Dear John,

Thank you for sharing the ideas. Well, my servers are running with 
Linux. Hence haproxy with failover come closer to the requirement. As 
per the links you shared, seems  DNS route with two load balancing can 
do the job. four servers are required in total.


The challenge is to maintain unique web server log across the nodes. Any 
clue about that ?
Again for pages which send emails, all nodes must have running postfix 
with same domain.

I'm also wondering how to do that.

Thanks and regards,
Bob



On Monday 15 February 2016 01:32 PM, Meta Correio wrote:

Bob,

simple diagram for what you are looking for:

http://www.1stserv.com/images/Load-balancer-Setup1.png

And here is a more detailed document:

https://f5.com/resources/white-papers/load-balancing-101-nuts-and-bolts

If you're using MS Windows Server to host your Apache Servers you can 
look into using Microsoft NLB. It's a low cost solution that works 
fine and does not require any extra HW:


https://technet.microsoft.com/en-us/library/cc725691.aspx

About your questions:

>What can be done to assure the high-availability of the reverse proxy 
itself ?


User redundant LBs or MS NLB.

>What about the latency if the master and hot standby located in two 
different data center


I don't have that scenario so can't help you much with this question.
If you are looking into geographically distribute your application I 
would suggest the DNS route:


https://www.digitalocean.com/community/tutorials/how-to-configure-dns-round-robin-load-balancing-for-high-availability

Cheers,

John

On Mon, Feb 15, 2016 at 9:33 AM, Bob > wrote:


Hello John,

Could you please give me some more clue / pointers/ link ?

Please allow me repeating my questions again

What can be done to assure the high-availability of the reverse
proxy itself ?
What about the latency if the master and hot standby located in
two different data center ?




On Monday 15 February 2016 09:02 AM, Meta Correio wrote:

We have it implemented using and external, redundant , load
balancer.
It really comes down to your budget.

John

On Mon, Feb 15, 2016 at 8:58 AM, Bob > wrote:

Hello,

Thanks for the valuable suggestions.

What can be done to assure the high-availability of the
reverse proxy itself ?
What about the latency if the master and hot standby located
in two different data center ?



On Sunday 14 February 2016 10:43 PM, Yehuda Katz wrote:


We use three different methods:
1. Content on NFS server
2. Content auto-committing and auto-pulling over git about
every 15 minutes
3. Separate database server - with replication for backup.

- Y

Sent from a device with a very small keyboard and
hyperactive autocorrect.

On Feb 14, 2016 5:28 PM, "Rose, John B" > wrote:

What is your preferred approach to keeping content in sync?

Sent from my iPad

On Feb 14, 2016, at 3:47 PM, Daniel > wrote:


with a reverse proxy in front of both, you use balancer
setup specifying the second web server as hot standby

El dom., 14 feb. 2016 a las 16:49, Bob
(>)
escribió:

Hello list,

I have two servers. One is already up with apache,
mysql etc..
Now I wonder if I can configure the second server
as a fallback web server.
The idea is.. if first web server is down , the
second one will serve
the requests.

Any suggestion / idea is very much welcome.

Thanks and regards,
Bob


-
To unsubscribe, e-mail:

users-unsubscr...@httpd.apache.org

For additional commands, e-mail:
users-h...@httpd.apache.org












Re: [users@httpd] Second apache as fallback server

2016-02-15 Thread Meta Correio
Bob,

simple diagram for what you are looking for:

http://www.1stserv.com/images/Load-balancer-Setup1.png

And here is a more detailed document:

https://f5.com/resources/white-papers/load-balancing-101-nuts-and-bolts

If you're using MS Windows Server to host your Apache Servers you can look
into using Microsoft NLB. It's a low cost solution that works fine and does
not require any extra HW:

https://technet.microsoft.com/en-us/library/cc725691.aspx

About your questions:

>What can be done to assure the high-availability of the reverse proxy
itself ?

User redundant LBs or MS NLB.

>What about the latency if the master and hot standby located in two
different data center

I don't have that scenario so can't help you much with this question.
If you are looking into geographically distribute your application I would
suggest the DNS route:

https://www.digitalocean.com/community/tutorials/how-to-configure-dns-round-robin-load-balancing-for-high-availability

Cheers,

John

On Mon, Feb 15, 2016 at 9:33 AM, Bob  wrote:

> Hello John,
>
> Could you please give me some more clue / pointers/ link ?
>
> Please allow me repeating my questions again
>
> What can be done to assure the high-availability of the reverse proxy
> itself ?
> What about the latency if the master and hot standby located in two
> different data center ?
>
>
>
>
> On Monday 15 February 2016 09:02 AM, Meta Correio wrote:
>
> We have it implemented using and external, redundant , load balancer.
> It really comes down to your budget.
>
> John
>
> On Mon, Feb 15, 2016 at 8:58 AM, Bob  wrote:
>
>> Hello,
>>
>> Thanks for the valuable suggestions.
>>
>> What can be done to assure the high-availability of the reverse proxy
>> itself ?
>> What about the latency if the master and hot standby located in two
>> different data center ?
>>
>>
>>
>> On Sunday 14 February 2016 10:43 PM, Yehuda Katz wrote:
>>
>> We use three different methods:
>> 1. Content on NFS server
>> 2. Content auto-committing and auto-pulling over git about every 15
>> minutes
>> 3. Separate database server - with replication for backup.
>>
>> - Y
>>
>> Sent from a device with a very small keyboard and hyperactive autocorrect.
>> On Feb 14, 2016 5:28 PM, "Rose, John B"  wrote:
>>
>>> What is your preferred approach to keeping content in sync?
>>>
>>> Sent from my iPad
>>>
>>> On Feb 14, 2016, at 3:47 PM, Daniel < 
>>> dferra...@gmail.com> wrote:
>>>
>>> with a reverse proxy in front of both, you use balancer setup specifying
>>> the second web server as hot standby
>>>
>>> El dom., 14 feb. 2016 a las 16:49, Bob (< 
>>> bobnli...@gmail.com>) escribió:
>>>
 Hello list,

 I have two servers. One is already up with apache, mysql etc..
 Now I wonder if I can configure the second server as a fallback web
 server.
 The idea is.. if first web server is down , the second one will serve
 the requests.

 Any suggestion / idea is very much welcome.

 Thanks and regards,
 Bob

 -
 To unsubscribe, e-mail: 
 users-unsubscr...@httpd.apache.org
 For additional commands, e-mail: 
 users-h...@httpd.apache.org


>>
>
>


Re: [users@httpd] Second apache as fallback server

2016-02-15 Thread Bob

Hello John,

Could you please give me some more clue / pointers/ link ?

Please allow me repeating my questions again

What can be done to assure the high-availability of the reverse proxy 
itself ?
What about the latency if the master and hot standby located in two 
different data center ?





On Monday 15 February 2016 09:02 AM, Meta Correio wrote:

We have it implemented using and external, redundant , load balancer.
It really comes down to your budget.

John

On Mon, Feb 15, 2016 at 8:58 AM, Bob > wrote:


Hello,

Thanks for the valuable suggestions.

What can be done to assure the high-availability of the reverse
proxy itself ?
What about the latency if the master and hot standby located in
two different data center ?



On Sunday 14 February 2016 10:43 PM, Yehuda Katz wrote:


We use three different methods:
1. Content on NFS server
2. Content auto-committing and auto-pulling over git about every
15 minutes
3. Separate database server - with replication for backup.

- Y

Sent from a device with a very small keyboard and hyperactive
autocorrect.

On Feb 14, 2016 5:28 PM, "Rose, John B" > wrote:

What is your preferred approach to keeping content in sync?

Sent from my iPad

On Feb 14, 2016, at 3:47 PM, Daniel > wrote:


with a reverse proxy in front of both, you use balancer
setup specifying the second web server as hot standby

El dom., 14 feb. 2016 a las 16:49, Bob (>) escribió:

Hello list,

I have two servers. One is already up with apache, mysql
etc..
Now I wonder if I can configure the second server as a
fallback web server.
The idea is.. if first web server is down , the second
one will serve
the requests.

Any suggestion / idea is very much welcome.

Thanks and regards,
Bob


-
To unsubscribe, e-mail:
users-unsubscr...@httpd.apache.org

For additional commands, e-mail:
users-h...@httpd.apache.org









Re: [users@httpd] Second apache as fallback server

2016-02-15 Thread Meta Correio
We have it implemented using and external, redundant , load balancer.
It really comes down to your budget.

John

On Mon, Feb 15, 2016 at 8:58 AM, Bob  wrote:

> Hello,
>
> Thanks for the valuable suggestions.
>
> What can be done to assure the high-availability of the reverse proxy
> itself ?
> What about the latency if the master and hot standby located in two
> different data center ?
>
>
>
> On Sunday 14 February 2016 10:43 PM, Yehuda Katz wrote:
>
> We use three different methods:
> 1. Content on NFS server
> 2. Content auto-committing and auto-pulling over git about every 15 minutes
> 3. Separate database server - with replication for backup.
>
> - Y
>
> Sent from a device with a very small keyboard and hyperactive autocorrect.
> On Feb 14, 2016 5:28 PM, "Rose, John B"  wrote:
>
>> What is your preferred approach to keeping content in sync?
>>
>> Sent from my iPad
>>
>> On Feb 14, 2016, at 3:47 PM, Daniel < 
>> dferra...@gmail.com> wrote:
>>
>> with a reverse proxy in front of both, you use balancer setup specifying
>> the second web server as hot standby
>>
>> El dom., 14 feb. 2016 a las 16:49, Bob () escribió:
>>
>>> Hello list,
>>>
>>> I have two servers. One is already up with apache, mysql etc..
>>> Now I wonder if I can configure the second server as a fallback web
>>> server.
>>> The idea is.. if first web server is down , the second one will serve
>>> the requests.
>>>
>>> Any suggestion / idea is very much welcome.
>>>
>>> Thanks and regards,
>>> Bob
>>>
>>> -
>>> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
>>> For additional commands, e-mail: 
>>> users-h...@httpd.apache.org
>>>
>>>
>


Re: [users@httpd] Second apache as fallback server

2016-02-15 Thread Bob

Hello,

Thanks for the valuable suggestions.

What can be done to assure the high-availability of the reverse proxy 
itself ?
What about the latency if the master and hot standby located in two 
different data center ?



On Sunday 14 February 2016 10:43 PM, Yehuda Katz wrote:


We use three different methods:
1. Content on NFS server
2. Content auto-committing and auto-pulling over git about every 15 
minutes

3. Separate database server - with replication for backup.

- Y

Sent from a device with a very small keyboard and hyperactive autocorrect.

On Feb 14, 2016 5:28 PM, "Rose, John B" > wrote:


What is your preferred approach to keeping content in sync?

Sent from my iPad

On Feb 14, 2016, at 3:47 PM, Daniel > wrote:


with a reverse proxy in front of both, you use balancer setup
specifying the second web server as hot standby

El dom., 14 feb. 2016 a las 16:49, Bob (>) escribió:

Hello list,

I have two servers. One is already up with apache, mysql etc..
Now I wonder if I can configure the second server as a
fallback web server.
The idea is.. if first web server is down , the second one
will serve
the requests.

Any suggestion / idea is very much welcome.

Thanks and regards,
Bob

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org

For additional commands, e-mail: users-h...@httpd.apache.org






Re: [users@httpd] Second apache as fallback server

2016-02-14 Thread Rose, John B
What is your preferred approach to keeping content in sync?

Sent from my iPad

On Feb 14, 2016, at 3:47 PM, Daniel 
> wrote:

with a reverse proxy in front of both, you use balancer setup specifying the 
second web server as hot standby

El dom., 14 feb. 2016 a las 16:49, Bob 
(>) escribió:
Hello list,

I have two servers. One is already up with apache, mysql etc..
Now I wonder if I can configure the second server as a fallback web server.
The idea is.. if first web server is down , the second one will serve
the requests.

Any suggestion / idea is very much welcome.

Thanks and regards,
Bob

-
To unsubscribe, e-mail: 
users-unsubscr...@httpd.apache.org
For additional commands, e-mail: 
users-h...@httpd.apache.org



Re: [users@httpd] Second apache as fallback server

2016-02-14 Thread Daniel
with a reverse proxy in front of both, you use balancer setup specifying
the second web server as hot standby

El dom., 14 feb. 2016 a las 16:49, Bob () escribió:

> Hello list,
>
> I have two servers. One is already up with apache, mysql etc..
> Now I wonder if I can configure the second server as a fallback web server.
> The idea is.. if first web server is down , the second one will serve
> the requests.
>
> Any suggestion / idea is very much welcome.
>
> Thanks and regards,
> Bob
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>
>


Re: [users@httpd] Second apache as fallback server

2016-02-14 Thread Yehuda Katz
We use three different methods:
1. Content on NFS server
2. Content auto-committing and auto-pulling over git about every 15 minutes
3. Separate database server - with replication for backup.

- Y

Sent from a device with a very small keyboard and hyperactive autocorrect.
On Feb 14, 2016 5:28 PM, "Rose, John B"  wrote:

> What is your preferred approach to keeping content in sync?
>
> Sent from my iPad
>
> On Feb 14, 2016, at 3:47 PM, Daniel  wrote:
>
> with a reverse proxy in front of both, you use balancer setup specifying
> the second web server as hot standby
>
> El dom., 14 feb. 2016 a las 16:49, Bob () escribió:
>
>> Hello list,
>>
>> I have two servers. One is already up with apache, mysql etc..
>> Now I wonder if I can configure the second server as a fallback web
>> server.
>> The idea is.. if first web server is down , the second one will serve
>> the requests.
>>
>> Any suggestion / idea is very much welcome.
>>
>> Thanks and regards,
>> Bob
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
>> For additional commands, e-mail: users-h...@httpd.apache.org
>>
>>