Failed to generate additional resources using 'eval_generate': wrong header line format

[Steve Neuharth]

I've upgraded to puppet v2.6.2 on ubuntu (clients and server) and now
I get this error messages related to pluginsync:

info: Retrieving plugin
err: /File[/var/lib/puppet/lib]: Failed to generate additional
resources using 'eval_generate': wrong header line format
err: /File[/var/lib/puppet/lib]: Could not evaluate: wrong header line
format Could not retrieve file metadata for puppet://mcp.c42/plugins:
wrong header line format

this seems to be related to bug #4830. there was a 'workaround' to add
some lib directories to my modules. I did that and it didn't work.
There was another workaround that involves creating a bogus plugins
mount in fileserver.conf and setting pluginsource to that mount. While
that does eliminate the error, it also breaks pluginsync (not cool).

my fileserver.conf looks like this:
[plugins]
# path /var/lib/puppet/plugins
allow *

my puppet.conf looks like this:

[main]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl
server = mcp.c42
factpath = $vardir/lib/facter
# client = false

[user]
vardir = /var/lib/puppet
logdir = /var/log/puppet
rundir = /var/run/puppet
ssldir = $vardir/ssl

[agent]
pluginsync=true
#pluginsource=puppet:///plugins/
listen = true
report = true
classfile = $vardir/classes.txt
localconfig = $vardir/localconfig
runinterval = 1800
# runinterval = 21600 # Run every 6 hours

<snip>

It looks to me like either:
a) a bug... but it doesn't seem to be a common problem which leads me
to believe that it's...
b) configuration related... but dudes, I've tried everything.

any ideas? does anything look really, really wrong in my config?

[James Turnbull]

Steve Neuharth wrote:
> I've upgraded to puppet v2.6.2 on ubuntu (clients and server) and now
> I get this error messages related to pluginsync:

How did you upgrade? I've seen this when files from previous versions
hung around on the master/client too.

Regards

James

--
Puppet Labs - http://www.puppetlabs.com
C: 503-734-8571

[Steve Neuharth]

jeez, sorry... gentoo. This is on gentoo, not ubuntu, so I used
portage.

I suppose I could try to scrub my puppetmaster of everything puppet
related and reinstall... definitely not the ideal solution. I'll look
through the ruby libs and see if I can find any dupes first.

thanks James.

[Steve Neuharth]

OK, I unmerged and re-emerged the package and I get the same message.
I also verified that all remnants of the ruby puppet stuff was gone
from site_ruby before I reinstalled.

I'm fairly certain that it's not my manifests as this error seems to
occur in the phase where puppet is gathering it's plugins and I tried
running puppetd on a server with no node defs, no classes, etc... same
thing

I'll cc: the package maintainer. Maybe he's seen it before. Maybe the
gem at http://distfiles.gentoo.org/distfiles/puppet-2.6.2.gem is bad?

[Steve Neuharth]

I verified that the gem wasn't corrupted and I've narrowed the problem
down to the following REST operation:

GET /production/file_metadatas/plugins?&ignore=---+%0A++-+.svn%0A++-
+CVS%0A++-+.git&recurse=true&links=manage&checksum_type=md5

when it runs, I get:

expected next name, value pair in object at '}
'!closed

any ideas?

On Nov 12, 12:48 pm, Steve Neuharth <steve.neuha...@gmail.com> wrote:
> OK, I unmerged and re-emerged the package and I get the same message.
> I also verified that all remnants of the ruby puppet stuff was gone
> from site_ruby before I reinstalled.
>
> I'm fairly certain that it's not my manifests as this error seems to
> occur in the phase where puppet is gathering it's plugins and I tried
> running puppetd on a server with no node defs, no classes, etc... same
> thing
>
> I'll cc: the package maintainer. Maybe he's seen it before. Maybe the

> gem athttp://distfiles.gentoo.org/distfiles/puppet-2.6.2.gemis bad?