# Empty context.json prevents access to app (v1.6)

**URL:** <https://discourse.openondemand.org/t/empty-context-json-prevents-access-to-app-v1-6/1147>\
**Category:** Get Help\
**Created:** [October 6, 2020, 1:38pm UTC](https://discourse.openondemand.org/t/empty-context-json-prevents-access-to-app-v1-6/1147 "2020-10-06T13:38:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![emily.dragowsky](https://avatars.discourse-cdn.com/v4/letter/e/c68b51/32.png) [@emily.dragowsky](https://discourse.openondemand.org/u/emily.dragowsky)\
**Post date:** [October 6, 2020, 1:38pm UTC](https://discourse.openondemand.org/t/empty-context-json-prevents-access-to-app-v1-6/1147/1 "2020-10-06T13:38:15Z")

</div>

Greetings –

We report a situation with Ood 1.6. A problem was resolved yesterday related to an empty context.json file. To be clear, the file existed, but had no contents (file size 0). As a result, the enduser was unable to access the form for an interactive application (in this case, an implementation of kde desktop).

The error to the end user was ‘Internal Server Error’.

Removing the file resolved the problem.  
/home//ondemand/data/sys/dashboard/batch\_connect/sys/bc\_kde\_desktop\_rider/context.json

Perhaps error trapping against an empty context.json would be appropriate?

From a diagnostic point of view, we were able to look in the error\_ssl logs (/var/log/httpd24) and the user-level nginx logs to see http error codes, e.g.  
/var/log/ondemand-nginx//error.log

Was there other information to glean from these log files? or other log files to examine?

Cheers  
~ Em  
ps planning an upgrade to latest release 1.8.x this week.

---

<div class="post-metadata">

**Author:** ![efranz](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/efranz/32/27_2.png) [@efranz](https://discourse.openondemand.org/u/efranz)\
**Post date:** [October 7, 2020, 1:19am UTC](https://discourse.openondemand.org/t/empty-context-json-prevents-access-to-app-v1-6/1147/2 "2020-10-07T01:19:07Z")

</div>

Thank you for the report! Those are the two locations you would look for an error like this.

In 1.8 an exception raised around reading this context.json file will result in a warning message displayed to the user and the web form with default values set [https://github.com/OSC/ondemand/blob/4a3be9df479ea14ce89c70abf393f684ca8c22fa/apps/dashboard/app/controllers/batch\_connect/session\_contexts\_controller.rb#L12-L16](https://github.com/OSC/ondemand/blob/4a3be9df479ea14ce89c70abf393f684ca8c22fa/apps/dashboard/app/controllers/batch_connect/session_contexts_controller.rb#L12-L16)

After you upgrade if you still have problems with this please let us know.

---

<div class="post-metadata">

**Author:** ![westburg.2](https://avatars.discourse-cdn.com/v4/letter/w/0ea827/32.png) [@westburg.2](https://discourse.openondemand.org/u/westburg.2)\
**Post date:** [May 26, 2022, 3:43pm UTC](https://discourse.openondemand.org/t/empty-context-json-prevents-access-to-app-v1-6/1147/3 "2022-05-26T15:43:08Z")

</div>

Closed on May 26, 2022, 3:43pm UTC