After a clean install i type #apt-get install puppet following which i change the line in /etc/default/puppet from START=no to START=yes
then i join the puppet client to my puppet server using #puppetd --server servername --waitforcert 60 --test on the client side and #puppetca --sign servername on the server side then the following session can occur: root@testserv1:~# pgrep puppet root@testserv1:~# dpkg -s puppet Package: puppet Status: install ok installed Priority: optional Section: admin Installed-Size: 336 Maintainer: Ubuntu Developers <ubuntu-devel-disc...@lists.ubuntu.com> Architecture: all Version: 2.7.11-1ubuntu2.1 Depends: puppet-common (= 2.7.11-1ubuntu2.1), ruby1.8 Pre-Depends: dpkg (>= 1.15.7.2) Recommends: rdoc Suggests: puppet-el, vim-puppet, etckeeper Conffiles: /etc/init.d/puppet 05404948b351469e8d56ac080f5d92fe /etc/default/puppet 9e5a0cf174ccff1af10342297b8b1bdb Description: Centralized configuration management - agent startup and compatibility scripts This package contains the startup script and compatbility scripts for the puppet agent, which is the process responsible for configuring the local node. . Puppet lets you centrally manage every important aspect of your system using a cross-platform specification language that manages all the separate elements normally aggregated in different files, like users, cron jobs, and hosts, along with obviously discrete elements like packages, services, and files. . Puppet's simple declarative specification language provides powerful classing abilities for drawing out the similarities between hosts while allowing them to be as specific as necessary, and it handles dependency and prerequisite relationships between objects clearly and explicitly. Homepage: http://projects.puppetlabs.com/projects/puppet Original-Maintainer: Puppet Package Maintainers <pkg-puppet-de...@lists.alioth.debian.org> root@testserv1:~# uname -a Linux testserv1 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:16:45 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux root@testserv1:~# cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=12.04 DISTRIB_CODENAME=precise DISTRIB_DESCRIPTION="Ubuntu 12.04.1 LTS" root@testserv1:~# /etc/init.d/puppet start * Starting puppet agent ...done. root@testserv1:~# pgrep puppet 8459 root@testserv1:~# /etc/init.d/puppet stop * Stopping puppet agent ...done. root@testserv1:~# pgrep puppet 8459 root@testserv1:~# /etc/init.d/puppet start * Starting puppet agent ...done. root@testserv1:~# pgrep puppet 8459 8941 root@testserv1:~# /etc/init.d/puppet stop * Stopping puppet agent ...done. root@testserv1:~# pgrep puppet 8459 8941 root@testserv1:~# /etc/init.d/puppet start * Starting puppet agent ...done. root@testserv1:~# pgrep puppet 8459 8941 9395 root@testserv1:~# pkill puppet root@testserv1:~# pgrep puppet 9395 root@testserv1:~# pkill puppet root@testserv1:~# pgrep puppet root@testserv1:~# exit as you can see, the /etc/init.d/puppet stop appears to have no effect - puppet processes remain running after it is called. the reason appears to be because the /etc/init.d/puppet file contains the line: PIDFILE="/var/run/puppet/${NAME}.pid" I assume in this case ${NAME} resolves to "puppet" therefore when it is attempting to stop puppet it searches for /var/run/puppet/puppet.pid but the agent creates /var/run/puppet/agent.pid Simply changing the line in the /etc/init.d/puppet file from "${NAME}" to "agent" should (and does) solve the problem -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1060184 Title: puppet client init script pid file error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
