Red Hat Satellite installer fails with error Failed to load feature test for posix: can't find user for 0.

Solution Verified - Updated -


  • Red Hat Satellite 6
  • Puppet


  • Satellite installer failing with following logs in /var/log/foreman-installer/satellite.log:
[ERROR 2019-03-18T09:53:04 main]  Systemd start for puppetserver failed!
[ERROR 2019-03-18T09:53:04 main] journalctl log for puppetserver:
[ERROR 2019-03-18T09:53:04 main] -- Logs begin at Tue 2019-03-12 17:09:35 CDT, end at Mon 2019-03-18 09:53:04 CDT. --
[ERROR 2019-03-18T09:53:04 main] Mar 18 09:52:24 prlsattl001 systemd[1]: Starting puppetserver Service...
[ERROR 2019-03-18T09:53:04 main] Mar 18 09:53:03 prlsattl001 puppetserver[16361]: Failed to load feature test for posix: can't find user for 0


  • Remove all/any hardening parameters on any of the filesystems:
[root@satellite]# cat /etc/fstab |grep -i tmp
/dev/mapper/system-tmp  /tmp                    xfs     nodev,noexec,nosuid 0 0

Root Cause

  • Puppet Server will not function if noexec permission is set on the temporary mount point that Java uses.

Diagnostic Steps

  • Hardening parameters set for /tmp:
[root@satellite]# mount | grep '/tmp' | grep -i noexec
/dev/mapper/system-tmp on /tmp type xfs (rw,nosuid,nodev,noexec,relatime,seclabel,attr2,inode64,noquota) [tmp]

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.


CIS benchmarks require /tmp to be mounted with 'noexec' option. This can be accommodated by adding "" to JAVA_ARGS variable in /etc/sysconfig/puppetserver. Simply telling people not to use 'noexec' is not a valid solution.

This solution provides different options to resolve the same problem: