Hi, I am also running into this issue using 1.9.4 (i.e. the current "latest" docker image) with absolutely no load at all (1 client):
[ALERT] 044/001000 (1) : sendmsg()/writev() failed in logger #1: No such file or directory (errno=2) [NOTICE] 044/001000 (1) : New worker #1 (8) forked [ALERT] 044/001011 (1) : Current worker #1 (8) exited with code 139 (Segmentation fault) [ALERT] 044/001011 (1) : exit-on-failure: killing every workers with SIGTERM [WARNING] 044/001011 (1) : All workers exited. Exiting... (139) I do not have this issue with 1.8. (Also, I've been looking for commit 451c5a88 and can't find it anywhere). Cheers, -Hugues On Wed, Feb 13, 2019 at 2:15 AM Christopher Faulet <[email protected]> wrote: > Le 13/02/2019 à 09:40, [email protected] a écrit : > > Thanks Vincent, got a core dump. > > > > Here is the backtrace > > > > #0 0x00005577fb060375 in __pool_get_from_cache (pool=0x5577fb3f7540 > > <pool_base_start>) at include/common/memory.h:199 > > 199 include/common/memory.h: No such file or directory. > > > > (gdb) bt full > > #0 0x00005577fb060375 in __pool_get_from_cache (pool=0x5577fb3f7540 > > <pool_base_start>) at include/common/memory.h:199 > > __ret = 0x5577fb583280 > > item = 0x5577fb583280 > > #1 __pool_get_first (pool=0x5577fb3f7540 <pool_base_start>) at > > include/common/memory.h:216 > > cmp = <optimized out> > > #2 pool_alloc_dirty (pool=0x5577fb3f7540 <pool_base_start>) at > > include/common/memory.h:258 > > p = 0x5577fb583280 > > #3 pool_alloc (pool=0x5577fb3f7540 <pool_base_start>) at > > include/common/memory.h:272 > > No locals. > > #4 http_process_request (s=0x5577fb580d50, req=<optimized out>, > > an_bit=2048) at src/proto_http.c:2880 > > sess = 0x5577fb57e7a0 > > txn = <optimized out> > > msg = <optimized out> > > So I confirm, it is a crash during the allocation of s->unique_id. The > commit 451c5a88 fixes this bug. > > > -- > Christopher Faulet > >
