Ok, I'm thoroughly confused. I gave up and started over, delete all of the configs and went to the simplest recipe.
I get this error now puppetd --test --verbose --debug --server ev-unixutil.adeq.lcl err: Could not retrieve catalog: Could not parse for environment production: Could not match 'class' at /etc/puppet/manifests/classes/sudo.pp:2 warning: Not using cache on failed catalog This is the recipe I'm using http://reductivelabs.com/trac/puppet/wiki/SimplestPuppetInstallRecipe I've uninstalled and reinstalled the rpm's, any idea what is causing this? Or should I just give up and reinstall with the .22.4-1 clients which I've used before (on a different machine) Is it possible there is a cache somewhere that needs deleting? -- Matt Marshall -----Original Message----- From: puppet-users@googlegroups.com [mailto:puppet-us...@googlegroups.com] On Behalf Of Matt Marshall Sent: Monday, January 12, 2009 8:19 AM To: puppet-users@googlegroups.com Subject: [Puppet Users] Re: Parsing issues This is what I get if I run parseonly on autofs.pp [r...@ev-unixutil manifests]# puppet --parseonly classes/autofs.pp err: Could not parse for environment production: Could not match '}' at /etc/puppet/manifests/classes/autofs.pp:1 [r...@ev-unixutil manifests]# puppetd --server ev-unixutil.adeq.lcl --parseonly --test classes/autofs.pp err: Could not retrieve catalog: Could not parse for environment production: Could not match '}' at /etc/puppet/manifests/classes/autofs.pp:1 warning: Not using cache on failed catalog If I then delete site.pp and move autofs.pp to it's location, I get the following error [r...@ev-unixutil manifests]# puppetd --test --server ev-unixutil.adeq.lcl err: Could not retrieve catalog: Could not parse for environment production: Could not match '}' at /etc/puppet/manifests/site.pp:1 warning: Not using cache on failed catalog The file looks like this [r...@ev-unixutil manifests]# cat site.pp class autofs { file { "auto.master": name => "/etc/auto.master", owner => "root", group => "root", mode => 645 } } If I run parseonly on the other files they all come back with no errors. I then created a new file called test.pp and put the mysql server recipe in it from the wiki (it was the first one I saw) and removed the autofs.pp file. Now puppet seems to work, if I put the autofs file in breaks again. Any other ideas? Or should I give up on managing autofs? Thanks -- Matt -----Original Message----- From: puppet-users@googlegroups.com [mailto:puppet-us...@googlegroups.com] On Behalf Of Luke Kanies Sent: Sunday, January 11, 2009 9:45 AM To: puppet-users@googlegroups.com Subject: [Puppet Users] Re: Parsing issues On Jan 9, 2009, at 4:52 PM, Matt Marshall wrote: > I'm running into a very odd occurrence. I started with a new puppet > server and was able to add a few classes, however as I try and add > new ones I get odd parsing error messages, the most common being > Could not match '}' at whatever file. > Here is the exact error I get > err: Could not retrieve catalog: Could not parse for environment > production: Could not match '}' at /etc/puppet/manifests/classes/ > autofs.pp:1 > Here is the file it refers to > class autofs { > file { "auto.master": > name => "/etc/auto.master", > owner => "root", > group => "root", > mode => 645 > } > } > > Whats weird, is if I delete all the files that have been added since > it originally worked, it works fine, but if I try to create any new > classes I get the above error, even if I copy and paste an already > existing and working class into a new file and just change the name. > > I'm running puppet-0.24.6-1.el5 on Centos 5.2 and have looked > through the archives of this mailing list, but haven't been able to > find anything. Any ideas? I can only guess that it's wrong about the file it's finding the error in. I recommend using --parseonly to test individual files, which should lead you to the actual error. -- Is life worth living? That is a question for an embryo, not a man. --Samuel Butler --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com ********************************************************************** NOTICE: This e-mail (and any attachments) may contain PRIVILEGED OR CONFIDENTIAL information and is intended only for the use of the specific individual(s) to whom it is addressed. It may contain information that is privileged and confidential under state and federal law. This information may be used or disclosed only in accordance with law, and you may be subject to penalties under law for improper use or further disclosure of the information in this e-mail and its attachments. If you have received this e- mail in error, please immediately notify the person named above by reply e- mail, and then delete the original e-mail. Thank you. ********************************************************************** NOTICE: This e-mail (and any attachments) may contain PRIVILEGED OR CONFIDENTIAL information and is intended only for the use of the specific individual(s) to whom it is addressed. It may contain information that is privileged and confidential under state and federal law. This information may be used or disclosed only in accordance with law, and you may be subject to penalties under law for improper use or further disclosure of the information in this e-mail and its attachments. If you have received this e- mail in error, please immediately notify the person named above by reply e- mail, and then delete the original e-mail. Thank you. --~--~---------~--~----~------------~-------~--~----~ 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+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
