I just tried to install puppet 3.0.0rc2 using source rpm.
The following 2 lines should be moved to be in section "%package
server":
Requires: hiera >= 1.0.0
Requires: hiera-puppet >= 1.0.0
And the spec file does not mention files under /sbin, like
puppetmasterd, and I could not find
If you're running puppet as a daemon with selinux in enforcing mode, I
think you may need to run:
setsebool puppetmaster_use_db on
In the current state and presuming that the audit daemon is running,
/var/log/audit/audit.log should be reporting which aspect of selinux is
preventing the access req
I have set ours up like this.
One top-level puppet server, hosting the CA, Filebucket, and Dashboard. This
uses mod_balancer and mod_proxy to route to...
Three backend puppet masters, handling the production environment manifests
One backend puppet server, handling the dev and test environment
solved:
cat /path/to/sqlfile.sql | /usr/bin/mysql -uroot -ppass
works. Obviously some issue with the redirection.
On Monday, 28 May 2012 06:18:45 UTC+10, hohum wrote:
>
> I'm a noob. I'm wondering if I'm doing something fundamentally wrong and
> am looking for some debugging advise.
>
> I get
Hi,
[snip]
>
>- Hack the RPM package names to include a version discriminator (e.g.
>"packageV1-1.0-noarch.rpm" rather than "package-1.0-noarch.rpm") to allow
>them all to be installed on Puppet maste
>
> This is a practice that is already used for the kernel, so it seems like a
legit
I'm a noob. I'm wondering if I'm doing something fundamentally wrong and
am looking for some debugging advise.
I get an error that the exec command failed because it returned 1 instead
of 0 but when I copy the command puppet outputs as an error, and paste that
into a shell it works perfectly.
Using Phusion Passenger RPM Repository for my 300+ nodes cluster and worked
fine, so far. Cheers!!
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/puppet-users/-/at049cpe
you need to run this command from the dashboard's root directory e.g. *
/usr/share/puppet-dashboard/*
Cheers!!
On Sunday, May 27, 2012 2:13:12 AM UTC+1, Gmoney wrote:
>
> Whenever i run this command i get this error, how do I resolve it?
>
> rake RAILS_ENV=production db:migrate --trace
> rake
This error is due to the attributes which are applied to the paticular file.
Check lsattr & remove the chattr attribute then run puppet
again
mac
On Fri, May 25, 2012 at 11:22 PM, Ed Greenberg wrote:
> I have three (out of 90) machines with the error: cannot generate
> tempfile `/tmp/pupp
Thanks Brian!
I'm still trying to find out how to make it work, with no such joy so far.
Anyone from PuppetLab care to comment?
Cheers!!
On Monday, May 14, 2012 1:08:38 PM UTC+1, Brian Gupta wrote:
>
> I've run into permission errors like this if apparmor is enabled, and not
> configured for t
10 matches
Mail list logo