[
https://issues.apache.org/jira/browse/AIRAVATA-2517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16244745#comment-16244745
]
Marcus Christie commented on AIRAVATA-2517:
-------------------------------------------
I was able to test this on dev. Here's what I did:
# Reverted the configuration fix in standalone.xml
# Restarted Keycloak on iamdev.scigap.org
# Verify that I can log into Keycloak and use the admin console
# Restarted the MariaDB server
# In the log I get the expected error messages like the ones posted in earlier
comments
# However, now I can't do anything in Keycloak. I can't log out, log in or use
any of the views. I get an error page.
#* As an aside, for some reason soon after the whole VM "freezes up". My SSH
session becomes unresponsive and I can't log back in. I have to soft reboot the
instance in the Jetstream Horizon console.
Then I put the configuration change back in. Now when I run through those
steps, after rebooting MariaDB, Keycloak is able to keep going and working.
Now that I know that the fix works I feel good about moving this into
production.
> Cannot view Users in seagrid gateway - Keycloak MySQL connection closed
> -----------------------------------------------------------------------
>
> Key: AIRAVATA-2517
> URL: https://issues.apache.org/jira/browse/AIRAVATA-2517
> Project: Airavata
> Issue Type: Bug
> Environment: https://seagrid.org
> Reporter: Eroma
> Assignee: Marcus Christie
> Priority: Critical
> Attachments: Screen Shot 2017-09-14 at 10.49.25 AM.png
>
>
> Cannot view users in the gateway, getting Invalid argument supplied for
> foreach()
> this restrict giving access to new users. or changing roles of existing in
> the gateway.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
