Uploaded image for project: 'IGB'
  1. IGB
  2. IGBF-1963

Fix codec error in Apache log

        Details

        • Type: Bug
        • Status: Closed (View Workflow)
        • Priority: Major
        • Resolution: Done
        • Affects Version/s: None
        • Fix Version/s: None
        • Labels:
          None

          Description

          When I was setting up the new alpha App Store, I had some problems with my S3 access token.

          The error message was printed to the Apache log file (error_log), which I used to diagnose the problem.

          However, there were a number of unrelated errors that also got printed to the log. It looks like these errors have something to do with how error messages are getting printed.

          snip

          [Thu Aug 08 22:53:06.700416 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] During h
          andling of the above exception, another exception occurred:
          [Thu Aug 08 22:53:06.700456 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823]
          [Thu Aug 08 22:53:06.700502 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] Tracebac
          k (most recent call last):
          [Thu Aug 08 22:53:06.700586 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] File "
          /var/www/vhosts/appstore/venv/appstore/lib/python3.6/site-packages/django/core/handlers/exception.py", line 34, in in
          ner
          [Thu Aug 08 22:53:06.700635 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] resp
          onse = get_response(request)
          [Thu Aug 08 22:53:06.700684 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] File "
          /var/www/vhosts/appstore/venv/appstore/lib/python3.6/site-packages/django/utils/deprecation.py", line 94, in _call_
          [Thu Aug 08 22:53:06.700730 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] resp
          onse = response or self.get_response(request)
          [Thu Aug 08 22:53:06.700784 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] File "
          /var/www/vhosts/appstore/venv/appstore/lib/python3.6/site-packages/django/core/handlers/exception.py", line 36, in in
          ner
          [Thu Aug 08 22:53:06.700830 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] resp
          onse = response_for_exception(request, exc)
          [Thu Aug 08 22:53:06.700878 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] File "
          /var/www/vhosts/appstore/venv/appstore/lib/python3.6/site-packages/django/core/handlers/exception.py", line 90, in re
          sponse_for_exception
          [Thu Aug 08 22:53:06.700924 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] resp
          onse = handle_uncaught_exception(request, get_resolver(get_urlconf()), sys.exc_info())
          [Thu Aug 08 22:53:06.700973 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] File "
          /var/www/vhosts/appstore/venv/appstore/lib/python3.6/site-packages/django/core/handlers/exception.py", line 125, in h
          andle_uncaught_exception
          [Thu Aug 08 22:53:06.701019 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] retu
          rn debug.technical_500_response(request, *exc_info)
          [Thu Aug 08 22:53:06.701068 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] File "
          /var/www/vhosts/appstore/venv/appstore/lib/python3.6/site-packages/django/views/debug.py", line 94, in technical_500_
          response
          [Thu Aug 08 22:53:06.701120 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] html
          = reporter.get_traceback_html()
          [Thu Aug 08 22:53:06.701170 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] File "
          /var/www/vhosts/appstore/venv/appstore/lib/python3.6/site-packages/django/views/debug.py", line 332, in get_traceback
          _html
          [Thu Aug 08 22:53:06.701215 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] t =
          DEBUG_ENGINE.from_string(fh.read())
          [Thu Aug 08 22:53:06.701263 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] File "
          /usr/lib/python3.6/encodings/ascii.py", line 26, in decode
          [Thu Aug 08 22:53:06.701308 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] retu
          rn codecs.ascii_decode(input, self.errors)[0]
          [Thu Aug 08 22:53:06.701364 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823] UnicodeD
          ecodeError: 'ascii' codec can't decode byte 0xe2 in position 9735: ordinal not in range(128)
          [Thu Aug 08 22:53:06.701422 2019] [wsgi:error] [pid 20495:tid 140495602620160] [remote 209.239.128.14:51823]

          This is just a sample.

          This needs to be fixed to avoid filling up the Apache log file with error messages that are not related to the initial exception that triggered all of this.

          See attached.

            Attachments

              Activity

              Hide
              Permalink
              sameer Sameer Shanbhag (Inactive) added a comment -

              Prof. [~aloraine]

              The error log consists of the TraceBack errors which are generated by wsgi as a part of [wsgi:error] module and we do not have control over it.

              Things we have control over:

              1. To stop the print statements to make its way to the error/access logs use the following command in the Apache Config file:

              WSGIRestrictStdout Off

              2. To restrict the error file to avoid warning and info messages but to have 'only' error logs can be done by adding following line to the Apache config:

              LogLevel error

              Info: There are three attributes accepted by LogLevel > info, warning, error | Info Level is the most basic level which shows info + warning + error logs | warning level shows only warning and error logs | error level shows only error logs.

              The error we see above is something we have no control over and it is similar to StackTrace in Java

              Show
              sameer Sameer Shanbhag (Inactive) added a comment - Prof. [~aloraine] The error log consists of the TraceBack errors which are generated by wsgi as a part of [wsgi:error] module and we do not have control over it. Things we have control over: 1. To stop the print statements to make its way to the error/access logs use the following command in the Apache Config file: WSGIRestrictStdout Off 2. To restrict the error file to avoid warning and info messages but to have 'only' error logs can be done by adding following line to the Apache config: LogLevel error Info: There are three attributes accepted by LogLevel > info, warning, error | Info Level is the most basic level which shows info + warning + error logs | warning level shows only warning and error logs | error level shows only error logs. The error we see above is something we have no control over and it is similar to StackTrace in Java

                People

                • Assignee:
                  sameer Sameer Shanbhag (Inactive)
                  Reporter:
                  ann.loraine Ann Loraine
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  2 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: