Replies: 1 comment
-
From the error message above (and experience) this is unlikely a build issue but rather a configuration issue and likely a configuration issue with the application server. The message mentions SignServerDS so it probably has to do with database/persistence configuration in WildFly. You can also try using the binary distribution of SignServer, instead of building from source, however you would likely end up with the same result as it looks to be the configuration of WildFly and/or database that is the issue here. |
Beta Was this translation helpful? Give feedback.
0 replies
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.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi everyone!
I've been trying to build SignServer from source using the steps provided on the official website, but unfortunately, I haven't been successful. I followed the documented instructions closely, but ran into issues during the process.
If anyone has an alternative method, a more detailed guide it would be incredibly helpful.
I got the following error while deploying:
"{ \"WFLYCTL0412: Required services that are not installed:\" => [\"jboss.naming.context.java.SignServerDS\"], \"WFLYCTL0180: Services with missing/unavailable dependencies\" => [ \"service jboss.persistenceunit.\\\"signserver.ear#ejbca\\\" is missing [jboss.naming.context.java.SignServerDS]\", \"service jboss.persistenceunit.\\\"signserver.ear#ejbca\\\".__FIRST_PHASE__ is missing [jboss.naming.context.java.SignServerDS]\", \"service jboss.persistenceunit.\\\"signserver.ear#SignServerJPA\\\".__FIRST_PHASE__ is missing [jboss.naming.context.java.SignServerDS]\", \"service jboss.persistenceunit.\\\"signserver.ear#SignServerJPA\\\" is missing [jboss.naming.context.java.SignServerDS]\" ]
Beta Was this translation helpful? Give feedback.
All reactions