Neil, I cleaned this up yesterday with flushing my servers *.db and $(workdir)/state/* dir. Oh yeah I also in desperation trashed my $(workdir)/ppkeys/* except my server keys these I kept. This in essences had reset the server, but let the populated clients still retain the server key. This was not ideal but I was not sure how bad off I was. In hind site I should have investigated more but well a few hosts I updated went find and no client connect to older server issues so upped the server.
I had my 40 down for a while while I was going through this motion. About 4 hours which was about 16 runs per host. Also confirm your getting rid of the root-.pub key with a tidy or some other method. Oh wait add the ::ffff:<subnet> to your allow lines in your server stanza. This was the final move I made. Also I did not have to define them all, its in the post I did yesterday on why we needed to define out the ipv4 if we are not utilizing the ipv6. If your talking Karma lets take a minute and thank Mark and the team for all their efforts.... - G On Wed, Feb 2, 2011 at 10:27 AM, <no-re...@cfengine.com> wrote: > Forum: Cfengine Help > Subject: Re: Upgrade 3.0.2 to 3.1.2 pains > Author: neilhwatson > Link to topic: https://cfengine.com/forum/read.php?3,20386,20406#msg-20406 > > C3 member with bad CF karma. That's depressing. I am in some serious > trouble with this on. I have at least a hundred hosts suffering from this > problem. > > _______________________________________________ > Help-cfengine mailing list > Help-cfengine@cfengine.org > https://cfengine.org/mailman/listinfo/help-cfengine > _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
