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?
**********************************************************************
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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
I''ve not heard of anyone else having this issue. The symptoms see quite odd to me. What happens if you try --parseonly on that file? or take away all the classes and add this as the only one? On Fri, Jan 9, 2009 at 3:52 PM, Matt Marshall <Marshall.Matt@azdeq.gov>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? > ------------------------------ > 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+unsubscribe@googlegroups.com For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en -~----------~----~----~----~------~----~------~--~---
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 --~--~---------~--~----~------------~-------~--~----~ 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 what I get if I run parseonly on autofs.pp
[root@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
[root@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
[root@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
[root@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-users@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.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
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-users@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
[root@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
[root@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
[root@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
[root@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-users@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+unsubscribe@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en
-~----------~----~----~----~------~----~------~--~---
On Jan 12, 2009, at 3:42 PM, Matt Marshall wrote:> 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?Hmm, I really don''t think so; the server doesn''t have any kind of cache, and the client should never cache this kind of result. You clearly have something pretty strange going on. By chance, is there any kind of exception on the server that''s not visible here? Do you get any additional information if you run the server with --trace (I''m only interested in the server-side logs here)? If you paste all of the code into a different file and run that with ''puppet'' (rather than puppet{master,}d), do you still get an error? -- It''s not the voting that''s democracy, it''s the counting. -- Tom Stoppard --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
Luke, Thanks for helping with this, I believe I found out what the problem is, it looks like the editor I was using (eclipse) decided to use windows style end of line characters. These appear to throw puppet for a loop. I found that out when I was concatenating the files from the recipe together, site.pp was in a unix style format because I created it locally, and sudo.pp was in windows format from creating it in eclipse. I can''t believe I didn''t catch this, thanks again for all your help. -- Matt Marshall -----Original Message----- From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of Luke Kanies Sent: Monday, January 12, 2009 4:30 PM To: puppet-users@googlegroups.com Subject: [Puppet Users] Re: Parsing issues On Jan 12, 2009, at 3:42 PM, Matt Marshall wrote:> 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?Hmm, I really don''t think so; the server doesn''t have any kind of cache, and the client should never cache this kind of result. You clearly have something pretty strange going on. By chance, is there any kind of exception on the server that''s not visible here? Do you get any additional information if you run the server with --trace (I''m only interested in the server-side logs here)? If you paste all of the code into a different file and run that with ''puppet'' (rather than puppet{master,}d), do you still get an error? -- It''s not the voting that''s democracy, it''s the counting. -- Tom Stoppard --------------------------------------------------------------------- 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. --~--~---------~--~----~------------~-------~--~----~ 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 Jan 12, 2009, at 6:05 PM, Matt Marshall wrote:> Luke, > Thanks for helping with this, I believe I found out what the problem > is, > it looks like the editor I was using (eclipse) decided to use windows > style end of line characters. These appear to throw puppet for a > loop. I > found that out when I was concatenating the files from the recipe > together, site.pp was in a unix style format because I created it > locally, and sudo.pp was in windows format from creating it in > eclipse. > I can''t believe I didn''t catch this, thanks again for all your help.Wow, that''s a new one, and certainly would be a difficult one to catch. Can you file that as a bug? I don''t know that we''ll be able to solve it, although I''d think that we could, but I''d like to have it in the db in case others run across it. Cheers, Luke -- Think twice before you speak, and then you may be able to say something more insulting than if you spoke right out at once. -- Evan Esar --------------------------------------------------------------------- Luke Kanies | http://reductivelabs.com | http://madstop.com --~--~---------~--~----~------------~-------~--~----~ 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 Mon, 2009-01-12 at 18:37 -0600, Luke Kanies wrote:> On Jan 12, 2009, at 6:05 PM, Matt Marshall wrote: > > > Luke, > > Thanks for helping with this, I believe I found out what the problem > > is, > > it looks like the editor I was using (eclipse) decided to use windows > > style end of line characters. These appear to throw puppet for a > > loop. I > > found that out when I was concatenating the files from the recipe > > together, site.pp was in a unix style format because I created it > > locally, and sudo.pp was in windows format from creating it in > > eclipse. > > I can''t believe I didn''t catch this, thanks again for all your help. > > > Wow, that''s a new one, and certainly would be a difficult one to catch.Maybe not: what if we change the RETURN token definition to /\r?\n/ ? I didn''t test, though... -- Brice Figureau Days of Wonder http://www.daysofwonder.com/ --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
I created the bug, #1863 http://projects.reductivelabs.com/issues/show/1863. Thanks again for the help. -- Matt Marshall -----Original Message----- From: puppet-users@googlegroups.com [mailto:puppet-users@googlegroups.com] On Behalf Of Luke Kanies Sent: Monday, January 12, 2009 5:38 PM To: puppet-users@googlegroups.com Subject: [Puppet Users] Re: Parsing issues On Jan 12, 2009, at 6:05 PM, Matt Marshall wrote:> Luke, > Thanks for helping with this, I believe I found out what the problem > is, > it looks like the editor I was using (eclipse) decided to use windows > style end of line characters. These appear to throw puppet for a > loop. I > found that out when I was concatenating the files from the recipe > together, site.pp was in a unix style format because I created it > locally, and sudo.pp was in windows format from creating it in > eclipse. > I can''t believe I didn''t catch this, thanks again for all your help.Wow, that''s a new one, and certainly would be a difficult one to catch. Can you file that as a bug? I don''t know that we''ll be able to solve it, although I''d think that we could, but I''d like to have it in the db in case others run across it. Cheers, Luke -- Think twice before you speak, and then you may be able to say something more insulting than if you spoke right out at once. -- Evan Esar --------------------------------------------------------------------- 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. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---