-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
supervisord-watchdog (exit status 1; not expected) #114
Comments
What version are you running? |
The latest docker all in one. It was working fine yesterday then this morning it stopped. Tried restart and reboot.
… On Jun 22, 2020, at 4:06 PM, Justin Hammond ***@***.***> wrote:
What version are you running?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub <#114 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAKYR65GLPOIOMXYAZ3IMTDRX7BUDANCNFSM4OETTZ2Q>.
|
I installed "latest" today and it was 3 days behind, I now am running 145 and this error/issue went away. |
I'm having the same warning in my logs too. I've only just tried to set this up with docker-compose last night, and it's all I get.
It seems to be starting everything, and after a couple seconds ozwdaemon crashes, is relaunched and crashes again, and repeats once more at which point docker gives up because of how quickly it was looping. When I vnc in, I also can't access the remote panel like @trebolcinco, it also just gives me "Connection Refused". Running on a Raspberry Pi 3, fully up to date Raspbian (per apt-get update). HomeAssistant is on a second Raspberry Pi on the network, not on the same hardware. @trebolcinco, when you launch the docker in the terminal, do you get the ozwdaemon process exiting as well before the supervisord-watchdog starts quiting on you too? If not, my issue is probably different and I'll open a separate issue |
I've just updated the docker to the latest -allinone image, 154. Is there anything I can do to get more information to help identify a cause for this? |
I, too, am experiencing this stack trace with the |
If your architecture is amd64, then Providing all of log files would be more helpful. |
@kpine I mentioned I'm getting the same stack trace as @FreelancerJay when viewing the logs of the container – where would I find application logs? |
There is a logs directory, default location would be in the config directory. |
Also, allinone builds > 150 are known to be broken (at least use of ozwadmin, what else?) because of changes in the QT5 version. A fix is in the works. |
@kpine Here are my logs from a clean run of |
to anyone not aware: using the ozw-admin client on your desktop is a work around for the time being. |
@bachya Your ozwdaemon.log is showing problems with MQTT.
If ozwd disconnects from the broker it will restart, which seems to be happening here. Not sure if it will help or not, but you could try increasing the log levels, via a container environment variable:
|
Here's what I see, in comparison:
|
@kpine What MQTT broker do you use? I use VerneMQ with several clients and it works great. That EDIT: user error. 🤦 I wasn't using the name of my MQTT container as the hostname. Everything working now; I still think I'm encountering the QT5 issue over VNC (disconnects suddenly), so I'll wait for new versions to test again. |
I'm using mosquitto.
😆 Most of us have done that at some point... Some better logging of connection errors might be useful. |
ozwdaemon is now logging as much info as we can get about connection failures, but its not a lot on the MQTT side unfortunately. I've added some additional logging when ozwdaemon exits about its failure and a message to "read the log files" about why it failed that hopefully will help some what. |
This morning I started receiving this WARN: "supervisord-watchdog (exit status 1; not expected)". It was preceded by: INFO " supervisord-watchdog: event was rejected". I can access the admin panel but when I try to Open the Remote Daemon it says: "Connection Refused". I tried rebooting and restarting docker, neither helped.
The text was updated successfully, but these errors were encountered: