In the beaker installation documentation at: http://beaker-project.org/docs/admin-guide/installation.html It says to run: su apache -c 'beaker-init -u admin -p testing -e root@localhost' On my RHEL6.4 server, this errors out every time: [root@localhost ~]# su apache -c 'beaker-init -u admin -p testing -e root@localhost' This account is currently not available. But if I change the command to be the following, it works: sudo -u apache beaker-init -u admin -p testing -e root@localhost
I guess the "su" command requires that the apache user have a login shell defined, which is a bad assumption.
(In reply to Nick Coghlan from comment #2) > I guess the "su" command requires that the apache user have a login shell > defined, which is a bad assumption. su apache -s /bin/bash -c 'beaker-init -u admin -p testing -e root@localhost' should work.
Does it even need to run as apache anymore? I thought the only reason was to avoid it writing to the beaker logs as root, but they go to syslog (or in this case, stderr) now.
(In reply to Dan Callaghan from comment #4) > Does it even need to run as apache anymore? I thought the only reason was to > avoid it writing to the beaker logs as root, but they go to syslog (or in > this case, stderr) now. Actually yes, I was thinking the same. I don't recall running it as apache. So, we basically need to update our documentation.
*** This bug has been marked as a duplicate of bug 1032377 ***