search

hassio-addons / addon-node-red

Node-RED - Home Assistant Community Add-ons
https://addons.community
MIT License
535 stars 125 forks source link

Not loading RPi.GPIO pallete #1209

Closed hellresistor closed 2 years ago

hellresistor commented 2 years ago

Problem/Motivation

Addon Log Reports Error on loading RPi.GPIO pallete. I am in Raspberry pi 4 8GB in supervised HA using Debian 11 aarch64

Expected behavior

RPi.GPIO be loaded successfull after NodeRed Addon Start.

Actual behavior

[10:45:42] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
12 Dec 10:45:45 - [info] 
Welcome to Node-RED
===================
12 Dec 10:45:45 - [info] Node-RED version: v2.1.4
12 Dec 10:45:45 - [info] Node.js  version: v16.13.1
12 Dec 10:45:45 - [info] Linux 5.10.0-9-arm64 arm64 LE
12 Dec 10:45:47 - [info] Loading palette nodes
12 Dec 10:45:54 - [info] Dashboard version 3.1.2 started at /endpoint/ui
Traceback (most recent call last):
  File "/opt/node_modules/node-red-node-pi-gpio/testgpio.py", line 3, in <module>
    import RPi.GPIO as GPIO
  File "/usr/lib/python3.9/site-packages/RPi/GPIO/__init__.py", line 23, in <module>
    from RPi._GPIO import *
RuntimeError: This module can only be run on a Raspberry Pi!
12 Dec 10:45:56 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
12 Dec 10:45:56 - [info] Settings file  : /etc/node-red/config.js
12 Dec 10:45:56 - [info] Context store  : 'default' [module=memory]
12 Dec 10:45:56 - [info] User directory : /config/node-red/
12 Dec 10:45:56 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Dec 10:45:56 - [info] Flows file     : /config/node-red/flows.json
12 Dec 10:45:56 - [info] Server now running at http://127.0.0.1:46836/
12 Dec 10:45:56 - [info] Starting flows
12 Dec 10:45:56 - [info] Started flows
[10:45:56] INFO: Starting NGinx...

Steps to reproduce

Start NodeRed Addon

Proposed changes

dethpickle commented 2 years ago

I'm seeing something similar after upgrading to the Node-Red integration 10.2.0 and HA to 2021.12.0. I honestly can't recall if it was working in the in-between couple of minutes between the two upgrades.

I'm running it as a VM:

System Health

version core-2021.12.0
installation_type Home Assistant OS
dev false
hassio true
docker true
user root
virtualenv false
python_version 3.9.7
os_name Linux
os_version 5.10.83
arch x86_64
timezone America/Los_Angeles
Home Assistant Community Store GitHub API | ok -- | -- Github API Calls Remaining | 5000 Installed Version | 1.18.0 Stage | running Available Repositories | 910 Installed Repositories | 27
Home Assistant Cloud logged_in | true -- | -- subscription_expiration | January 7, 2022, 4:00 PM relayer_connected | true remote_enabled | true remote_connected | true alexa_enabled | true google_enabled | false remote_server | us-west-2-0.ui.nabu.casa can_reach_cert_server | ok can_reach_cloud_auth | ok can_reach_cloud | ok
Home Assistant Supervisor host_os | Home Assistant OS 7.0 -- | -- update_channel | stable supervisor_version | supervisor-2021.12.1 docker_version | 20.10.9 disk_total | 58.4 GB disk_used | 27.2 GB healthy | true supported | true board | ova supervisor_api | ok version_api | ok installed_addons | Samba share (9.5.1), Mosquitto broker (6.0.1), SSH & Web Terminal (9.1.1), Node-RED (10.2.0), Studio Code Server (3.7.0), Home Assistant Google Drive Backup (0.105.2), Let's Encrypt (4.12.0)
Universal Devices ISY994 host_reachable | ok -- | -- device_connected | true last_heartbeat | December 12, 2021, 7:19 PM websocket_status | connected
Lovelace dashboards | 4 -- | -- resources | 15 views | 17 mode | storage

Node-Red just gives the following when you go to it's page:

502 Bad Gateway

nginx

Node-Red Log:

12 Dec 19:17:37 - [error] [cron:December Cycle] Invalid Expression
12 Dec 19:17:37 - [info] Started flows
12 Dec 19:17:37 - [info] [mqtt-broker:Local MQTT] Connected to broker: nodered@http://<<redacted/
12 Dec 19:17:37 - [warn] [sun events:ae9be1e3.2e7ab] calculating sunevents for <<redacted>>
12 Dec 19:17:37 - [red] Uncaught Exception:
12 Dec 19:17:37 - [error] HTTPError: Response code 502 (Bad Gateway)
    at EventEmitter.<anonymous> (/config/node-red/node_modules/got/source/as-promise.js:74:19)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
[19:17:37] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
12 Dec 19:17:38 - [info] 
Welcome to Node-RED
===================
12 Dec 19:17:38 - [info] Node-RED version: v2.1.4
12 Dec 19:17:38 - [info] Node.js  version: v16.13.1
12 Dec 19:17:38 - [info] Linux 5.10.83 x64 LE
12 Dec 19:17:39 - [info] Loading palette nodes
12 Dec 19:17:41 - [info] Dashboard version 3.1.2 started at /endpoint/ui
Traceback (most recent call last):
  File "/opt/node_modules/node-red-node-pi-gpio/testgpio.py", line 3, in <module>
    import RPi.GPIO as GPIO
  File "/usr/lib/python3.9/site-packages/RPi/GPIO/__init__.py", line 23, in <module>
    from RPi._GPIO import *
RuntimeError: This module can only be run on a Raspberry Pi!
12 Dec 19:17:41 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
12 Dec 19:17:41 - [info] Settings file  : /etc/node-red/config.js
12 Dec 19:17:41 - [info] Context store  : 'default' [module=memory]
12 Dec 19:17:41 - [info] User directory : /config/node-red/
12 Dec 19:17:41 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Dec 19:17:41 - [info] Flows file     : /config/node-red/flows.json
12 Dec 19:17:41 - [info] Server now running at http://127.0.0.1:46836/
12 Dec 19:17:41 - [info] Starting flows
[2021-12-12 19:17:42] info: US Controller created
[2021-12-12 19:17:42] info: Bluelinky is loging in automatically, to disable use autoLogin: false
12 Dec 19:17:42 - [error] [cron:December Cycle] Invalid Expression
12 Dec 19:17:42 - [info] Started flows
12 Dec 19:17:42 - [info] [mqtt-broker:Local MQTT] Connected to broker: nodered@http://<<redacted/
12 Dec 19:17:42 - [warn] [sun events:ae9be1e3.2e7ab] calculating sunevents for <<redacted>>
12 Dec 19:17:42 - [red] Uncaught Exception:
12 Dec 19:17:42 - [error] HTTPError: Response code 502 (Bad Gateway)
    at EventEmitter.<anonymous> (/config/node-red/node_modules/got/source/as-promise.js:74:19)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
[19:17:42] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
12 Dec 19:17:43 - [info] 
Welcome to Node-RED
===================
12 Dec 19:17:43 - [info] Node-RED version: v2.1.4
12 Dec 19:17:43 - [info] Node.js  version: v16.13.1
12 Dec 19:17:43 - [info] Linux 5.10.83 x64 LE
12 Dec 19:17:44 - [info] Loading palette nodes
12 Dec 19:17:46 - [info] Dashboard version 3.1.2 started at /endpoint/ui
Traceback (most recent call last):
  File "/opt/node_modules/node-red-node-pi-gpio/testgpio.py", line 3, in <module>
    import RPi.GPIO as GPIO
  File "/usr/lib/python3.9/site-packages/RPi/GPIO/__init__.py", line 23, in <module>
    from RPi._GPIO import *
RuntimeError: This module can only be run on a Raspberry Pi!
12 Dec 19:17:47 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
12 Dec 19:17:47 - [info] Settings file  : /etc/node-red/config.js
12 Dec 19:17:47 - [info] Context store  : 'default' [module=memory]
12 Dec 19:17:47 - [info] User directory : /config/node-red/
12 Dec 19:17:47 - [warn] Projects disabled : editorTheme.projects.enabled=false
12 Dec 19:17:47 - [info] Flows file     : /config/node-red/flows.json
12 Dec 19:17:47 - [info] Server now running at http://127.0.0.1:46836/
12 Dec 19:17:47 - [info] Starting flows
[2021-12-12 19:17:47] info: US Controller created
[2021-12-12 19:17:47] info: Bluelinky is loging in automatically, to disable use autoLogin: false
12 Dec 19:17:47 - [error] [cron:December Cycle] Invalid Expression
12 Dec 19:17:47 - [info] Started flows
12 Dec 19:17:47 - [info] [mqtt-broker:Local MQTT] Connected to broker: nodered@http://<<redacted/
12 Dec 19:17:47 - [warn] [sun events:ae9be1e3.2e7ab] calculating sunevents for <<redacted>>
12 Dec 19:17:47 - [red] Uncaught Exception:
12 Dec 19:17:47 - [error] HTTPError: Response code 502 (Bad Gateway)
    at EventEmitter.<anonymous> (/config/node-red/node_modules/got/source/as-promise.js:74:19)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
[19:17:47] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
12 Dec 19:17:49 - [info] 
Welcome to Node-RED
===================
12 Dec 19:17:49 - [info] Node-RED version: v2.1.4
12 Dec 19:17:49 - [info] Node.js  version: v16.13.1
12 Dec 19:17:49 - [info] Linux 5.10.83 x64 LE
12 Dec 19:17:49 - [info] Loading palette nodes
dethpickle commented 2 years ago

Please disregard - I found the other issue: #1198 and used what folks were saying to figure out that my issue was the Bluelinky module. I removed from packages.json as they described and my node-red is working again.

@hellresistor, you might try looking in the rest of your log and seeing if you have something similar to chase down.

Cheers!

hellresistor commented 2 years ago

NodeRed Addon Full LOG

[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: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 10.2.0
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 11 (bullseye)  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.12.1
 Home Assistant Supervisor: 2021.12.1
-----------------------------------------------------------
 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] customizations.sh: executing... 
[cont-init.d] customizations.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] node-red.sh: executing... 
patching file nodes/ui_base.html
Hunk #1 succeeded at 1162 (offset 631 lines).
up to date, audited 1 package in 2s
found 0 vulnerabilities
[cont-init.d] node-red.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[07:05:47] INFO: Starting Node-RED...
> start
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
13 Dec 07:05:51 - [info] 
Welcome to Node-RED
===================
13 Dec 07:05:51 - [info] Node-RED version: v2.1.4
13 Dec 07:05:51 - [info] Node.js  version: v16.13.1
13 Dec 07:05:51 - [info] Linux 5.10.0-9-arm64 arm64 LE
13 Dec 07:05:52 - [info] Loading palette nodes
13 Dec 07:06:00 - [info] Dashboard version 3.1.2 started at /endpoint/ui
Traceback (most recent call last):
  File "/opt/node_modules/node-red-node-pi-gpio/testgpio.py", line 3, in <module>
    import RPi.GPIO as GPIO
  File "/usr/lib/python3.9/site-packages/RPi/GPIO/__init__.py", line 23, in <module>
    from RPi._GPIO import *
RuntimeError: This module can only be run on a Raspberry Pi!
13 Dec 07:06:01 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
13 Dec 07:06:01 - [info] Settings file  : /etc/node-red/config.js
13 Dec 07:06:01 - [info] Context store  : 'default' [module=memory]
13 Dec 07:06:01 - [info] User directory : /config/node-red/
13 Dec 07:06:01 - [warn] Projects disabled : editorTheme.projects.enabled=false
13 Dec 07:06:01 - [info] Flows file     : /config/node-red/flows.json
13 Dec 07:06:01 - [info] Server now running at http://127.0.0.1:46836/
13 Dec 07:06:01 - [info] Starting flows
13 Dec 07:06:01 - [info] Started flows
[07:06:01] INFO: Starting NGinx...
13 Dec 07:06:06 - [info] [server:Home Assistant] Connecting to undefined
13 Dec 07:06:06 - [info] [server:Home Assistant] Connected to undefined

Keeps with HA Core update core-2021.12.1

hellresistor commented 2 years ago

Keeps after NodeRed Addon v10.2.1 update

Configuration:

certfile: fullchain.pem
credential_secret: basicpassword
http_node:
  password: ''
  username: ''
http_static:
  password: ''
  username: ''
init_commands:
  - npm fund
  - npm audit fix
keyfile: privkey.pem
npm_packages:
  - node-red-node-pi-gpio
ssl: false
system_packages: []
theme: default
[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: Node-RED
 Flow-based programming for the Internet of Things
-----------------------------------------------------------
 Add-on version: 10.2.1
 You are running the latest version of this add-on.
 System: Debian GNU/Linux 11 (bullseye)  (aarch64 / raspberrypi4-64)
 Home Assistant Core: 2021.12.3
 Home Assistant Supervisor: 2021.12.2
-----------------------------------------------------------
 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] customizations.sh: executing... 
[17:51:40] INFO: Starting installation of custom NPM/Node-RED packages...
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'node-red-contrib-modbus@5.16.0',
npm WARN EBADENGINE   required: { node: '>=10 <15' },
npm WARN EBADENGINE   current: { node: 'v16.13.1', npm: '8.1.3' }
npm WARN EBADENGINE }
up to date, audited 690 packages in 8s
88 packages are looking for funding
  run `npm fund` for details
9 vulnerabilities (4 moderate, 5 high)
To address issues that do not require attention, run:
  npm audit fix
Some issues need review, and may require choosing
a different dependency.
Run `npm audit` for details.
addon-node-red
├── https://www.buymeacoffee.com/mbonani
│   └── @node-red-contrib-themes/theme-collection@2.1.4, @node-red-contrib-themes/dark@2.1.3, @node-red-contrib-themes/dracula@2.1.3, @node-red-contrib-themes/midnight-red@2.1.3, @node-red-contrib-themes/oled@2.1.3, @node-red-contrib-themes/solarized-dark@2.1.4, @node-red-contrib-themes/solarized-light@2.1.4
├─┬ https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=XDPSATTXBXHCL
│ │ └── node-red-contrib-cast@0.2.17
│ └── https://github.com/sponsors/ljharb
│     └── deep-equal@1.1.1, is-arguments@1.1.1, call-bind@1.0.2, get-intrinsic@1.1.1, has-symbols@1.0.2, has-tostringtag@1.0.0, is-date-object@1.0.5, is-regex@1.1.4, object-is@1.1.5, regexp.prototype.flags@1.3.1, string.prototype.matchall@4.0.6, es-abstract@1.19.1, es-to-primitive@1.2.1, is-symbol@1.0.4, get-symbol-description@1.0.0, is-callable@1.2.4, is-negative-zero@2.0.2, is-shared-array-buffer@1.0.1, is-string@1.0.7, is-weakref@1.0.2, object-inspect@1.12.0, object.assign@4.1.2, string.prototype.trimend@1.0.4, string.prototype.trimstart@1.0.4, unbox-primitive@1.0.1, has-bigints@1.0.1, which-boxed-primitive@1.0.2, is-bigint@1.0.4, is-boolean-object@1.1.2, is-number-object@1.0.6, side-channel@1.0.4
├─┬ https://opencollective.com/node-red-contrib-modbus
│ │ └── node-red-contrib-modbus@5.16.0
│ └── https://opencollective.com/serialport/donate
│     └── serialport@9.0.8, @serialport/binding-mock@9.2.4, @serialport/binding-abstract@9.2.3, @serialport/bindings@9.2.8, @serialport/parser-byte-length@9.2.4, @serialport/parser-cctalk@9.2.4, @serialport/parser-delimiter@9.2.4, @serialport/parser-inter-byte-timeout@9.2.4, @serialport/parser-readline@9.2.4, @serialport/parser-ready@9.2.4, @serialport/parser-regex@9.2.4, @serialport/stream@9.2.4, serialport@9.2.8
├── https://github.com/sponsors/jaredhanson
│   └── oauth2orize@1.11.1, passport@0.5.0
├── https://github.com/sponsors/epoberezkin
│   └── ajv@6.12.6
├─┬ https://github.com/cheeriojs/cheerio?sponsor=1
│ │ └── cheerio@1.0.0-rc.10
│ ├─┬ https://github.com/sponsors/fb55
│ │ │ └── cheerio-select@1.5.0, css-select@4.2.0, css-what@5.1.0, domelementtype@2.2.0
│ │ └── https://github.com/fb55/domutils?sponsor=1
│ │     └── domutils@2.8.0
│ ├─┬ https://github.com/cheeriojs/dom-serializer?sponsor=1
│ │ │ └── dom-serializer@1.3.2
│ │ └── https://github.com/fb55/entities?sponsor=1
│ │     └── entities@2.2.0
│ ├── https://github.com/fb55/domhandler?sponsor=1
│ │   └── domhandler@4.3.0
│ └── https://github.com/fb55/htmlparser2?sponsor=1
│     └── htmlparser2@6.1.0
├─┬ https://github.com/sindresorhus/got?sponsor=1
│ │ └── got@11.8.3
│ ├── https://github.com/sindresorhus/is?sponsor=1
│ │   └── @sindresorhus/is@4.2.0
│ └── https://github.com/sponsors/sindresorhus
│     └── decompress-response@6.0.0, mimic-response@3.1.0, get-stream@5.2.0, normalize-url@6.1.0, quick-lru@5.1.1, os-locale@5.0.0, is-stream@2.0.1, onetime@5.1.2
├── https://github.com/sponsors/isaacs
│   └── glob@7.2.0
└── https://github.com/sponsors/RubenVerborgh
    └── follow-redirects@1.14.6
npm WARN audit fix minimist@0.0.10 node_modules/node-red-node-email/node_modules/optimist/node_modules/minimist
npm WARN audit fix minimist@0.0.10 is a bundled dependency of
npm WARN audit fix minimist@0.0.10 node-red-node-email@1.13.0 at node_modules/node-red-node-email
npm WARN audit fix minimist@0.0.10 It cannot be fixed automatically.
npm WARN audit fix minimist@0.0.10 Check for updates to the node-red-node-email package.
npm WARN audit fix nodemailer@6.5.0 node_modules/node-red-node-email/node_modules/mailparser/node_modules/nodemailer
npm WARN audit fix nodemailer@6.5.0 is a bundled dependency of
npm WARN audit fix nodemailer@6.5.0 node-red-node-email@1.13.0 at node_modules/node-red-node-email
npm WARN audit fix nodemailer@6.5.0 It cannot be fixed automatically.
npm WARN audit fix nodemailer@6.5.0 Check for updates to the node-red-node-email package.
npm WARN audit fix optimist@0.6.1 node_modules/node-red-node-email/node_modules/optimist
npm WARN audit fix optimist@0.6.1 is a bundled dependency of
npm WARN audit fix optimist@0.6.1 node-red-node-email@1.13.0 at node_modules/node-red-node-email
npm WARN audit fix optimist@0.6.1 It cannot be fixed automatically.
npm WARN audit fix optimist@0.6.1 Check for updates to the node-red-node-email package.
npm WARN audit fix mailparser@3.2.0 node_modules/node-red-node-email/node_modules/mailparser
npm WARN audit fix mailparser@3.2.0 is a bundled dependency of
npm WARN audit fix mailparser@3.2.0 node-red-node-email@1.13.0 at node_modules/node-red-node-email
npm WARN audit fix mailparser@3.2.0 It cannot be fixed automatically.
npm WARN audit fix mailparser@3.2.0 Check for updates to the node-red-node-email package.
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: 'node-red-contrib-modbus@5.16.0',
npm WARN EBADENGINE   required: { node: '>=10 <15' },
npm WARN EBADENGINE   current: { node: 'v16.13.1', npm: '8.1.3' }
npm WARN EBADENGINE }
added 2 packages, and audited 692 packages in 13s
89 packages are looking for funding
  run `npm fund` for details
# npm audit report
glob-parent  <5.1.2
Severity: high
Regular expression denial of service - https://github.com/advisories/GHSA-ww39-953v-wcq6
No fix available
node_modules/glob-parent
  glob-stream  5.3.0 - 6.1.0
  Depends on vulnerable versions of glob-parent
  node_modules/glob-stream
    help-me  1.0.0 - 1.1.0
    Depends on vulnerable versions of glob-stream
    node_modules/node-red-contrib-alexa-home-skill/node_modules/help-me
      mqtt  1.14.1 - 4.2.6
      Depends on vulnerable versions of help-me
      node_modules/node-red-contrib-alexa-home-skill/node_modules/mqtt
        node-red-contrib-alexa-home-skill  *
        Depends on vulnerable versions of mqtt
        node_modules/node-red-contrib-alexa-home-skill
minimist  <0.2.1
Severity: moderate
Prototype Pollution in minimist - https://github.com/advisories/GHSA-vh95-rmgr-6w4m
fix available via `npm audit fix`
node_modules/node-red-node-email/node_modules/optimist/node_modules/minimist
  optimist  >=0.6.0
  Depends on vulnerable versions of minimist
  node_modules/node-red-node-email/node_modules/optimist
nodemailer  <6.6.1
Severity: moderate
Header injection in nodemailer - https://github.com/advisories/GHSA-hwqf-gcqm-7353
fix available via `npm audit fix`
node_modules/node-red-node-email/node_modules/mailparser/node_modules/nodemailer
  mailparser  2.3.1 - 3.2.0
  Depends on vulnerable versions of nodemailer
  node_modules/node-red-node-email/node_modules/mailparser
9 vulnerabilities (4 moderate, 5 high)
To address issues that do not require attention, run:
  npm audit fix
Some issues need review, and may require choosing
a different dependency.
[17:50:34] FATAL: Failed executing init command: npm audit fix
[cont-init.d] customizations.sh: exited 1.
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing... 
-----------------------------------------------------------
                Oops! Something went wrong.

 We are so sorry, but something went terribly wrong when
 starting or running this add-on.

 Be sure to check the log above, line by line, for hints.
-----------------------------------------------------------
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.
github-actions[bot] commented 2 years ago

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!