The first error means that there are existing tables in the local H2
database (under standalone/data there are keycloak.* files).
It looks like the logic determined that they are of some previous db schema
version, and tried to upgrade the schema to latest version, but
unexpectedly the schema in place already seems to contain the tables it
wasn't supposed to contain.
I suppose that could happen if upgrade process is interrupted by restarting
the server?
Since you are using the default H2 database I assume you don't care about
any existing data. The solution for you then is to stop the server, delete
the database (rm standalone/data/keycloak.*), and start the server again.
On Sun, Jun 19, 2016 at 2:44 PM, John Dennis <jdennis(a)redhat.com> wrote:
[Note: you may get 2 copies of this email, I sent one previously from
my
private email account and it was held for moderator approval, re-sending
this under my redhat account which is subscribed to this list.]
Using the latest release candidate /devel/candidates/jboss/sso/RHSSO-7.0.0
built on 6/13
the server will not initialize, server.log has a number of errors the
following being the significant one I believe.
Failed to start service
jboss.undertow.deployment.default-server.default-host./auth
For a while now we've seen errors related to database operations in the
log, those errors are also present in the attached log but even with those
database errors the server had seemed to start OK.
Would someone be kind enough to look at the attached log and suggest why
the server won't start and what errors in the log should be concerning?
Many thanks,
--
John
_______________________________________________
keycloak-dev mailing list
keycloak-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-dev