frenck
commented
3 years ago Please provide startup logs
Closed lsilva171 closed 3 years ago
frenck
commented
3 years ago Please provide startup logs
lsilva171
commented
3 years ago Hi,
Here it is. An v0.8.2 image was restored from a previous backup and upgraded to v0.8.3
This allowed me to get rid of several errors regarding missing modules and also allowed me have the necessary settings in place.
You can see, at the bottom, the PANIC error messages created when I tried to access the Web UI.
[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] done.,
[cont-init.d] executing container initialization scripts...,
[cont-init.d] 00-banner.sh: executing... ,
-----------------------------------------------------------,
Add-on: Z-Wave to MQTT,
Fully configurable Z-Wave to MQTT gateway and control panel,
-----------------------------------------------------------,
Add-on version: 0.8.3,
You are running the latest version of this add-on.,
System: HassOS 5.5 (aarch64 / odroid-c4),
Home Assistant Core: 0.118.5,
Home Assistant Supervisor: 2020.12.6,
-----------------------------------------------------------,
Please, share the above information when looking for help,
or support in, e.g., GitHub, forums or the Discord chat.,
-----------------------------------------------------------,
[cont-init.d] 00-banner.sh: exited 0.,
[cont-init.d] 01-log-level.sh: executing... ,
[cont-init.d] 01-log-level.sh: exited 0.,
[cont-init.d] nginx.sh: executing... ,
[cont-init.d] nginx.sh: exited 0.,
[cont-init.d] zwave2mqtt.sh: executing... ,
[cont-init.d] zwave2mqtt.sh: exited 0.,
[cont-init.d] done.,
[services.d] starting services,
[services.d] done.,
[00:35:02] INFO: Starting the Z-Wave to MQTT...,
2020-12-11T05:35:03.368Z z2m:Store scenes.json not found,
2020-12-11T05:35:04.674Z z2m:App Zwave2Mqtt version: 4.0.6,
2020-12-11T05:35:04.676Z z2m:App Application path:/opt,
Initialising OpenZWave 1.6.974 binary addon for Node.JS.,
OpenZWave Security API is ENABLED,
ZWave device db : /etc/openzwave,
User settings path : /opt/store,
Option Overrides : --Logging undefined --ConsoleOutput undefined --QueueLogLevel 6 --DriverMaxAttempts 9999 --SaveConfiguration true --PollInterval 10000 --AutoUpdateConfigFile true --NetworkKey
lsilva171
commented
3 years ago And here a trace log from a brand new v0.8.3 instance created from scratch, instead of using a snapshot as I did above.
[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] done., [cont-init.d] executing container initialization scripts..., [cont-init.d] 00-banner.sh: executing... , -----------------------------------------------------------, Add-on: Z-Wave to MQTT, Fully configurable Z-Wave to MQTT gateway and control panel, -----------------------------------------------------------, Add-on version: 0.8.3, You are running the latest version of this add-on., System: HassOS 5.5 (aarch64 / odroid-c4), Home Assistant Core: 0.118.5, Home Assistant Supervisor: 2020.12.6, -----------------------------------------------------------, Please, share the above information when looking for help, or support in, e.g., GitHub, forums or the Discord chat., -----------------------------------------------------------, [cont-init.d] 00-banner.sh: exited 0., [cont-init.d] 01-log-level.sh: executing... , Log level is set to TRACE, [cont-init.d] 01-log-level.sh: exited 0., [cont-init.d] nginx.sh: executing... , [00:01:50] TRACE: bashio::config.true: ssl, [00:01:50] TRACE: bashio::config: ssl, [00:01:50] TRACE: bashio::jq: /data/options.json if (.ssl == null) then, null, elif (.ssl | type == "string") then, .ssl // empty, elif (.ssl | type == "boolean") then, .ssl // false, elif (.ssl | type == "array") then, if (.ssl == []) then, empty, else, .ssl[], end, elif (.ssl | type == "object") then, if (.ssl == {}) then, empty, else, .ssl, end, else, .ssl, end, [00:01:50] TRACE: bashio::var.true: false, [00:01:50] TRACE: bashio::config.true: ssl, [00:01:50] TRACE: bashio::config: ssl, [00:01:50] TRACE: bashio::jq: /data/options.json if (.ssl == null) then, null, elif (.ssl | type == "string") then, .ssl // empty, elif (.ssl | type == "boolean") then, .ssl // false, elif (.ssl | type == "array") then, if (.ssl == []) then, empty, else, .ssl[], end, elif (.ssl | type == "object") then, if (.ssl == {}) then, empty, else, .ssl, end, else, .ssl, end, [00:01:51] TRACE: bashio::var.true: false, [00:01:51] TRACE: bashio::dns.host, [00:01:51] TRACE: bashio::dns dns.info.host .host, [00:01:51] TRACE: bashio::cache.exists: dns.info.host, [00:01:51] TRACE: bashio::fs.file_exists: /dev/shm/bashio/dns.info.host.cache, [00:01:51] TRACE: bashio::cache.exists: dns.info, [00:01:51] TRACE: bashio::fs.file_exists: /dev/shm/bashio/dns.info.cache, [00:01:51] TRACE: bashio::api.supervisor GET /dns/info false, [00:01:51] DEBUG: Requested API resource: http://supervisor/dns/info, [00:01:51] DEBUG: Request method: GET, [00:01:51] DEBUG: Request data: {}, [00:01:51] DEBUG: API HTTP Response code: 200, [00:01:51] DEBUG: API Response: {"result": "ok", "data": {"version": "2020.11.0", "version_latest": "2020.11.0", "update_available": false, "host": "172.30.32.3", "servers": [], "locals": ["dns://10.0.0.1"]}}, [00:01:51] TRACE: bashio::jq: {"result": "ok", "data": {"version": "2020.11.0", "version_latest": "2020.11.0", "update_available": false, "host": "172.30.32.3", "servers": [], "locals": ["dns://10.0.0.1"]}}, .result, [00:01:51] TRACE: bashio::var.true: false, [00:01:51] TRACE: bashio::jq: {"result": "ok", "data": {"version": "2020.11.0", "version_latest": "2020.11.0", "update_available": false, "host": "172.30.32.3", "servers": [], "locals": ["dns://10.0.0.1"]}}, if .data == {} then empty else .data end, [00:01:51] TRACE: bashio::var.has_value: , [00:01:51] TRACE: bashio::cache.set: dns.info {"version":"2020.11.0","version_latest":"2020.11.0","update_available":false,"host":"172.30.32.3","servers":[],"locals":["dns://10.0.0.1"]}, [00:01:51] TRACE: bashio::fs.directory_exists: /dev/shm/bashio, [00:01:51] TRACE: bashio::var.has_value: .host, [00:01:51] TRACE: bashio::jq: {"version":"2020.11.0","version_latest":"2020.11.0","update_available":false,"host":"172.30.32.3","servers":[],"locals":["dns://10.0.0.1"]} .host, [00:01:52] TRACE: bashio::cache.set: dns.info.host 172.30.32.3, [00:01:52] TRACE: bashio::fs.directory_exists: /dev/shm/bashio, [cont-init.d] nginx.sh: exited 0., [cont-init.d] zwave2mqtt.sh: executing... , [cont-init.d] zwave2mqtt.sh: exited 0., [cont-init.d] done., [services.d] starting services, [services.d] done., [00:01:52] TRACE: bashio::net.wait_for 44920, [00:01:52] INFO: Starting the Z-Wave to MQTT..., 2020-12-11T05:01:53.151Z z2m:Store settings.json not found, 2020-12-11T05:01:53.175Z z2m:Store scenes.json not found, 2020-12-11T05:01:53.177Z z2m:Store nodes.json not found, 2020-12-11T05:01:54.436Z z2m:App Zwave2Mqtt version: 4.0.6, 2020-12-11T05:01:54.437Z z2m:App Application path:/opt, 2020-12-11T05:01:54.621Z z2m:Gateway Zwave settings are not valid, 2020-12-11T05:01:54.877Z z2m:App Listening on port 44920, [00:01:55] INFO: Starting NGinx..., [00:01:55] TRACE: bashio::config.true: leave_front_door_open, [00:01:55] TRACE: bashio::config: leave_front_door_open, [00:01:55] TRACE: bashio::jq: /data/options.json if (.leave_front_door_open == null) then, null, elif (.leave_front_door_open | type == "string") then, .leave_front_door_open // empty, elif (.leave_front_door_open | type == "boolean") then, .leave_front_door_open // false, elif (.leave_front_door_open | type == "array") then, if (.leave_front_door_open == []) then, empty, else, .leave_front_door_open[], end, elif (.leave_front_door_open | type == "object") then, if (.leave_front_door_open == {}) then, empty, else, .leave_front_door_open, end, else, .leave_front_door_open, end, [00:01:55] TRACE: bashio::var.true: null, nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html), PANIC: unprotected error in call to Lua API (bad light userdata pointer), PANIC: unprotected error in call to Lua API (bad light userdata pointer),
lsilva171
commented
3 years ago My current Home Assistant environment is:
System Health
Home Assistant Core Integration
version: 0.118.5 installation_type: Home Assistant OS dev: false hassio: true docker: true virtualenv: false python_version: 3.8.6 os_name: Linux os_version: 5.9.6 arch: aarch64 timezone: America/Toronto
Home Assistant Cloud
logged_in: true subscription_expiration: December 25, 2020, 7:00 PM relayer_connected: true remote_enabled: false remote_connected: false alexa_enabled: true google_enabled: true can_reach_cert_server: ok can_reach_cloud_auth: ok can_reach_cloud: undefined
Hass.io
host_os: HassOS 5.5 update_channel: stable supervisor_version: 2020.12.6 docker_version: 19.03.12 disk_total: 28.0 GB disk_used: 5.4 GB healthy: true supported: true board: odroid-c4 supervisor_api: ok version_api: ok installed_addons: Samba share (9.3.0), MariaDB (2.2.1), ADB - Android Debug Bridge (0.6.3), Glances (0.9.1), Mosquitto broker (5.1), Network UPS Tools (0.3.1), AirCast (2.4.1), AppDaemon 4 (0.3.2), Check Home Assistant configuration (3.6.0), Portainer (1.3.0), TasmoAdmin (0.13.1), Zigbee2mqtt (1.16.2.2), Ring Livestream (1.35), Z-Wave to MQTT (0.8.3)
Lovelace
dashboards: 2 mode: auto-gen resources: 5
lsilva171
commented
3 years ago Any news about this issue?
frenck
commented
3 years ago No, or you would have seen an response.
smithdo
commented
3 years ago Is there a way to install 0.8.2 as a workaround until this can be addressed?
smithdo
commented
3 years ago Also tried turning off ssl by setting it to false and it did not work, still get the SSL error on the page and look in the log and still has a panic message
Problem/Motivation
Running Home Assistant on Odroid C4 with Z-Wave to MQTT v0.8.3 and when trying to open the Web UI, it fails with an ERR_EMPTY_RESPONSE error
Expected behavior
Z-Wave to MQTT Web UI to show web page
Actual behavior
It opens a new tab in the web browser and shows an ERR_EMPTY_RESPONSE error.
Generates "PANIC: unprotected error in call to Lua API (bad light userdata pointer)" message in the log.
There is no additional information generated in any other log levels.
Steps to reproduce
Proposed changes