Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Healthcheck fails after update to 2.20.0 #166

Closed
2 tasks done
kaldevian opened this issue Jan 31, 2023 · 11 comments
Closed
2 tasks done

Healthcheck fails after update to 2.20.0 #166

kaldevian opened this issue Jan 31, 2023 · 11 comments
Assignees
Labels
type:bug Something isn't working

Comments

@kaldevian
Copy link

Is there an existing issue for this?

  • I have searched the existing issues
  • And it has nothing to do with Traefik

Describe the bug

The container stays unhealthy because the healthcheck fails. This seems to be caused by the change

  • Flags --verbose, --debug and --log-json are deprecated, use --log-level and --log-format instead chore: Better CLI #163

since the healthcheck is still

HEALTHCHECK &{["CMD" "/bin/error-pages" "--log-json" "healthcheck"] "7s" "2s" "0s" '\x00'}

Steps to reproduce

No response

Configuration files

No response

Relevant log output

No response

Anything else?

No response

@kaldevian kaldevian added the type:bug Something isn't working label Jan 31, 2023
@tarampampam
Copy link
Owner

How to reproduce it? On my side:

$ docker run --rm ghcr.io/tarampampam/error-pages:2.20.0
Unable to find image 'ghcr.io/tarampampam/error-pages:2.20.0' locally
2.20.0: Pulling from tarampampam/error-pages
8fa9176ffe45: Pull complete 
4f4fb700ef54: Pull complete 
Digest: sha256:47549faeaa41b225312b1bebb3e593f1a29ed02fcdbe175a4eb1e20ec7bd5e9b
Status: Downloaded newer image for ghcr.io/tarampampam/error-pages:2.20.0
{"level":"info","ts":1675193130.0279217,"msg":"We will use the requested template","name":"ghost"}
{"level":"info","ts":1675193130.0280774,"msg":"Server starting","addr":"0.0.0.0","port":8080,"default error page":"404","default HTTP response code":404,"proxy headers":[],"show request details":false,"localization disabled":false}
$ docker ps
CONTAINER ID   IMAGE                                    COMMAND                  CREATED         STATUS                   PORTS     NAMES
f2475bfee335   ghcr.io/tarampampam/error-pages:2.20.0   "/bin/error-pages --…"   2 minutes ago   Up 2 minutes (healthy)             sleepy_moser

All seems ok

@kaldevian
Copy link
Author

kaldevian commented Jan 31, 2023

Strange, i had restarted and also pulled the image to no avail. But after trying again, the healthcheck seems ok. Nevermind, i'll close the issue.

@SAOPP
Copy link

SAOPP commented Feb 2, 2023

Actually I got the same at tag:2 and checked it at tag:latest right now. Unhealthy state. How to reproduce? Just update container :D

Really nothing was chaged by me, just updated, what the additional info u need?

@SAOPP
Copy link

SAOPP commented Feb 2, 2023

image

@tarampampam
Copy link
Owner

How do you update, where, and what commands should I execute to reproduce the behavior?

@SAOPP
Copy link

SAOPP commented Feb 3, 2023

Get da latest container and recreate it. I dunno what I need to add more. And I as see this issue is not mine only.

@tarampampam
Copy link
Owner

@SAOPP I mean how to reproduce it locally? Which commands I should run to see the failed health check?

@SAOPP
Copy link

SAOPP commented Feb 5, 2023

I don't have this info, cause I've updated my container and saw after several days that it unhealthy and error pages didn't work. It's all what I have homie.

@tarampampam
Copy link
Owner

Maybe you have overridden the healcheck command somewhere? Without context and examples helping is very difficult

@SAOPP
Copy link

SAOPP commented Feb 5, 2023

Incorrect Usage: flag provided but not defined: -log-json NAME: error-pages healthcheck - Health checker for the HTTP server. Use case - docker healthcheck USAGE: error-pages healthcheck command [command options] [arguments...] COMMANDS: help, h Shows a list of commands or help for one command OPTIONS: --port value, -p value TCP port number (default: 8080) [$LISTEN_PORT] --help, -h show help flag provided but not defined: -log-json

@SAOPP
Copy link

SAOPP commented Feb 6, 2023

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants