Puppet users - Jul 2011 - err: Could not retrieve catalog from remote server: Could not intern from pson: Could not convert from pson: Could not find relationship target "File[]"

I''m running Puppet 2.7.1 on the master as well as the agent and just
received a new error which doesn''t actually reference a module or a
file, so
I''m somewhat stuck as to how to debug this. Any pointers?
The error is  err: Could not retrieve catalog from remote server: Could not
intern from pson: Could not convert from pson: Could not find relationship
target "File[]"

-- 
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.

On Fri, Jul 1, 2011 at 6:24 PM, Michael Halligan
<mhalligan@pagerduty.com>wrote:
> I''m running Puppet 2.7.1 on the master as well as the agent and
just
> received a new error which doesn''t actually reference a module or
a file, so
> I''m somewhat stuck as to how to debug this. Any pointers?
> The error is  err: Could not retrieve catalog from remote server: Could not
> intern from pson: Could not convert from pson: Could not find relationship
> target "File[]"
>
>
It looks like you''ve got a relationship defined somewhere including
something like  "File[$somevariable]" and $somevariable is undefined.

This is an annoying error as it is hard to debug. I tend to grep for
references matching the pattern above and analyse by hand if it''s a
small
enough set.

-- 
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.

This is usually because somewhere you have a File resource whose name
is a variable, and the variable''s undefined. So either:

package { "whatever" : ...  require =>
File["$somevariable"] }

- or -

file { "$somevariable":  .. .blah blah }

On Jul 1, 6:24 pm, Michael Halligan <mhalli...@pagerduty.com>
wrote:
> I''m running Puppet 2.7.1 on the master as well as the agent and
just
> received a new error which doesn''t actually reference a module or
a file, so
> I''m somewhat stuck as to how to debug this. Any pointers?
> The error is  err: Could not retrieve catalog from remote server: Could not
> intern from pson: Could not convert from pson: Could not find relationship
> target "File[]"
-- 
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.

On 07/02/2011 03:20 PM, Eric Sorenson wrote:
> This is usually because somewhere you have a File resource whose name
> is a variable, and the variable''s undefined.
And a common reason for that to happen is that you''ve
mistyped the variable name.  Your design could be just fine.

This is a good reason to test early and often.  It reduces the
search space to those files you recently touched.

-- 
vagn

-- 
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.

Forgive my cluelessness, but why is it so difficult for Puppet to at least
tell me what file this came from like 90% of other errors I''ve
encountered?

On Sat, Jul 2, 2011 at 12:33 PM, vagn scott <vagnscott@gmail.com> wrote:
> On 07/02/2011 03:20 PM, Eric Sorenson wrote:
>
>> This is usually because somewhere you have a File resource whose name
>> is a variable, and the variable''s undefined.
>>
> And a common reason for that to happen is that you''ve
> mistyped the variable name.  Your design could be just fine.
>
> This is a good reason to test early and often.  It reduces the
> search space to those files you recently touched.
>
> --
> vagn
>
>
> --
> 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 <puppet-users%2Bunsubscribe@googlegroups.com>.
> For more options, visit this group at http://groups.google.com/**
>
group/puppet-users?hl=en<http://groups.google.com/group/puppet-users?hl=en>
> .
>
>

-- 
Michael T. Halligan | DevOps Evangelist | @mhalligan | 415.722.1101

-- 
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.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 07/04/2011 08:49 PM, Michael Halligan wrote:
> Forgive my cluelessness, but why is it so difficult for Puppet to at least
> tell me what file this came from like 90% of other errors I''ve
encountered?
I don''t think there is a particular reason. Did you look for bugreports
and/or submitted an error message improvement request?

~pete
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk4SNOoACgkQbwltcAfKi38J0wCaA6xk3UiaUEXrxu3gVKbKYO2l
UHMAnRFfJc4icgV7Srt6Darz2Q54cqQO
=L6+R
-----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.

On 07/04/2011 02:49 PM, Michael Halligan wrote:
> Forgive my cluelessness, but why is it so difficult for Puppet to at 
> least tell me what file this came from
OK, I''ll take a crack at an answer.

---------------

typical compiler versus parser problem.

If the parser saw this, it could stop immediately
and say , hey, look here!  This ain''t right!

         File[ "$foo" ]]]]

But, the parser sees this, which is perfectly OK.

         File[ "$foo" ]

Much later, after all the files are read and the
details of syntax forgotten, it is finally evaluated
by the compiler as something not OK.

         File[ ]

But, where is the error?  Is it that $foo was not set?
Or was $foo dependent on something else, far removed,
that failed to be set or evaluated?

What should the compiler say about this?

         $foo = inline_template( ... )
         $baz = inline_template( ... )
         File[ "$foo$baz" ]


-- 
vagn

-- 
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.

Why would you pass the output from inline_template as the title of a
resource?

On Mon, Jul 4, 2011 at 8:03 PM, vagn scott <vagnscott@gmail.com> wrote:
>
>        $foo = inline_template( ... )
>        $baz = inline_template( ... )
>        File[ "$foo$baz" ]
>
>
>
> --
> vagn
>
> --
> 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 <puppet-users%2Bunsubscribe@googlegroups.com>.
> For more options, visit this group at http://groups.google.com/**
>
group/puppet-users?hl=en<http://groups.google.com/group/puppet-users?hl=en>
> .
>
>
-- 
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.

Because the name depends on other parameters in a non-trivial way.
But that''s neither here nor there.  remeber the context:
We were talking about parser v compiler error reporting.

-- 
vagn

On 07/04/2011 11:53 PM, Scott Smith wrote:
> Why would you pass the output from inline_template as the title of a 
> resource?
>
> On Mon, Jul 4, 2011 at 8:03 PM, vagn scott <vagnscott@gmail.com 
> <mailto:vagnscott@gmail.com>> wrote:
>
>
>            $foo = inline_template( ... )
>            $baz = inline_template( ... )
>            File[ "$foo$baz" ]
>
-- 
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.