similar to: Parsing issues

Displaying 20 results from an estimated 30000 matches similar to: "Parsing issues"

2007 Oct 03
4
puppet exit codes and svn pre-commit hook
Hi everyone, I''m using a svn pre-commit hook to check manifests for syntax errors. I''ve recently upgraded puppet from 0.22.4 to 0.23.2 and the hook stopped working. I use the following command to parse .pp files: /usr/local/bin/puppet --confdir=/tmp --vardir=/tmp --parseonly --ignoreimport /tmp/$$.pp Now, I make a decision based on the exit code. If 0 then commit, else exit
2007 Feb 12
8
How to validate puppet manifests without actually executing puppet?
Hi, I want to validate my puppet manifests before I check them into source control. I just want to make sure that the manifest syntaxes are legal, not to do any more complex testing - the checkin may be on my laptop and not on the system that the manifests may be intended to run on. Ideally I''d be able to do this from ruby code - and I did try to instantiate some classes and override
2007 Mar 19
11
Parsechecking in a commit hook
This has been a much-requested feature, and is now a reality (in svn trunk): There is a new option, --ignoreimport, that will (surprisingly) ignore import statements. This is really only useful when using -- parseonly in a commit hook, and note that you''ll have to add the option to --parseonly, none of the puppet executables will add it for you. You should be able to
2009 Feb 04
1
Issue with template.pp
Hi i am creating a template.pp for different OS.. Following is my template.pp file node basenode { case $operatingsystem { fedora: { include fedora } default: { include debian } } include baseapps, sshd, admin, default } <=== line 7 node default inherits basenode {} I receive an error. err: Could not parse for environment production: Syntax error
2010 Dec 03
6
audit=>content
Hi All, sorry if this was discussed before but I didn''t find any solution for my problem. Test site.pp consists of 1 line: file { "/tmp/bar": audit => content } exec { ''/usr/bin/true'': refreshonly => true, subscribe => File[''/tmp/bar''] } and it produces this error every time: err: /Stage[main]//Node[localhost]/File[/tmp/bar]:
2007 Dec 17
1
Configuration check script
We have started having developers make changes to our manifests file. We have a couple of changes with errors that have broken updating for all clients. We even ran into a bug where a broken configuration on puppetmaster start would cause it to return 500 server errors to all clients. I would like to have a way for developers to check their changes before committing them to version control and
2007 Dec 20
5
Apache2 module -- feedback appreciated
Hey folks, I''ve just uploaded an apache2 module[1] to our Google Code repository[2]. It''s based largely on the recipe available on the Puppet trac[3], but with a fair amount of modification and generalization... Basically, it provides abstractions for config file snippets, site definitions, and apxs modules -- and then "basic" and "debian"
2012 Apr 16
2
configured puppet server as client now no updates are working
Hi, My puppet server was working up until I configured it to be a puppet client. I applied the configuration on the server which seemed to work fine. However, now when ever a client or itself asks for an updated configuration it always comes back with a successful poll, no updates, and the configuration version changed. So configuration changes are not being applied anymore. Is there some
2007 Jan 17
32
Managing manifests
Hi, I was talking to Luke today about managing manifests and related files, and he suggested that I post to the list.. What would be nice (and what I''ve use in in-house systems I''ve used previously) is to have a way to dynamically include manifest fragments at runtime. Lets assume that you''re setting up bugzilla using puppet. In the ''main'' manifest
2010 Jun 04
5
running puppet withput puppetmasterd
Hi, I''m pretty sure I once did some experiments with running puppet wihtout a puppertmasterd - but having a "normal" puppet manifests and modules structure in /etc/puppet. Sadly, I can''t find how to do that anymore. I know I can write plain puppet instructions in a file.pp and run them plainly - but I want the whole config as if it would reside on a server) When I
2010 Dec 10
2
Problem with syntax checking
Hello! I''m trying to use pre-commit SVN hook for checking puppet syntax. For it I try to use some scripts from this thread: http://groups.google.com/group/puppet-users/browse_thread/thread/50ff2eb268f982da?pli=1 But when I try some of the scripts I see the common problem, expression like this: # puppet --parseonly --ignoreimport file.pp produces no output, but "file.pp" has a
2010 Dec 10
11
pp grammar test-files?
Hi, I am working on some tools that read and write pp files, and I wonder if there are some pp files available somewhere that can be used to test a parser. I am especially interested in if there are some tests written that capture invalid syntax. - henrik -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send
2008 Jan 17
1
SVN pre-commit hook
Hi is anybody using the svn pre-commit hook from http://www.reductivelabs.com/trac/puppet/wiki/VersionControlPuppet with 0.24.1 . It was working fine with 0.23.1 and I like it to test stupid typos before checking in. However after updating to 0.24.1 I get the following error for the site.pp: Could not parse for environment development: No file(s) found for import of
2010 Jul 22
9
First Foray into Parameterized Classes.... not so good
I have this: class foo::foobar ($version) { } which is called like this: class facility::sanjose inherits facility::common { class { foo::foobar: version => "1.3.13" } } puppet complains with this on the client: Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find parent resource type ''facility::sanjose'' of type hostclass in
2011 Feb 27
3
learning, but puppet does not detect change
Hi, I''ve just installed Puppet on two CentOS 5.5 servers, "S" for "A". "A" does not have the ntp package installed nor of course ntp running. The Puppet server is started on "S" with the ntp class from this tutorial: http://bitfieldconsulting.com/puppet-tutorial (included below) however when I run the agent on "A" it don''t
2007 Jan 17
11
scope issue after upgrade
I just upgraded to 0.22.0 from 0.18.4 and I''m running into what I think are problems due to changes in scope rules. In my site.pp manifest, I have the following: import "classes/*" node nfsserver { include nfsserver } node webserver { include webserver } class cluster1_sites { website { "example.com": ...; "example2.com": ...; } } node
2011 Dec 29
21
Puppetserver error
Hello everyone, I am new to puppet. I have installed on redhat Enterprise 5and seems to be working fine. Couple days ago I was testing some permissions on / etc folder and applied 600 /etc and sub folders. Although I have reverted the permission but I am having issues on puppetmaster. Currently I have these permission on etc 755 and puppet folder: my /etc folder is 755 and puppet folder with tese
2012 May 30
12
resource override
hi All, I''m a bit new to puppet. Is there a mailing list for puppet beginners?:) I have a service module called postfix, which defines file in a class: file { ''/etc/postfix/main.cf'': owner => "root", group => "root", mode => 644, content =>
2010 Feb 19
11
Strange messages on 0.25.4.
Hi all. I am testing 0.25.4 to upgrade from 0.23.2. In testing, I found two strange messages on 0.25.4 which I have never found on 0.24.3. So could you tell me what these messages mean and how to fix them. [Environment] Puppetmasterd -version : 0.25.4 -OS : Solaris10 10/09 Puppetd -version : same as Puppetmasterd -OS : same as Puppetmasterd [Strange messages] 1.When Puppetd
2012 Jan 20
9
client not getting updates no error message
whenever i run a test from client it finishes sucessfully but client is not getting any configuration changes from server [root@PROXY-02 tmp]# puppetd --noop --test notice: Ignoring --listen on onetime run info: Caching catalog for proxy-02.carnation.in info: Applying configuration version ''1327091881'' notice: Finished catalog run in 0.02 seconds [root@PROXY-03 modules]# puppet