kbintl2@gmail.com
2008-Nov-30 05:05 UTC
[Puppet Users] err: Parameter path failed: File paths must be fully qualified
We have run puppet version 0.23.1 for a long time and today having
upgraded to version 0.24.6 (lastest), running puppetd on the client
now fails on error;
err: Could not create : Parameter path failed: File paths must be
fully qualified
err: Parameter path failed: File paths must be fully qualified
We downgraded back to version 0.23.1 and ran puppetd again and it also
outputs this same error as above, but continues on with configuration
(0.24.6 aborts on this error).
Based on the error (File paths must be fully qualified), we suspect
that is an issue with one of our manifest/module files, however which
one? When running in debug mode it doesn''t give any clue as to what is
causing the error. The debug output is below, however does anyone
have any suggestions on how this can be resolved?
Thanks,
Paul
---------------
# puppetd --server <server> -v --test --debug --trace
debug: Parsing /etc/puppet/puppet.conf
info: Loading fact if_name
info: Loading fact if_broadcast
debug: /puppetconfig/main/File[/var/lib/puppet/lib]: Autorequiring File
[/var/lib/puppet]
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/private]:
Autorequiring File[/var/lib/puppet/ssl]
debug: /puppetconfig/puppetd/File[/var/lib/puppet/state/puppetdlock]:
Autorequiring File[/var/lib/puppet/state]
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/public_keys/
<hostname>.pem]: Autorequiring File[/var/lib/puppet/ssl/public_keys]
debug: /puppetconfig/puppetd/File[/var/lib/puppet/localconfig]:
Autorequiring File[/var/lib/puppet]
debug: /puppetconfig/main/File[/var/lib/puppet/plugins]: Autorequiring
File[/var/lib/puppet]
debug: /puppetconfig/main/File[/var/lib/puppet/facts]: Autorequiring
File[/var/lib/puppet]
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/certs]:
Autorequiring File[/var/lib/puppet/ssl]
debug: /puppetconfig/main/File[/var/lib/puppet/state]: Autorequiring
File[/var/lib/puppet]
debug: /puppetconfig/main/File[/var/lib/puppet/state/state.yaml]:
Autorequiring File[/var/lib/puppet/state]
debug: /puppetconfig/puppetd/File[/var/log/puppet/http.log]:
Autorequiring File[/var/log/puppet]
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/public_keys]:
Autorequiring File[/var/lib/puppet/ssl]
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/private/password]:
Autorequiring File[/var/lib/puppet/ssl/private]
debug: /puppetconfig/main/File[/var/lib/puppet/ssl]: Autorequiring File
[/var/lib/puppet]
debug: /puppetconfig/main/File[/etc/puppet/namespaceauth.conf]:
Autorequiring File[/etc/puppet]
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/private_keys]:
Autorequiring File[/var/lib/puppet/ssl]
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/csr_<hostname>.pem]:
Autorequiring File[/var/lib/puppet/ssl]
debug: /puppetconfig/puppetd/File[/var/lib/puppet/classes.txt]:
Autorequiring File[/var/lib/puppet]
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/certs/
<hostname>.pem]: Autorequiring File[/var/lib/puppet/ssl/certs]
debug: /puppetconfig/puppetd/File[/etc/puppet/puppet.conf]:
Autorequiring File[/etc/puppet]
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/certs/ca.pem]:
Autorequiring File[/var/lib/puppet/ssl/certs]
debug: /puppetconfig/puppetd/File[/var/log/puppet/puppetd.log]:
Autorequiring File[/var/log/puppet]
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/private_keys/
<hostname>.pem]: Autorequiring File[/var/lib/puppet/ssl/private_keys]
debug: /puppetconfig/main/File[/etc/puppet/namespaceauth.conf]: File
does not exist
debug: /puppetconfig/puppetd/File[/var/log/puppet/puppetd.log]: File
does not exist
debug: /puppetconfig/puppetd/File[/var/log/puppet/http.log]: File does
not exist
debug: /puppetconfig/main/File[/var/lib/puppet/plugins]: File does not
exist
debug: /puppetconfig/puppetd/File[/var/lib/puppet/localconfig]: File
does not exist
debug: /puppetconfig/ssl/File[/var/lib/puppet/ssl/private/password]:
File does not exist
debug: /puppetconfig/puppetd/File[/var/lib/puppet/state/puppetdlock]:
File does not exist
debug: Finishing transaction -605629618 with 0 changes
debug: Creating default schedules
debug: Loaded state in 0.00 seconds
debug: Retrieved facts in 0.05 seconds
notice: Ignoring cache
debug: getting config
debug: Calling puppetmaster.getconfig
debug: Retrieved configuration in 2.34 seconds
info: Caching configuration at /var/lib/puppet/localconfig.yaml
debug: Finishing transaction -612171388 with 0 changes
debug: package provider rpm: Executing ''/bin/rpm -ql rpm''
debug: package provider yum: Executing ''/bin/rpm -ql rpm''
debug: package provider aptrpm: Executing ''/bin/rpm -ql rpm''
debug: package provider urpmi: Executing ''/bin/rpm -ql rpm''
debug: package provider aptitude: Not suitable: missing /usr/bin/
aptitude
debug: package provider appdmg: Not suitable: missing /Library/
Receipts
debug: package provider rpm: Not suitable: false value
debug: package provider sun: Not suitable: missing /usr/bin/pkginfo
debug: package provider sunfreeware: Not suitable: missing pkg-get
debug: package provider rug: Not suitable: operatingsystem not in suse
debug: package provider apt: Not suitable: missing /usr/bin/apt-get
debug: package provider portage: Not suitable: missing /usr/bin/emerge
debug: package provider fink: Not suitable: missing /sw/bin/fink
debug: package provider dpkg: Not suitable: missing /usr/bin/dpkg
debug: package provider apple: Not suitable: missing /Library/Receipts
debug: package provider gem: Not suitable: missing gem
debug: package provider ports: Not suitable: missing /usr/local/sbin/
pkg_deinstall
debug: package provider pkgdmg: Not suitable: missing /Library/
Receipts
debug: package provider up2date: Not suitable: operatingsystem not in
redhat
debug: package provider darwinport: Not suitable: operatingsystem not
in Darwin
debug: package provider aptrpm: Not suitable: missing apt-get
debug: package provider freebsd: Not suitable: operatingsystem not in
freebsd
debug: package provider urpmi: Not suitable: missing urpmi
debug: package provider openbsd: Not suitable: operatingsystem not in
openbsd
debug: package provider blastwave: Not suitable: missing pkg-get
debug: package provider yum: Not suitable: false value
debug: package provider yum: Not suitable: false value
debug: package provider yum: Not suitable: false value
debug: package provider yum: Not suitable: false value
debug: package provider yum: Not suitable: false value
debug: package provider yum: Not suitable: false value
err: Could not create : Parameter path failed: File paths must be
fully qualified
err: Parameter path failed: File paths must be fully qualified
debug: package provider yum: Not suitable: false value
debug: service provider smf: Not suitable: missing /usr/sbin/svcadm
debug: service provider debian: Not suitable: missing /usr/sbin/update-
rc.d
debug: service provider gentoo: Not suitable: missing /sbin/rc-update
debug: Puppet::Network::Client::File: defining fileserver.describe
debug: Puppet::Network::Client::File: defining fileserver.list
debug: Puppet::Network::Client::File: defining fileserver.retrieve
notice: Starting configuration run
debug: Prefetching yum resources for package
debug: package provider yum: Executing ''/bin/rpm -qa --nosignature --
nodigest --qf ''%{NAME} %{VERSION}-%{RELEASE}
''''
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
James Turnbull
2008-Nov-30 07:31 UTC
[Puppet Users] Re: err: Parameter path failed: File paths must be fully qualified
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 kbintl2@gmail.com wrote:> We have run puppet version 0.23.1 for a long time and today having > upgraded to version 0.24.6 (lastest), running puppetd on the client > now fails on error; > > err: Could not create : Parameter path failed: File paths must be > fully qualified > err: Parameter path failed: File paths must be fully qualified > > We downgraded back to version 0.23.1 and ran puppetd again and it also > outputs this same error as above, but continues on with configuration > (0.24.6 aborts on this error). >Do you have any non-fully qualified file paths in your resources, i.e. paths that don''t start with /? James Turnbull - -- Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/product/1590596099/) * Hardening Linux (http://www.amazon.com/gp/product/1590594444/) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJMkE89hTGvAxC30ARAtnvAKCN921+nCEnl87akmyJwD0cHXqVZwCgmJY/ UxE4n9drcjLSOkDTRhKc5Dg=QQ/w -----END PGP SIGNATURE----- --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---