similar to: sqlite errors

Hi, I''m upgrading from 23.2 to the latest and have "dbmigrate = true" in my config. When I try to run puppetd, I''m getting: Could not migrate database: SQLite3::SQLException: no such table: schema_info: SELECT version FROM schema_info I''m perfectly blowing away my old db (by deleting /var/lib/puppet/ state/clientconfigs.sqlite3 ?), but I haven''t

Hi, I currently have a MySQL database containing all Puppet storeconfigs. My intention is to migrate to PuppetDB on a PostgreSQL server, so the first step is to use the ''storeconfigs'' face to export all the DB to a file PuppetDB can later consume. But the ''puppet storeconfigs export'' command always ends up being killed, I suspect due to some sort of OOM

Hullo, I am attempting to use collections in order to distribute ssh keys across (soon) many hosts but I am hitting some trouble (the recipe I am using is at the end of this email). Namely it looks like sshkeys resources are not marked as exported in the sqlite db. I.e. if I do: sqlite3 clientconfigs.sqlite3 SQLite version 3.3.5 Enter ".help" for instructions sqlite> select *

Hello all, what exactly is the "design decision" that is needed here? We currently have the problem that 0.23.2-3 (debian package) does not work when it comes to collecting exported resources. The resources are saved in the database, so picking them up is the problem (db is Mysql5.x). This is a major problem for us, since we are using this a lot for our monitoring services. I

For those of you out there using export/collect (which we really need to come up with a better name for...), can you test the current SVN code? I''m mostly wondering if the performance is any better. To use it, you''ll have to remove your current database, since the database schema is significantly changed. I''m getting what looks like an additional 25% reduction

I had a host that was exporting a resource to another host to trigger backups. The first host has now gone away, but the second host is still seeing the exported resource (because it still exists in the puppetmaster''s database). I fixed the problem by going in to the database and deleting all the rows I could find that related to the absent host, but I''m wondering if

Hello, I am not sure if I trigger a bug and if so it could also be in ruby sqlite3 backend. However, maybe I do something totally wrong. I have the following part in puppet.conf: [master] storeconfigs = true dblocation = /var/lib/puppet/state/clientconfigs.sqlite3 dbadapter = sqlite3 Now every time a client (agent in puppet speak) is run I get one more connection to the

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.

I have a node that has some bad stored configs (namely the wrong ssh host keys) that I''m trying to clear out. Looking around it seems I''m supposed to do: puppet node clean foo.example.com However, that keeps bailing out because it''s trying to open a SQLite3 db where stored configs are normally kept, but my stored configs are kept in puppetdb (http://pastie.org/7814483

Hi all, As I understand it, storeconfigs needs to be enabled on both the agent and the master to function ideally. I have a couple of questions: -> Can the various agents and the master safely share the same storeconfigs db (say, a postgresql server)? Is there any benefit to setting things up this way? -> Is there any benefit for an _agent_ to use an RDBMS vs sqlite for its

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

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

Hello, I just installed the latest version of puppet and puppetmaster on an up to date RHEL4 system. If I turn on ''storeconfigs'' on the puppetmaster server I get the following error: debug: Calling puppetmaster.getconfigerr: Could not retrieve configuration: Uncaught exception No such file to load -- sqlite3 in method puppetmaster.getconfig I have gems and rails installed

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

A concrete example: We''re building a system to organize the information about workshops being held in various conventions. A convention has more than one workshop, and each workshop can be held in more than one convention. Also each workshop has a host, who is specific to a workshop being held in a specific convention. For example, Matz may host an "Introduction to Ruby"

redux patchset permitting a vm to be associated with multiple networks and vice-versa. updated patchset so as to be applicable against current oVirt server HEAD these patches may be applied in any order, they all need to be pushed together

After upgrading my puppetmaster to 0.24.7 from 0.24.6 i am getting the following errors in the puppetmaster logs. Any help would be appreciated. Thu Dec 18 16:11:39 +1100 2008 Puppet (err): Could not store configs: undefined method `environment='' for #<Puppet::Rails::Host:0xb72c0c38> I do not use environment''s and they are not defined anywhere in the puppet.conf

This patchset contains changes to the ovirt server frontend, backend, and tests components, permitting vms to be associated with multiple networks and vice versa. Also included are two patches which are required for the frontend bits; a patch adding collapsable sections to the vm form, which in itself depends on the second patch that provides default values for the cpu and memory vm table fields

[cc'ing back to r-help] On Fri, Nov 18, 2011 at 4:39 PM, matteo dossena <matteo.dossena at gmail.com> wrote: > Thanks a lot, > > just to make sure i got it right, > > if (using the real dataset) from the LogLikelihood ratio test model1 isn't "better" than model, > means that temporal auto correlation isn't seriously affecting the model? yes. (or

Hello, When I tested out SVN 1987, puppetmasterd barfs because gems is looking in puppet/rails/lib no puppet/rails. This is under FC6 with gems/rails installed from source. The simple fix for me was to create the directory lib and link the files in /puppet/rails there. .r'' Original error: # puppetmasterd --debug /usr/lib/ruby/site_ruby/1.8/rubygems/custom_require.rb:27:in