Question #14996
closed
class configured for Signature (provider: BC) cannot be found
Description
Environment:
rudder server 5.0.11
rudder nodes at 5.0.11
Hello,
I updated from 5.0.10 to 5.0.11.
In the dashboard I noticed several nodes still being reported as 5.0.10
I checked those nodes and 5.0.11 is correctly installed. I then proceeded to check inventory,
no errors on nodes. In webapp I noticed that the node data is 7 days old. I checked the log
in /var/log/rudder/webapp and found the following error:
[2019-05-31 09:22:19] ERROR inventory-processing - Error when trying to process inventory 'connect-pdc-03-3d7c281f-bf53-4511-b361-f8f5641bded6.ocs' <- Error when trying to check inventory signature <- class configured for Signature (provider: BC) cannot be found.
I found corresponding issue https://issues.rudder.io/issues/12606 but the proposed solution (entry in java.security) is already present.
Does anyone have an idea what else could be wrong?
Thanks in advance
Tobias
Updated by François ARMAND over 5 years ago
Hello,
I don't see why an upgrade from 5.0.10 to 5.0.11 would cause that kind of problem.
Could you run on the server:
jrunscript -e 'exit (javax.crypto.Cipher.getMaxAllowedKeyLength("RC5") >= 256 ? 0 : 1);'; echo $?
If 1 is returned, then there's a problem with configuration (cipher strengh is limited). If 0 is returned, we will need to continu investigation.
Updated by Tobias Ell over 5 years ago
I executed the jrunscript - returncode was 0.
Updated by Tobias Ell over 5 years ago
Sorry - I restarted jetty and now the error is gone - should have tried this earlier.
Still very strange.
Thanks for your support François
Updated by François ARMAND over 5 years ago
- Status changed from New to Resolved
Tobias: no problem, it's nice that it now works. It may happen that if jetty is not correctly retarted, it keeps old jars in memory in place of the new one. It tends to lead to lots of strange behavior. This can be one of these cases.