Can someone tell me why, when I restart puppet on the client, I get this: Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: Could not retrieve catalog from remote server: Error 400 on SERVER: Syntax error at '';''; expected ''}'' at /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node db01.pax.livegamer.com and then, on subsequent restarts of the puppet client, I get: Sep 4 20:42:26 s_sys@db01.pax.livegamer.com puppet-agent[26980]: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find class oracle::server::environment in namespaces facility::paloalto::oracleserver at /etc/puppet/modules/facility/manifests/paloalto/oracleserver.pp:2 on node db01.pax.livegamer.com It seems like the error handling in puppet 2.6 is generally kinda broken. Doug. -- 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.
----- "Douglas Garstang" <doug.garstang@gmail.com> wrote:> Can someone tell me why, when I restart puppet on the client, I get > this: > > Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: > Could not retrieve catalog from remote server: Error 400 on SERVER: > Syntax error at '';''; expected ''}'' at > /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node > db01.pax.livegamer.com > > and then, on subsequent restarts of the puppet client, I get: > > Sep 4 20:42:26 s_sys@db01.pax.livegamer.com puppet-agent[26980]: > Could not retrieve catalog from remote server: Error 400 on SERVER: > Could not find class oracle::server::environment in namespaces > facility::paloalto::oracleserver at > /etc/puppet/modules/facility/manifests/paloalto/oracleserver.pp:2 on > node db01.pax.livegamer.comThis isn''t new behavior, I''ve seen this countless times. -- 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 Sat, Sep 4, 2010 at 1:46 PM, R.I.Pienaar <rip@devco.net> wrote:> > ----- "Douglas Garstang" <doug.garstang@gmail.com> wrote: > >> Can someone tell me why, when I restart puppet on the client, I get >> this: >> >> Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: >> Could not retrieve catalog from remote server: Error 400 on SERVER: >> Syntax error at '';''; expected ''}'' at >> /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node >> db01.pax.livegamer.com >> >> and then, on subsequent restarts of the puppet client, I get: >> >> Sep 4 20:42:26 s_sys@db01.pax.livegamer.com puppet-agent[26980]: >> Could not retrieve catalog from remote server: Error 400 on SERVER: >> Could not find class oracle::server::environment in namespaces >> facility::paloalto::oracleserver at >> /etc/puppet/modules/facility/manifests/paloalto/oracleserver.pp:2 on >> node db01.pax.livegamer.com > > > This isn''t new behavior, I''ve seen this countless times. > > -- > 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. > >Hmmm. Definitely a new thing since 0.24.8, and probably new since 0.25.5 too. Doug. -- 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.
----- "Douglas Garstang" <doug.garstang@gmail.com> wrote:> > Hmmm. Definitely a new thing since 0.24.8, and probably new since > 0.25.5 too. >0.25.5 with a deliberate error: first run: puppetmasterd[3006]: Syntax error at ''{''; expected ''}'' at /etc/puppet/manifests/common/modules/users/manifests/psy.pp:4 on node x 2nd run: puppetmasterd[3006]: Could not find class users::psy at /etc/puppet/manifests/nodes/nephilim.ml.org:26 on node x Anyway, clearly my previous attitude of just simply ignoring you was best, so I''ll go back to that. -- R.I.Pienaar -- 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 Sat, Sep 4, 2010 at 10:44 PM, Douglas Garstang <doug.garstang@gmail.com> wrote:> Can someone tell me why, when I restart puppet on the client, I get this: > > Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: > Could not retrieve catalog from remote server: Error 400 on SERVER: > Syntax error at '';''; expected ''}'' at > /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node > db01.pax.livegamer.comI think that the problem is the .pp files end of line format and enconding. It should be latin1 and (the most important) UNIX like end of lines == "\n", not "\r\n" like in Windows files. Check ALL the .pp files, not only the one that reports failure. Using Windows end of lines will cause completely random errors in random files. If you have a Windows formated .pp file somewhere it could make it fail, even if you don''t use it!! -- Atentamente Héctor Rivas -- 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.
2010/9/6 Héctor Rivas Gándara <keymon@gmail.com>:> On Sat, Sep 4, 2010 at 10:44 PM, Douglas Garstang > <doug.garstang@gmail.com> wrote: > >> Can someone tell me why, when I restart puppet on the client, I get this: >> >> Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: >> Could not retrieve catalog from remote server: Error 400 on SERVER: >> Syntax error at '';''; expected ''}'' at >> /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node >> db01.pax.livegamer.com > > I think that the problem is the .pp files end of line format and > enconding. It should be latin1 and (the most important) UNIX like end > of lines == "\n", not "\r\n" like in Windows files. > > Check ALL the .pp files, not only the one that reports failure. Using > Windows end of lines will cause completely random errors in random > files. > If you have a Windows formated .pp file somewhere it could make it > fail, even if you don''t use it!!Highly unlikely. I don''t touch Windows, ever. Doug. -- 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.
Douglas Garstang wrote:> 2010/9/6 Héctor Rivas Gándara <keymon@gmail.com>: >> On Sat, Sep 4, 2010 at 10:44 PM, Douglas Garstang >> <doug.garstang@gmail.com> wrote: >> >>> Can someone tell me why, when I restart puppet on the client, I get this: >>> >>> Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: >>> Could not retrieve catalog from remote server: Error 400 on SERVER: >>> Syntax error at '';''; expected ''}'' at >>> /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node >>> db01.pax.livegamer.com >> I think that the problem is the .pp files end of line format and >> enconding. It should be latin1 and (the most important) UNIX like end >> of lines == "\n", not "\r\n" like in Windows files.I reiterate R.I.''s comment - this has nothing to do with 2.6.1. This isn''t new behaviour. There is a syntax error somewhere in your manifests. Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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, Sep 6, 2010 at 11:31 AM, James Turnbull <james@puppetlabs.com> wrote:> Douglas Garstang wrote: >> 2010/9/6 Héctor Rivas Gándara <keymon@gmail.com>: >>> On Sat, Sep 4, 2010 at 10:44 PM, Douglas Garstang >>> <doug.garstang@gmail.com> wrote: >>> >>>> Can someone tell me why, when I restart puppet on the client, I get this: >>>> >>>> Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: >>>> Could not retrieve catalog from remote server: Error 400 on SERVER: >>>> Syntax error at '';''; expected ''}'' at >>>> /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node >>>> db01.pax.livegamer.com >>> I think that the problem is the .pp files end of line format and >>> enconding. It should be latin1 and (the most important) UNIX like end >>> of lines == "\n", not "\r\n" like in Windows files. > > I reiterate R.I.''s comment - this has nothing to do with 2.6.1. This > isn''t new behaviour. There is a syntax error somewhere in your manifests.My post was not about my error. My post was questioning how it can be possible to receive two different errors between subsequent runs of the puppet client without making changes to the server side. Here''s another example. The same error reported in two different locations between successive runs of the client, with no changes being made: Sep 6 18:14:20 s_sys@app01.pax.livegamer.com puppet-agent[11876]: Could not run Puppet configuration client: Parameter path failed: File paths must be fully qualified, not ''opt/jboss/current/server/tfel0/deploy/jmx-console.war/WEB-INF'' at /etc/puppet/modules/jboss/manifests/server/instance.pp:163 Sep 6 18:15:11 s_sys@app01.pax.livegamer.com puppet-agent[12596]: Could not run Puppet configuration client: Parameter path failed: File paths must be fully qualified, not ''opt/jboss/current/server/tfel0/conf/jboss.web'' at /etc/puppet/modules/jboss/manifests/server/instance.pp:163 James, I''m not even sure why you focused on the error itself. R.I clearly pointed out that he''s seen this issue countless times. It makes debugging kinda challenging. Doug. -- 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.
Douglas Garstang wrote:> > James, I''m not even sure why you focused on the error itself. R.I > clearly pointed out that he''s seen this issue countless times. It > makes debugging kinda challenging.I focused on it because you claimed it was an issue was with 2.6.x. It is not. I agree this might make debugging difficult - have you logged a bug? Regards James Turnbull -- Puppet Labs - http://www.puppetlabs.com C: 503-734-8571 -- 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.
>>>>> Can someone tell me why, when I restart puppet on the client, I get this: >>>>> >>>>> Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: >>>>> Could not retrieve catalog from remote server: Error 400 on SERVER: >>>>> Syntax error at '';''; expected ''}'' at >>>>> /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node >>>>> db01.pax.livegamer.com >>>> I think that the problem is the .pp files end of line format and >>>> enconding. It should be latin1 and (the most important) UNIX like end >>>> of lines == "\n", not "\r\n" like in Windows files. >> >> I reiterate R.I.''s comment - this has nothing to do with 2.6.1. This >> isn''t new behaviour. There is a syntax error somewhere in your manifests. > > My post was not about my error. My post was questioning how it can be > possible to receive two different errors between subsequent runs of > the puppet client without making changes to the server side.Sorry, I got mad with the windows EOL problem :) I noticed the same behavior than you: when you have a syntax error, second runs report missing definitions. I always thought that it was how puppet cached the code. But it is a harmless problem, once you are used to it you known that you just need to relaunch puppetd. -- Atentamente Héctor Rivas -- 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, Sep 6, 2010 at 11:53 AM, Douglas Garstang <doug.garstang@gmail.com> wrote:> On Mon, Sep 6, 2010 at 11:31 AM, James Turnbull <james@puppetlabs.com> wrote: >> Douglas Garstang wrote: >>> 2010/9/6 Héctor Rivas Gándara <keymon@gmail.com>: >>>> On Sat, Sep 4, 2010 at 10:44 PM, Douglas Garstang >>>> <doug.garstang@gmail.com> wrote: >>>> >>>>> Can someone tell me why, when I restart puppet on the client, I get this: >>>>> >>>>> Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: >>>>> Could not retrieve catalog from remote server: Error 400 on SERVER: >>>>> Syntax error at '';''; expected ''}'' at >>>>> /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node >>>>> db01.pax.livegamer.com >>>> I think that the problem is the .pp files end of line format and >>>> enconding. It should be latin1 and (the most important) UNIX like end >>>> of lines == "\n", not "\r\n" like in Windows files. >> >> I reiterate R.I.''s comment - this has nothing to do with 2.6.1. This >> isn''t new behaviour. There is a syntax error somewhere in your manifests. > > My post was not about my error. My post was questioning how it can be > possible to receive two different errors between subsequent runs of > the puppet client without making changes to the server side. > > Here''s another example. The same error reported in two different > locations between successive runs of the client, with no changes being > made: > > Sep 6 18:14:20 s_sys@app01.pax.livegamer.com puppet-agent[11876]: > Could not run Puppet configuration client: Parameter path failed: File > paths must be fully qualified, not > ''opt/jboss/current/server/tfel0/deploy/jmx-console.war/WEB-INF'' at > /etc/puppet/modules/jboss/manifests/server/instance.pp:163 > > Sep 6 18:15:11 s_sys@app01.pax.livegamer.com puppet-agent[12596]: > Could not run Puppet configuration client: Parameter path failed: File > paths must be fully qualified, not > ''opt/jboss/current/server/tfel0/conf/jboss.web'' at > /etc/puppet/modules/jboss/manifests/server/instance.pp:163 > > James, I''m not even sure why you focused on the error itself. R.I > clearly pointed out that he''s seen this issue countless times. It > makes debugging kinda challenging.I''ve actually always considered this to be relatively comprehensible. Client and server start with a clean slate. Client requests module X Server parses module X via autoloading, complains about parse error. Client requests module X Server tells you it can''t find it as it''s not going to reattempt parsing unless the file changes. Does it really impact upon debugging that much? What do you think makes more sense? To not present the parsing error to the client at all? Or to continuously try and parse manifests even though the server thinks that they have a parse error? I can''t think of an answer that is obviously more correct than the current behaviour in this situation, which is why I''m asking what you think should happen.> > Doug. > > -- > 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. > >-- nigel -- 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, Sep 6, 2010 at 4:52 PM, Nigel Kersten <nigelk@google.com> wrote:> On Mon, Sep 6, 2010 at 11:53 AM, Douglas Garstang > <doug.garstang@gmail.com> wrote: >> On Mon, Sep 6, 2010 at 11:31 AM, James Turnbull <james@puppetlabs.com> wrote: >>> Douglas Garstang wrote: >>>> 2010/9/6 Héctor Rivas Gándara <keymon@gmail.com>: >>>>> On Sat, Sep 4, 2010 at 10:44 PM, Douglas Garstang >>>>> <doug.garstang@gmail.com> wrote: >>>>> >>>>>> Can someone tell me why, when I restart puppet on the client, I get this: >>>>>> >>>>>> Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: >>>>>> Could not retrieve catalog from remote server: Error 400 on SERVER: >>>>>> Syntax error at '';''; expected ''}'' at >>>>>> /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node >>>>>> db01.pax.livegamer.com >>>>> I think that the problem is the .pp files end of line format and >>>>> enconding. It should be latin1 and (the most important) UNIX like end >>>>> of lines == "\n", not "\r\n" like in Windows files. >>> >>> I reiterate R.I.''s comment - this has nothing to do with 2.6.1. This >>> isn''t new behaviour. There is a syntax error somewhere in your manifests. >> >> My post was not about my error. My post was questioning how it can be >> possible to receive two different errors between subsequent runs of >> the puppet client without making changes to the server side. >> >> Here''s another example. The same error reported in two different >> locations between successive runs of the client, with no changes being >> made: >> >> Sep 6 18:14:20 s_sys@app01.pax.livegamer.com puppet-agent[11876]: >> Could not run Puppet configuration client: Parameter path failed: File >> paths must be fully qualified, not >> ''opt/jboss/current/server/tfel0/deploy/jmx-console.war/WEB-INF'' at >> /etc/puppet/modules/jboss/manifests/server/instance.pp:163 >> >> Sep 6 18:15:11 s_sys@app01.pax.livegamer.com puppet-agent[12596]: >> Could not run Puppet configuration client: Parameter path failed: File >> paths must be fully qualified, not >> ''opt/jboss/current/server/tfel0/conf/jboss.web'' at >> /etc/puppet/modules/jboss/manifests/server/instance.pp:163 >> >> James, I''m not even sure why you focused on the error itself. R.I >> clearly pointed out that he''s seen this issue countless times. It >> makes debugging kinda challenging. > > I''ve actually always considered this to be relatively comprehensible. > > Client and server start with a clean slate. > Client requests module X > Server parses module X via autoloading, complains about parse error. > Client requests module X > Server tells you it can''t find it as it''s not going to reattempt > parsing unless the file changes. > > Does it really impact upon debugging that much? > > What do you think makes more sense? To not present the parsing error > to the client at all? Or to continuously try and parse manifests even > though the server thinks that they have a parse error? > > I can''t think of an answer that is obviously more correct than the > current behaviour in this situation, which is why I''m asking what you > think should happen.I''m not sure we''re talking about the same thing here. How can the outputs change (ie the error) if the inputs (the source) don''t? That would be like compiling a C application and getting different errors each time from the same source. Doug. -- 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, Sep 6, 2010 at 6:09 PM, Douglas Garstang <doug.garstang@gmail.com> wrote:> On Mon, Sep 6, 2010 at 4:52 PM, Nigel Kersten <nigelk@google.com> wrote: >> On Mon, Sep 6, 2010 at 11:53 AM, Douglas Garstang >> <doug.garstang@gmail.com> wrote: >>> On Mon, Sep 6, 2010 at 11:31 AM, James Turnbull <james@puppetlabs.com> wrote: >>>> Douglas Garstang wrote: >>>>> 2010/9/6 Héctor Rivas Gándara <keymon@gmail.com>: >>>>>> On Sat, Sep 4, 2010 at 10:44 PM, Douglas Garstang >>>>>> <doug.garstang@gmail.com> wrote: >>>>>> >>>>>>> Can someone tell me why, when I restart puppet on the client, I get this: >>>>>>> >>>>>>> Sep 4 20:41:49 s_sys@db01.pax.livegamer.com puppet-agent[26756]: >>>>>>> Could not retrieve catalog from remote server: Error 400 on SERVER: >>>>>>> Syntax error at '';''; expected ''}'' at >>>>>>> /etc/puppet/modules/oracle/manifests/server/environment.pp:40 on node >>>>>>> db01.pax.livegamer.com >>>>>> I think that the problem is the .pp files end of line format and >>>>>> enconding. It should be latin1 and (the most important) UNIX like end >>>>>> of lines == "\n", not "\r\n" like in Windows files. >>>> >>>> I reiterate R.I.''s comment - this has nothing to do with 2.6.1. This >>>> isn''t new behaviour. There is a syntax error somewhere in your manifests. >>> >>> My post was not about my error. My post was questioning how it can be >>> possible to receive two different errors between subsequent runs of >>> the puppet client without making changes to the server side. >>> >>> Here''s another example. The same error reported in two different >>> locations between successive runs of the client, with no changes being >>> made: >>> >>> Sep 6 18:14:20 s_sys@app01.pax.livegamer.com puppet-agent[11876]: >>> Could not run Puppet configuration client: Parameter path failed: File >>> paths must be fully qualified, not >>> ''opt/jboss/current/server/tfel0/deploy/jmx-console.war/WEB-INF'' at >>> /etc/puppet/modules/jboss/manifests/server/instance.pp:163 >>> >>> Sep 6 18:15:11 s_sys@app01.pax.livegamer.com puppet-agent[12596]: >>> Could not run Puppet configuration client: Parameter path failed: File >>> paths must be fully qualified, not >>> ''opt/jboss/current/server/tfel0/conf/jboss.web'' at >>> /etc/puppet/modules/jboss/manifests/server/instance.pp:163 >>> >>> James, I''m not even sure why you focused on the error itself. R.I >>> clearly pointed out that he''s seen this issue countless times. It >>> makes debugging kinda challenging. >> >> I''ve actually always considered this to be relatively comprehensible. >> >> Client and server start with a clean slate. >> Client requests module X >> Server parses module X via autoloading, complains about parse error. >> Client requests module X >> Server tells you it can''t find it as it''s not going to reattempt >> parsing unless the file changes. >> >> Does it really impact upon debugging that much? >> >> What do you think makes more sense? To not present the parsing error >> to the client at all? Or to continuously try and parse manifests even >> though the server thinks that they have a parse error? >> >> I can''t think of an answer that is obviously more correct than the >> current behaviour in this situation, which is why I''m asking what you >> think should happen. > > I''m not sure we''re talking about the same thing here. How can the > outputs change (ie the error) if the inputs (the source) don''t? That > would be like compiling a C application and getting different errors > each time from the same source.Restart your puppetmaster. Do you get the first error again or not?> > Doug. > > -- > 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. > >-- nigel -- 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, 6 Sep 2010 16:52:05 -0700 Nigel Kersten <nigelk@google.com> wrote:> I''ve actually always considered this to be relatively comprehensible. > > Client and server start with a clean slate. > Client requests module X > Server parses module X via autoloading, complains about parse error. > Client requests module X > Server tells you it can''t find it as it''s not going to reattempt > parsing unless the file changes. > > Does it really impact upon debugging that much?I''ve also found the inconsistency in the errors very confusing, but this explanation makes perfect sense.> What do you think makes more sense? To not present the parsing error > to the client at all? Or to continuously try and parse manifests even > though the server thinks that they have a parse error?Maybe cache the error for consistency if that''s not too much work, or at least document the behavior, maybe as a FAQ? -- Dan Urist durist@ucar.edu 303-497-2459 -- 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 Tue, Sep 7, 2010 at 7:47 AM, Dan Urist <durist@ucar.edu> wrote:> On Mon, 6 Sep 2010 16:52:05 -0700 > Nigel Kersten <nigelk@google.com> wrote: > > >> I''ve actually always considered this to be relatively comprehensible. >> >> Client and server start with a clean slate. >> Client requests module X >> Server parses module X via autoloading, complains about parse error. >> Client requests module X >> Server tells you it can''t find it as it''s not going to reattempt >> parsing unless the file changes. >> >> Does it really impact upon debugging that much? > > I''ve also found the inconsistency in the errors very confusing, but > this explanation makes perfect sense. > >> What do you think makes more sense? To not present the parsing error >> to the client at all? Or to continuously try and parse manifests even >> though the server thinks that they have a parse error? > > Maybe cache the error for consistency if that''s not too much work, or at > least document the behavior, maybe as a FAQ?Doug, did you put a bug report in? If there''s a clear way to cache the initial error, that does seem like the most user friendly solution.> > > -- > Dan Urist > durist@ucar.edu > 303-497-2459 > > -- > 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. > >-- 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.