Opened 4 years ago

Closed 4 years ago

#797 closed defect (invalid)

Error in kernel log

Reported by: ilantipov@… Owned by:
Priority: minor Milestone:
Component: nginx-core Version: 1.8.x
Keywords: Cc:
uname -a: Linux rusbb.ru 3.13.0-35-generic #62-Ubuntu SMP Fri Aug 15 01:58:42 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
nginx -V: nginx version: nginx/1.8.0 built by gcc 4.8.2 (Ubuntu 4.8.2-19ubuntu1) built with OpenSSL 1.0.1f 6 Jan 2014 TLS SNI support enabled configure arguments: --error-log-path=/var/log/nginx/nginx_error.log --pid-path=/var/run/nginx.pid --lock-path=/var/lock/nginx.lock --http-log-path=/var/log/nginx/nginx_access.log --http-client-body-temp-path=/var/tmp/nginx/body --http-proxy-temp-path=/var/tmp/nginx/proxy --http-fastcgi-temp-path=/var/tmp/nginx/fastcgi --user=www-data --group=www-data --with-http_ssl_module --with-zlib=/usr/local/src/zlib-1.2.8 --with-http_gzip_static_module --with-http_stub_status_module --with-http_realip_module

Description

[23450344.977051] INFO: task nginx:3473 blocked for more than 120 seconds.
[23450344.977727] Not tainted 3.13.0-35-generic #62-Ubuntu
[23450344.978296] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[23450344.979111] nginx D ffff88081ea14440 0 3473 28169 0x00000000
[23450344.979114] ffff8800027afc40 0000000000000082 ffff88003935e000 ffff8800027affd8
[23450344.979116] 0000000000014440 0000000000014440 ffff88003935e000 ffff880051b47880
[23450344.979118] ffff880051b47884 ffff88003935e000 00000000ffffffff ffff880051b47888
[23450344.979120] Call Trace:
[23450344.979126] [<ffffffff81722c69>] schedule_preempt_disabled+0x29/0x70
[23450344.979129] [<ffffffff81724ad5>] mutex_lock_slowpath+0x135/0x1b0
[23450344.979131] [<ffffffff81724b6f>] mutex_lock+0x1f/0x2f
[23450344.979134] [<ffffffff8171ae7d>] lookup_slow+0x33/0xa7
[23450344.979138] [<ffffffff811cc095>] path_lookupat+0x725/0x790
[23450344.979142] [<ffffffff816911fc>] ? inet_recvmsg+0x6c/0x80
[23450344.979144] [<ffffffff8160a1da>] ? sock_recvmsg+0x9a/0xd0
[23450344.979148] [<ffffffff811a21e5>] ? kmem_cache_alloc+0x35/0x1e0
[23450344.979150] [<ffffffff811ccfff>] ? getname_flags+0x4f/0x190
[23450344.979152] [<ffffffff811cc12b>] filename_lookup+0x2b/0xc0
[23450344.979154] [<ffffffff811cdcc4>] user_path_at_empty+0x54/0x90
[23450344.979156] [<ffffffff8160a348>] ? SYSC_recvfrom+0xe8/0x160
[23450344.979158] [<ffffffff811cdd11>] user_path_at+0x11/0x20
[23450344.979159] [<ffffffff811c1f30>] vfs_fstatat+0x50/0xa0
[23450344.979161] [<ffffffff811c23cf>] SYSC_newstat+0x1f/0x40
[23450344.979162] [<ffffffff811c261e>] SyS_newstat+0xe/0x10
[23450344.979164] [<ffffffff8172ed6d>] system_call_fastpath+0x1a/0x1f

Change History (1)

comment:1 Changed 4 years ago by mdounin

  • Resolution set to invalid
  • Status changed from new to closed

Call trace suggests that nginx process stuck in kernel, waiting for some network filesystem operation to complete. No bug in nginx here, it's your filesystem problem (likely some connectivity issue).

Note well that's basically why it's not recommended to use NFS and other network filesystems with nginx: operations can easily block for a long time, blocking the whole nginx process and clients it servers. If you want to serve files from different servers, consider using proxy_pass instead.

Note: See TracTickets for help on using tickets.