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

Help - update caused container state = unhealthy #480

Closed
DSew20 opened this issue Jul 1, 2022 · 3 comments
Closed

Help - update caused container state = unhealthy #480

DSew20 opened this issue Jul 1, 2022 · 3 comments

Comments

@DSew20
Copy link

DSew20 commented Jul 1, 2022

Hello,

I updated homer via iotstack, and it no longer starts. I get a state = unhealthy, and the following in the log. Any idea what could have caused this and any fixes?

4147-08-20 07:32:16: (server.c.1568) server started (lighttpd/1.4.64)
4147-08-20 07:32:16: (server.c.263) warning: clock jumped -68719476736 secs
4147-08-20 07:32:16: (server.c.271) attempting graceful restart in < ~5 seconds, else hard restart
1970-01-01 00:00:00: (server.c.1011) [note] graceful shutdown started
1970-01-01 00:00:00: (server.c.2077) server stopped by UID = 1000 PID = 12

Thank you

@theandychung
Copy link

This works for me:

Update your assets directory permissions (ex: chown -R 1000:1000 /your/assets/folder/, chmod -R u+rw /your/assets/folder/)

Source:
https://github.com/bastienwirtz/homer/blob/main/docs/troubleshooting.md#my-docker-container-refuse-to-start--is-stuck-at-restarting

@bastienwirtz
Copy link
Owner

Hi @DSew20,

Which version did you try ? This issue has been fixed in the latest release.

Let me know if that works for you!

@bastienwirtz
Copy link
Owner

I'm closing this one as it should be all good now.

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

3 participants