<div dir="ltr">Another thing to try would be:<div><br></div><div>bin/jboss-cli.sh --connect shutdown</div><div><br></div><div>This one will wait until first time boot is completed properly, and only then perform a shutdown.</div><div><br></div><div>If it times out while waiting, the process will exit with error code, and display a message:</div><div>
<p class=""><span class="">Failed to connect to the controller: Timeout waiting for the system to boot.</span></p></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 22, 2016 at 8:37 AM, Stian Thorgersen <span dir="ltr"><<a href="mailto:sthorger@redhat.com" target="_blank">sthorger@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Initializing the database can take a while (1-2min), so you'd need a relatively long timeout on a first startup. Either pinging '<a href="http://localhost:8080/auth/" style="font-size:12.8px" target="_blank">http://localhost:8080/auth/</a><span style="font-size:12.8px">' or looking in the log would work just fine. You can also use jboss-cli to check the status, for example to check if server is started fully:</span><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">bin/jboss-cli.sh --connect ':read-attribute(name=server-state)'</span></div><div><span style="font-size:12.8px"><br></span></div><div>Or check the status of Keycloak individually:</div><div><br></div><div>bin/jboss-cli.sh --connect 'deployment-info --name=keycloak-server.war'<br></div><div><br></div><div>An alternative is to use Liqubase to extract the SQL schema for your database. That way Ansible can setup the database fully prior to starting Keycloak in the first place. If you're interested in that approach let me know and I'll let you know the details for that.</div><div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px"><br></span></div></div></div><div class="gmail_extra"><br><div class="gmail_quote"><div><div class="h5">On 22 June 2016 at 00:46, John Dennis <span dir="ltr"><<a href="mailto:jdennis@redhat.com" target="_blank">jdennis@redhat.com</a>></span> wrote:<br></div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">FYI, the following Jira issue was opened for this.<br>
<br>
<a href="https://issues.jboss.org/browse/KEYCLOAK-3150" rel="noreferrer" target="_blank">https://issues.jboss.org/browse/KEYCLOAK-3150</a><br>
</div></div><div><div><span class="HOEnZb"><font color="#888888"><br>
--<br>
John</font></span><span class=""><br>
_______________________________________________<br>
keycloak-dev mailing list<br>
<a href="mailto:keycloak-dev@lists.jboss.org" target="_blank">keycloak-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/keycloak-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/keycloak-dev</a><br>
</span></div></div></blockquote></div><br></div>
</blockquote></div><br></div>