On 2015-08-19 09:01, oscaretu . wrote:
> Hello.
>
> Perhaphs this can help you about the out of memory: OOM Killer:
>
> https://www.google.com/search?client=ubuntu&channel=fs&q=OOM+Kiler&ie=utf-8&oe=utf-8
> [6]
>
Oscar, and list,

I just looked at the several /var/log/messages files. The last one is
from August 16th.
It contains in equal parts lines like:

kernel: php-fpm invoked oom-killer: gfp_mask=0x201da, order=0,
oom_adj=0...

and "kernel: mysqld invoked oom-killer: ..." etc etc.

Not really useful. I am (re)reading this right now:

http://www.oracle.com/technetwork/articles/servers-storage-dev/oom-killer-1911807.html

but so far it doesn't seem to be really helpful either. I had already
figured out that, for some reason, mysqld and/or php-fpm were consuming
much more memory than would be reasonable. The question is **what**, in
their, or nginx's configuration can make that happen?

As it turned out yesterday, a good part of the problem was, indeed, the
persistent mysqld connections in php.ini. Turning them off made the
situation much better, but not fix it. Today, the question is what else,
exactly, to look for in which logs, and above all if something in the
nginx/
php-fpm configuration I posted in my previous message is the trigger of
this behaviour and must be changed/optimized. Ideas, anybody?

Thanks,
Marco

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx