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

Log viewer does not start #158

Open
hartmood opened this issue Apr 2, 2023 · 1 comment
Open

Log viewer does not start #158

hartmood opened this issue Apr 2, 2023 · 1 comment

Comments

@hartmood
Copy link

hartmood commented Apr 2, 2023

Problem/Motivation

(Why the issue was filed)

Add on does not start on a raspi 4. Error message from the sidebar: “add-on is not running. Please start first”

s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun logviewer (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
s6-rc: info: service legacy-services successfully started
[22:48:36] INFO: Starting Log Viewer...
[22:48:37] INFO: Starting NGINX...
2023-04-02T20:48:37.308Z logview:debug start tailing /config/home-assistant.log
2023-04-02T20:48:37.325Z logview:info listening on port 4277 (HTTP)

Expected behavior

(What you expected to happen)

Start of the add on

Actual behavior

(What actually happened)

add on fails to start

Steps to reproduce

(How can someone else make/see it happen)

Uninstalled and reinstalled. As well as several restarts.

Proposed changes

(If you have a proposed change, workaround or fix,
describe the rationale behind it)

@Zynth-dev
Copy link

Zynth-dev commented Jun 18, 2023

Same issue here.
Running on Intel NUC.

Update: solved by a reboot. Restarting home assistant was not good enough.

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