We have Upgraded Puppet 0.24.8 to 0.25.4 but we''re seeing init script
problem with 0.25.4.
On Linux where we''re using the init script included with Puppet itself,
puppet-server.pid" This everytime happens when I run
''/etc/init.d/puppet
start'' on the command line.
Here''s a sample:
Starting Puppet:
# /etc/init.d/puppet-server start
Starting puppetmaster service [Failed] //but actually the
puppet server process is started
# ps -ef | grep puppet
puppet 8732 1 0 12:23 ? 00:00:00 ruby
/usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp
--logdest=/var/log/puppet/puppetmaster.log
Stopping puppet:
# /etc/init.d/puppet-server stop
Shutting down puppetmaster [done]: //but actually it isn''t
shutsdown the server and the process is still running
Restarting the Server:
# /etc/init.d/puppet-server start
Starting puppet: Could not prepare for execution: Could not
create PID file: /var/puppet/run/puppetmaster.pid
this is happening with the client too.
what is the problem here? is it a file permission issue?
looking forward to hear some replies
--
M. Haris Farooque
--
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+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
I had a similiar problem... Have a look at your init script. In my case there was a line like this "startproc $PUPPETMASTER $PUPPETMASTER_OPTS". Change the line to "$PUPPETMASTER $PUPPETMASTER_OPTS" and when you start puppet again the script should report a success. And for the shutting down problem I think you should check if $pidfile points to the correct pidfile...in my case it pointed to a wrong location and so the pid file wasn''t deleted when puppet was shut down. I hope that works for you, too. christian On 11 Mrz., 12:54, Haris Farooque <mfha...@fleetboard.com> wrote:> We have Upgraded Puppet 0.24.8 to 0.25.4 but we''re seeing init script > problem with 0.25.4. > > On Linux where we''re using the init script included with Puppet itself, > puppet-server.pid" This everytime happens when I run ''/etc/init.d/puppet > start'' on the command line. > > Here''s a sample: > > Starting Puppet: > > # /etc/init.d/puppet-server start > Starting puppetmaster service [Failed] //but actually the > puppet server process is started > # ps -ef | grep puppet > puppet 8732 1 0 12:23 ? 00:00:00 ruby > /usr/sbin/puppetmasterd --manifest=/etc/puppet/manifests/site.pp > --logdest=/var/log/puppet/puppetmaster.log > > Stopping puppet: > # /etc/init.d/puppet-server stop > Shutting down puppetmaster [done]: //but actually it isn''t > shutsdown the server and the process is still running > > Restarting the Server: > > # /etc/init.d/puppet-server start > Starting puppet: Could not prepare for execution: Could not > create PID file: /var/puppet/run/puppetmaster.pid > > this is happening with the client too. > > what is the problem here? is it a file permission issue? > > looking forward to hear some replies > -- > > M. Haris Farooque-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Zitat von christian <christian@cust.in>:> I had a similiar problem... > > Have a look at your init script. In my case there was a line like this > "startproc $PUPPETMASTER $PUPPETMASTER_OPTS". Change the line to > "$PUPPETMASTER $PUPPETMASTER_OPTS" and when you start puppet again the > script should report a success. > > And for the shutting down problem I think you should check if $pidfile > points to the correct pidfile...in my case it pointed to a wrong > location and so the pid file wasn''t deleted when puppet was shut down.is the faulty initscript upstream or from the distro. I assume latter regarding the name. So you might want to file it at the distro. cheers pete -- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
Well, I guess I should have mentioned that I''m using OpenSuse 11.1 and my puppet comes from their repositories ;) .... On 11 Mrz., 15:19, Peter Meier <peter.me...@immerda.ch> wrote:> Zitat von christian <christ...@cust.in>: > > > I had a similiar problem... > > > Have a look at your init script. In my case there was a line like this > > "startproc $PUPPETMASTER $PUPPETMASTER_OPTS". Change the line to > > "$PUPPETMASTER $PUPPETMASTER_OPTS" and when you start puppet again the > > script should report a success. > > > And for the shutting down problem I think you should check if $pidfile > > points to the correct pidfile...in my case it pointed to a wrong > > location and so the pid file wasn''t deleted when puppet was shut down. > > is the faulty initscript upstream or from the distro. I assume latter > regarding the name. So you might want to file it at the distro. > > cheers pete-- 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+unsubscribe@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.