acess log over nfs hanging

[Guilherme]

Anton,

I already had the same issue logging to NFS, but I'm curious about why
nginx hang in some nfs failures. Log phase is the last, if there is no post
action, so why nginx stop responding in some NFS failures? Do you think
that I can ease the situation tunning nfs client config, such as timeout
and retrans ?

tks





On Tue, Feb 11, 2014 at 3:33 PM, David Birdsong <david.birdsong at gmail.com>wrote:

>
>
>
> On Tue, Feb 11, 2014 at 1:30 AM, Anton Yuzhaninov <citrin at citrin.ru>wrote:
>
>> On 02/07/14 20:28, Jader H. Silva wrote:
>>
>>> It seems that when some processes are running in the nfs server, the
>>> share won't
>>> allow writing for some time and I noticed all nginx workers in status D
>>> and not
>>> processing requests.
>>>
>>
>> I general it is a bad idea to write logs over NFS instead local HDD.
>>
>> If you need central log store across many servers:
>> - write logs locally
>> - rotate as often as need (SIGUSR1)
>> - copy logs to cental log server (rsync is handy for this, but other
>> methods are possible)
>
>
> yeah, try out: http://hekad.readthedocs.org/
>
> it's like syslog but can write to pretty much any backend store.
>
>
>>
>>
>>  Are all access.log writes blocking?
>>>
>>
>> yes, blocking
>>
>>
>>  If my nfs server shutdown in an unexpected
>>> way, will nginx stop proxying requests to the backend or responses to
>>> the client?
>>>
>>
>> yes, will stop
>>
>> _______________________________________________
>> nginx mailing list
>> nginx at nginx.org
>> http://mailman.nginx.org/mailman/listinfo/nginx
>>
>
>
> _______________________________________________
> nginx mailing list
> nginx at nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20140213/53fcd47b/attachment-0001.html>