similar to: modulepath not working with environments

So I''m trying to get multiple environments to work with puppet 0.25.1 on ubuntu 8.04 and no matter what I do, puppet just completely ignores any environment setting. There''s really next to no information in terms of configuration on the multiple environments documentation page (http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments) other than saying that the

I''m seeing these in my logs on my puppetmaster: puppetmasterd[4111]: Could not store configs: SQLite3::SQLException: SQL logic error or missing database: DELETE FROM fact_values WHERE "id" = 8 currently this is 0.24.0 relect from some previously collected resource that wasn''t cleaned up? upgrade issue? nothing to worry about? that''s the only

At long last, 0.24.0 has been released. Look for your friendly packagers to package it up in the near future, but in the meantime you can download it: http://reductivelabs.com/downloads/puppet/puppet-0.24.0.tgz I''ll be walking the different release sites (RubyForge et al) and posting it there, too. Look for a related announcement later today on changes in development practices

Greetings all Am trying to solve a problem, not entirely sure I''m approaching it from the right angle. Setting up a reasonably big site (servercount in the four digits) with puppetmaster and clients (puppet 2.6.x). We are required to have versioned modules (base SOE module, app X module, app Y module, etc - all with multiple classes etc inside) managed on an underlying SVN repository. A

Hi, Puppet 3.1 now uses YARD to generate its API documentation. Is anybody aware of the possibility to generate nice YARD docs for a given module path, replacing the default RDOC-style site from "puppet doc --modulepath ..."? Could the YARD Template from Puppet 3.1 be used for this? -- You received this message because you are subscribed to the Google Groups "Puppet Users"

I''m trying to use environments and seem to be failing. Right now I have 4 defined environments: production, cat, development, beta They are defined as follows on my puppetmaster: cat /etc/puppet/puppet.conf [main] pluginsync = true vardir = /var/lib/puppet manifest = /etc/puppet/environments/production/site.pp modulepath = /etc/puppet/environments/production/modules [master] reports =

Hi all, We''re getting close to release[1], so I''d appreciate it if people would start testing the current ''master'' branch with their repositories. I made quite a few internal changes, most of which shouldn''t even be noticed unless there are bugs, so just running a server and/or client under the current code would be a big help. I''m

I''ve ran into a strange issue today while using my development environment I was receiving some errors about modules that shouldn''t have been used. After looking it looks like my agent (or master) isn''t respecting the environment I specify and is actually using the main (master) environment. This used to work and I haven''t had any changes beyond a upgrade ..

Warning - Puppet newby here. I am trying to set up a puppetmaster 3.3.2 and have run into a snag right out of the box. I want to add a new directory to modulepath= in /etc/puppet/puppet.conf So I added the following line in the [main] header modulepath = /etc/puppet/modules:/opt/our-repo/puppetmaster/modules And populated new new directory with modules I have written. I then run puppet

i got a little idea there, should not puppet use environement LANG=C when managing facts or packages etc... ? i have LANG=fr_FR.UTF-8 and puppet choke on quite a few facts (erors messages with uname for exemple: Pour en savoir davantage, faites: « uname --help ». ) and also with packages updates : /usr/bin/apt-cache policy mysql-client-4.1 => err:

I want to install a module into the modulepath. I can provide either a http url to a tar that contains the modules (like puppetforge but the path is not as structured) or I could provide a git url and path under that url where the module is. I want to first run puppet standalone on the vagrant vm host. This should download the appropriate modules and make them available on the filesystem

Hi List, Puppet Version: v2.7.13 Question - If I correctly setup multiple manifestdir''s in the puppet.conf file how can I import a node pp file located in a different directory tree to site.pp? My configuration information is below. In my puppet.conf file I have setup an environment called "stable", within this environment I have setup the manifestdir, modulepath and

Folks, I am interested in contributing to LLVM in the future. Meanwhile, I am reading many of the project documents (right now, "TableGen Language Reference"). Is there a way I can contribute corrections to these documents without cloning and building LLVM? ~~ Paul ---------------------------------------------------------------- Windfall Paul C. Anagnostopoulos

Hi, I exposed few days ago this situation on the IRC, but unfortunately I haven''t found a way to solve it yet. I run the Puppet Master with multiple environments, and everything is working good but a couple of nodes that are causing me some troubles. These nodes are pointing to my production environment and I need to point them back to development to grab some changes I made. I

I created ticket 961 "puppetd create too many/not closing TCP connections". I''m wondering if anyone else is seeing this? Depending on the client configuration a typical puppetd run will cause hunderds of simultaneous TCP connections to be opened to the puppet master. I''m gettting over 300 established connections for a single client in some cases. If the number of

Thank you for driving this Paul, I agree that it is better to have one doc on TableGen. This has been a point of confusion for me as well - when I land in the wrong one and can’t find what I’m looking for :-). -Chris > On Jul 31, 2020, at 1:49 PM, Paul C. Anagnostopoulos via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Thanks, David. I have started a new document titled

Hi guys I have a small question, I have 3 environments in puppet.conf file: [development] modulepath=/etc/puppet/development/modules manifests=/etc/puppet/development/manifests/site.pp I have defined the site.pp path, my question is do I need to make a nodes.pp for every environment?????? Thanks -- You received this message because you are subscribed to the Google Groups "Puppet

Hi, We are using pxelinux at my company to test our product. And there are limitations that we have hit in the past w.r.t. the max length of a path, or the max length of a module name (in mboot.c / mboot.c32). We've used workarounds in the past, and reorganized the directory structure, but we face that problem again. Out of the 128 / FILENAME_MAX chars that can be used, 110 - 120 go to the

Could you expand on this a bit? I see from my build directory that llvm-tblgen.exe was built before the Target/* .inc files. It sounds like you're saying that something has to be built between the .exe and the .inc files. At 8/4/2020 02:44 PM, Chris Lattner wrote: >> On Aug 4, 2020, at 11:31 AM, Paul C. Anagnostopoulos via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>

I''ve got a first version of a doc explaining how multiple environment support will work in the next release: http://reductivelabs.com/trac/puppet/wiki/UsingMultipleEnvironments As always, comments are appreciated. Even if you just don''t understand what the doc says, please let me know. It''s clear that the community is generally unhappy with the documentation I