[BUG] log spammed with "Server ready"

[nvanggaard]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When the container is running it keeps spamming the log with "Server ready"

Expected Behavior

I would expect it to write "Server ready" once

Steps To Reproduce

Start the container

Environment

- OS: 6.5.3-arch1-1 #1 SMP PREEMPT_DYNAMIC Wed, 13 Sep 2023 08:37:40 +0000 x86_64 GNU/Linux
- How docker service was installed: 
pacman -S docker docker-compose

CPU architecture

x86-64

Docker creation

swag:
    image: linuxserver/swag
    container_name: swag
    cap_add:
      - NET_ADMIN
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Copenhagen
      - URL=xxxxxxxxxx.xyz
      - SUBDOMAINS=xxxxxxxxxxxxxx
      - VALIDATION=http
      - DHLEVEL=2048 #optional
      - ONLY_SUBDOMAINS=false  #optional
      - STAGING=false #optional
    volumes:
      - ./config/nginx/:/config
    restart: unless-stopped
    depends_on:
      - 'homeassistant'
    ports:
      - 10.10.20.4:443:443
      - 10.10.20.4:80:80 # Set for new certificates
    networks:
      front:
        ipv4_address: 172.23.0.2

Container logs

| 2023-09-23T17:31:08.954558639Z Server ready
swag           | 2023-09-23T17:31:10.127008235Z Server ready
swag           | 2023-09-23T17:31:11.296889725Z Server ready
swag           | 2023-09-23T17:31:12.466333144Z Server ready
swag           | 2023-09-23T17:31:13.636906824Z Server ready
swag           | 2023-09-23T17:31:14.807398192Z Server ready
swag           | 2023-09-23T17:31:15.977911911Z Server ready
swag           | 2023-09-23T17:31:17.151067041Z Server ready
swag           | 2023-09-23T17:31:18.319157722Z Server ready
swag           | 2023-09-23T17:31:19.491462412Z Server ready
swag           | 2023-09-23T17:31:20.664287243Z Server ready
swag           | 2023-09-23T17:31:21.835244647Z Server ready
swag           | 2023-09-23T17:31:23.009271810Z Server ready
swag           | 2023-09-23T17:31:24.180618489Z Server ready
swag           | 2023-09-23T17:31:25.353483211Z Server ready
swag           | 2023-09-23T17:31:26.525194625Z Server ready
swag           | 2023-09-23T17:31:27.695474521Z Server ready
swag           | 2023-09-23T17:31:28.866420700Z Server ready
swag           | 2023-09-23T17:31:30.039590139Z Server ready
swag           | 2023-09-23T17:31:31.209198706Z Server ready
swag           | 2023-09-23T17:31:32.381385224Z Server ready
swag           | 2023-09-23T17:31:33.552893144Z Server ready
swag           | 2023-09-23T17:31:34.730577675Z Server ready
swag           | 2023-09-23T17:31:35.903480201Z Server ready
swag           | 2023-09-23T17:31:37.074955471Z Server ready
swag           | 2023-09-23T17:31:38.244508477Z Server ready
swag           | 2023-09-23T17:31:39.416430656Z Server ready
swag           | 2023-09-23T17:31:40.596050158Z Server ready
swag           | 2023-09-23T17:31:41.767130126Z Server ready
swag           | 2023-09-23T17:31:42.935645466Z Server ready
swag           | 2023-09-23T17:31:44.107152812Z Server ready

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[Roxedus]

post a full startup log, it seems like the nginx process might be crashing

[nemchik]

Also possibly outdated fail2ban conf. There was a plex regex that caused issues that has since been removed. #375

[adamaen87]

Hi, check your fail2ban logs, just had the same problem few days ago, it was a jail with the wrong log path the problem (made some change on a docker and forgot to modify the corresponding fail2ban).

[nvanggaard]

Sorry i forgot to return.
As i haven't made any change to fail2ban, i just simply removed the folder, and it was recreated. How I do not get a lot of "server ready" logs (and my fail2ban log does explode as well)