You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@airavata.apache.org by "Eroma (JIRA)" <ji...@apache.org> on 2016/08/11 14:41:20 UTC

[jira] [Commented] (AIRAVATA-2034) New account creation confirmation fails in dev.scigap.org with error message 'Unable to Connect to the Airavata Server Instance!'

    [ https://issues.apache.org/jira/browse/AIRAVATA-2034?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417348#comment-15417348 ] 

Eroma commented on AIRAVATA-2034:
---------------------------------

While getting the 'Unable to Connect to the Airavata Server Instance!' in the portal can see the menus Experiment, Admin Dashboard, etc...
When clicked on the admin dashboard menu gets error screen with AiravataSystemException 'Error while getting all the gateways. More info : Error while getting all the gateways. More info : Error while retrieving the resource GATEWAY'
image attached.

> New account creation confirmation fails in dev.scigap.org with error message 'Unable to Connect to the Airavata Server Instance!'
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: AIRAVATA-2034
>                 URL: https://issues.apache.org/jira/browse/AIRAVATA-2034
>             Project: Airavata
>          Issue Type: Bug
>          Components: PGA PHP Web Gateway
>    Affects Versions: 0.17-SNAPSHOT
>         Environment: https://dev.scigap.org/
>            Reporter: Eroma
>            Assignee: Nipurn Doshi
>
> When I entered username and password to confirm an account creation in  getting 'Unable to Connect to the Airavata Server Instance!' 
> But the airavata server is running and was able to successfully confirm account creation in a different gateway connecting to same airavata server.
> Also can successfully login with existing users as well. getting this message only when tried to confirm new account creation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)