Log keep spam 127.0.0.1 "GET /" 200 2996 "" "Wget"

[propserer]

My homer docker container log keep spamming with
1633369746 127.0.0.1 "GET /" 200 2996 "" "Wget"

here my compose file look like

version: "2"
services:

homer:
        ports:
            - "7000:8080"
        environment:
            - UID=${PUID}
            - GID=${PGID}
        volumes:
            - ${AppData}/homer:/www/assets
        restart: unless-stopped
        image: b4bz/homer:latest
        container_name: homer

Test with raspberry pi and on my linux mint machine both spamming the log with the same 127.0.0.1 "GET /" 200 2996 "" "Wget"
when i check glances and ctop it cause cpu spike

[sargonas]

same, I was wondering about this as well as I notice it on my docker container as well, when I glanced at my Greylog server and saw it full of them.

I thought this might be related to the service-up monitoring feature, but i disabled it via the config already... unless that's not being respected? (connectivityCheck: false)

[fbartels]

Its not the connectivity check from homer itself, but the container healthcheck that is the source of these. See

homer/Dockerfile

Lines 28 to 29 in 451b1ac

	HEALTHCHECK --interval=5s --timeout=5s --retries=3 \
	CMD wget --no-verbose --tries=1 --spider http://127.0.0.1:${PORT}/ || exit 1

[sargonas]

Ahhhh that makes sense, thanks! Knowing that I might just over-ride the intervals i the compose file, or maybe just disabled it entirely... I have other monitoring services in place anyways.

[fbartels]

Yes, a 5 second interval for the health check seems quite excessive.

[propserer]

Ahhhh that makes sense, thanks! Knowing that I might just over-ride the intervals i the compose file, or maybe just disabled it entirely... I have other monitoring services in place anyways.

How can i disable the health check?

[sargonas]

You can override the health check parameters defined inside the container by simply adding them to your startup command or compose file. For the compose file, you have 6 options you can set, with any omitted being loaded from the image and the disable overriding everything to turn it off.

healthcheck:
  test: [actual test commands go here]
  interval: 1m1s
  timeout: 1s
  retries: 1
  start_period: 2s
  disable: true

In the case of this container, I just added the following to kill it entirely for now until I take time to rethink how I want it to run long term:

healthcheck:
  disable: true

[propserer]

You can override the health check parameters defined inside the container by simply adding them to your startup command or compose file. For the compose file, you have 6 options you can set, with any omitted being loaded from the image and the disable overriding everything to turn it off.

healthcheck:
  test: [actual test commands go here]
  interval: 1m1s
  timeout: 1s
  retries: 1
  start_period: 2s
  disable: true

In the case of this container, I just added the following to kill it entirely for now until I take time to rethink how I want it to run long term:

healthcheck:
  disable: true

Thank you very much

[bastienwirtz]

Hi there!
I'm glad you found a solution.
@fbartels good remark, I just tuned it down a bit !

[baumheld]

I'd like to have the healthcheck enabled AND have no wget log messages. Is that possible?
These messages are spamming my Grafana Logs

homer  | 127.0.0.1 127.0.0.1:8080 - [16/Mar/2025:15:30:15 +0100] "GET / HTTP/1.1" 200 775 "-" "Wget"
homer  | 127.0.0.1 127.0.0.1:8080 - [16/Mar/2025:15:30:42 +0100] "GET / HTTP/1.1" 200 775 "-" "Wget

[bastienwirtz]

@baumheld requests from 127.0.0.1 are now filtered out, no more healthcheck spamming! Thanks for your message!