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.
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.
Was there other information to glean from these log files? or other log files to examine?
ps planning an upgrade to latest release 1.8.x this week.