On Tue, Feb 11, 2014 at 1:30 AM, Anton Yuzhaninov <[email protected]> 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 > [email protected] > http://mailman.nginx.org/mailman/listinfo/nginx >
_______________________________________________ nginx mailing list [email protected] http://mailman.nginx.org/mailman/listinfo/nginx
