Issue #16137 has been updated by Curtis Ruck.
The discrepancy with /sbin/service in (at least in RHEL) is by design, it
starts the init.d script with this line:
env -i PATH="$PATH" TERM="$TERM" "${SERVICEDIR}/${SERVICE}" ${OPTIONS}
The -i ignore's the existing environment variables, and it only sets PATH and
TERM.
Some other alternatives would be to use "su -l" or "runuser -l" instead of
daemon to launch the process. These would create login shells, and they would
have that user's full environment from /etc/profile.
----------------------------------------
Bug #16137: Cannot start Puppet service on Ubuntu
https://projects.puppetlabs.com/issues/16137#change-70145
Author: Justin Downing
Status: In Topic Branch Pending Review
Priority: Normal
Assignee: eric sorenson
Category:
Target version: 3.0.0
Affected Puppet version: 3.0.0-rc4
Keywords:
Branch:
I bootstrapped a new server on EC2 today with 3.0rc4 from Puppetlabs apt repo.
However, the service will not start:
root@tst01:~# service puppet start
* Starting puppet agent Error: Could not get application-specific
default settings: couldn't find HOME environment -- expanding `~/.puppet'
[fail]
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://projects.puppetlabs.com/my/account
--
You received this message because you are subscribed to the Google Groups
"Puppet Bugs" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/puppet-bugs?hl=en.
