Hello List, I'd like to ask whether You're aware of any change which might cause breakage in my setup involving spamc with a completely unchanged configuration in between - I'm getting the following error:
*"panic: master_reap: unknown pid"* I'm running Docker containers from Alpine images orchestrated by Kubernetes on ARMv6 with all services running in separate pods, but I have also tested on Debian to figure out whether it's an Alpine-specific problem - alas, it also occurs on Debian. The fatal step is invoking spamc via pipe, although that succeeds since spamd does receive the call, that is proven. (Everything is alright until that call is made, and then it reproducibly perishes every single time.) Spamd is 3.4.2 even in working cases, but failures also occur with both 3.4.1 and 3.4.2 client versions. I've spent 2 days trying to debug this on my own, but fail to comprehend the root cause of the problem, not even when diff'ing 'postconf -x' outputs. I thought it's either a different spamc version exiting in an unexpected manner or the pipe service handling exits from external processes differently, but changing spamc versions doesn't change the symptom, plus the code for pipe in Postfix doesn't seem to have changed in several years now. As hinted, reverting to a container with 3.3.0 immediately fixes the problem, but I'd like to be able to upgrade. Could You please assist me figure out what's going wrong here? Documentation says panics are meant to be resolved by the developers, so this is a justified call for help - I'd be happy to supply any information necessary. Thanks, Tamás
