Your message dated Wed, 4 Sep 2019 18:34:00 +0300 with message-id <[email protected]> and subject line Re: Bug#888447: radsecproxy fails with pthread_attr_setstacksize failed has caused the Debian Bug report #888447, regarding radsecproxy fails with pthread_attr_setstacksize failed to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact [email protected] immediately.) -- 888447: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888447 Debian Bug Tracking System Contact [email protected] with problems
--- Begin Message ---Package: radsecproxy Version: 1.6.8-1 Severity: normal Tags: upstream Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? installing radsecproxy on ppc64le * What exactly did you do (or not do) that was effective (or ineffective)? compiling radsecproxy and linking against latest libssl got it working * What was the outcome of this action? * What outcome did you expect instead? it should start normally *** End of the template - remove these template lines *** 11:38:27 (root@system)/(0)$ apt-get install radsecproxy Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: radsecproxy 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 0 B/79.1 kB of archives. After this operation, 337 kB of additional disk space will be used. Selecting previously unselected package radsecproxy. (Reading database ... 112117 files and directories currently installed.) Preparing to unpack .../radsecproxy_1.6.8-1_ppc64el.deb ... Unpacking radsecproxy (1.6.8-1) ... Setting up radsecproxy (1.6.8-1) ... Job for radsecproxy.service failed because the control process exited with error code. See "systemctl status radsecproxy.service" and "journalctl -xe" for details. invoke-rc.d: initscript radsecproxy, action "start" failed. ● radsecproxy.service - radsecproxy Loaded: loaded (/lib/systemd/system/radsecproxy.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Thu 2018-01-25 11:38:36 MST; 8ms ago Docs: man:radsecproxy(1) Process: 2193 ExecStart=/usr/sbin/radsecproxy -i /run/radsecproxy.pid (code=exited, status=1/FAILURE) CPU: 2ms 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'. -- System Information: Debian Release: 9.3 APT prefers stable APT policy: (500, 'stable') Architecture: ppc64el (ppc64le) Foreign Architectures: amd64 Kernel: Linux 4.9.0-5-powerpc64le (SMP w/160 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages radsecproxy depends on: ii init-system-helpers 1.48 ii libc6 2.24-11+deb9u1 ii libnettle6 3.3-1+b2 ii libssl1.0.2 1.0.2l-2+deb9u2 ii lsb-base 9.20161125 radsecproxy recommends no packages. radsecproxy suggests no packages. -- Configuration Files: /etc/radsecproxy.conf changed [not included] -- no debconf information
--- End Message ---
--- Begin Message ---On Tue, Jan 08, 2019 at 03:30:39AM +0200, Faidon Liambotis wrote: > 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? I haven't heard back and have been unable to reproduce this. I'm resolving this bug - feel free to reopen if you're still experiencing this. Regards, Faidon
--- End Message ---
