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

CKAN exit code 0 even when it crashes #4514

Open
frafra opened this issue Oct 22, 2018 · 2 comments
Open

CKAN exit code 0 even when it crashes #4514

frafra opened this issue Oct 22, 2018 · 2 comments
Assignees

Comments

@frafra
Copy link
Contributor

frafra commented Oct 22, 2018

CKAN Version if known (or site URL)

2.8.1, launched with docker-compose.yml

Please describe the expected behavior

When CKAN crashes, an exit code greater than 0 should be returned.

Please describe the actual behavior

CKAN returns 0, so the container is not marked as failed and restart: on-failed does not work as expected.

What steps can be taken to reproduce the issue?

  1. Add --reload to CMD
  2. docker-compose up
  3. Overwrite a file to restart CKAN
@frafra frafra changed the title CKAN exit code 0 even when crashes CKAN exit code 0 even when it crashes Oct 22, 2018
@amercader amercader self-assigned this Oct 23, 2018
@amercader
Copy link
Member

Can you provide more details about what command exactly is failing? It might be the paster development server which is returning this error.

Also if CKAN is crashing won't it crash again the next time the container is restarted?

@frafra
Copy link
Contributor Author

frafra commented Oct 23, 2018

Can you provide more details about what command exactly is failing? It might be the paster development server which is returning this error.

Sure; it is paster indeed, as I am using the Dockerfile provided by ckan.

Also if CKAN is crashing won't it crash again the next time the container is restarted?

It could, if it is not a temporary issue, as any other container which have issues (Docker automatically add delays between restarts if the container keeps failing). There is still a difference between a stopped container (exit code 0) and one that has errors (exit code >0). Having more information about the status of the CKAN container could both help monitoring and development (at least in my case, where I want ckan to restart after a bad crash).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants