Caddy healthcheck is flooding log files with "stream copy error"s

[dhlavaty]

Healtcheck at

seafile-admin-docs/manual/repo/docker/caddy.yml

Lines 17 to 22 in a8c9dcf

	healthcheck:
	test: ["CMD-SHELL", "curl --fail http://localhost:2019/metrics || exit 1"]
	start_period: 20s
	interval: 20s
	timeout: 5s
	retries: 3

is flooding log files with stream copy error every 20 seconds.

I followed official docs to run Seafile on my raspberry pi 5 running Debian GNU/Linux 12 (bookworm).

Nevertheless, the whole Seafile works properly.

I only found this healthcheck mentioned here in https://github.com/haiwen/seafile-admin-docs/ project, so I'm opening this issue here.

Example:

Jan 31 10:49:03 rpi5 dockerd[846]: time="2025-01-31T10:49:03.263113426+01:00" level=warning msg="Health check for container 68150f06ac84b4e5d48f9>
Jan 31 10:49:23 rpi5 dockerd[846]: time="2025-01-31T10:49:23.329812669+01:00" level=error msg="stream copy error: reading from a closed fifo"
Jan 31 10:49:23 rpi5 dockerd[846]: time="2025-01-31T10:49:23.329828521+01:00" level=error msg="stream copy error: reading from a closed fifo"
Jan 31 10:49:23 rpi5 dockerd[846]: time="2025-01-31T10:49:23.331945323+01:00" level=warning msg="Health check for container 68150f06ac84b4e5d48f9>
Jan 31 10:49:43 rpi5 dockerd[846]: time="2025-01-31T10:49:43.419218442+01:00" level=error msg="stream copy error: reading from a closed fifo"
Jan 31 10:49:43 rpi5 dockerd[846]: time="2025-01-31T10:49:43.419218461+01:00" level=error msg="stream copy error: reading from a closed fifo"
Jan 31 10:49:43 rpi5 dockerd[846]: time="2025-01-31T10:49:43.421551467+01:00" level=warning msg="Health check for container 68150f06ac84b4e5d48f9>
Jan 31 10:50:03 rpi5 dockerd[846]: time="2025-01-31T10:50:03.486763327+01:00" level=error msg="stream copy error: reading from a closed fifo"
Jan 31 10:50:03 rpi5 dockerd[846]: time="2025-01-31T10:50:03.486793346+01:00" level=error msg="stream copy error: reading from a closed fifo"
Jan 31 10:50:03 rpi5 dockerd[846]: time="2025-01-31T10:50:03.489752502+01:00" level=warning msg="Health check for container 68150f06ac84b4e5d48f9>
Jan 31 10:50:23 rpi5 dockerd[846]: time="2025-01-31T10:50:23.567312512+01:00" level=error msg="stream copy error: reading from a closed fifo"
Jan 31 10:50:23 rpi5 dockerd[846]: time="2025-01-31T10:50:23.567424494+01:00" level=error msg="stream copy error: reading from a closed fifo"
Jan 31 10:50:23 rpi5 dockerd[846]: time="2025-01-31T10:50:23.570884077+01:00" level=warning msg="Health check for container 68150f06ac84b4e5d48f9>
Jan

[wacmkxiaoyi]

Hello Dhlavaty,

Did you restart the dockered service or reboot your machine? We have tested the Caddy service by the newest deployment approach on the official docs, and we can’t get a problem like your post.

This problem seems related to the low-level communicator of dockered service, if you still have problem about the health-check and Caddy service can’t be started, you can remove or note the whole healthcheck subsection in caddy service.

Good luck,