Hi, On Sun, Feb 16, 2020 at 05:25:34PM +0100, Bernhard Übelacker wrote: > Could the call to palloc just before have failed to allocate memory?
If that's a question for me, then: extremely unlikely. I tried just restarting proftpd, I tried restarting the whole container. There are no memory limits for the container (I'm a poor admin, I know!). The host has cca half of its physical memory available, and plenty-ish of swap on top of that. So unless that palloc tries to allocate way more memory than it should, I don't think that's the problem. -- Tomáš Janoušek, a.k.a. Pivník, a.k.a. Liskni_si, http://work.lisk.in/
