log file is huge

__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.

1. ...Install InfluxDB in Mac OS
2. ...
3. ...

__Expected behavior:__
Describe what you expected to happen.

__Actual behavior:__
Describe What actually happened.
the log file increase its size up to 300 Gb in just one day. the file is located on
/usr/local/var/log/influxdb2/influxd_output.log
__Environment info:__
Mac iOS
* System info: Run `uname -srm` and copy the output here
* Darwin 21.5.0 x86_64
* InfluxDB version: Run `influxd version` and copy the output here
* InfluxDB 2.3.0 (git: 090f681737) build_date: 2022-06-16T18:48:06Z

This also happens with previous version 2.2.
* Other relevant environment details: Container runtime, disk info, etc

__Config:__
Copy any non-default config values here or attach the full config as a gist or file.
standard configuration

ls -l /usr/local/var/log/influxdb2/influxd_output.log
-rw-r--r-- joe admin 344053583798 Jul 30 10:43 /usr/local/var/log/influxdb2/influxd_output.log

__Logs:__
Include snippet of errors in log.

__Performance:__
Generate profiles with the following commands for bugs related to performance, locking, out of memory (OOM), etc.

```sh
# Commands should be run when the bug is actively happening.
# Note: This command will run for ~30 seconds.
curl -o profiles.tar.gz "http://localhost:8086/debug/pprof/all?cpu=30s"
iostat -xd 1 30 > iostat.txt
# Attach the `profiles.tar.gz` and `iostat.txt` output files.
```

Start by reviewing the reported log path, InfluxDB 2.3.0 environment details, and standard configuration. Reproduce the rapid growth if possible, using the provided profiling commands while it occurs; done means identifying why the log reaches 300 GB per day and verifying that it no longer grows abnormally.

Written by the indexing model from the issue text.