Re: Backporting "MEDIUM: mworker: reexec in waitpid mode after successful loading" to 2.4

2022-05-10 Thread William Lallemand
On Tue, May 10, 2022 at 12:09:59PM +0200, Christian Ruppert wrote: > > It even just happened when running with gdb, without a reload. > What the patch does is re-executing the master in wait-mode once the worker was started in order to free the master memory of huge data (maps, SSL certificates

[PATCH] DOC/MINOR: fix typos in the lua-api document

2022-05-10 Thread Boyang Li
Fixes a few typos in the Lua API document. --- doc/lua-api/index.rst | 12 ++-- 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/lua-api/index.rst b/doc/lua-api/index.rst index d1dd3397e..515d8853b 100644 --- a/doc/lua-api/index.rst +++ b/doc/lua-api/index.rst @@ -1357,7

[PATCH] BUG/MEDIUM: lua: fix argument handling in data removal functions

2022-05-10 Thread Boyang Li
Lua API Channel.remove() and HTTPMessage.remove() expects 1 to 3 arguments (counting the manipulated object), with offset and length being the 2nd and 3rd argument, respectively. hlua_{channel,http_msg}_del_data() incorrectly gets the 3rd argument as offset, and 4th (nonexistent) as length.

Re: Backporting "MEDIUM: mworker: reexec in waitpid mode after successful loading" to 2.4

2022-05-10 Thread William Lallemand
On Tue, May 10, 2022 at 11:05:01AM +0200, Christian Ruppert wrote: > Hi guys, William, > > can we please get that "MEDIUM: mworker: reexec in waitpid mode after > successful loading" - fab0fdce981149a4e3172f2b81113f505f415595 > backported to 2.4? > I seem to run into it, at least on one of our

Backporting "MEDIUM: mworker: reexec in waitpid mode after successful loading" to 2.4

2022-05-10 Thread Christian Ruppert
Hi guys, William, can we please get that "MEDIUM: mworker: reexec in waitpid mode after successful loading" - fab0fdce981149a4e3172f2b81113f505f415595 backported to 2.4? I seem to run into it, at least on one of our 40 LBs. This one is a VM though. It sometimes crashes after each reload.