Problem activating a partition #1046
erlispaula-coder
started this conversation in
General
Replies: 1 comment 1 reply
-
|
If the same HSM slot works on two different instances it is likely todo with the configuration of the Luna P11 library and it's Chrystoki.conf. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I am attempting to restore EJBCA CE 7.11.0 on an EC2 instance running Ubuntu 24.04.4 LTS (Noble Numbat). I am using WildFly version 26.0.1. The problem I am encountering is that, once the entire configuration process is complete and I am able to access the web administration interface, I am unable to activate the partition; it fails due to an alleged incorrect password, even though I am certain that the password is correct. To provide some context: I have an Ubuntu 22.04.5 LTS (Jammy Jellyfish) instance where everything is identical—except for the WildFly version, which is 24.0.1—and that instance is functioning correctly. My question is: could this be due to a data inconsistency within the database? Both instances are sharing the same database; I am running them in parallel because I am attempting to upgrade to newer versions of WildFly, and—although this is a test environment—I need to keep one instance operational. Another important detail: on the older instance, if I attempt to reactivate the partition via the admin interface, it also reports a password failure; however, I can simply restart WildFly afterward, and the partition activates automatically. Could I be missing a specific configuration setting that would allow the new EJBCA instance I am setting up to automatically activate the partition upon a WildFly restart? I have attached the logs.


Beta Was this translation helpful? Give feedback.
All reactions