Just to keep up on this thread... I updated my policysrv2 today. When I cleaned the db files up as I was not interested in the historical info and mostly policysrv2 was used for the policy testing. When I run I still see in this build (rebuild from the web released http://www.cfengine.org/tarballs/download.php?file=cfengine-3.1.2.tar.gz) that its looking for a root-.pub key.
Couldn't find a public key (/var/cfengine/ppkeys/root-.pub) !!! System error for fopen: "No such file or directory" Couldn't find a public key (/var/cfengine/ppkeys/root-.pub) !!! System error for fopen: "No such file or directory" [r...@policysrv2 cfengine]# In my ppkeys dir I dont have this and the new binaries have behaved and acted as expected - giving the md5sum naming. cf-key -s shows the proper match. One thing I noticed was the addition of the cf-hub and in verbose I see the notes about only in nova (although I have built binary file there). Is there a trunk release I can test? Does anyone have any thoughts on this? Regards, Gusto On Mon, Jan 10, 2011 at 6:11 PM, Gusto <gustofw...@gmail.com> wrote: > Thank you all for taking a look.... For tracking and investigation I > have created this bug: > https://cfengine.com/bugtracker/view.php?id=442 > -G > > On Mon, Jan 10, 2011 at 5:00 PM, Nicolas Charles > <nicolas.char...@normation.com> wrote: >> I had no problem at all, it went all flawlessly, the agent taking care >> of the keys migration. Tested on Debian 4 and 5, Centos 4 and 5, and Windows >> >> Nicolas CHARLES >> Normation SAS - http://www.normation.com >> 44 rue Cauchy – 94110 ARCUEIL >> +33 (0)1 83 62 26 96 - +33 (0)6 14 63 25 18 >> >> >> On 10/01/2011 18:28, Gusto wrote: >>> Hi Folks, >>> >>> I have a ppkeys question: Has anyone had issues with 3.0.4/3.0.5p1 >>> generated keys and the new 3.1.2 keys updates? Does the 3.1.0+ new >>> hash change the key so the server's public copy of the client no >>> longer matches? Ideally I am going to move everything just was looking >>> for others experiences... >>> >>> I have an established environment with 200+ machines which has grown >>> from 3.0.1 and is mostly at 3.0.5p1 at this point. I am testing the >>> update to the 3.1.2 on the clients (servers still at 3.0.5p1) but I >>> see some key issues preventing me from just making a large update. >>> >>> My current solution is to just removing the old keys from client and >>> server then run cf-key to get things working again. When we commit to >>> the update first to update are the main policy servers then the >>> clients. Ideally I would like to just update the binaries leaving keys >>> in place if possible. Before taking the 3.1.2 plunge I wanted to ask >>> if anyone has done similar site updates? >>> >>> Best Regards, >>> Gusto >>> _______________________________________________ >>> 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 >> > _______________________________________________ Help-cfengine mailing list Help-cfengine@cfengine.org https://cfengine.org/mailman/listinfo/help-cfengine
