Ask Your Question

Arguments to Resource[] are all empty/undefined

asked 2016-12-05 10:17:40 -0500

craymore gravatar image

updated 2016-12-05 10:19:53 -0500

Hi all !

I am currently trying to indentify the cause for some warnings I have in one of our puppet master logfile :

INFO  [puppet-server] Puppet Caching node for <nodename>
WARN  [puppet-server] Puppet Arguments to Resource[] are all empty/undefined
WARN  [puppet-server] Puppet Arguments to Resource[] are all empty/undefined
INFO  [puppet-server] Puppet Compiled catalog for <nodename> in environment <envname> in 3.83 seconds

This doesn't prevent the catalog from being compiled, but I would like to locate the piece of code that actually leads to these warnings.

How could I do that ?

Tanks beforehand

edit retag flag offensive close merge delete


I don't have further insight into this, but here is the parameter in the puppet codebase..

DarylW gravatar imageDarylW ( 2016-12-05 11:17:48 -0500 )edit

Indeed, that code statement is issuing the message I'm seing, but I was hoping that there might be an easier solution than going low-level debugging

craymore gravatar imagecraymore ( 2016-12-06 03:04:50 -0500 )edit

2 Answers

Sort by ยป oldest newest most voted

answered 2016-12-06 04:43:03 -0500

daft question - have you tried a puppet agent -t --debug on the nodename referenced in the logs? it could get you closer to seeing which module/manifest this warning is coming from.

edit flag offensive delete link more


I did a command line debug on the agent, but did not find more information on what the errors could be ( this warning only appears in the puppet master log )

craymore gravatar imagecraymore ( 2016-12-06 10:59:32 -0500 )edit

answered 2016-12-07 03:40:01 -0500

Henrik Lindberg gravatar image

It may be that you are on a version of puppet where there are issues with location information. The latest puppet produces file and line information for that warning.

The error occurs on the master side. In the latest version the warning is only issued if master --debug is on, the message is otherwise ignored. The cause is something like File[undef] (or some other resource type than File), or Class[undef]. Most likely caused by an expression that results in empty string or undef.

Try a puppet apply and see if that gives you file/line. If it does please file an issue for Puppet Server about location information missing.

edit flag offensive delete link more


I am currently running puppet server 1.2.0 / puppet 3.8.7 ( migration process to puppet 4.x is ongoing tough, so it's a good thing that the latest version provides more infos ) puppet apply doesn't give more clues, but I will have a look at the possible resources undef expressions

craymore gravatar imagecraymore ( 2016-12-07 04:21:54 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

1 follower


Asked: 2016-12-05 10:17:40 -0500

Seen: 40 times

Last updated: Dec 07 '16