similar to: 0.20.1 and sqlite3 error

Displaying 20 results from an estimated 2000 matches similar to: "0.20.1 and sqlite3 error"

2006 Dec 29
5
sqlite errors
Hello, When I kick off SVN1992 with storeconfigs=yes, I get the following error: err: Could not store configs: SQLite3::SQLException: SQL logic error or missing database: INSERT INTO resources ("exported", "line", "title", "host_id", "restype", "source_file_id") VALUES(NULL, 23, ''svnpkgadd-emacs-nox-etc'', NULL, NULL,
2010 Dec 06
7
error running puppetrun
Hi, I have been getting the below error for sometime now. Both master and client are using version 0.24.8. Output from /var/log/messages err: Could not call puppetmaster.getconfig: #<#<Class:0xb7b50a9c>: execution expired> err: Could not retrieve catalog: execution expired P.S- all of this was working absolutely fine and suddenly has started to misbehave. Regards, -- You
2009 May 12
3
Problem with storeconfigs
Hello all, I have what is certainly a stupid problem on my part. I have setup puppet in a test environment and it''s been working wonderfully. I am now in the process of moving this to our production systems and I have rebuilt our puppetmaster completely from scratch using the same modules/manifests, etc. from my test system. Unfortunately I am running into an issue with what I
2007 Oct 19
3
client update to 0.23.2: "Could not find value for"
hi all, we maintain about 30 puppet managed nodes. the version of the clients is 0.23.0 and 0.23.1. the master is 0.23.0. today we installed a new CentOS 5 node with David Lutterkort''s puppet 0.23.2 rpm. this host is a reinstall of an old FC4 on new hardware. we are getting this error on 0.23.2, never happened before: | Could not retrieve configuration: | Failed to parse template
2009 Jun 09
2
err: Connection timeout calling puppetmaster.getconfig: execution expired
Hi all, My current conf splits 188 clients execution in one hour, and puppet runs as a cron job. My server (2cpu 2 GB RAM) runs with mongrel (with 8 puppetmasterd) and this conf works fine. We''d like puppet to run clients all at same time (force a change, i.e.), so we''re testing several things. (Previous conf do not support massive execution). First and most important, is
2007 Jan 10
9
Definition specialization
There was a discussion a while ago about adding inheritance to definitions. There is a need for a way to specialize parameters while allowing passing other options. This comes up with remotefile where it would be nice to have a default server location but not specify all the parameters (and their defaults) in the definition. Was there a change to the syntax? Is there a way to accomplish this?
2007 Feb 22
33
Scaling Puppet 0.22.1 to hunderdes of nodes.
Hi, My environment is composed of ~250 workstations hitting a single puppetmaster server, which has been working fairly well up until now. The most recent change has been a migration of a lot of remote file copy objects which were previously handled with cfengine. client side puppetd calls to the puppetmaster.getconfig method are taking unreasonably long, on the order of 2-3 minutes. It
2006 Dec 03
12
Problem with user type on 0.20.1... uses group "absent"
Hi, I''m running into a problem with the user type with puppet 0.20.1... this worked before with 0.19.x at least, not sure about 0.20. But I''ve got adduser.pp: <snip> define adduser($uid, $gid, $groups="users", $membership="minimum") { group { $name: gid => $gid, allowdupe => false, ensure
2007 Dec 22
8
puppet with postgresql adapter
Hi all, i'' m trying to configure puppet to use rails with postgresql. I'' m having troubles to make it work. Got no error when running puppetmasterd but nothing is being populated in the DB. Is anybody using puppet with postgres ? my config (in puppet.conf) [rails] dbadapter = postgresql dbname = mydb dbserver = localhost dbuser = user dbpassword = password
2006 Nov 13
4
ANNOUNCE: 0.20.1
The latest release is finally out; here is the changelog: Mostly a bug-fix release, with the most important fix being the multiple-definition error. Completely rewrote the ParsedFile system; each provider is now much shorter and much more maintainable. However, fundamental problems were found with the ''port'' type, so it was disabled. Also, added
2007 Apr 12
14
how to make puppet a killer app
I''ve been thinking about how to make Puppet a killer app, and I think there is one specific thing that could be done to help make that happen: People using Puppet now to consistently state what they *really* wish Puppet could do for them -- the recent thread around Puppet on Windows is in that vein, but it''s not specific enough. For example, I''d like to know what
2007 May 27
1
puppetmasterd file handle problem
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi all, I''m running the latest version of puppet (debian 0.22.4-2), and I''ve gotten to a point with my configuration where puppetmasterd needs to be restarted every few days due to what seem like file handles not getting closed. I either see this set of errors: May 22 08:08:34 localhost puppetd[2810]: Could not get config; using
2007 Dec 10
3
Is the SSL issue solvable for (the apt-get) Puppet version 0.20.1 ??
Hi All, I''ve been trying to resolve the SSL issue as described on the link at the bottom. I understand the issue and I''ve tried to implement all the different patches (one at a time .. :-). However for most of them there are either files missing or code not found in the files. It seems this is due to a version difference in Puppet. The docs and patches seem to be for the
2008 Jun 08
1
SOLVED: Re: SSL delegation difficulties
The problem was solved when we moved to an Apache+mongrel setup from the initial webrick setup. Seems that webrick doens''t handle the SSL certs correctly enough to get this type of setup working. .r'' 2008/6/3 RijilV <rijilv@gmail.com>: > hey all, trying to get SSL cert deligation working based on > http://reductivelabs.com/trac/puppet/wiki/PuppetScalability.
2007 Dec 18
5
resource collection error
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
2008 Dec 31
6
tlsv1 alert decrypt error
I''m using the standard webrick server with puppet, and I just started getting this today (for no apparent reason). info: Loading fact custom_facts info: Retrieving plugins err: /File[/var/puppet/lib]: Failed to generate additional resources during transaction: Certificates were not trusted: tlsv1 alert decrypt error err: /File[/var/puppet/lib]: Failed to retrieve current state of
2008 Nov 10
12
CA_Server woes
I''m having difficulty getting my head around some CA issues My client has: [puppetd] ca_server=puppetca.mydomain.com and puppet resolves to a different machine. when puppet connects, it requests a signature from puppetca.mydomain.combut then on the next pass fails with the following: err: Could not retrieve catalog: Certificates were not trusted: SSL_connect returned=1 errno=0
2008 Oct 29
7
Package and log in puppet
Hi all, my name is Arnau Bria and I''m a sys admin in a center where we must deal with hundred hosts. We''re currently working with quattor, but it''s too complex for our purposes, so I''m looking for new admin tool. I''ve been playing with CFengine for few days (2 or 3) and I''ve seen some limitations that makes me thing that CFE is not our
2006 Nov 21
5
strange puppetd error
Greetings, I''m trying to set up a minimal CentOS 4 kickstart that installs puppet during the %post and then use puppet to build up the rest of the configuration. I''ve gotten things so that puppet 0.20.1-2 will install using yum during the %post in the kickstart, but now I''m seeing this error when it tries to run during %post and after I reboot the newly installed
2007 Jan 04
4
yumrepo err
I am just starting with puppet to replace a ''homegrown'' config distribution system and it is looking very promising, i will be playing with the templating next. I have run into an error when attempting to disable the shipped repo''s with CentOS 4.4. See the relevant info below. This is obviously a problem when repo definitions include multi-line baseurl''s.