"S. Banerian" <baner...@u.washington.edu> writes: > On 10/07/2016 02:04 PM, Ferenc Wágner wrote: > >>> Manually trying to start /usr/sbin/shibd -f -F never produces the >>> /run/shibboleth/shibd.sock nor any other files in that dir. >> >> This is really disturbing. You don't except the above command to give >> back your prompt, right? > > correct. > >> Could you please make sure shibd isn't running >> then show me the output of >> >> # sudo -u _shibd strace shibd -f -F > > the output is rather long... > I shall attach.
Thanks. Does it hang there indefinitely, with no further output for minutes? Does shibd still consume significant CPU according to top? What are its memory figures? Isn't your computer swapping heavily? Can you provide a full GDB backtrace (after installing shibboleth-sp2-utils-dbgsym; please yell if you need precise instructions). > Note: prior to the upgrade, shibboleth was working. Which version of shibboleth was working for you? Can you share your shibboleth2.xml? > We did note that sometimes shibd was more well-behaved when starting > from shell than via systemctl. Could you please make this more precise? How did it misbehave when started by systemctl? -- Thanks, Feri
