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

[bug] zwavejs2mqtt not starting - out of memory #485

Closed
2 tasks
dvbit opened this issue Feb 6, 2021 · 6 comments
Closed
2 tasks

[bug] zwavejs2mqtt not starting - out of memory #485

dvbit opened this issue Feb 6, 2021 · 6 comments
Assignees
Labels
bug Something isn't working

Comments

@dvbit
Copy link

dvbit commented Feb 6, 2021

Before submitting a bug please read: https://zwave-js.github.io/zwavejs2mqtt/#/troubleshooting/bug_report

Version

latest

Build/Run method

  • [ X] Docker
  • PKG
  • Manually built (git clone - npm install - npm run build )

zwavejs2mqtt version: latest
zwavejs version: latest

Describe the bug

node bails out with out of memory message
|___ / (_) |__ \ | | | | / /_ ____ ___ _____ _ ___ ) |_ __ ___ __ _| |_| |_ / /\ \ /\ / / _ \ \ / / _ \ / | / /| ' _ \ / _ | | |
/ /\ V V / (| |\ V / _/ _ / /| | | | | | (| | || |_
/
|_/_/ _,| _/ _| |/|| || ||_, |_|__|
/ | | |
|__/ |
|

2021-02-06 17:23:03.794 WARN STORE: scenes.json not found
/bin/sh: git: not found
2021-02-06 17:23:14.007 INFO APP: Version: 1.0.5
2021-02-06 17:23:14.012 INFO APP: Application path:/usr/src/app
2021-02-06 17:23:14.604 INFO MQTT: Connecting to mqtt://hass.fritz.box:1883
2021-02-06 17:23:15.117 INFO ZWAVE: Connecting to /dev/ttyACM0
2021-02-06 17:23:15.343 INFO APP: Listening on port 8091

<--- Last few GCs --->
lu[1:0x3541c30] 22946 ms: Mark-sweep 231.6 (234.8) -> 231.5 (234.8) MB, 191.4 / 0.1 ms (+ 81.2 ms in 13 steps since start of marking, biggest step 16.1 ms, walltime since start of marking 295 ms) (average mu = 0.140, current mu = 0.081) allocation failu[1:0x3541c30] 23213 ms: Mark-sweep 231.9 (234.8) -> 231.8 (234.8) MB, 201.5 / 0.1 ms (+ 54.8 ms in 5 steps since start of marking, biggest step 15.1 ms, walltime since start of marking 266 ms) (average mu = 0.093, current mu = 0.041) allocation failur

<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x32600469
0: builtin exit frame: stringify(this=0x3260f925 ,0x3e180279 ,0x5d85a289 <JSFunction (sfi = 0x212fef8d)>,0x370ad5dd ,0x3260f925 )

1: arguments adaptor frame: 2->3
2: serialize [0x277a2615] [/usr/src/app/node_modules/nedb/lib/model.js:~69] [pc=0x599f2ec8](this=0x27798219 <Object map = 0x3c25cb75>,0x370a...

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory`

To Reproduce

Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior

Zwavejs2mqtt running

Additional context

Add any other context about the problem here.

@dvbit dvbit added the bug Something isn't working label Feb 6, 2021
@robertsLando
Copy link
Member

@dvbit Disable persistent storage in mqtt settings, it's bugged

@robertsLando
Copy link
Member

Ref #220

@dvbit
Copy link
Author

dvbit commented Feb 7, 2021

@robertsLando grazie. I searched the issues before opening and could not find it. By the way, sticking to zwavejs2mqtt despite homeassistant is introducing a new integration. Your development is by far more flexible modular and advanced ;-)

@robertsLando
Copy link
Member

Grazie a te 🙏 :)

@RezzZ
Copy link

RezzZ commented Feb 18, 2021

@dvbit Disable persistent storage in mqtt settings, it's bugged

you mean disable this in mosquitto or in the settings inside zwavejs2mqtt.
it's a bit hard to disable in zwavejs2mqtt if it crashes on start.

I'll try to edit the settings.json then.
TIP: perhaps the file can be properly formatted as json instead of a 1liner?
makes it easier to edit.

edit:
ok, change the value "store":true to "store":false in the mqtt settings from the settings.json file and zwavejs2mqtt is back online!

@robertsLando
Copy link
Member

@RezzZ Glad you fixed!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants