On Thursday, February 28, 2013 6:09:35 PM UTC+1, Ken Barber wrote: > > FYI, I just upgraded only the PuppetDB part to 1.1.1, using the old > 1.0.2 terminus I get no errors: > > 2013-02-28 17:06:27,711 WARN [qtp1478462104-39] [http.server] Use of > unversioned APIs is deprecated; please use /v1/commands > 2013-02-28 17:06:28,284 INFO [command-proc-44] [puppetdb.command] > [7a4a1f70-1e85-4256-8f95-21008b6c1199] [replace facts] puppetdb2.vm > 2013-02-28 17:06:30,724 WARN [qtp1478462104-32] [http.server] Use of > unversioned APIs is deprecated; please use /v1/commands > 2013-02-28 17:06:32,693 INFO [command-proc-44] [puppetdb.command] > [a87001c5-f064-4a2d-9f9e-de903f62f824] [replace catalog] puppetdb2.vm > > As I was saying, we're not entirely sure that this behaviour was causes by the upgrade. We only noticed it one week after the upgrade (so unfortunately the postgres logs from before the update were rotated, that's the default setting), and it might be a coincidence. Then again. maybe not. :)
> If at all possible - I wouldn't mind a full copy of your puppetdb.log > ... to dig a bit deeper. And I know I told you to clear the KahaDB > queue (I always make this mistake) but I don't suppose you kept an old > copy of it? > We kept the KahaDB backup both times we flushed the queue. The sizes in /var/lib/puppetdb/mq/localhost/ are as follows: 1.3G ./KahaDB 637M ./KahaDB.old2 1.1G ./scheduler 6.2G ./KahaDB.old The big one is a 25 000 queue. I would happily send the logs over, but this is something I have discuss with my colleagues. Again, thank you for helping! :) ak0ska -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
