|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
|
|
16 May 2023, Konstantin Olchanski, Bug Report, excessive logging of http requests
|
16 May 2023, Konstantin Olchanski, Bug Report, excessive logging of http requests
|
16 May 2023, Stefan Ritt, Bug Report, excessive logging of http requests
|
02 Aug 2023, Konstantin Olchanski, Bug Report, excessive logging of http requests
|
03 Aug 2023, Konstantin Olchanski, Bug Report, excessive logging of http requests
|
14 Aug 2023, Konstantin Olchanski, Bug Report, excessive logging of http requests
|
16 Aug 2023, Konstantin Olchanski, Bug Report, excessive logging of http requests
|
17 Aug 2023, Konstantin Olchanski, Bug Report, excessive logging of http requests
|
|
Message ID: 2516
Entry time: 16 May 2023
Reply to this: 2517
|
Author: |
Konstantin Olchanski |
Topic: |
Bug Report |
Subject: |
excessive logging of http requests |
|
|
Our default configuration of apache httpd logs every request. MIDAS custom web pages can easily make a huge number of RPC calls creating a
huge log file and filling system disk to 100% capacity
this example has around 100 RPC requests per second. reasonable/unreasonable? available hardware can handle it (web browser, network
httpd, mhttpd, etc), so we should try to get this to work. perhaps filter the apache httpd logs to exclude mjsonrpc requests? of course we
can ask the affected experiment why they make so many RPC calls, is there a bug?
[14/May/2023:03:49:01 -0700] 142.90.111.176 TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 "POST /?mjsonrpc HTTP/1.1" 299
[14/May/2023:03:49:01 -0700] 142.90.111.176 TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 "POST /?mjsonrpc HTTP/1.1" 299
[14/May/2023:03:49:01 -0700] 142.90.111.176 TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 "POST /?mjsonrpc HTTP/1.1" 299
[14/May/2023:03:49:01 -0700] 142.90.111.176 TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 "POST /?mjsonrpc HTTP/1.1" 299
[14/May/2023:03:49:01 -0700] 142.90.111.176 TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384 "POST /?mjsonrpc HTTP/1.1" 299
K.O. |