Bug 1004064

Summary:	beaker-init command listed in documentation errors out
Product:	[Retired] Beaker	Reporter:	Tim Flink <tflink>
Component:	Doc	Assignee:	beaker-dev-list
Status:	CLOSED DUPLICATE	QA Contact:	tools-bugs <tools-bugs>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	0.14	CC:	aigao, asaha, dcallagh, llim, qwan, rmancy
Target Milestone:	---	Keywords:	Documentation
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-27 05:17:51 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tim Flink 2013-09-03 20:27:22 UTC

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

Comment 2 Nick Coghlan 2013-09-04 04:05:36 UTC

I guess the "su" command requires that the apache user have a login shell defined, which is a bad assumption.

Comment 3 Amit Saha 2013-09-04 04:13:13 UTC

(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.

Comment 4 Dan Callaghan 2013-09-04 07:55:10 UTC

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.

Comment 5 Amit Saha 2013-09-04 08:00:40 UTC

(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.

Comment 7 Raymond Mancy 2013-11-27 05:17:51 UTC


*** This bug has been marked as a duplicate of bug 1032377 ***