Hi Nathan, On Thu, Jan 25, 2018 at 11:44:02AM -0700, Nathan Rini wrote: > * What led up to the situation? > installing radsecproxy on ppc64le > > <snip> > > Jan 25 11:38:36 stargate4 systemd[1]: Starting radsecproxy... > Jan 25 11:38:36 stargate4 radsecproxy[2193]: pthread_attr_setstacksize failed > Jan 25 11:38:36 stargate4 systemd[1]: radsecproxy.service: Control process > exited, code=exited status=1 > Jan 25 11:38:36 stargate4 systemd[1]: Failed to start radsecproxy. > Jan 25 11:38:36 stargate4 systemd[1]: radsecproxy.service: Unit entered > failed state. > Jan 25 11:38:36 stargate4 systemd[1]: radsecproxy.service: Failed with result > 'exit-code'.
Apologies for the very late response. I just uploaded radsecproxy 1.7.2-1 and during the course of those changes, I was also investigating this bug. Unfortunately, I'm unable to reproduce this, even on a ppc64el system (plummer.debian.org specifically). I looked closely at the code as well, and I don't see anything wrong with this particular piece of code (other than, potentially, not ignoring this error). Perhaps you have custom limits set for RLIMIT_STACK? Is there anything of note in your /etc/security/limits.conf? What are the values of "ulimit -s -S" and "ulimit -s -H" on your system? What is the output of "grep -r 'define PTHREAD_STACK_MIN' /usr/include/" on this system? Kree, Faidon
