Hello,
thanks for your feedback and nice to hear its solved.
have a nice day.
Alexander
Am 03.07.2013 08:50, schrieb imanenkov:
> Alexander Kunz Wrote:
>> i am no drupal user/developer but if i google about drupal cache it
>> sounds, there is not only one cache, and it sounds like its not onl
Alexander Kunz Wrote:
> i am no drupal user/developer but if i google about drupal cache it
> sounds, there is not only one cache, and it sounds like its not only
> one
> click to disable it complete. Perhaps you can find some informations
> about the cache here:
>
> https://drupal.org/node/797346
i'd suggest you'll start with low-level-debugging:
- goto host1 and make a tcpdump port 8080 / tail -f against access-logs
of that server;
- make a request
- check., what happens to that request, e.g. where it "hangs"
you could also, just in case, make a "tcpdump port 808 and host host2" onm
your
I have 2 upstream servers host1 and host2.
host1 is up and running and listening on port 8080host2 is powered off.
When I sent a request to nginx, I received response after 2 minutes. Until 2
minutes the request is waiting.
Thanks,Sandeep.
> To: nginx@nginx.org
> Subject: Re: RE: Nginx upstream s
you are sure, your upstream-servers are not answering on given ports?
http://wiki.nginx.org/HttpUpstreamModule#server
vs
http://wiki.nginx.org/NginxHttpProxyModule#proxy_connect_timeout
http://wiki.nginx.org/NginxHttpProxyModule#proxy_read_timeout
Posted at Nginx Forum:
http://forum.nginx.org
Hi Parikh,
I used following configuration but still its waiting for long time.
server host1.example.com:8080 max_fails=2 fail_timeout=5s;
As you suggested removed off
proxy_next_upstream error timeout http_404 http_500 http_502 http_503 http_504;
Thanks,Sandeep.
Date: Wed, 3 Jul 2013 00:47:31 -050
In your proxy_next_upstream, why do you
have 'off' enabled.
off — it forbids the request transfer to the next server.
Remove 'off' from that line.
Sajan Parikh
Owner, Noppix LLC
e: sa...@noppix.com
p: (563) 726
@Parikh I tried with proxy_next_upstream also but facing same issue.
Regarding fail_timeout I used values from 10s to 30s but facing same issue.
I used following configuration, just check and let me know If I am missing any
thing.
upstream appcluster { server host1.example.com:8080 max_fails=2
you allow 600 seconds to pass until you npotice, that your upstream-server
is not responsible.
... max_fails=2 fail_timeout=300s;
why?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,240513,240515#msg-240515
___
nginx mailing list
nginx@ng
Have you looked at the
proxy_next_upstream configuration?
http://wiki.nginx.org/NginxHttpProxyModule#proxy_next_upstream
It should do what you want.
Also, depending on yourapplication and traffic, it might also be
worth looking into lowe
Hi,
I am trying to configure nginx with upstream.
We have 3 machines where we run application server and proxy passing all
requests from nginx to application serves.
I used following configuration in nginx:
upstream appcluster {
server host1.example.com:8080 max_fails=2 fa
Sorry, maybe it is only related to the permalink structure which worked with
Apache before server move.
The gallery script adds it own extensions to the address.
You can see it live on www.peleke.de/galerie and then click on one of the
three gallery sources (Flickr, Facebook or Google+).
Can you
On Tue, Jul 02, 2013 at 05:24:15PM -0400, Peleke wrote:
Hi there,
> I have set the open_file_cache variable to max=5000 inactive=20s so that it
> is enabled globally but now I want to disable all caching for a specific
> virtual location on a domain:
http://nginx.org/r/open_file_cache describes
I have set the open_file_cache variable to max=5000 inactive=20s so that it
is enabled globally but now I want to disable all caching for a specific
virtual location on a domain:
- open_file_cache max=5000 inactive=20s;
-- location ^~ /gallery {
open_file_cache off;
}
Sadly that
Hello all,
I have some problem , I use version nginx/1.2.2 and nginx/1.0.11, should I
upgrade my version first or just compile then send you my debug log
thanks,
Rizki
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,205826,240499#msg-240499
__
Hello,
Am 02.07.2013 15:46, schrieb imanenkov:
> Alexander Kunz Wrote:
> ---
>>
>> do you use a PHP framework? Most frameworks can cache also.
> Yes, site based on Drupal 7. I trying to switch off drupal cache, all the
> same.
i am no drupal us
Alexander Kunz Wrote:
---
>
> do you use a PHP framework? Most frameworks can cache also.
Yes, site based on Drupal 7. I trying to switch off drupal cache, all the
same.
> What
> happens
> if you request the page with a unique parameter which is
Changes with nginx 1.5.2 02 Jul 2013
*) Feature: now several "error_log" directives can be used.
*) Bugfix: the $r->header_in() embedded perl method did not return value
of the "Cookie" and "X-Forwarded-For" request header lines; the bug
A maint mode switch sounds probable.
--
Jonathan Matthews
Oxford, London, UK
http://www.jpluscplusm.com/contact.html
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Hello,
Am 02.07.2013 14:37, schrieb imanenkov:
> Maxim Dounin Wrote:
>> If you want to change nginx configuration - just add
>> $upstream_cache_status variable to a log, it will show if a
>> response was from nginx cache (HIT) or was requested from a
>> backend.
>>
>> Other upstream-related var
Hello!
On Tue, Jul 02, 2013 at 08:37:05AM -0400, imanenkov wrote:
> Maxim Dounin Wrote:
> > If you want to change nginx configuration - just add
> > $upstream_cache_status variable to a log, it will show if a
> > response was from nginx cache (HIT) or was requested from a
> > backend.
> >
> >
Maxim Dounin Wrote:
> If you want to change nginx configuration - just add
> $upstream_cache_status variable to a log, it will show if a
> response was from nginx cache (HIT) or was requested from a
> backend.
>
> Other upstream-related variables may be interesting too, in
> particular $upstre
Hello!
On Tue, Jul 02, 2013 at 07:49:56AM -0400, imanenkov wrote:
> Maxim Dounin Wrote:
> ---
> > Unfortunately, all the tests you did actually prove nothing.
> > You've been told to switch off php-fpm, not to change nginx
> > configuration.
Maxim Dounin Wrote:
---
> Unfortunately, all the tests you did actually prove nothing.
> You've been told to switch off php-fpm, not to change nginx
> configuration.
Do you mean stopping php-fpm with "/etc/init.d/php5-fpm stop" command? In
this
Hi guys,
I'm getting a lot of errors on logs right now and we've already tried
everything to solve the problem without success.
Everything was running just fine until last week.
We use nginx and php-fpm.
nginx version: nginx/1.2.0
The errors that we getting are from random pages and random domai
Hello!
On Tue, Jul 02, 2013 at 02:08:52AM -0400, imanenkov wrote:
> Maxim Dounin Wrote:
> > On the other hand, 100-200 msec is way too long for nginx to
> > return a cached response.
> >
> > If you assume the response is cached by nginx somehow, simpliest
> > test is to switch off php-fpm and
26 matches
Mail list logo
