Tag Info

Hot answers tagged

4

Redundancy, resiliency, scalability and flexibility are factors here. Many environments can and do scale beyond a single server in the web-tier. It also makes sense to understand what the realistic bottleneck of the environment is: CPU? RAM? Network?


3

When using SSL-Session-Cache, the performance of keep-alive connections over SSL might be enormously increased. When the server does have it enabled, it is not necessary for the client to do a full SSL-handshake every request, thus saving time and cpu-resources. You can read up more here: ...


2

According to that blog post, Please note, that it’s not possible to embed variables in error_log directives, as any potential error would not be able to be logged if the file cannot be written. With that in mind, it is not possible to have the error log automatically rotated with the naming format error-$year-$month-$day.log using that Nginx method. ...


2

See my comment above, and cpburnz's reasoning, but if you really want to proceed: You could write a script which writes just the log commands to an include file, with the current date hard-coded. You'd have that included into your nginx config file, and your script would restart or reload nginx after writing the log commands to the include file. Something ...


2

Your location blocks are in the wrong place. They have to be inside a server block. I recommend that you study nginx configuration much more closely, so that you understand the whole concept. Otherwise you will only get problems in the future.


1

You might try setting up multiple server instances, each responding to the appropriate server_name and then proxying from each one as follows: server { listen x.x.x.x:400; # your one IP server_name domain1.com; location / { proxy_pass http://192.168.1.1; } } server { listen x.x.x.x:400: # your one IP server_name ...


1

wp-admin is a separate page from index.php so your location directive will never access it. You basically set your location as /WordPress and nest your .php location within it. I'm on a tablet so will add an example code fragment when I get on a desktop/laptop again.


1

You are actually redirecting the client to a different server. Assuming you configured DNS to point to server1, you want to mask the presence of server2. To do this configure apache as a reverse proxy and proxy /forum requests to server2. You do not need to configure SSL on server2.


1

I think logrotate manual is clear about most of your points. Here are my answers: Using daily causes log rotation to happen every day. So, you need to check why it is not happening on daily basis. For example, this can be caused by the other option notifempty if the log file was empty for few days. I can't find an option to do it every 6 months, but you ...


1

I think the configuration options you require are: proxy_cache_use_stale updating; proxy_cache_lock on; This serves out of date elements from cache, and issuing updates from backend. So when your backend servers a page after 2 seconds, the client already got the old ressource from cache. The second locks one element from cache, while already a ...


1

In addition to @Bazze's excellent comment regarding libsas, you may be missing a dependency ( or a dependency on the right architecture) Note that it is fairly common to have to install both 32-bit and 64-bit libraries for some applications. If you use ldd /path/to/amazon-elasticache-cluster-client.so, do you see any lines mentioning ‘unresolved’ or ...


1

From the comments, four things come to my mind. Routing - Are the two nodes in a network that makes it able to connect to each other. Use networking tool such as traceroute, arp, arping to check it (arp to ensure the node is the same). Is there a firewall or security policy in between that blocks the said ports. Is your server running RHEL/CentOS/Fedora ...


1

You can utilize magic variables group_names and groups to look up groups defined in your inventory: --- - hosts: webservers vars: dcs: [dc_1, dc_2, dc_3] tasks: - debug: msg: | upstream backend { {%- for dc in dcs %} {%- if dc in group_names %} {%- for host in groups[dc+'_appservers'] %} server ...


1

Remove: more_set_headers "Content-Type: text/html;charset=utf-8"; You are set header Content-Type: text/html;charset=utf-8 for all responses



Only top voted, non community-wiki answers of a minimum length are eligible