Troubleshooting HTTP errors

Problems can be caused by issues as diverse as system errors, Web server errors, fglrun process errors, incorrect configurations, or other issues. Use the GAS logs to try to isolate the problem and determine if it is an issue that you can resolve or one that needs the assistance of your local Four Js support center.

Viewing information about the GAS

You need to have access to the following logs:
Web services logs:
  • The dispatcher log for the dispatcher process. For example, <dispatcher-name>.log.
  • The GWS proxy logs. For example, look for the gwsproxy-<group>-app-name.log started to serve each Web service.
  • The VM logs. For example, look for the vm-<group>-app-name-<number>.log for each fglrun process used to serve the Web service.
Web application logs:
  • The dispatcher log for the dispatcher process. For example, <dispatcher-name>.log.
  • The UA proxy logs. For example, look for the uaproxy-<session-id>.log started for each Web application.
  • The VM logs. For example, look for the vm-<session-id>.log for each fglrun process used to serve a Web application.
Tip: If the dispatcher is still running, you can troubleshoot the dispatcher and proxy logs using the monitor URL. Otherwise, locate the GAS logs in your appdata/log/<dispatcher-name>/<date> directory. See Log files.
Important:

Sensitive and personal data may be written to the output. Make sure that the log output is written to files that can only be read by administrators, and review the management strategy for log files.

  1. Check the VM logs for standard errors or error messages.

    It is recommended that you check your VM logs first because if there is an indication that the fglrun process crashes, then this will also lead to HTTP errors appearing in the proxy logs.

  2. Check the proxy logs, Web services (gwsproxy) or Web applications (uaproxy), for errors.

    If an error is reported in the proxy logs, it should have a corresponding entry in the dispatcher or VM logs for the process that was active at the time.

  3. Check the dispatcher log file for HTTP request failures, etc.

    If, for example, you are troubleshooting HTTP request failures, search for HTTP codes other than 200. Codes in the 400 range indicate a request that failed given the information provided (for example, a required parameter was missing, etc.). Codes in the 500 range indicate an error with the server. For an example, see Troubleshoot error 503.

  4. If further assistance is required, contact your local Four Js support center. If requested to send the GAS logs, copy the logs for the date the issue arose to a zip file and email it to your support contact. Typically these logs are needed:
    • appdata/log/*.log.
    • Related dispatcher daily logs (dispatcher, proxy, and vm) for the date the issue arose.