Closed bradsk88 closed 3 years ago
MQTT (NodeRed) settings
ozwdaemon settings
overview
[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] ozw-logs: applying... [fix-attrs.d] ozw-logs: exited 0. [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] ozw-logs: executing... [cont-init.d] ozw-logs: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. [ozwdaemon]: Setting Up..... [novnc]: Executing: /usr/local/bin/websockify --web /opt/novnc/ 7800 127.0.0.1:5901 [ozwadmin]: /usr/local/bin/ozwadmin -platform vnc:port=5901 -c /opt/ozw/config/ -u /opt/ozw/config/ [ozwdaemon]: [ozwdaemon]: ======================================================================== [ozwdaemon]: Detailed Logging is available in the logs directory of the mapped volume [ozwdaemon]: ======================================================================== [ozwdaemon]: [ozwdaemon]: Waiting until the MQTT broker at 192.168.1.124:1883 is available... [ozwdaemon]: Starting... [ozwdaemon]: Executing: /usr/local/bin/ozwdaemon [ozwdaemon]: Exited with Status Code 253 [ozwdaemon]: Shutting Down Container [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] waiting for services. [s6-finish] sending all processes the TERM signal.
I'm not getting a ton from these logs. Not sure what Code 253 refers to. Sometimes I get Code 256 as well.
This was my fault. I mistakenly assumed NodeRed was an MQTT server but it's actually just a visualization program. I needed to install MQTT (available in the CA).
Now everything is working
MQTT (NodeRed) settings
ozwdaemon settings
overview
I'm not getting a ton from these logs. Not sure what Code 253 refers to. Sometimes I get Code 256 as well.