On 11/13/2012 03:46 PM, Darin Perusich wrote:
This is systemd weirdness. I've run into this error before on SuSE
with other init scripts and the fix was to reboot the machine. Then
you won't get the "Loaded: error (Reason: No such file or directory)"
anymore.
:-/
A little offtopic but I'm not
Just to finish this one up, I had the service name wrong.
# puppet resource service puppetagent enable=yes ensure=running
Works just fine.
Bret
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To view this discussion on the web visit
https:/
On Tuesday, November 13, 2012 12:03:36 PM UTC-5, Michael Stanhke wrote:
>
> On Tue, Nov 13, 2012 at 8:31 AM, Bret Wortman
> >
> wrote:
> > It is kind of funny that we're talking about using puppet's tricks for
> > working around bad start scripts for puppet's own software
> >
> >
> > On
On Tue, Nov 13, 2012 at 8:31 AM, Bret Wortman wrote:
> It is kind of funny that we're talking about using puppet's tricks for
> working around bad start scripts for puppet's own software
>
>
> On Tuesday, November 13, 2012 9:58:57 AM UTC-5, jcbollinger wrote:
>>
>>
>>
>> On Tuesday, November 1
It is kind of funny that we're talking about using puppet's tricks for
working around bad start scripts for puppet's own software
On Tuesday, November 13, 2012 9:58:57 AM UTC-5, jcbollinger wrote:
>
>
>
> On Tuesday, November 13, 2012 7:40:08 AM UTC-6, Martin Alfke wrote:
>>
>> Hi Bret,
>>
>
This problem has continued through multiple reboots across multiple systems.
On Tuesday, November 13, 2012 9:47:03 AM UTC-5, Darin Perusich wrote:
>
> This is systemd weirdness. I've run into this error before on SuSE
> with other init scripts and the fix was to reboot the machine. Then
> you wo
On Tuesday, November 13, 2012 7:40:08 AM UTC-6, Martin Alfke wrote:
>
> Hi Bret,
>
> On 13.11.2012, at 13:18, Bret Wortman wrote:
>
> I'm getting this problem on all the puppet client's I've been setting up
> and it's got me both scratching my head (because I'm not seeing anything
> obvious in
This is systemd weirdness. I've run into this error before on SuSE
with other init scripts and the fix was to reboot the machine. Then
you won't get the "Loaded: error (Reason: No such file or directory)"
anymore.
--
Later,
Darin
On Tue, Nov 13, 2012 at 9:29 AM, Bret Wortman wrote:
> It does no
It does not (and this is odd since I'm using F17):
# service puppet status
Redirecting to /bin/systemctl status puppet.service
puppet.service
Loaded: error (Reason: No such file or directory)
Active: inactive (dead)
and yet ps still shows it running.
But with your help, this a
Hi Bret,
On 13.11.2012, at 13:18, Bret Wortman wrote:
> I'm getting this problem on all the puppet client's I've been setting up and
> it's got me both scratching my head (because I'm not seeing anything obvious
> in any system logs) and pausing in my rollout until I get it solved:
>
> # puppe
I'm getting this problem on all the puppet client's I've been setting up
and it's got me both scratching my head (because I'm not seeing anything
obvious in any system logs) and pausing in my rollout until I get it solved:
# puppet resource service puppet ensure=running enable=true
Error: Could
11 matches
Mail list logo
