any ideas on how i could fix this one
FYI the
ncf/50_techniques folder should not be downloaded, and there should be an exclusion, which seems to fail for some reason. We say it happen on 5.1 (still in dev), but though it was due to changes we were making.
is there any way to check keyfiles /var/rudder/cfengine-community/ppkeys/localhost.{pub,priv}
?
e.g.: whether they are valid and matching
you mean if the public key matches the private one ? Or do you mean if the couple one an agent agree with the known public key on the server ?
this was for a specific node on prev. weekend
the host was re-installed to sles12sp2(from sles11) and the old cf-keys(that were used for agent v2.11.13) were re-used on rudder-agent 4.1.10
the host was re-installed to sles12sp2(from sles11) and the old cf-keys(that were used for agent v2.11.13) were re-used on rudder-agent 4.1.10
could this be a problem to re-use the old keys?
well, in all cases, rudder shouldn't report that the PEM is invalid if it was previously
node uuid and hostname didn't change?
however, the node was connecting to the old master(version 3.1.17) and added to the new master(version 4.1.7) after reinstalled to sles12sp2
[2019-07-26 22:52:07] ERROR com.normation.rudder.domain.nodes.NodeInfo - Error when trying to get the CFEngine-MD5 digest of CFEngine public key for node ... <- problem extracting key: java.lang.IllegalArgumentException: failed to construct sequence from byte[]: corrupted stream - out of bounds length found
yes in the webapp log
the keys in the agent are standard openssl keys, so you may be able to check them using openssl, for example https://kb.wisc.edu/page.php?id=4064
openssl rsa -noout -text -in localhost.priv
Enter pass phrase for localhost.priv:
Enter pass phrase for localhost.priv:
but i get another public key using comand
openssl rsa -in localhost.priv -pubout
Enter pass phrase for localhost.priv:
openssl rsa -in localhost.priv -pubout
Enter pass phrase for localhost.priv:
i'd say replace the public one and re run an incentory
I have a problem with a node
I rename his hostname
and rudder agent update, failed
I have remove the node from rudder and reinit the node agent
it solve
:)