<div dir="ltr">
<span class="gmail-tlid-translation gmail-translation" lang="en"><span title="" class="gmail-">Because the memory
<span class="gmail-tlid-translation gmail-translation" lang="en"><span title="" class="gmail-">
<span class="gmail-tlid-translation gmail-translation" lang="en"><span title="" class="gmail-">suddenly</span></span></span></span>

 rises , n<span class="gmail-tlid-translation gmail-translation" lang="en"><span title="" class="gmail-">o time to run 'etop'. 
<span class="gmail-tlid-translation gmail-translation" lang="en"><span title="" class="gmail-">I suspect that the responseof the request is too large, and  <span class="gmail-tlid-translation gmail-translation" lang="en"><span title="" class="gmail-">the flood-like keep-alive request caused such a result.</span></span>

</span></span>

</span></span>

<span class="gmail-tlid-translation gmail-translation" lang="en"><span title="" class="gmail-"></span></span>

</span></span>

</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Marc Worrell <<a href="mailto:marc@worrell.nl">marc@worrell.nl</a>> 于2019年5月21日周二 下午2:50写道：<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style="overflow-wrap: break-word;"><div>Do you have some other logs?</div><div>Preferably the one where the message below is printed.</div><div><br><blockquote type="cite"><div>On 21 May 2019, at 05:39, Monk Boy <<a href="mailto:boyofmonk@gmail.com" target="_blank">boyofmonk@gmail.com</a>> wrote:</div><br class="gmail-m_5718015770193455750Apple-interchange-newline"><div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">#2  0x000000000045806e in erl_exit_vv (n=1, flush_async=flush_async@entry=0, fmt=fmt@entry=0x5fbce8 "%s: Cannot %s %lu bytes of memory (of type \"%s\", thread %d).\n", args1=args1@entry=0x7fda361ba830, args2=args2@entry=0x7fda361ba848)</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;float:none;display:inline">    at beam/erl_init.c:2123</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"></div></blockquote></div><br><div>This could be out of memory, but also something else “Cannot %s” …</div><div><br></div><div>If it is OOM then you can easily check the memory usage of beam.smp whilst it is running.</div><div>That would give enough hints.</div><div><br></div><div>Also check your running server with ‘etop’. </div><div><br></div><div>Cowboy has configurations max request content length, it will refuse the request with a 4xx error.</div><div>Afaik it defaults to 64K for urlencoded bodies and 8M for other bodies.</div><div><br></div><div>- Marc</div><div><br></div></div></blockquote></div>