On Tue, Nov 24, 2009 at 2:19 AM, Adrian Bridgett <adr...@smop.co.uk> wrote: > Package: puppet > Version: 0.25.1-2 > > Hi there, > > I've upgraded my clients and received this error: > err: Could not retrieve catalog from remote server: No such file or > directory - /var/lib/puppet/client_yaml/catalog > > This turned out to be caused by /var/lib/puppet/client_yaml not > existing on the client (not puppetmaster). A strace shows:
Adrian, are you sure you were on 0.25.1-2 ? This looks like it should have been fixed upstream with: http://projects.reductivelabs.com/issues/2237 at least upstream seems to think so :) > > 6114 stat64("/var/lib/puppet/client_yaml/catalog", 0xffc5b988) = -1 > ENOENT (No such file or directory) > 6114 mkdir("/var/lib/puppet/client_yaml/catalog", 0777) = -1 ENOENT > (No such file or directory) > > As /var/lib/puppet/client_yaml does not exist that mkdir is failing. > Creating it owned by root seems to be acceptible, it doesn't need to > be owned by puppet. > > puppet.conf contains: > [main] > logdir=/var/log/puppet > vardir=/var/lib/puppet > ssldir=$vardir/ssl > rundir=/var/run/puppet > factpath=$vardir/lib/facter > pluginsync=true > dbmigrate=true > server=puppet1.example.com > > [puppetmasterd] > templatedir=/etc/puppet/templates > factpath=/etc/puppet/facts > certname=puppet1.example.com > storeconfigs=true > dbadapter=sqlite3 > > [puppetca] > certname=puppet1.example.com > > [puppetd] > catalog_format=marshal > runinterval=7200 > #report=true > > > Adrian > -- > bitcube.co.uk - Linux infrastructure consultancy > Puppet, Debian, Red Hat, Ubuntu, CentOS, ... > > > > _______________________________________________ > Pkg-puppet-devel mailing list > pkg-puppet-de...@lists.alioth.debian.org > http://lists.alioth.debian.org/mailman/listinfo/pkg-puppet-devel > -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
