I have a release that has a serious flood of terms being thrown either in error, or I don’t even know what. This is going to be hard to communicate, so bear with me.
In development, I have some `httpc’ requests that work just fine… passing along some headers and things for successful oauth2 requests.
Other than the requesting host differences (one is 127.0.0.1:9004, the other troubled one is https://example.com) there aren’t any differences in what is being sent along on the erlang side. The boxes are both OpenBSD, both are running OTP26 (usually just fine).
Anyway, when I perform this in-production request, at some point, my server locks and I get an endless barrage of terms that knocks my wee production server out of commission. The shape of these terms in my logs are:
...
{cert,
<<48,130,3,119,48,130,2... ,123,167,157>>,
{'OTPCertificate',
{'OTPTBSCertificate',v3,664...
{'SignatureAlgorithm',{1,2,...11},'NULL'},
{rdnSequence,
...
I was wondering if anyone could see what libs/apps may be squawking!? I have a terrible hack to halt the VM after a few seconds before the IO is so intense that I can’t interact with the REPL, and my logs are being quickly written over that makes it unknown what is the failing calling process. But to be honest, I can’t tell if this is a failure due to an error yet… Anyone can help point me in the right direction?