Benjamin Priestman
2012-Dec-18 15:47 UTC
[Puppet Users] Error 400 on SERVER: Invalid parameter lib in puppetlabs-apache module
Hi, I''m trying to move back to using the standard puppetlabs-apache module, after having been using a heavily customised version and am running into the following error: err: Could not retrieve catalog from remote server: Error 400 on SERVER: Invalid parameter lib at /etc/puppet/unstable/branches/shared_linux/modules/apache/manifests/mod.pp:33 on node .......... I''m using tag 0.5.0-rc1 from github, although this also happens with tag 0.4.0 (or rather the commit immediately after that, which fixes a 2.6 parsing issue). My puppet master and clients are at 2.6.16 (I know, an upgrade is on the list, but the module claims to work with 2.6) on RHEL 6. stdlib and firewall modules are present. This looks similar to the bugfix discussed in http://projects.puppetlabs.com/issues/16418 but I can''t find any other references to this issue. Has anyone else seen this? Going back to my custom version for now... -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To view this discussion on the web visit https://groups.google.com/d/msg/puppet-users/-/4LFyhYp3eB4J. 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.
Seemingly Similar Threads
- How to properly override manage_config_file parameter in puppetlabs-mysql module?
- Puppet Dashboard Error 400 Invalid Parameter at passenger pp:48
- apache 2.4 support in puppetlabs/apache
- Error: Could not find dependency Yumrepo[puppetlabs-products] for Package[puppet]
- Unable to connect to PuppetLabs repository