spants Posted July 1, 2022 Author Share Posted July 1, 2022 all looks good. (I am also looking at another solution for MQTT with a webui for users and authorisations-will post here after finishing my tests) Quote Link to comment
de Techneut Posted July 4, 2022 Share Posted July 4, 2022 On 7/1/2022 at 3:06 PM, spants said: all looks good. (I am also looking at another solution for MQTT with a webui for users and authorisations-will post here after finishing my tests) How's the test going? If I can help you, let me know. Would be glad to help. Quote Link to comment
Diode663 Posted July 15, 2022 Share Posted July 15, 2022 My Node Red docker recently got borked. It looks like a permissions issue. > [email protected] start > node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data" 15 Jul 07:53:58 - [info] Welcome to Node-RED =================== 15 Jul 07:53:58 - [info] Node-RED version: v3.0.0 15 Jul 07:53:58 - [info] Node.js version: v16.16.0 15 Jul 07:53:58 - [info] Linux 5.15.46-Unraid x64 LE 15 Jul 07:53:59 - [info] Loading palette nodes 15 Jul 07:54:03 - [info] Dashboard version 3.1.7 started at /ui 15 Jul 07:54:03 - [error] Failed to start server: 15 Jul 07:54:03 - [error] Error: EACCES: permission denied, unlink '/data/.config.nodes.json.backup' [email protected]:/mnt/user/appdata/nodered# ls -all total 228 drwxr-xr-x 1 nobody users 4096 Jun 14 15:55 ./ drwxrwxrwx 1 nobody users 4096 Jun 4 05:32 ../ -rw-r--r-- 1 nobody users 30855 Jun 4 05:49 .config.nodes.json -rw-r--r-- 1 nobody users 30232 Jun 4 05:49 .config.nodes.json.backup -rw-r--r-- 1 nobody users 95 Jun 4 05:32 .config.runtime.json -rw-r--r-- 1 nobody users 543 Jun 4 05:33 .config.users.json -rw-r--r-- 1 nobody users 468 Jun 4 05:33 .config.users.json.backup -rw-r--r-- 1 nobody users 10360 Jun 14 15:55 .flows.json.backup -rw-r--r-- 1 nobody users 79 Jun 4 05:53 .flows_cred.json.backup drwxr-xr-x 1 nobody users 83 Jun 4 05:49 .npm/ -rw-r--r-- 1 nobody users 10366 Jun 14 15:55 flows.json -rw-r--r-- 1 nobody users 107 Jun 4 05:53 flows_cred.json drwxr-xr-x 1 nobody users 19 Jun 4 05:32 lib/ drwxr-xr-x 1 nobody users 20480 Jun 4 05:49 node_modules/ -rw-r--r-- 1 nobody users 67713 Jun 4 05:49 package-lock.json -rw-r--r-- 1 nobody users 440 Jun 4 05:49 package.json -rw-r--r-- 1 nobody users 20498 Jun 4 05:32 settings.js I tried doing a chmod 777 but Im not able to start the container I tried setting the extra parameters flag to --user nobody and that allowed the docker to start but all my flows are missing and I cannot install any nodes. Im not sure where to go from here and any help would be appretiated. 1 Quote Link to comment
SM411 Posted July 24, 2022 Share Posted July 24, 2022 I ran into the same issue. Found a fix for it here: https://github.com/node-red/node-red-docker/wiki/Permissions-and-Persistence This command fixed my issue (might need to be modified for your setup) sudo chown -R 1000:1000 /mnt/user/appdata/nodered 1 Quote Link to comment
Abrechen2 Posted July 30, 2022 Share Posted July 30, 2022 hey i have a issue with one of my nodered Docker (have 3). the docker is running with no problems at all, but i cant update or install Nodes anymore. tried everything i found for all the problems in the log. nothing works.😩 Nodered Log: 2022-07-30T13:34:57.904Z Installieren : node-red-contrib-bigtimer 2.8.2 2022-07-30T13:34:57.354Z npm install --no-audit --no-update-notifier --no-fund --save --save-prefix=~ --production --engine-strict [email protected] 2022-07-30T13:34:57.580Z [err] npm 2022-07-30T13:34:57.580Z [err] 2022-07-30T13:34:57.580Z [err] WARN config production Use `--omit=dev` instead. 2022-07-30T13:34:58.152Z [err] npm WARN old lockfile 2022-07-30T13:34:58.152Z [err] npm WARN old lockfile The package-lock.json file was created with an old version of npm, 2022-07-30T13:34:58.152Z [err] npm WARN 2022-07-30T13:34:58.152Z [err] old lockfile so supplemental metadata must be fetched from the registry. 2022-07-30T13:34:58.152Z [err] npm WARN old lockfile 2022-07-30T13:34:58.152Z [err] npm WARN old lockfile This is a one-time fix-up, please be patient... 2022-07-30T13:34:58.152Z [err] npm WARN old lockfile 2022-07-30T13:35:35.629Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile Error: git dep preparation failed 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:63:27) 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile at ChildProcess.emit (node:events:527:28) 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile at maybeClose (node:internal/child_process:1092:16) 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile Could not fetch metadata for [email protected]+ssh://[email protected]/node-red/node-red.git#8d98b228ab2309f72dbc84e1b7599b36f443579d Error: git dep preparation failed 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/lib/index.js:63:27) 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile at ChildProcess.emit (node:events:527:28) 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile at maybeClose (node:internal/child_process:1092:16) 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.630Z [err] at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5) { 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile cmd: '/usr/local/bin/node', 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile args: [ 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile '/usr/local/lib/node_modules/npm/bin/npm-cli.js', 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile 'install', 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile '--force', 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile '--cache=/data/.npm', 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.630Z [err] '--prefer-offline=false', 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile '--prefer-online=false', 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile '--offline=false', 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.630Z [err] '--no-progress', 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile '--no-save', 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile '--no-audit', 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile '--include=dev', 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile '--include=peer', 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.630Z [err] '--include=optional', 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile '--no-package-lock-only', 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile '--no-dry-run' 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile ], 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile code: 1, 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.630Z [err] signal: null, 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile stdout: '', 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile stderr: 'npm WARN using --force Recommended protections disabled.\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected].1: See https://github.com/lydell/source-map-url#deprecated\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.630Z [err] 'npm WARN deprecated [email protected]: this library is no longer supported\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: This project is unmaintained\n' + 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile 'npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: Please use the native JSON object instead of JSON 3\n' + 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile 'npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.630Z [err] 'npm WARN deprecated [email protected]: This package is unmaintained. Use @sinonjs/formatio instead\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: This package has been deprecated in favour of @sinonjs/samsam\n' + 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile 'npm WARN deprecated [email protected]: This project is unmaintained\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: Please upgrade to latest, [email protected] or [email protected]! Check these notes: https://bit.ly/2ZEqIau\n' + 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile 'npm WARN deprecated [email protected]: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10.\n' + 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile 'npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.\n' + 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile 'npm WARN deprecated [email protected]: This project is unmaintained\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: Package no longer supported. Contact [email protected] for more info.\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: not maintained anymore\n' + 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile 'npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details.\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: Mailparser versions older than v2.3.0 are deprecated\n' + 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile 'npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.630Z [err] 'npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142\n' + 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile 'npm WARN deprecated [email protected]: versions < v5.0.0 do not handle NUL in passwords properly\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.630Z [err] 'npm WARN deprecated [email protected]: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>.\n' + 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile 'npm WARN deprecated [email protected]: This module is no longer maintained, try this instead:\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated npm i nyc\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.\n' + 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile 'npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap.\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: The zlib module provides APIs for brotli compression/decompression starting with Node.js v10.16.0, please use it over iltorb\n' + 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile 'npm WARN deprecated [email protected]: you can use npm install i18next from version 2.0.0\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: outdated version, please use @next\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm WARN deprecated [email protected]: [email protected]<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.\n' + 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile 'npm ERR! code 1\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm ERR! path /data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/fibers\n' + 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile 'npm ERR! command failed\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.630Z [err] 'npm ERR! command sh -c node build.js || nodejs build.js\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm ERR! gyp info it worked if it ends with ok\n' + 2022-07-30T13:35:35.630Z [err] npm WARN 2022-07-30T13:35:35.630Z [err] old lockfile 'npm ERR! gyp info using [email protected]\n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 'npm ERR! gyp info using [email protected] | linux | x64\n' + 2022-07-30T13:35:35.630Z [err] npm 2022-07-30T13:35:35.630Z [err] WARN old lockfile 'npm ERR! gyp ERR! configure error \n' + 2022-07-30T13:35:35.630Z [err] npm WARN old lockfile 2022-07-30T13:35:35.631Z [err] `npm ERR! gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.\n` + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! stack at PythonFinder.failNoPython (/data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/node-gyp/lib/configure.js:484:19)\n' + 2022-07-30T13:35:35.631Z [err] npm WARN 2022-07-30T13:35:35.631Z [err] old lockfile 'npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/node-gyp/lib/configure.js:406:16)\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! stack at F (/data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/which/which.js:68:16)\n' + 2022-07-30T13:35:35.631Z [err] npm 2022-07-30T13:35:35.631Z [err] WARN old lockfile 'npm ERR! gyp ERR! stack at E (/data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/which/which.js:80:29)\n' + 2022-07-30T13:35:35.631Z [err] npm WARN 2022-07-30T13:35:35.631Z [err] old lockfile 'npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/which/which.js:89:16\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/isexe/index.js:42:5\n' + 2022-07-30T13:35:35.631Z [err] npm 2022-07-30T13:35:35.631Z [err] WARN old lockfile 'npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/isexe/mode.js:8:5\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 2022-07-30T13:35:35.631Z [err] 'npm ERR! gyp ERR! stack at FSReqCallback.oncomplete (node:fs:198:21)\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! System Linux 5.15.46-Unraid\n' + 2022-07-30T13:35:35.631Z [err] npm 2022-07-30T13:35:35.631Z [err] WARN old lockfile 'npm ERR! gyp ERR! command "/usr/local/bin/node" "/data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/.bin/node-gyp" "rebuild" "--release"\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! cwd /data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/fibers\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! node -v v16.16.0\n' + 2022-07-30T13:35:35.631Z [err] npm WARN 2022-07-30T13:35:35.631Z [err] old lockfile 'npm ERR! gyp ERR! node-gyp -v v3.8.0\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! not ok \n' + 2022-07-30T13:35:35.631Z [err] npm 2022-07-30T13:35:35.631Z [err] WARN old lockfile 'npm ERR! node-gyp exited with code: 1\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 2022-07-30T13:35:35.631Z [err] 'npm ERR! Please make sure you are using a supported platform and node version. If you\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! would like to compile fibers on this machine please make sure you have setup your\n' + 2022-07-30T13:35:35.631Z [err] npm 2022-07-30T13:35:35.631Z [err] WARN old lockfile 'npm ERR! build environment--\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 2022-07-30T13:35:35.631Z [err] 'npm ERR! Windows + OS X instructions here: https://github.com/nodejs/node-gyp\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! Ubuntu users please run: `sudo apt-get install g++ build-essential`\n' + 2022-07-30T13:35:35.631Z [err] npm WARN 2022-07-30T13:35:35.631Z [err] old lockfile 'npm ERR! Alpine users please run: `sudo apk add python make g++`\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp info it worked if it ends with ok\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp info using [email protected]\n' + 2022-07-30T13:35:35.631Z [err] npm WARN 2022-07-30T13:35:35.631Z [err] old lockfile 'npm ERR! gyp info using [email protected] | linux | x64\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! configure error \n' + 2022-07-30T13:35:35.631Z [err] npm 2022-07-30T13:35:35.631Z [err] WARN old lockfile `npm ERR! gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable.\n` + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 2022-07-30T13:35:35.631Z [err] 'npm ERR! gyp ERR! stack at PythonFinder.failNoPython (/data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/node-gyp/lib/configure.js:484:19)\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/node-gyp/lib/configure.js:406:16)\n' + 2022-07-30T13:35:35.631Z [err] npm WARN 2022-07-30T13:35:35.631Z [err] old lockfile 'npm ERR! gyp ERR! stack at F (/data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/which/which.js:68:16)\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! stack at E (/data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/which/which.js:80:29)\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/which/which.js:89:16\n' + 2022-07-30T13:35:35.631Z [err] npm WARN 2022-07-30T13:35:35.631Z [err] old lockfile 'npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/isexe/index.js:42:5\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/isexe/mode.js:8:5\n' + 2022-07-30T13:35:35.631Z [err] npm 2022-07-30T13:35:35.631Z [err] WARN old lockfile 'npm ERR! gyp ERR! stack at FSReqCallback.oncomplete (node:fs:198:21)\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 2022-07-30T13:35:35.631Z [err] 'npm ERR! gyp ERR! System Linux 5.15.46-Unraid\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! command "/usr/local/bin/node" "/data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/.bin/node-gyp" "rebuild" "--release"\n' + 2022-07-30T13:35:35.631Z [err] npm 2022-07-30T13:35:35.631Z [err] WARN old lockfile 'npm ERR! gyp ERR! cwd /data/.npm/_cacache/tmp/git-cloneEhLNhh/node_modules/fibers\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 2022-07-30T13:35:35.631Z [err] 'npm ERR! gyp ERR! node -v v16.16.0\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! gyp ERR! node-gyp -v v3.8.0\n' + 2022-07-30T13:35:35.631Z [err] npm WARN 2022-07-30T13:35:35.631Z [err] old lockfile 'npm ERR! gyp ERR! not ok \n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! node-gyp exited with code: 1\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! Please make sure you are using a supported platform and node version. If you\n' + 2022-07-30T13:35:35.631Z [err] npm WARN 2022-07-30T13:35:35.631Z [err] old lockfile 'npm ERR! would like to compile fibers on this machine please make sure you have setup your\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! build environment--\n' + 2022-07-30T13:35:35.631Z [err] npm 2022-07-30T13:35:35.631Z [err] WARN old lockfile 'npm ERR! Windows + OS X instructions here: https://github.com/nodejs/node-gyp\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 2022-07-30T13:35:35.631Z [err] 'npm ERR! Ubuntu users please run: `sudo apt-get install g++ build-essential`\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! Alpine users please run: `sudo apk add python make g++`\n' + 2022-07-30T13:35:35.631Z [err] npm 2022-07-30T13:35:35.631Z [err] WARN old lockfile '\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! A complete log of this run can be found in:\n' + 2022-07-30T13:35:35.631Z [err] npm WARN old lockfile 'npm ERR! /data/.npm/_logs/2022-07-30T13_35_08_523Z-debug-0.log\n' 2022-07-30T13:35:35.631Z [err] npm WARN 2022-07-30T13:35:35.631Z [err] old lockfile } 2022-07-30T13:35:36.050Z [err] npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. 2022-07-30T13:35:36.070Z [err] npm WARN deprecated [email protected]: versions < v5.0.0 do not handle NUL in passwords properly 2022-07-30T13:35:36.116Z [err] npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. 2022-07-30T13:35:36.259Z [err] npm WARN deprecated [email protected]: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future 2022-07-30T13:35:36.318Z [err] npm WARN deprecated [email protected]: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410 2022-07-30T13:35:42.085Z [err] npm ERR! code 1 2022-07-30T13:35:42.086Z [err] npm ERR! git dep preparation failed 2022-07-30T13:35:42.086Z [err] npm ERR! command /usr/local/bin/node /usr/local/lib/node_modules/npm/bin/npm-cli.js install --force --cache=/data/.npm --prefer-offline=false --prefer-online=false --offline=false --no-progress --no-save --no-audit --include=dev --include=peer --include=optional --no-package-lock-only --no-dry-run 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN using --force Recommended protections disabled. 2022-07-30T13:35:42.086Z [err] npm 2022-07-30T13:35:42.086Z [err] ERR! npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-url#deprecated 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: Please see https://github.com/lydell/urix#deprecated 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: this library is no longer supported 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: This project is unmaintained 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: https://github.com/lydell/resolve-url#deprecated 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: All versions below 4.0.1 of Nodemailer are deprecated. See https://nodemailer.com/status/ 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: Please use the native JSON object instead of JSON 3 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: See https://github.com/lydell/source-map-resolve#deprecated 2022-07-30T13:35:42.086Z [err] npm ERR! 2022-07-30T13:35:42.086Z [err] npm WARN deprecated [email protected]: This package is unmaintained. Use @sinonjs/formatio instead 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: This package has been deprecated in favour of @sinonjs/samsam 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: This project is unmaintained 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: Please upgrade to latest, [email protected] or [email protected]! Check these notes: https://bit.ly/2ZEqIau 2022-07-30T13:35:42.086Z [err] npm ERR! 2022-07-30T13:35:42.086Z [err] npm WARN deprecated [email protected]: Multer 1.x is affected by CVE-2022-24434. This is fixed in v1.4.4-lts.1 which drops support for versions of Node.js before 6. Please upgrade to at least Node.js 6 and version 1.4.4-lts.1 of Multer. If you need support for older versions of Node.js, we are open to accepting patches that would fix the CVE on the main 1.x release line, whilst maintaining compatibility with Node.js 0.10. 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: This project is unmaintained 2022-07-30T13:35:42.086Z [err] npm 2022-07-30T13:35:42.086Z [err] ERR! npm WARN deprecated [email protected]: Package no longer supported. Contact [email protected] for more info. 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: not maintained anymore 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. 2022-07-30T13:35:42.086Z [err] npm ERR! 2022-07-30T13:35:42.086Z [err] npm WARN deprecated [email protected]: Mailparser versions older than v2.3.0 are deprecated 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142 2022-07-30T13:35:42.086Z [err] npm 2022-07-30T13:35:42.086Z [err] ERR! npm WARN deprecated [email protected]: versions < v5.0.0 do not handle NUL in passwords properly 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>. 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: This module is no longer maintained, try this instead: 2022-07-30T13:35:42.086Z [err] npm 2022-07-30T13:35:42.086Z [err] ERR! npm WARN deprecated npm i nyc 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives. 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. 2022-07-30T13:35:42.086Z [err] npm 2022-07-30T13:35:42.086Z [err] ERR! npm WARN deprecated [email protected]: The zlib module provides APIs for brotli compression/decompression starting with Node.js v10.16.0, please use it over iltorb 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: you can use npm install i18next from version 2.0.0 2022-07-30T13:35:42.086Z [err] npm ERR! npm WARN deprecated [email protected]: outdated version, please use @next 2022-07-30T13:35:42.086Z [err] npm ERR! 2022-07-30T13:35:42.086Z [err] npm WARN deprecated [email protected]: [email protected]<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. 2022-07-30T13:35:42.086Z [err] npm ERR! npm ERR! code 1 2022-07-30T13:35:42.086Z [err] npm ERR! npm ERR! path /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/fibers 2022-07-30T13:35:42.086Z [err] npm ERR! npm ERR! command failed 2022-07-30T13:35:42.086Z [err] npm 2022-07-30T13:35:42.087Z [err] ERR! npm ERR! command sh -c node build.js || nodejs build.js 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp info it worked if it ends with ok 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp info using [email protected] 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp info using [email protected] | linux | x64 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! configure error 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at PythonFinder.failNoPython (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/node-gyp/lib/configure.js:484:19) 2022-07-30T13:35:42.087Z [err] npm ERR! 2022-07-30T13:35:42.087Z [err] npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/node-gyp/lib/configure.js:406:16) 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at F (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:68:16) 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at E (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:80:29) 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:89:16 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/isexe/index.js:42:5 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/isexe/mode.js:8:5 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at FSReqCallback.oncomplete (node:fs:198:21) 2022-07-30T13:35:42.087Z [err] npm ERR! 2022-07-30T13:35:42.087Z [err] npm ERR! gyp ERR! System Linux 5.15.46-Unraid 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! command "/usr/local/bin/node" "/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/.bin/node-gyp" "rebuild" "--release" 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! cwd /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/fibers 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! node -v v16.16.0 2022-07-30T13:35:42.087Z [err] npm 2022-07-30T13:35:42.087Z [err] ERR! npm ERR! gyp ERR! node-gyp -v v3.8.0 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! not ok 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! node-gyp exited with code: 1 2022-07-30T13:35:42.087Z [err] npm ERR! 2022-07-30T13:35:42.087Z [err] npm ERR! Please make sure you are using a supported platform and node version. If you 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! would like to compile fibers on this machine please make sure you have setup your 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! build environment-- 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! Windows + OS X instructions here: https://github.com/nodejs/node-gyp 2022-07-30T13:35:42.087Z [err] npm 2022-07-30T13:35:42.087Z [err] ERR! npm ERR! Ubuntu users please run: `sudo apt-get install g++ build-essential` 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! Alpine users please run: `sudo apk add python make g++` 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp info it worked if it ends with ok 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp info using [email protected] 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp info using [email protected] | linux | x64 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! configure error 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. 2022-07-30T13:35:42.087Z [err] npm ERR! 2022-07-30T13:35:42.087Z [err] npm ERR! gyp ERR! stack at PythonFinder.failNoPython (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/node-gyp/lib/configure.js:484:19) 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/node-gyp/lib/configure.js:406:16) 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at F (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:68:16) 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at E (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:80:29) 2022-07-30T13:35:42.087Z [err] npm 2022-07-30T13:35:42.087Z [err] ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:89:16 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/isexe/index.js:42:5 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/isexe/mode.js:8:5 2022-07-30T13:35:42.087Z [err] npm ERR! 2022-07-30T13:35:42.087Z [err] npm ERR! gyp ERR! stack at FSReqCallback.oncomplete (node:fs:198:21) 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! System Linux 5.15.46-Unraid 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! command "/usr/local/bin/node" "/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/.bin/node-gyp" "rebuild" "--release" 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! cwd /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/fibers 2022-07-30T13:35:42.087Z [err] npm 2022-07-30T13:35:42.087Z [err] ERR! npm ERR! gyp ERR! node -v v16.16.0 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! node-gyp -v v3.8.0 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! gyp ERR! not ok 2022-07-30T13:35:42.087Z [err] npm ERR! 2022-07-30T13:35:42.087Z [err] npm ERR! node-gyp exited with code: 1 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! Please make sure you are using a supported platform and node version. If you 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! would like to compile fibers on this machine please make sure you have setup your 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! build environment-- 2022-07-30T13:35:42.087Z [err] npm 2022-07-30T13:35:42.087Z [err] ERR! npm ERR! Windows + OS X instructions here: https://github.com/nodejs/node-gyp 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! Ubuntu users please run: `sudo apt-get install g++ build-essential` 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! Alpine users please run: `sudo apk add python make g++` 2022-07-30T13:35:42.087Z [err] npm ERR! 2022-07-30T13:35:42.087Z [err] 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! A complete log of this run can be found in: 2022-07-30T13:35:42.087Z [err] npm ERR! npm ERR! /data/.npm/_logs/2022-07-30T13_35_36_616Z-debug-0.log 2022-07-30T13:35:42.088Z [err] 2022-07-30T13:35:42.088Z [err] npm ERR! A complete log of this run can be found in: 2022-07-30T13:35:42.088Z [err] npm ERR! /data/.npm/_logs/2022-07-30T13_34_57_563Z-debug-0.log 2022-07-30T13:35:42.113Z rc=1 Docker Log: npm ERR! npm WARN deprecated [email protected]: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies npm ERR! npm WARN deprecated [email protected]: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm ERR! npm WARN deprecated [email protected]: This project is unmaintained npm ERR! npm WARN deprecated [email protected]: Package no longer supported. Contact [email protected] for more info. npm ERR! npm WARN deprecated [email protected]: not maintained anymore npm ERR! npm WARN deprecated [email protected]: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm ERR! npm WARN deprecated [email protected]: Mailparser versions older than v2.3.0 are deprecated npm ERR! npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm ERR! npm WARN deprecated [email protected]: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.) npm ERR! npm WARN deprecated [email protected]: request has been deprecated, see https://github.com/request/request/issues/3142 npm ERR! npm WARN deprecated [email protected]: versions < v5.0.0 do not handle NUL in passwords properly npm ERR! npm WARN deprecated [email protected]: Please upgrade to @mapbox/node-pre-gyp: the non-scoped node-pre-gyp package is deprecated and only the @mapbox scoped package will recieve updates in the future npm ERR! npm WARN deprecated [email protected]: Please upgrade to v7.0.2+ of superagent. We have fixed numerous issues with streams, form-data, attach(), filesystem errors not bubbling up (ENOENT on attach()), and all tests are now passing. See the releases tab for more information at <https://github.com/visionmedia/superagent/releases>. npm ERR! npm WARN deprecated [email protected]: This module is no longer maintained, try this instead: npm ERR! npm WARN deprecated npm i nyc npm ERR! npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives. npm ERR! npm WARN deprecated [email protected]: This version of tar is no longer supported, and will not receive security updates. Please upgrade asap. npm ERR! npm WARN deprecated [email protected]: The zlib module provides APIs for brotli compression/decompression starting with Node.js v10.16.0, please use it over iltorb npm ERR! npm WARN deprecated [email protected]: you can use npm install i18next from version 2.0.0 npm ERR! npm WARN deprecated [email protected]: outdated version, please use @next npm ERR! npm WARN deprecated [email protected]: [email protected]<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm ERR! npm ERR! code 1 npm ERR! npm ERR! path /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/fibers npm ERR! npm ERR! command failed npm ERR! npm ERR! command sh -c node build.js || nodejs build.js npm ERR! npm ERR! gyp info it worked if it ends with ok npm ERR! npm ERR! gyp info using [email protected] npm ERR! npm ERR! gyp info using [email protected] | linux | x64 npm ERR! npm ERR! gyp ERR! configure error npm ERR! npm ERR! gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. npm ERR! npm ERR! gyp ERR! stack at PythonFinder.failNoPython (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/node-gyp/lib/configure.js:484:19) npm ERR! npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/node-gyp/lib/configure.js:406:16) npm ERR! npm ERR! gyp ERR! stack at F (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:68:16) npm ERR! npm ERR! gyp ERR! stack at E (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:80:29) npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:89:16 npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/isexe/index.js:42:5 npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/isexe/mode.js:8:5 npm ERR! npm ERR! gyp ERR! stack at FSReqCallback.oncomplete (node:fs:198:21) npm ERR! npm ERR! gyp ERR! System Linux 5.15.46-Unraid npm ERR! npm ERR! gyp ERR! command "/usr/local/bin/node" "/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/.bin/node-gyp" "rebuild" "--release" npm ERR! npm ERR! gyp ERR! cwd /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/fibers npm ERR! npm ERR! gyp ERR! node -v v16.16.0 npm ERR! npm ERR! gyp ERR! node-gyp -v v3.8.0 npm ERR! npm ERR! gyp ERR! not ok npm ERR! npm ERR! node-gyp exited with code: 1 npm ERR! npm ERR! Please make sure you are using a supported platform and node version. If you npm ERR! npm ERR! would like to compile fibers on this machine please make sure you have setup your npm ERR! npm ERR! build environment-- npm ERR! npm ERR! Windows + OS X instructions here: https://github.com/nodejs/node-gyp npm ERR! npm ERR! Ubuntu users please run: `sudo apt-get install g++ build-essential` npm ERR! npm ERR! Alpine users please run: `sudo apk add python make g++` npm ERR! npm ERR! gyp info it worked if it ends with ok npm ERR! npm ERR! gyp info using [email protected] npm ERR! npm ERR! gyp info using [email protected] | linux | x64 npm ERR! npm ERR! gyp ERR! configure error npm ERR! npm ERR! gyp ERR! stack Error: Can't find Python executable "python", you can set the PYTHON env variable. npm ERR! npm ERR! gyp ERR! stack at PythonFinder.failNoPython (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/node-gyp/lib/configure.js:484:19) npm ERR! npm ERR! gyp ERR! stack at PythonFinder.<anonymous> (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/node-gyp/lib/configure.js:406:16) npm ERR! npm ERR! gyp ERR! stack at F (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:68:16) npm ERR! npm ERR! gyp ERR! stack at E (/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:80:29) npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/which/which.js:89:16 npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/isexe/index.js:42:5 npm ERR! npm ERR! gyp ERR! stack at /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/isexe/mode.js:8:5 npm ERR! npm ERR! gyp ERR! stack at FSReqCallback.oncomplete (node:fs:198:21) npm ERR! npm ERR! gyp ERR! System Linux 5.15.46-Unraid npm ERR! npm ERR! gyp ERR! command "/usr/local/bin/node" "/data/.npm/_cacache/tmp/git-clonediApKb/node_modules/.bin/node-gyp" "rebuild" "--release" npm ERR! npm ERR! gyp ERR! cwd /data/.npm/_cacache/tmp/git-clonediApKb/node_modules/fibers npm ERR! npm ERR! gyp ERR! node -v v16.16.0 npm ERR! npm ERR! gyp ERR! node-gyp -v v3.8.0 npm ERR! npm ERR! gyp ERR! not ok npm ERR! npm ERR! node-gyp exited with code: 1 npm ERR! npm ERR! Please make sure you are using a supported platform and node version. If you npm ERR! npm ERR! would like to compile fibers on this machine please make sure you have setup your npm ERR! npm ERR! build environment-- npm ERR! npm ERR! Windows + OS X instructions here: https://github.com/nodejs/node-gyp npm ERR! npm ERR! Ubuntu users please run: `sudo apt-get install g++ build-essential` npm ERR! npm ERR! Alpine users please run: `sudo apk add python make g++` npm ERR! npm ERR! npm ERR! A complete log of this run can be found in: npm ERR! npm ERR! /data/.npm/_logs/2022-07-30T13_35_36_616Z-debug-0.log npm ERR! A complete log of this run can be found in: npm ERR! /data/.npm/_logs/2022-07-30T13_34_57_563Z-debug-0.log 30 Jul 14:35:42 - [warn] ------------------------------------------ Error: Install failed at /usr/src/node-red/node_modules/@node-red/registry/lib/installer.js:285:25 at runMicrotasks (<anonymous>) at processTicksAndRejections (node:internal/process/task_queues:96:5) 30 Jul 14:35:42 - [error] Error: Install failed tryed comands npm install --package-lock-only npm i -g npm if you need more infos please ask. and please try to help me. 1 Quote Link to comment
de Techneut Posted August 3, 2022 Share Posted August 3, 2022 On 7/1/2022 at 12:24 PM, spants said: Hi all, As you are discovering, this docker is quite old and needs to be updated. If you can bear with me, please try the manual steps to get a later version of MQTT and solve permissions problems. Please follow these steps and stop any existing MQTT container. I am using a directory called "/mnt/user/appdata/mos/" for my config - change if you wish. 1) In a shell on unRaid, create the mosquitto directories mkdir -p /mnt/user/appdata/mos/config mkdir -p /mnt/user/appdata/mos/data mkdir -p /mnt/user/appdata/mos/log 2) create a configuration file nano /mnt/user/appdata/mos/config/mosquitto.conf with the following text persistence true persistence_location /mosquitto/data/ user mosquitto # Listen on all interfaces listener 1883 #Allow connection without authentication allow_anonymous true log_dest file /mosquitto/log/mosquitto.log log_dest stdout 3) Set the ownership of the directories to nobody:users chown -R nobody:users /mnt/user/appdata/mos 4) download and start the docker (called mqttnew for testing) sudo docker run -itd -p 1883:1883 -e PUID=1000 -e PGID=1000 \ --name=mqttnew \ --net=bridge \ -v /mnt/user/appdata/mos/config:/mosquitto/config \ -v /mnt/user/appdata/mos/data:/mosquitto/data \ -v /mnt/user/appdata/mos/log:/mosquitto/log \ eclipse-mosquitto If you want to add users and disable anonomous logins: 5) On the running docker icon, right click and choose CONSOLE and type: (replace <username>) mosquitto_passwd -c /mosquitto/config/credentials <username> 6) stop the docker 7) edit the /mnt/user/appdata/mos/config/mosquitto.conf file nano /mnt/user/appdata/mos/config/mosquitto.conf to look like: persistence true persistence_location /mosquitto/data/ user mosquitto # Listen on all interfaces listener 1883 #Allow connection without authentication allow_anonymous false log_dest file /mosquitto/log/mosquitto.log log_dest stdout password_file /mosquitto/config/credentials 8 - test and let me know how you get on. I will template this if it works for all. I did this a while ago, now unraid says mqtt has an update but I don't know how to update it. Can someone tell me how to apply the update? Quote Link to comment
Kilrah Posted August 3, 2022 Share Posted August 3, 2022 5 minutes ago, de Techneut said: I did this a while ago, now unraid says mqtt has an update but I don't know how to update it. Can someone tell me how to apply the update? Click on "apply update" right there? Quote Link to comment
de Techneut Posted August 3, 2022 Share Posted August 3, 2022 10 minutes ago, Kilrah said: Click on "apply update" right there? If that was working I wouldn't be here. This docker is created with docker compose, so I don't knop if the "auto update" supposed to be working here. Quote Link to comment
Kilrah Posted August 3, 2022 Share Posted August 3, 2022 If it's a container that comes from a compose stack the "update ready" is meaningless. You can do a "Compose down", delete the orphan image (need to switch the docker page to Advanced view) then "Compose up" on the stack and if there's an update it'll pull it. Quote Link to comment
de Techneut Posted August 3, 2022 Share Posted August 3, 2022 14 minutes ago, Kilrah said: If it's a container that comes from a compose stack the "update ready" is meaningless. You can do a "Compose down", delete the orphan image (need to switch the docker page to Advanced view) then "Compose up" on the stack and if there's an update it'll pull it. I don't know these commands? When I do a "docker --help" I get the following result: [email protected]:~# docker --help Usage: docker [OPTIONS] COMMAND A self-sufficient runtime for containers Options: --config string Location of client config files (default "/root/.docker") -c, --context string Name of the context to use to connect to the daemon (overrides DOCKER_HOST env var and default context set with "docker context use") -D, --debug Enable debug mode -H, --host list Daemon socket(s) to connect to -l, --log-level string Set the logging level ("debug"|"info"|"warn"|"error"|"fatal") (default "info") --tls Use TLS; implied by --tlsverify --tlscacert string Trust certs signed only by this CA (default "/root/.docker/ca.pem") --tlscert string Path to TLS certificate file (default "/root/.docker/cert.pem") --tlskey string Path to TLS key file (default "/root/.docker/key.pem") --tlsverify Use TLS and verify the remote -v, --version Print version information and quit Management Commands: builder Manage builds config Manage Docker configs container Manage containers context Manage contexts image Manage images manifest Manage Docker image manifests and manifest lists network Manage networks node Manage Swarm nodes plugin Manage plugins secret Manage Docker secrets service Manage services stack Manage Docker stacks swarm Manage Swarm system Manage Docker trust Manage trust on Docker images volume Manage volumes Commands: attach Attach local standard input, output, and error streams to a running container build Build an image from a Dockerfile commit Create a new image from a container's changes cp Copy files/folders between a container and the local filesystem create Create a new container diff Inspect changes to files or directories on a container's filesystem events Get real time events from the server exec Run a command in a running container export Export a container's filesystem as a tar archive history Show the history of an image images List images import Import the contents from a tarball to create a filesystem image info Display system-wide information inspect Return low-level information on Docker objects kill Kill one or more running containers load Load an image from a tar archive or STDIN login Log in to a Docker registry logout Log out from a Docker registry logs Fetch the logs of a container pause Pause all processes within one or more containers port List port mappings or a specific mapping for the container ps List containers pull Pull an image or a repository from a registry push Push an image or a repository to a registry rename Rename a container restart Restart one or more containers rm Remove one or more containers rmi Remove one or more images run Run a command in a new container save Save one or more images to a tar archive (streamed to STDOUT by default) search Search the Docker Hub for images start Start one or more stopped containers stats Display a live stream of container(s) resource usage statistics stop Stop one or more running containers tag Create a tag TARGET_IMAGE that refers to SOURCE_IMAGE top Display the running processes of a container unpause Unpause all processes within one or more containers update Update configuration of one or more containers version Show the Docker version information wait Block until one or more containers stop, then print their exit codes Run 'docker COMMAND --help' for more information on a command. To get more help with docker, check out our guides at https://docs.docker.com/go/guides/ Quote Link to comment
Kilrah Posted August 3, 2022 Share Posted August 3, 2022 (edited) Well how did you get those docker-compose stacks installed on your server? The compose manager plugin shows you buttons for them. Manually it's docker-compose down / up while being in the folder where the docker-compose.yml file is located. Edited August 3, 2022 by Kilrah Quote Link to comment
stlrox Posted August 3, 2022 Share Posted August 3, 2022 Suddenly MQTT container stopped working. There is no information in the logs. This container worked without any issues for the last two years. Recently I upgraded to OS 6.10.3. I verified directory path and there is no issue with the permissions. I tried to restart this several times but didn't produce any helpful information in the logs. I appreciate any tips for solving this issue. Quote Link to comment
BKS Posted August 14, 2022 Share Posted August 14, 2022 I use your node-red container, thank you for maintaining it. A few node plugins I'd like to use give me errors when I try to add to the node-red palette. Logs show (excerpt): today at 1:54:50 PMnpm ERR! npm ERR! Please make sure you are using a supported platform and node version. If you today at 1:54:50 PMnpm ERR! npm ERR! would like to compile fibers on this machine please make sure you have setup your today at 1:54:50 PMnpm ERR! npm ERR! build environment-- today at 1:54:50 PMnpm ERR! npm ERR! Windows + OS X instructions here: https://github.com/nodejs/node-gyp today at 1:54:50 PMnpm ERR! npm ERR! Ubuntu users please run: `sudo apt-get install g++ build-essential` today at 1:54:50 PMnpm ERR! npm ERR! Alpine users please run: `sudo apk add python make g++` today at 1:54:50 PMnpm ERR! today at 1:54:50 PMnpm ERR! npm ERR! A complete log of this run can be found in: today at 1:54:50 PMnpm ERR! npm ERR! /data/.npm/_logs/2022-08-14T17_54_38_092Z-debug-0.log Looks like I need to get some packages installed for compiling python code. Is this not included in the container by default? Any recommendations on best way for me to add it? Thanks! Quote Link to comment
goinsnoopin Posted August 20, 2022 Share Posted August 20, 2022 (edited) I have been using this container successfully for over a year. I am getting an error when I attempt to update a palette. Please note that all three palette's give the same error...just with specifics for each palette. Here is the excerpt from the logs for one example: 51 verbose type system 52 verbose stack FetchError: Invalid response body while trying to fetch https://registry.npmjs.org/node-red-contrib-power-monitor: ENOSYS: function not implemented, link '/data/.npm/_cacache/tmp/536b9d89' -> '/data/.npm/_cacache/content-v2/sha512/ca/78/ecf9ea9e429677649e945a71808de04bdb7c3b007549b9a2b8c1e2f24153a034816fdb11649d9265afe902d0c1d845c02ac702ae46967c08ebb58bc2ca53' 52 verbose stack at /usr/local/lib/node_modules/npm/node_modules/minipass-fetch/lib/body.js:168:15 52 verbose stack at async RegistryFetcher.packument (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/registry.js:99:25) 52 verbose stack at async RegistryFetcher.manifest (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/registry.js:124:23) 52 verbose stack at async Arborist.[nodeFromEdge] (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:1108:19) 52 verbose stack at async Arborist.[buildDepStep] (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:976:11) 52 verbose stack at async Arborist.buildIdealTree (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:218:7) 52 verbose stack at async Promise.all (index 1) 52 verbose stack at async Arborist.reify (/usr/local/lib/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/reify.js:153:5) 52 verbose stack at async Install.exec (/usr/local/lib/node_modules/npm/lib/commands/install.js:156:5) 52 verbose stack at async module.exports (/usr/local/lib/node_modules/npm/lib/cli.js:78:5) 53 verbose cwd /data 54 verbose Linux 5.15.46-Unraid 55 verbose node v16.16.0 56 verbose npm v8.11.0 57 error code ENOSYS 58 error syscall link 59 error path /data/.npm/_cacache/tmp/536b9d89 60 error dest /data/.npm/_cacache/content-v2/sha512/ca/78/ecf9ea9e429677649e945a71808de04bdb7c3b007549b9a2b8c1e2f24153a034816fdb11649d9265afe902d0c1d845c02ac702ae46967c08ebb58bc2ca53 61 error errno ENOSYS 62 error Invalid response body while trying to fetch https://registry.npmjs.org/node-red-contrib-power-monitor: ENOSYS: function not implemented, link '/data/.npm/_cacache/tmp/536b9d89' -> '/data/.npm/_cacache/content-v2/sha512/ca/78/ecf9ea9e429677649e945a71808de04bdb7c3b007549b9a2b8c1e2f24153a034816fdb11649d9265afe902d0c1d845c02ac702ae46967c08ebb58bc2ca53' 63 verbose exit 1 64 timing npm Completed in 3896ms 65 verbose unfinished npm timer reify 1661012682451 66 verbose unfinished npm timer reify:loadTrees 1661012682455 67 verbose code 1 68 error A complete log of this run can be found in: 68 error /data/.npm/_logs/2022-08-20T16_24_42_307Z-debug-0.log I cleared my browser cache and have tried from a second browser (chrome is primary...tried from firefox also). Any help would be greatly appreciated! Dan Edited August 20, 2022 by goinsnoopin 1 Quote Link to comment
goinsnoopin Posted August 20, 2022 Share Posted August 20, 2022 Update to post above: I rolled my docker tag from latest to the 3.0.1 release of about a month ago and all functions as it is supposed to. The releases 3.0.1-1 (23 days ago) and 3.0.2 (16 days ago) I get the error above. For now I am staying rolled back to 3.0.1 release. 1 Quote Link to comment
spants Posted August 21, 2022 Author Share Posted August 21, 2022 (edited) 21 hours ago, goinsnoopin said: Update to post above: I rolled my docker tag from latest to the 3.0.1 release of about a month ago and all functions as it is supposed to. The releases 3.0.1-1 (23 days ago) and 3.0.2 (16 days ago) I get the error above. For now I am staying rolled back to 3.0.1 release. Please check with the owner of node-red-contrib-power-monitor as it may be an issue there (npm/node version?). The template just loads the official nodered docker so there is nothing that I can do to fix it. Edited August 21, 2022 by spants Quote Link to comment
goinsnoopin Posted August 21, 2022 Share Posted August 21, 2022 (edited) The issue is not with this palette...it is all palettes...installing new or updating. I have gotten some help from the nodered github. Here is the issue as I understand it....link does not work within the nodered container and starting with nodered 3.0.1-1 they moved the location of cache to inside the /data path. Here is the link to the github issue I raised with nodered...has some info that may be helpful: github issue Edited August 24, 2022 by goinsnoopin 1 Quote Link to comment
Iceman24 Posted August 29, 2022 Share Posted August 29, 2022 On 8/3/2022 at 9:47 AM, stlrox said: Suddenly MQTT container stopped working. There is no information in the logs. This container worked without any issues for the last two years. Recently I upgraded to OS 6.10.3. I verified directory path and there is no issue with the permissions. I tried to restart this several times but didn't produce any helpful information in the logs. I appreciate any tips for solving this issue. Did you ever get this fixed? I just updated to 6.10.3 from 6.9.2 and it killed my MQTT. Quote Link to comment
Skylord123 Posted August 29, 2022 Share Posted August 29, 2022 4 hours ago, Iceman24 said: Did you ever get this fixed? I just updated to 6.10.3 from 6.9.2 and it killed my MQTT. Try deleting your MQTT database file and starting again. My db file got corrupted by improper shutdown (my UPS failed) and this was only way to fix it. May be your issue as well. Quote Link to comment
Iceman24 Posted August 29, 2022 Share Posted August 29, 2022 1 hour ago, Skylord123 said: Try deleting your MQTT database file and starting again. My db file got corrupted by improper shutdown (my UPS failed) and this was only way to fix it. May be your issue as well. Thanks, but I already switched to mosquitto. Most of the way through redoing entities as that got all messed up. I had to delete and recreate, thought I was clear, but now I have Frigate issues where it doesn't work right with MQTT to HA anymore, but I'm so deep in the switch, not sure I want to reverse. Ugh. Quote Link to comment
bdydrp Posted August 30, 2022 Share Posted August 30, 2022 (edited) Where do i find extended logs of Node Red?? My NR container stopped, and the logs from the webui dont go back far enough.. Any one have any suggestions on how i can get a notiifcation when NR stops?? Thanks Edited August 31, 2022 by bdydrp Quote Link to comment
johnny2678 Posted September 3, 2022 Share Posted September 3, 2022 On 8/21/2022 at 2:54 PM, goinsnoopin said: The issue is not with this palette...it is all palettes...installing new or updating. I have gotten some help from the nodered github. Here is the issue as I understand it....link does not work within the nodered container and starting with nodered 3.0.1-1 they moved the location of cache to inside the /data path. Here is the link to the github issue I raised with nodered...has some info that may be helpful: github issue Did you get this working? Github issue you referenced is now closed and says `Solution is to enable hard links in Unraid.`, but hardlinks are already enabled on my server and I'm still getting the same error? Quote Link to comment
leonokio Posted September 7, 2022 Share Posted September 7, 2022 (edited) Hi guys, I got issue when starting mqtt docker app. I have this logs: Warning: store_clean_interval is no longer needed. 1662533991: Error: No error information. 1662533991: Error: Couldn't open database. I tried to reinstall it, without success (not started and same logs) I see that my mosquitto.db is 0Kb, how is that possible? Please, can you help me? thanks! Edited September 7, 2022 by leonokio Quote Link to comment
OsoPolar Posted September 24, 2022 Share Posted September 24, 2022 (edited) HI Guys None of my pallet items will update everything refuses to update. See log here Edited September 24, 2022 by OsoPolar Quote Link to comment
TDA Posted October 1, 2022 Share Posted October 1, 2022 Hello Everyone, I'm triying to setup MQTT. I've started the container ONCE, then stoppen and created: password.txt Unfortunately after I've saved all and triyed to start the container again I've received following: 1664635327: Error in poll: Interrupted system call. 1664635327: mosquitto version 1.4.8 terminating 1664635327: Saving in-memory database to /config/data/mosquitto.db. 1664635327: Error saving in-memory database, unable to open /config/data/mosquitto.db.new for writing. 1664635327: Error: Permission denied. Warning: store_clean_interval is no longer needed. Someone know how to fix this? Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.