THANK YOU! I found the error.
Thanks to Ken for the strace idea, I looked through the resultant log and found this line: 9519 read(8, "# Default limit for number of user's processes to prevent\n# accidental fork bombs.\n# See rhbz #432903 for reasoning.\n\n* soft nproc 1024\nroot soft nproc unlimited\n", 4096) = 191 That didn't jive with /etc/security/limits.conf so it stood out in my visual scan. Looking up a few lines to see where it got that from I see: 9519 open("/etc/security/limits.d/90-nproc.conf", O_RDONLY) = 8 Ok, so /etc/security/limits.d/90-nproc.conf over-rules /etc/security/limits.conf Good to know. I raised the nproc limit and the su- worked. Thanks again to all of you. Brian Brian Chabot On Mon, Mar 10, 2014 at 10:32 AM, Mark Komarinski <mkomarin...@wayga.org> wrote: > > On 3/10/2014 10:20 AM, Brian Chabot wrote: >> Also, disk space and RAM are aplenty... >> >> Is there any way to tell *which* resource is unavailable? >> Brian Chabot >> > > Two other thoughts: > > - Is SELinux enabled? Check the logs and see if there's anything > strange there. > - try using strace to see which call returns the error. It might give > you a clue about what it's trying to do. > _______________________________________________ > gnhlug-discuss mailing list > gnhlug-discuss@mail.gnhlug.org > http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/ _______________________________________________ gnhlug-discuss mailing list gnhlug-discuss@mail.gnhlug.org http://mail.gnhlug.org/mailman/listinfo/gnhlug-discuss/