Package: puppet Version: 0.23.2-13 Severity: normal When restarting puppetmaster after puppetd, when both run on the same node, I get this warning:
Nov 20 06:21:29 puppet puppetmasterd[32165]: (/puppetconfig/main/File[/var/lib/puppet/state/state.yaml]/mode) change from 640 to 660 failed: failed to chmod /var/lib/puppet/state/state.yaml: Operation not permitted - /var/lib/puppet/state/state.yaml This is because puppet changed the directory back to root:root when being restarted (I guess!). Fixing the permissions to puppet:puppet silences the warning, until puppetd is restarted. I think the state directory should be seperate for puppet and puppetmaster. -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (990, 'stable'), (1, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.22-1-686 Locale: LANG=fr_CA.UTF-8, LC_CTYPE=fr_CA.UTF-8 (charmap=UTF-8) Versions of packages puppet depends on: ii adduser 3.102 Add and remove users and groups ii facter 1.3.5-1 a library for retrieving facts fro ii libopenssl-ruby 1.0.0+ruby1.8.2-1 OpenSSL interface for Ruby ii libshadow-ruby1.8 1.4.1-7 Interface of shadow password for R ii libxmlrpc-ruby 1.8.2-1 XML-RPC support for Ruby ii lsb-base 3.1-23.2etch1 Linux Standard Base 3.1 init scrip ii ruby 1.8.2-1 An interpreter of object-oriented Versions of packages puppet recommends: ii rdoc 1.8.2-1 Generate documentation from ruby s -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
