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 <b...@thewortmans.org> wrote:
> 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 at least starts it now, but I can't get the
> "ensure" bit working, and that's the really critical piece for us. Looks
> like Puppet is expecting to chkconfig this and that's not working. I also
> have no file in /etc/init.d at all, so there's apparently no start script on
> my system at all. I installed from the Puppetlabs repos.
>
> # puppet resource service puppet hasstatus=false ensure=running enable=true
> Error: Could not enable puppet: Execution of '/sbin/chkconfig puppet on'
> returned 1: error reading information on service puppet: No such file or
> directory
> :
> :
> service { 'puppet':
> ensure => running,
> enable => false,
> }
> #
>
> On Tuesday, November 13, 2012 8:40:08 AM UTC-5, 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 any system logs) and pausing in my rollout until I get it solved:
>>
>> # puppet resource service puppet ensure=running enable=true
>>
>>
>> does the service script has a status option and does the status deliver
>> proper results?
>>
>> service puppet status
>>
>> Some service scripts do not check properly for the status or they deliver
>> wrong exit codes.
>> If this is the case you can set
>> hasstatus => false
>>
>> hth,
>>
>> Martin
>>
>> Error: Could not start Service[puppet]: Execution of '/sbin/service puppet
>> start' returned 1:
>> Error: /Service[puppet]/ensure: change from stopped to running failed:
>> Could not start Service[puppet]: Execution of '/sbin/service puppet start'
>> returned 1:
>> service { 'puppet':
>> ensure => 'stopped',
>> enable => 'false',
>> }
>> # ps aux | grep 'puppet agent' | grep -v grep
>> # puppet agent
>> # ps aux | grep 'puppet agent' | grep -v grep
>> root 55055 12.4 0.1 383924 45928 ? Ssl 07:15 0:01
>> /usr/bin/ruby /bin/puppet agent
>> #
>>
>> Where should I look first? I'm not sure why this will start for me
>> interactively but not from the agent (this also fails if the agent is
>> already running in exactly the same fashion).
>>
>> Thanks!
>>
>>
>> Bret Wortman
>>
>> --
>> 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/-/Craxa7MPMXUJ.
>> To post to this group, send email to puppet...@googlegroups.com.
>> To unsubscribe from this group, send email to
>> puppet-users...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/puppet-users?hl=en.
>>
>>
> --
> 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/-/62Ns4IuyUJgJ.
> To post to this group, send email to puppet-users@googlegroups.com.
> To unsubscribe from this group, send email to
> puppet-users+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/puppet-users?hl=en.
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
