nginx стоит балансировщиком и переадресует запросы скажем
на группу серверов
192.168.0.1
192.168.0.2
192.168.0.2
через proxy_pass
Например запрос перешел на 192.168.0.1, можно ли как-то вернуть в заголовке
команду для балансировщика
сменить upstream сервер с 192.168.0.1 на 192.168.0.2 или
модульными тестами проверяете ? поделитесь ?
6 марта 2013 г., 22:54 пользователь Anatoly Mikhailov
anat...@sonru.comнаписал:
добрый день,
Какая версия PCRE совместимы с Nginx 1.3.12+?
В Wiki сказано PCRE version 4.4 -- 8.21, но я давно устанавливаю 8.30 -
все совместимо.
Но уже доступна
On Mar 6, 2013, at 6:51 PM, Валентин Бартенев vb...@nginx.com wrote:
On Wednesday 06 March 2013 20:54:34 Anatoly Mikhailov wrote:
добрый день,
Какая версия PCRE совместимы с Nginx 1.3.12+?
В Wiki сказано PCRE version 4.4 — 8.21, но я давно устанавливаю 8.30 -
все совместимо. Но уже
добрый день,
Вопрос балансировки нагрузки не дает мне покоя несколько дней, пока склоняюсь к
использованию
Nginx в роли балансировщика. Таким образом будет каскад Nginx - (Nginx -
Unicorn) x 5.
У нас связка Nginx+Unicorn на нескольких независимых серверах разного
назначения (Main, Admin, API,
On Tue, Mar 05, 2013 at 12:17:03AM +, Jonathan Matthews wrote:
A slight thinko crept in to my original mail; there's a small
difference (which does remove a minor complexity) as I've marked below
...
On 4 March 2013 23:58, Jonathan Matthews cont...@jpluscplusm.com wrote:
[snip]
For beter understanding here is my config sniper
upstream super_upstream {
keepalive 128;
server be1 max_fails=45 fail_timeout=3s;
server be2 max_fails=45 fail_timeout=3s;
server be3 max_fails=45 fail_timeout=3s;
}
server {
server_name pytn.ru;
location ^~
Hello!
On Wed, Mar 06, 2013 at 01:23:28AM +0100, Arman Mirk wrote:
I notice our server is rapidly responding 500 errors for random pages.
Our setup is pretty basic. We are running Nginx 0.7.6 with Unicorn and a
Rails app on a Ubuntu 10.4 server.
What ever the problem, it doesn't seem to
Hi,
I'm having issues with nginx where my cache directory keeps growing until
the hdd is full.
If anyone can give me any information on how to solve this it will be
appreciated.
nginx -V:
nginx version: nginx/1.2.1
built by gcc 4.4.6 20110731 (Red Hat 4.4.6-3) (GCC)
TLS SNI support enabled
Hello!
On Wed, Mar 06, 2013 at 07:02:28AM -0500, jan5134 wrote:
Hi,
I'm having issues with nginx where my cache directory keeps growing until
the hdd is full.
If anyone can give me any information on how to solve this it will be
appreciated.
nginx -V:
nginx version: nginx/1.2.1
Thanks for the quick reply.
I would like to test that but i'm kind of new to nginx and also our website
can't have any downtime.
Any other suggestion maybe?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236987,236989#msg-236989
___
nginx
Hello!
On Wed, Mar 06, 2013 at 07:16:39AM -0500, jan5134 wrote:
Thanks for the quick reply.
I would like to test that but i'm kind of new to nginx and also our website
can't have any downtime.
Any other suggestion maybe?
Try to reproduce the problem in a sandbox, it should help with
your
Hello!
On Wed, Mar 06, 2013 at 05:28:12AM -0500, yvlasov wrote:
Hello
In our setup we have an NGNX as front-end and several back-end.
The problem is our load profile, we have a lot of simple and fast http
requests, and very few but very heavy in terms of time and BE cpu requests.
So my
Hi,
Is there a way to server files only below a certain size?
eg. Return 403 on files bigger than 5MB?
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hi,
On Sun, Mar 03, 2013 at 07:38:39PM +0100, GASPARD kévin wrote:
Hi there,
Probably a single extra try_files line will work for you.
This is my new config file :
location ~ \.php$ {
try_files $uri $uri/ /index.php?q=$uri$args;
}
You will probably
Hi,
I have noticed that when I set 'proxy_intercept_errors on;' in my nginx config
it kills tcp connection to the origin server if it returns 4xx or 5xx?
This is my example config to reproduce the
situation(https://gist.github.com/kirilkalchev/5098882). I am in a situation
where my backend
Hello!
On Wed, Mar 06, 2013 at 03:44:37PM +0200, Kiril Kalchev wrote:
I have noticed that when I set 'proxy_intercept_errors on;' in
my nginx config it kills tcp connection to the origin server if
it returns 4xx or 5xx?
This is my example config to reproduce the
Is there any way to force nginx to read request body? I really don't care about
this overhead, I hit connection limit much more faster. Thank you for the super
fast answer.
Regards,
Kiril
On Mar 6, 2013, at 3:54 PM, Maxim Dounin wrote:
Hello!
On Wed, Mar 06, 2013 at 03:44:37PM +0200,
Hello!
On Wed, Mar 06, 2013 at 04:02:30PM +0200, Kiril Kalchev wrote:
Is there any way to force nginx to read request body? I really
don't care about this overhead, I hit connection limit much more
faster. Thank you for the super fast answer.
No, there is no way to force nginx to read
Just for the record, I think I found a kind of solution. It looks good if my
backend returns http codes 3xx. I have tried with 333 and 334 and it looks
great. I know it is an ugly hack, but my findings may help to other poor souls.
I hope this behavior will not change in the next versions.
Ah, thank you. Removing the site configuration file did fix the gateway
error, but now the server is still pointing at the default Nginx welcome
page. Can you (or anyone else here) give me any advice on how to get the
server to point to my actual service?
BTW, you pointed out that there was an
Joseph O. Wrote:
---
Ah, thank you. Removing the site configuration file did fix the
gateway
error, but now the server is still pointing at the default Nginx
welcome
page. Can you (or anyone else here) give me any advice on how to get
the
Thanks! The Resolver did the trick.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236969,237020#msg-237020
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Unfortunately the way big files are getting there is beyond my control.
On Wed, Mar 6, 2013 at 5:30 PM, Jonathan Matthews
cont...@jpluscplusm.comwrote:
On 6 March 2013 13:28, Calin Don calin@gmail.com wrote:
Hi,
Is there a way to server files only below a certain size?
eg. Return
Are you saying that you do not have administrative control of your system?
Jonathan is right - set policies that disallow large file sizes and enforce
them.
If necessary use chron to check for large files and remove them.
On Wed, Mar 6, 2013 at 2:28 PM, Calin Don calin@gmail.com wrote:
*sigh* Clearly I am missing something here, as the only nginx.conf file
I have is the one I posted last night. There is no upstream server; the
code for that was from the example config file I was trying to modify
for my purposes.
It seems that this copypasta approach isn't adequate for
Hey,
As a quick test you may try switching to a proxy + proxy_cache
setup instead of slowfs_cache to see if slowfs_cache module
problem or something more general.
It's a known issue with my ngx_slowfs_cache module.
Best regards,
Piotr Sikora piotr.sik...@frickle.com
Sent from my BlackBerry 10 smartphone.
Hi,
Thanks for your contribution to the nginx community Piotr and your reply.
Do you have any suggestions on how to bypass this problem?
Any update on the module in the near future that might fix this issue?
Thanks
Jan
Posted at Nginx Forum:
28 matches
Mail list logo