Hi Steve,
Thanks for your pointers, although still with no results (which
probably is the fault of my still meager puppet-knowledge)...
Indeed the libs weren't copied to /var/lib/puppet/lib/* but doing so
did not solve the problem: still no db gets created, still no errors
in the logfile.
I'm
So you probably thought the Dashboard didn't love you anymore ... that
we'd forgotten about you and we're very sorry for that. But we're
trying to make up for it ... starting with the Puppet Dashboard 1.0.1
release.
The 1.0.1 release is a maintenance release that fixes a lot of the
outstanding
Hi all
I've updated the RPM and DEB packages for the Puppet Dashboard 1.0.1
release. These packages are now signed with our new Puppet Labs GPG key
- this means you will need to update the keys you have added previously.
The new packages are available via APT and Yum repositories hosted by
Hi, I'm just gettting back into using puppet.
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=10.04
DISTRIB_CODENAME=lucid
DISTRIB_DESCRIPTION=Ubuntu 10.04 LTS
On install adduser mentioned that the /var/lib/puppet directory was
not owned by the puppet user.
What's the workaround for this?
--
You received
Are there recipes in puppet to deal with configuring nginx virtual
host files?
Ideally they'd be parameterized..
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe
On Sat, Jul 17, 2010 at 11:40 AM, kevin lazy...@gmail.com wrote:
On install adduser mentioned that the /var/lib/puppet directory was
not owned by the puppet user.
What's the workaround for this?
The problem is the package you're using is probably setting the puppet
account home directory to
There is a related issue:http://projects.puppetlabs.com/issues/4204
Please update the issue with your own experiences and issues if it
looks to be the same as you're experiencing.
Yikes. Must be a better way...
--
You received this message because you are subscribed to the Google Groups
On Sat, Jul 17, 2010 at 1:18 PM, kevin lazy...@gmail.com wrote:
There is a related issue:http://projects.puppetlabs.com/issues/4204
Please update the issue with your own experiences and issues if it
looks to be the same as you're experiencing.
Yikes. Must be a better way...
A better way
Done.
http://projects.puppetlabs.com/issues/4266
http://projects.puppetlabs.com/issues/4267
Also: for those that've never gone through this process before (such as me),
could use a hint somewhere on the bugtracker (at least on the Issues page)
that you need to register to create a new issue.
Jim Bala wrote:
Also: for those that've never gone through this process before (such
as me), could use a hint somewhere on the bugtracker (at least on the
Issues page) that you need to register to create a new issue.
Since the New Issue link doesn't show up at all until you've
registered and
At least to me, the optimal placement would be under the New Issue tab, which
is always there regardless of login status. If you aren't logged in, it says,
Please login or register for an account to create a new issue. Just seems
counterintuitive to hide the tab/link.
-Jim
On Jul 17, 2010,
Jim Bala wrote:
At least to me, the optimal placement would be under the New Issue
tab, which is always there regardless of login status. If you aren't
logged in, it says, Please login or register for an account to
create a new issue. Just seems counterintuitive to hide the
tab/link.
12 matches
Mail list logo
