So I get the move to systemd (whatever that is) if that's what Fedora uses,
but why rename the service, that means I have to add a special case in my
puppet module just for Fedora to set the name of the service resource to
puppetagent? Unless it's a change they're going to roll out to all their
Yep that worked, I had to enable the puppetlabs-devel repo in
/etc/yum.repos.d/puppetlabs.repo (instead of yum
--enablerepo=puppetlabs-devel) but it works fine now, lesson learned :)
Thanks
--
You received this message because you are subscribed to the Google Groups
Puppet Users group.
To
Wait... spoke too soon:
*Error: Could not start Service[puppet]: Execution of '/sbin/service puppet
start' returned 6: *
*Error: /Stage[main]/Puppet/Service[puppet]/ensure: change from stopped to
running failed: Could not start Service[puppet]: Execution of
'/sbin/service puppet start' returned
It would seem that the puppet package has been removed/changed. Reinstall it
again.
Craig
On May 20, 2013, at 3:36 PM, Tom Poulton wrote:
Wait... spoke too soon:
Error: Could not start Service[puppet]: Execution of '/sbin/service puppet
start' returned 6:
Error:
Yeah they switched to systemd on fedora so the init scripts went away
(finally!)
They also renamed the service to puppetagent
Try this.
systemctl start puppetagent
On 21 May 2013 08:36, Tom Poulton poulton...@gmail.com wrote:
Wait... spoke too soon:
*Error: Could not start Service[puppet]:
I setup the Puppet Labs yum repo via sudo rpm -ivh
http://yum.puppetlabs.com/el/6/products/i386/puppetlabs-release-6-6.noarch.rpm
So far between me and a colleague we've tried:
F18 GNOME:
Seemed fine I think (but GNOME 3 didn't play nice with VirtualBox, very
very slow)
F18 KDE: Initially
Tom,
Why are installing the EL 6 release package for Fedora 18? Have you
tried
http://yum.puppetlabs.com/fedora/f18/products/i386/puppetlabs-release-18-7.noarch.rpm
instead?
On Fri, May 17, 2013 at 1:04 PM, Tom Poulton poulton...@gmail.com wrote:
I setup the Puppet Labs yum repo via sudo rpm
Hahaha, I didn't even think about that, I just copied the script blindly
from out EC2 setup, that'll teach me
I'll test it out on Monday morning and update
If that is the answer: thanks in advance
Tom
--
You received this message because you are subscribed to the Google Groups
Puppet Users
I'm using Fedora 18 KDE in VirtualBox, fresh install this morning with full
updates using yum.
I installed puppet by adding the puppet labs yum repo and then sudo yum
install puppet, so now I'm running puppet version 3.1.1
Running puppet --version or sudo puppet agent --test gave me the
Hi Tom,
Fedora 18 is the standard environment for new nodes in my environemnt and I
have never had this issue getting puppet to work.
Admittedly I have two repos setup, one for fedora 17 with a low priority
and one for 18 with normal priority.
I was running the fedora 17 repos before they started
10 matches
Mail list logo
