Closed rfrenchseti closed 1 year ago
fyellin
commented
1 year ago Before I spend too much time on this. I don't have the command line you use to run the error_analyzer report. Is 10.1.10.1 one of the ignored IPs?
I would suspect that all requests for fields.json are generated internally.
rfrenchseti
commented
1 year ago There are no ignored IPs for errors. All occurrences of api/fields.json should be externally-generated, and probably only by the log analyzer.
python error_analyzer.py --ignore-errors-file /opus/src/pds-webserver/opus_servers/cron_files/error_analyzer_ignore_file.txt --cronjob -o "/tmp/error_analyzer_results_temp/%Y-%m/OPUS-error-analysis-%Y-%m-%d.txt" "/Volumes/opus/shared/apache_logs/tools_error_log-%Y-%m-%d" "/Volumes/opus/shared/apache_logs/tools2_error_log-%Y-%m-%d" "/Volumes/opus/shared/apache_logs/tools_access_log-%Y-%m-%d" "/Volumes/opus/shared/apache_logs/tools2_access_log-%Y-%m-%d"error_analyzer_ignore_file.txt:
WARNING [django.request:228] Not Found
WARNING [django.request:228] Bad Request
AH01264: script not found or unable to stat
AH01276: Cannot serve directory
AH00126: Invalid URI in request
AH02042: rejecting client initiated renegotiation
to ALLOWED_HOSTS.Sorry. I didn't quite say what I meant clearly.
Very early in the error analyzer, you mentioned that the error analyzer should only handle errors that came from outside users. It was to ignore errors generated from within SETI because they were most likely you or someone else testing the system. The log analyzer is "inside".
The code specifically has the following line:
# private networks mean a VPN or the local link
if not entry.host_ip.is_private10.1.10.1 is a private address.
I can delete this line. It means you'll see all the errors generated by your testing. But you'll also see these bad errors. I'm not sure how to distinguish them. Confirm that that's what you want.
On Tue, Feb 14, 2023 at 1:00 PM Robert French @.***> wrote:
There are no ignored IPs for errors. All occurrences of api/fields.json should be externally-generated, and probably only by the log analyzer.
python error_analyzer.py --ignore-errors-file /opus/src/pds-webserver/opus_servers/cron_files/error_analyzer_ignore_file.txt --cronjob -o "/tmp/error_analyzer_results_temp/%Y-%m/OPUS-error-analysis-%Y-%m-%d.txt" "/Volumes/opus/shared/apache_logs/tools_error_log-%Y-%m-%d" "/Volumes/opus/shared/apache_logs/tools2_error_log-%Y-%m-%d" "/Volumes/opus/shared/apache_logs/tools_access_log-%Y-%m-%d" "/Volumes/opus/shared/apache_logs/tools2_access_log-%Y-%m-%d"
error_analyzer_ignore_file.txt:
WARNING [django.request:228] Not Found WARNING [django.request:228] Bad Request AH01264: script not found or unable to stat AH01276: Cannot serve directory AH00126: Invalid URI in request AH02042: rejecting client initiated renegotiation to ALLOWED_HOSTS.
— Reply to this email directly, view it on GitHub https://github.com/SETI/pds-opus/issues/1295#issuecomment-1430370582, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABC2LIIRZLUGYDC7CL3HGMLWXPW47ANCNFSM6AAAAAAU34KJEA . You are receiving this because you were assigned.Message ID: @.***>
rfrenchseti
commented
1 year ago Oh, I see. We really don't do that kind of testing anymore. I'd much rather see all the errors.
The following error appears in the apache logs but is missing from the nightly error_analyzer report.
The relevant logs are in DropBox in the
logs-2023-02-14directory.