search for: facts

I would like to trace functions, displaying their arguments and return value, but I haven't been able to figure out how to do this with the 'trace' function. After some thrashing, I got as far as this: fact <- function(x) if(x<1) 1 else x*fact(x-1) tracefnc <- function() dput(as.list(parent.frame()), # parent.frame() holds arg list

I would like to trace functions, displaying their arguments and return value, but I haven't been able to figure out how to do this with the 'trace' function. After some thrashing, I got as far as this: fact <- function(x) if(x<1) 1 else x*fact(x-1) tracefnc <- function() dput(as.list(parent.frame()), # parent.frame() holds arg list

Some time ago i sent to the list a problem i was having with facts on fedora core 6 and wasn''t able to find a solution at that time, but with the release of RHEL5 and CentOS 5 based on fc6 i have hit the problem again. i have written several facts to collect information about a clients network and i am also using the vmware fact from the wiki. i have...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I''m having a problem pulling down new facts. On one of my nodes I''m getting this error: err: fact_collector/file=/var/lib/puppet/facts/source: Could not describe /facts: Fileserver module ''facts'' not mounted notice: fact_collector/file=/var/lib/puppet/facts: source puppet://puppet/facts does not exist err: fact_co...

All, When I take a subset of a factor the reduced factor still maintains all the original levels of the factor when say forming the key in a plot. The data is correct, but the variable still "remembers" the original levels. See below for reproducible code. Does anyone know how to fix this? cheers, dave fact = as.factor(c(rep("A", 3),rep("B", 3), rep("C",

...round to releasing Facter 1.5. As the version bump implies, this is a relatively significant release (for a 2.3k line program, anyway). Mostly, the biggest change is refactoring the code internally so that all of the functionality is split into separate classes in separate files. Also, the facts are all loaded on-demand, which provides dramatic speedups for printing individual facts, but generally doesn''t affect how Puppet and Facter interact, other than making it possible for Facter to load facts that Puppet syncs via its pluginsync. Here''s the ChangeLog: Fi...

I have some facter file to distribute before running puppet on the platform. The problem is : how can i send the facter local.rb file so the rest of the .pp file take into account the new facts created ? ex: i have sudopath as a facter fact and one sudoers class that need that sudopath to work. How do you model that ? it seems puppet would have to rerun after the new local.rb is downloaded ? -- Cordialement, Ghislain _______________________________________________ Puppet-users...

...certificate request for xxxxxxxxxxxxxxxxx info: Requesting certificate warning: peer certificate won''t be verified in this SSL session notice: Did not receive certificate info: Requesting certificate warning: peer certificate won''t be verified in this SSL session info: Retrieving facts err: fact_collector/file=/usr/local/.aqadmin/puppet/var/facts/source: Could not describe /facts: Certificates were not trusted: certificate verify failed notice: fact_collector/file=/usr/local/.aqadmin/puppet/var/facts: source puppet://xxxxxxxxxxxx/facts does not exist err: fact_collector/file=/...

Dear Listers, can anyone help me, please. Since several days i try to figure out, how to assign values, vectors, functions etc to variables with dynamically generated names inside of functions. Sometimes I succeed, but the success is rather arbitrary, it seems. up to now i don't fully understand, why things like get, assign, <<- etc do sometimes work, and sometimes not. here's one

I have a small environment with a single puppetmaster and puppetdb on the same node that I get sporadic "Failed to submit ''replace facts'' command" errors from nodes. It isn''t consistent about which nodes are causing the error and I can''t find anything else going on at the same time on either the master or the agent that these errors happen. Here are the logs from a previous event The puppet clien...

I have a requirement where I want a Fact to be stored in PuppetDB during the manifest run and not during the initial fact gathering phase. I know I can, in my manifests, create a file in /etc/facter/facts.d or I can write a Ruby script that will then be distributed by plugin sync. But both of these methods will only publish the fact during the initial phase of the puppet agent run. What I want to be able to do is set a fact during the manifest run portion that will then be stored in the PuppetDB...

Hello all, I am running puppet 2.7.1 with mongrel and an apache proxy. I have been seeing an issue where it appears that the puppetmaster is completely ignoring any facts that are sent to it. When a client connects, any configuration that relies on facts shows those variables as being empty strings. (I have been testing this with a simple notify resource that prints out the IP address and the FQDN. Both of these are coming up as empty strings.) If I check the lis...

I am trying to expose a custom fact that requires a certain gem to be installed. However, the facts are being loaded before the module is loaded (and I see why this is the case sine the fact should be made available to the module). So my question is, is there a way to avoid this chicken and egg problem? I tried putting the module in a stage before main, but it still looks like the facts are...

Hi I''m trying to add extra facts to facter. The puppetd is running on Debian Etch Amd64 as Xen 3.1 guest. I''ve follow the Wiki on adding the facts. First I used relative path in the manifest and added "factsync=true" in client''s puppetd.conf. And then tested it with "puppetd -vt". But no matte...

fact loads: I use facter to search the rsync path and then i write this sudoers line: Cmnd_Alias BACKUPCOMMANDS = /usr/bin/rsync I call puppet like this: puppetd --factsync --server=xxx.yyy.61.131 --waitforcert 60 --test the recipe is: sudoensure_line { sudobackupcommands: ligne => "Cmnd_Alias BACKUPCOMMANDS = $rsyncpath", before => sudoensure_line["sudoaqbackup"] }...

Dear all, This is a continuation of another thread, but I think the question diverged enough to create a new one. I have a hiera hierarchy like this: :hierarchy: - %{fqdn} - %{secundary_group} - %{primary_group} - %{productname} - all And I need to define the secondary/primary groups as facts, on the nodes. Gary has suggested me to use plugins, that they will provide the facts before puppet runs... but I was thinking: for plugins to give facts, taken directly from within the puppet code, puppet needs to run first, doesn''t it? So, I guess I could create a module and a ruby...

...t adds a string to a fact. However I have written a module but it appears to me that the custom fact has been applied to all my machines without me specifying any node definitions. When I run a puppet agent --test --noop, I see the custom fact appear in /var/lib/puppet/lib/facter. Info: Loading facts in /var/lib/puppet/lib/facter/addfacter.rb I checked my nodes by running facter and it doesn''t appear, unless I run facter -p I only want my custom fact to run on a specific node via a definition My question is, do custom facts scripts run by default regardless of any node definition...

I''m working with a pretty simple config at the moment to track down some issues I''m seeing with custom facts and plugins. I have factsync = true (default locations) and I have a simple fact in /var/lib/puppet/facts/ (actually it''s David''s netmask plugin) my pp file I''m testing with contains only: notice "netmask: ${netmask}" puppet -v test.pp give sme... info: Loadin...

Hi, For a long time now when we run puppetd --test I get the following double output on our custom facts, info: Retrieving plugin info: Loading facts in scratch info: Loading facts in os_name info: Loading facts in pam_limits_d info: Loading facts in os_platform info: Loading facts in nvidia_graphics info: Loading facts in hostname_hour info: Loading facts in os_version info: Loading facts in rhn inf...

...cter, i.e. network -> interface -> ipaddress. 2. Additional output formats - JSON, XML? (winces) - Facter already outputs in YAML. 3. Additional collection mechanisms, for example the ability to specify a fact file, /etc/facter.conf, containing fact name=value pairs. 4. A more Ruby DSL for facts 5. Rich data structures/values in facts If you have additional ideas/requirements/issues/comments we''d welcome feedback. Regards James Turnbull - -- Author of: * Pulling Strings with Puppet (http://www.amazon.com/gp/product/1590599780/) * Pro Nagios 2.0 (http://www.amazon.com/gp/produ...