Hi all,
On Sun, Apr 5, 2020 at 8:59 PM Suresh Marru <[email protected]> wrote: > Hi Isuru, > > I wonder if it is related to renew tokens? Any insights? > There is a chance. But, AFAIK the server caches authorization decisions for at least one hour through auth cache (by default this is enabled). So it is unlikely that the server may try to renew tokens before that time. Breaking in 30 minutes interval is wired. Anyhow, there is a probability of occurring this if sever unable to access sharing registry. Hence, I think better to check whether DB connections and IAM sever connections are correctly established. Is there any error logs on server-side ? thanks Isuru > > Suresh > > On Apr 3, 2020, at 6:48 AM, Dinuka Desilva <[email protected]> > wrote: > > Hi, > > I got the airava and airavata-django-portal running on localhost by > executing following script on 4 terminals one after the other. > > 1. docker-compose down && rm -rf database_data/ && docker-compose up > 2. mvn exec:java > -Dexec.mainClass="org.apache.airavata.ide.integration.APIServerStarter" > 3. . ./build_js.sh > 4. source ./venv/bin/activate && rm -rf ./tmp/ && rm -rf db.sqlite3 && > python manage.py migrate && python manage.py load_default_gateway && python > manage.py runserver > > > With this I could access the localhost server at http://localhost:8000. > But, only for less than half an hour it worked and then it's ended up with > the following error. It has the logged in user though an error occurred. > > <Screenshot 2020-04-03 at 4.03.25 PM.png> > > Neither restarting the servers nor clearing cache didn't solve this issue. > And I had to execute above four script again which recreates the database. > For kind of each 20-30 minutes, I had to do this. I'm doubtful whether I'm > doing anything wrong. > > Also, below I have attached the settings_local.py. > > Thanka & Regards, > Dinuka > <settings_local.py> > > > -- Research Software Engineer Indiana University, IN
