-
-
Notifications
You must be signed in to change notification settings - Fork 206
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
[bug] zwavejs 5.0.0 doesn't run #1326
Comments
@robertsLando Maybe it's the same issue. I did a container recreate to update to release 5.00. After that upgrade the containers starts successful but ZwaveJs2Mqtt isn't running. I saw the following error in de log in the Docker container `Error: Cannot find module '/usr/src/app/bin/www'
code: 'MODULE_NOT_FOUND', requireStack: [] } node:internal/modules/cjs/loader:927 throw err; ^ |
@RualdOrdelman Could you try to remove the container, drop the local z2m image and pull a fresh new one using latest tag? |
@yajrendrag Please show me all the steps you are doing to run z2m. I think you may have forgot to run |
i am running a package version. i simply unzip it - it overwrites the bindings.node and zwavejs2mqtt executable, then i start with systemctl. (see initial post additional context section for my systemd unit file). BTW, i do have a 2nd instance that i run in docker and that one runs fine (& i updated that one like you suggest avboce - removing container, dropping the image and then pull a new one with latest tag). |
tried the fix - still doesn't work... different error message now: log file content after installing release 5.01:
systemctl status message:
|
@yajrendrag Could you please share the complete log output of the service? |
sure, but need a little help understanding what you mean by "complete log output" - are you looking for store/zwavejs_[date].log or something else/additional? if just that file, then above output was the complete output in the logfile after upgrading, but am happy to do it again... there are other log files in the store directory, but am thinking some may be old... as well as additional content in syslog.. |
Actually also the outupt you attached in your previous command is trimmed. I mean |
ok, will be back in front of it in about 6 hours from now and will send then.. |
ok, here's a shell session which should show everything you're looking for...
There are a couple of lines in syslog from the same time as the systemctl status command - that don't appear in the output of systemctl status - here's the full list from syslog - it's the 1st 8 lines that don't appear in the systemctl status command:
|
@yajrendrag Ok so this is a problem with serialport binidings, we are speaking about it with serialport authors. BTW did you also try with 5.0.2? |
same problem with 5.0.2 |
Wait until #1346 is fixed |
Evidently, i can't update hass now as #1346 is still open and homeassistant 2021.7.x needs a newer version of zwavejs than i'm able to run using the pkg version... so, wondering if it's possible/easy to migrate to a docker version? can i just map my store directory that i use w/ the pkg version to the /usr/src/app/store directory in the container? |
Fixed, release is coming |
Version
Checklist:
Build/Run method
zwavejs2mqtt version: 5.0.0
zwave-js version: 7.7.3
Describe the bug
zwavejs2mqtt doesn't start
Error in logfile:
Results of
systemctl status zwavejs2mqtt
:● zwavejs2mqtt.service - zwavejs2mqtt server
Loaded: loaded (/etc/systemd/system/zwavejs2mqtt.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Thu 2021-06-10 13:52:27 MDT; 11s ago
Process: 45269 ExecStart=/home/jhass/zwavejs2mqtt/zwavejs2mqtt (code=exited, status=1/FAILURE)
Main PID: 45269 (code=exited, status=1/FAILURE)
Jun 10 13:52:27 hass zwavejs2mqtt[45269]: at Object.Module._extensions..node (internal/modules/cjs/loader.js:1248:18)
Jun 10 13:52:27 hass zwavejs2mqtt[45269]: at Module.load (internal/modules/cjs/loader.js:1047:32)
Jun 10 13:52:27 hass zwavejs2mqtt[45269]: at Function.Module._load (internal/modules/cjs/loader.js:935:14)
Jun 10 13:52:27 hass zwavejs2mqtt[45269]: at Module.require (internal/modules/cjs/loader.js:1087:19)
Jun 10 13:52:27 hass zwavejs2mqtt[45269]: at Module.require (pkg/prelude/bootstrap.js:1338:31)
Jun 10 13:52:27 hass zwavejs2mqtt[45269]: at require (internal/modules/cjs/helpers.js:73:18)
Jun 10 13:52:27 hass zwavejs2mqtt[45269]: at bindings (/snapshot/zwavejs2mqtt/node_modules/bindings/bindings.js:112:48)
Jun 10 13:52:27 hass zwavejs2mqtt[45269]: at Object. (/snapshot/zwavejs2mqtt/node_modules/@serialport/bindings/lib/linux.js:2:3
Jun 10 13:52:27 hass systemd[1]: zwavejs2mqtt.service: Main process exited, code=exited, status=1/FAILURE
Jun 10 13:52:27 hass systemd[1]: zwavejs2mqtt.service: Failed with result 'exit-code'.
The text was updated successfully, but these errors were encountered: