Установка Node-RED на Wiren board 6 Release name wb-2207 Release suite stable

zrin · 28.Декабрь.2022 20:05:19

Не удается установить Node-Red после обновления системы с W2201 на W2207

apt update && apt install -y nodejs git make g++ gcc build-essential

Hit:1 http://security.debian.org stretch/updates InRelease
Ign:2 Index of /debian stretch InRelease
Hit:3 Index of /debian stretch-updates InRelease
Hit:4 Index of /debian stretch Release
Hit:5 http://deb.wirenboard.com/wb6/stretch stable InRelease
Hit:6 Index of /debian stretch-backports InRelease
Reading package lists… Done
Building dependency tree
Reading state information… Done
1 package can be upgraded. Run ‘apt list --upgradable’ to see it.
Reading package lists… Done
Building dependency tree
Reading state information… Done
build-essential is already the newest version (12.3).
g++ is already the newest version (4:6.3.0-4).
gcc is already the newest version (4:6.3.0-4).
git is already the newest version (1:2.11.0-3+deb9u7).
make is already the newest version (4.1-9.1).
The following NEW packages will be installed:
nodejs
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 16.2 MB of archives.
After this operation, 86.4 MB of additional disk space will be used.
Get:1 http://deb.wirenboard.com/wb6/stretch stable/main armhf nodejs armhf 12.19.0-1nodesource1 [16.2 MB]
Fetched 16.2 MB in 8min 51s (30.5 kB/s)
Selecting previously unselected package nodejs.
(Reading database … 30354 files and directories currently installed.)
Preparing to unpack …/nodejs_12.19.0-1nodesource1_armhf.deb …
Unpacking nodejs (12.19.0-1nodesource1) …
Setting up nodejs (12.19.0-1nodesource1) …
root@wirenboard-AE3UHZCX:~# npm install -g --unsafe-perm node-red@2.2
npm WARN deprecated multer@1.4.4: 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.
npm ERR! Unexpected end of JSON input while parsing near ‘…id":"SHA256:jl3bwswu8’

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-12-28T19_41_13_108Z-debug.log

Нужна помощь

Alexander_Rakhman · 29.Декабрь.2022 06:11:29

Здравствуйте!
А точно хватает места?
Что лежит в /root/.npm/_logs/2022-12-28T19_41_13_108Z-debug.log?

zrin · 29.Декабрь.2022 06:19:35

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli ‘/usr/bin/node’,
1 verbose cli ‘/usr/bin/npm’,
1 verbose cli ‘install’,
1 verbose cli ‘-g’,
1 verbose cli ‘–unsafe-perm’,
1 verbose cli ‘node-red@2.2’
1 verbose cli ]
2 info using npm@6.14.8
3 info using node@v12.19.0
4 verbose npm-session 2f8e108ac01f6106
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 http fetch GET 304 https://registry.npmjs.org/node-red 3112ms (from cache)
8 silly pacote range manifest for node-red@2.2 fetched in 3391ms
9 timing stage:loadCurrentTree Completed in 3604ms
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 timing stage:loadIdealTree:cloneCurrentTree Completed in 6ms
13 silly install loadShrinkwrap
14 timing stage:loadIdealTree:loadShrinkwrap Completed in 41ms
15 silly install loadAllDepsIntoIdealTree
16 silly resolveWithNewModule node-red@2.2.3 checking installable status
17 http fetch GET 304 https://registry.npmjs.org/@node-red%2Feditor-api 3303ms (from cache)
18 http fetch GET 304 https://registry.npmjs.org/fs-extra 3022ms (from cache)
19 silly pacote version manifest for @node-red/editor-api@2.2.3 fetched in 3489ms
20 silly resolveWithNewModule @node-red/editor-api@2.2.3 checking installable status
21 http fetch GET 304 https://registry.npmjs.org/basic-auth 3471ms (from cache)
22 http fetch GET 304 https://registry.npmjs.org/bcryptjs 3448ms (from cache)
23 http fetch GET 304 https://registry.npmjs.org/node-red-admin 3266ms (from cache)
24 http fetch GET 304 https://registry.npmjs.org/nopt 3308ms (from cache)
25 http fetch GET 304 https://registry.npmjs.org/@node-red%2Fruntime 3781ms (from cache)
26 http fetch GET 304 https://registry.npmjs.org/@node-red%2Fnodes 3771ms (from cache)
27 silly pacote version manifest for fs-extra@10.0.0 fetched in 3556ms
28 silly resolveWithNewModule fs-extra@10.0.0 checking installable status
29 silly pacote version manifest for bcryptjs@2.4.3 fetched in 3834ms
30 silly resolveWithNewModule bcryptjs@2.4.3 checking installable status
31 silly pacote version manifest for basic-auth@2.0.1 fetched in 3918ms
32 silly resolveWithNewModule basic-auth@2.0.1 checking installable status
33 silly pacote range manifest for node-red-admin@^2.2.3 fetched in 3645ms
34 silly resolveWithNewModule node-red-admin@2.2.4 checking installable status
35 silly pacote version manifest for nopt@5.0.0 fetched in 3650ms
36 silly resolveWithNewModule nopt@5.0.0 checking installable status
37 silly pacote version manifest for @node-red/runtime@2.2.3 fetched in 4196ms
38 silly resolveWithNewModule @node-red/runtime@2.2.3 checking installable status
39 silly pacote version manifest for @node-red/nodes@2.2.3 fetched in 4197ms
40 silly resolveWithNewModule @node-red/nodes@2.2.3 checking installable status
41 http fetch GET 304 https://registry.npmjs.org/express 4048ms (from cache)
42 silly pacote version manifest for express@4.17.2 fetched in 4228ms
43 silly resolveWithNewModule express@4.17.2 checking installable status
44 http fetch GET 304 https://registry.npmjs.org/@node-red%2Futil 4485ms (from cache)
45 silly pacote version manifest for @node-red/util@2.2.3 fetched in 4571ms
46 silly resolveWithNewModule @node-red/util@2.2.3 checking installable status
47 http fetch GET 304 https://registry.npmjs.org/semver 1220ms (from cache)
48 silly pacote version manifest for semver@7.3.5 fetched in 1261ms
49 silly resolveWithNewModule semver@7.3.5 checking installable status
50 http fetch GET 304 https://registry.npmjs.org/bcrypt 1443ms (from cache)
51 silly pacote version manifest for bcrypt@5.0.1 fetched in 1527ms
52 silly resolveWithNewModule bcrypt@5.0.1 checking installable status
53 http fetch GET 304 https://registry.npmjs.org/cors 2096ms (from cache)
54 http fetch GET 304 https://registry.npmjs.org/express-session 2101ms (from cache)
55 http fetch GET 304 https://registry.npmjs.org/memorystore 2114ms (from cache)
56 http fetch GET 304 https://registry.npmjs.org/mime 2118ms (from cache)
57 http fetch GET 304 https://registry.npmjs.org/body-parser 2232ms (from cache)
58 http fetch GET 304 https://registry.npmjs.org/@node-red%2Feditor-client 2273ms (from cache)
59 http fetch GET 304 https://registry.npmjs.org/multer 2229ms (from cache)
60 http fetch GET 304 https://registry.npmjs.org/mustache 2248ms (from cache)
61 silly pacote version manifest for express-session@1.17.2 fetched in 2369ms
62 silly resolveWithNewModule express-session@1.17.2 checking installable status
63 silly pacote version manifest for cors@2.8.5 fetched in 2401ms
64 silly resolveWithNewModule cors@2.8.5 checking installable status
65 silly pacote version manifest for memorystore@1.6.7 fetched in 2398ms
66 silly resolveWithNewModule memorystore@1.6.7 checking installable status
67 silly pacote version manifest for mime@3.0.0 fetched in 2467ms
68 silly resolveWithNewModule mime@3.0.0 checking installable status
69 silly pacote version manifest for body-parser@1.19.1 fetched in 2610ms
70 silly resolveWithNewModule body-parser@1.19.1 checking installable status
71 silly pacote version manifest for multer@1.4.4 fetched in 2574ms
72 warn deprecated multer@1.4.4: 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.
73 silly resolveWithNewModule multer@1.4.4 checking installable status
74 silly pacote version manifest for @node-red/editor-client@2.2.3 fetched in 2667ms
75 silly resolveWithNewModule @node-red/editor-client@2.2.3 checking installable status
76 silly pacote version manifest for mustache@4.2.0 fetched in 2645ms
77 silly resolveWithNewModule mustache@4.2.0 checking installable status
78 http fetch GET 304 https://registry.npmjs.org/oauth2orize 3187ms (from cache)
79 http fetch GET 304 https://registry.npmjs.org/clone 3398ms (from cache)
80 silly pacote version manifest for oauth2orize@1.11.1 fetched in 3449ms
81 silly resolveWithNewModule oauth2orize@1.11.1 checking installable status
82 silly pacote version manifest for clone@2.1.2 fetched in 3646ms
83 silly resolveWithNewModule clone@2.1.2 checking installable status
84 http fetch GET 304 https://registry.npmjs.org/passport-oauth2-client-password 2421ms (from cache)
85 http fetch GET 304 https://registry.npmjs.org/passport-http-bearer 2446ms (from cache)
86 http fetch GET 304 https://registry.npmjs.org/passport 2552ms (from cache)
87 silly pacote version manifest for passport-http-bearer@1.0.1 fetched in 2686ms
88 silly resolveWithNewModule passport-http-bearer@1.0.1 checking installable status
89 silly pacote version manifest for passport-oauth2-client-password@0.1.2 fetched in 2689ms
90 silly resolveWithNewModule passport-oauth2-client-password@0.1.2 checking installable status
91 silly pacote version manifest for passport@0.5.2 fetched in 2780ms
92 silly resolveWithNewModule passport@0.5.2 checking installable status
93 http fetch GET 304 https://registry.npmjs.org/ws 2826ms (from cache)
94 silly pacote version manifest for ws@7.5.6 fetched in 2920ms
95 silly resolveWithNewModule ws@7.5.6 checking installable status
96 http fetch GET 304 https://registry.npmjs.org/json-stringify-safe 1383ms (from cache)
97 http fetch GET 304 https://registry.npmjs.org/jsonata 1367ms (from cache)
98 http fetch GET 304 https://registry.npmjs.org/moment-timezone 1394ms (from cache)
99 http fetch GET 304 https://registry.npmjs.org/lodash.clonedeep 1436ms (from cache)
100 silly pacote version manifest for jsonata@1.8.6 fetched in 1469ms
101 silly resolveWithNewModule jsonata@1.8.6 checking installable status
102 silly pacote version manifest for json-stringify-safe@5.0.1 fetched in 1516ms
103 silly resolveWithNewModule json-stringify-safe@5.0.1 checking installable status
104 silly pacote version manifest for moment-timezone@0.5.34 fetched in 1572ms
105 silly resolveWithNewModule moment-timezone@0.5.34 checking installable status
106 silly pacote range manifest for lodash.clonedeep@^4.5.0 fetched in 1659ms
107 silly resolveWithNewModule lodash.clonedeep@4.5.0 checking installable status
108 http fetch GET 304 https://registry.npmjs.org/i18next 1895ms (from cache)
109 silly pacote version manifest for i18next@21.6.11 fetched in 2127ms
110 silly resolveWithNewModule i18next@21.6.11 checking installable status
111 http fetch GET 304 https://registry.npmjs.org/graceful-fs 1125ms (from cache)
112 http fetch GET 304 https://registry.npmjs.org/jsonfile 1132ms (from cache)
113 http fetch GET 304 https://registry.npmjs.org/universalify 1147ms (from cache)
114 silly pacote range manifest for jsonfile@^6.0.1 fetched in 1189ms
115 silly resolveWithNewModule jsonfile@6.1.0 checking installable status
116 silly pacote range manifest for graceful-fs@^4.2.0 fetched in 1225ms
117 silly resolveWithNewModule graceful-fs@4.2.10 checking installable status
118 silly pacote range manifest for universalify@^2.0.0 fetched in 1201ms
119 silly resolveWithNewModule universalify@2.0.0 checking installable status
120 http fetch GET 304 https://registry.npmjs.org/@babel%2Fruntime 329ms (from cache)
121 silly pacote range manifest for @babel/runtime@^7.12.0 fetched in 388ms
122 silly resolveWithNewModule @babel/runtime@7.20.7 checking installable status
123 http fetch GET 304 https://registry.npmjs.org/regenerator-runtime 679ms (from cache)
124 silly pacote range manifest for regenerator-runtime@^0.13.11 fetched in 710ms
125 silly resolveWithNewModule regenerator-runtime@0.13.11 checking installable status
126 http fetch GET 304 https://registry.npmjs.org/moment 291ms (from cache)
127 silly pacote range manifest for moment@>= 2.9.0 fetched in 354ms
128 silly resolveWithNewModule moment@2.29.4 checking installable status
129 http fetch GET 304 https://registry.npmjs.org/@mapbox%2Fnode-pre-gyp 448ms (from cache)
130 http fetch GET 304 https://registry.npmjs.org/node-addon-api 467ms (from cache)
131 silly pacote range manifest for @mapbox/node-pre-gyp@^1.0.0 fetched in 532ms
132 silly resolveWithNewModule @mapbox/node-pre-gyp@1.0.10 checking installable status
133 silly pacote range manifest for node-addon-api@^3.1.0 fetched in 532ms
134 silly resolveWithNewModule node-addon-api@3.2.1 checking installable status
135 http fetch GET 304 https://registry.npmjs.org/detect-libc 1385ms (from cache)
136 http fetch GET 304 https://registry.npmjs.org/https-proxy-agent 1372ms (from cache)
137 http fetch GET 304 https://registry.npmjs.org/make-dir 1363ms (from cache)
138 http fetch GET 304 https://registry.npmjs.org/node-fetch 1391ms (from cache)
139 http fetch GET 304 https://registry.npmjs.org/rimraf 1385ms (from cache)
140 silly pacote range manifest for detect-libc@^2.0.0 fetched in 1570ms
141 silly resolveWithNewModule detect-libc@2.0.1 checking installable status
142 silly pacote range manifest for https-proxy-agent@^5.0.0 fetched in 1565ms
143 silly resolveWithNewModule https-proxy-agent@5.0.1 checking installable status
144 silly pacote range manifest for make-dir@^3.1.0 fetched in 1565ms
145 silly resolveWithNewModule make-dir@3.1.0 checking installable status
146 silly pacote range manifest for rimraf@^3.0.2 fetched in 1529ms
147 silly resolveWithNewModule rimraf@3.0.2 checking installable status
148 silly pacote range manifest for node-fetch@^2.6.7 fetched in 1583ms
149 silly resolveWithNewModule node-fetch@2.6.7 checking installable status
150 http fetch GET 304 https://registry.npmjs.org/tar 1588ms (from cache)
151 silly pacote range manifest for tar@^6.1.11 fetched in 1812ms
152 silly resolveWithNewModule tar@6.1.13 checking installable status
153 http fetch GET 304 https://registry.npmjs.org/npmlog 1896ms (from cache)
154 silly pacote range manifest for npmlog@^5.0.1 fetched in 1936ms
155 silly resolveWithNewModule npmlog@5.0.1 checking installable status
156 http fetch GET 304 https://registry.npmjs.org/debug 435ms (from cache)
157 http fetch GET 304 https://registry.npmjs.org/agent-base 484ms (from cache)
158 silly pacote range manifest for debug@4 fetched in 491ms
159 silly resolveWithNewModule debug@4.3.4 checking installable status
160 silly pacote range manifest for agent-base@6 fetched in 522ms
161 silly resolveWithNewModule agent-base@6.0.2 checking installable status
162 http fetch GET 304 https://registry.npmjs.org/ms 327ms (from cache)
163 silly pacote version manifest for ms@2.1.2 fetched in 361ms
164 silly resolveWithNewModule ms@2.1.2 checking installable status
165 silly pacote range manifest for semver@^6.0.0 fetched in 45ms
166 silly resolveWithNewModule semver@6.3.0 checking installable status
167 http fetch GET 304 https://registry.npmjs.org/whatwg-url 267ms (from cache)
168 silly pacote range manifest for whatwg-url@^5.0.0 fetched in 338ms
169 silly resolveWithNewModule whatwg-url@5.0.0 checking installable status
170 http fetch GET 304 https://registry.npmjs.org/tr46 350ms (from cache)
171 http fetch GET 304 https://registry.npmjs.org/webidl-conversions 360ms (from cache)
172 silly pacote range manifest for tr46@~0.0.3 fetched in 407ms
173 silly resolveWithNewModule tr46@0.0.3 checking installable status
174 silly pacote range manifest for webidl-conversions@^3.0.0 fetched in 411ms
175 silly resolveWithNewModule webidl-conversions@3.0.1 checking installable status
176 http fetch GET 304 https://registry.npmjs.org/abbrev 292ms (from cache)
177 silly pacote range manifest for abbrev@1 fetched in 322ms
178 silly resolveWithNewModule abbrev@1.1.1 checking installable status
179 http fetch GET 304 https://registry.npmjs.org/are-we-there-yet 753ms (from cache)
180 http fetch GET 304 https://registry.npmjs.org/console-control-strings 768ms (from cache)
181 http fetch GET 304 https://registry.npmjs.org/gauge 791ms (from cache)
182 silly pacote range manifest for are-we-there-yet@^2.0.0 fetched in 840ms
183 silly resolveWithNewModule are-we-there-yet@2.0.0 checking installable status
184 silly pacote range manifest for console-control-strings@^1.1.0 fetched in 844ms
185 silly resolveWithNewModule console-control-strings@1.1.0 checking installable status
186 http fetch GET 304 https://registry.npmjs.org/set-blocking 845ms (from cache)
187 silly pacote range manifest for gauge@^3.0.0 fetched in 896ms
188 silly resolveWithNewModule gauge@3.0.2 checking installable status
189 silly pacote range manifest for set-blocking@^2.0.0 fetched in 921ms
190 silly resolveWithNewModule set-blocking@2.0.0 checking installable status
191 http fetch GET 304 https://registry.npmjs.org/delegates 476ms (from cache)
192 http fetch GET 304 https://registry.npmjs.org/readable-stream 505ms (from cache)
193 silly pacote range manifest for delegates@^1.0.0 fetched in 592ms
194 silly resolveWithNewModule delegates@1.0.0 checking installable status
195 silly pacote range manifest for readable-stream@^3.6.0 fetched in 576ms
196 silly resolveWithNewModule readable-stream@3.6.0 checking installable status
197 http fetch GET 304 https://registry.npmjs.org/inherits 568ms (from cache)
198 http fetch GET 304 https://registry.npmjs.org/string_decoder 614ms (from cache)
199 http fetch GET 304 https://registry.npmjs.org/util-deprecate 656ms (from cache)
200 silly pacote range manifest for inherits@^2.0.3 fetched in 698ms
201 silly resolveWithNewModule inherits@2.0.4 checking installable status
202 silly pacote range manifest for string_decoder@^1.1.1 fetched in 733ms
203 silly resolveWithNewModule string_decoder@1.3.0 checking installable status
204 silly pacote range manifest for util-deprecate@^1.0.1 fetched in 754ms
205 silly resolveWithNewModule util-deprecate@1.0.2 checking installable status
206 http fetch GET 304 https://registry.npmjs.org/safe-buffer 433ms (from cache)
207 silly pacote range manifest for safe-buffer@~5.2.0 fetched in 457ms
208 silly resolveWithNewModule safe-buffer@5.2.1 checking installable status
209 http fetch GET 304 https://registry.npmjs.org/aproba 1299ms (from cache)
210 http fetch GET 304 https://registry.npmjs.org/color-support 1288ms (from cache)
211 http fetch GET 304 https://registry.npmjs.org/has-unicode 1286ms (from cache)
212 http fetch GET 304 https://registry.npmjs.org/object-assign 1284ms (from cache)
213 http fetch GET 304 https://registry.npmjs.org/signal-exit 1286ms (from cache)

zrin · 29.Декабрь.2022 06:20:43

root@wirenboard-AWE7DENS:~# npm install -g --unsafe-perm node-red
npm WARN deprecated multer@1.4.4: 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.
npm WARN deprecated axios@0.27.0: Formdata complete broken, incorrect build size
/usr/bin/node-red → /usr/lib/node_modules/node-red/red.js
/usr/bin/node-red-pi → /usr/lib/node_modules/node-red/bin/node-red-pi

bcrypt@5.0.1 install /usr/lib/node_modules/node-red/node_modules/bcrypt
node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! install response status 404 Not Found on https://github.com/kelektiv/node.bcrypt.js/releases/download/v5.0.1/bcrypt_lib-v5.0.1-napi-v3-linux-arm-glibc.tar.gz
node-pre-gyp WARN Pre-built binaries not installable for bcrypt@5.0.1 and node@12.19.0 (node-v72 ABI, glibc) (falling back to source compile with node-gyp)
node-pre-gyp WARN Hit error response status 404 Not Found on https://github.com/kelektiv/node.bcrypt.js/releases/download/v5.0.1/bcrypt_lib-v5.0.1-napi-v3-linux-arm-glibc.tar.gz
make: Entering directory ‘/usr/lib/node_modules/node-red/node_modules/bcrypt/build’
CC(target) Release/obj.target/nothing/…/node-addon-api/nothing.o
AR(target) Release/obj.target/…/node-addon-api/nothing.a
COPY Release/nothing.a
CXX(target) Release/obj.target/bcrypt_lib/src/blowfish.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt.o
CXX(target) Release/obj.target/bcrypt_lib/src/bcrypt_node.o
SOLINK_MODULE(target) Release/obj.target/bcrypt_lib.node
COPY Release/bcrypt_lib.node
COPY /usr/lib/node_modules/node-red/node_modules/bcrypt/lib/binding/napi-v3/bcrypt_lib.node
TOUCH Release/obj.target/action_after_build.stamp
make: Leaving directory ‘/usr/lib/node_modules/node-red/node_modules/bcrypt/build’

node-red@2.2.2
added 293 packages from 376 contributors in 130.962s
root@wirenboard-AWE7DENS:~# nano /etc/systemd/system/nodered.service
root@wirenboard-AWE7DENS:~# systemctl start nodered
root@wirenboard-AWE7DENS:~# systemctl status nodered
● nodered.service - Node-RED graphical event wiring tool
Loaded: loaded (/etc/systemd/system/nodered.service; disabled; vendor preset: enabled)
Active: active (running) since Mon 2022-06-06 10:57:52 UTC; 5s ago
Main PID: 17691 (node)
CGroup: /system.slice/nodered.service
├─17691 node /usr/bin/node-red --max_old_space_size=256
└─17737 npm

Jun 06 10:57:52 wirenboard-AWE7DENS systemd[1]: Started Node-RED graphical event wiring tool.
Jun 06 10:57:57 wirenboard-AWE7DENS Node-RED[17691]: 6 Jun 10:57:57 - [info]
Jun 06 10:57:57 wirenboard-AWE7DENS Node-RED[17691]: Welcome to Node-RED
Jun 06 10:57:57 wirenboard-AWE7DENS Node-RED[17691]: ===================
Jun 06 10:57:57 wirenboard-AWE7DENS Node-RED[17691]: 6 Jun 10:57:57 - [info] Node-RED version: v2.2.2
Jun 06 10:57:57 wirenboard-AWE7DENS Node-RED[17691]: 6 Jun 10:57:57 - [info] Node.js version: v12.19.0
Jun 06 10:57:57 wirenboard-AWE7DENS Node-RED[17691]: 6 Jun 10:57:57 - [info] Linux 5.10.35-wb104 arm LE

Alexander_Rakhman · 29.Декабрь.2022 06:21:12

Окей, а что говорит df про место на диске?

zrin · 29.Декабрь.2022 06:22:10

load_average_1min

0 . 72tasks

load_average_5min

0 . 9tasks

load_average_15min

0 . 93tasks

ram_available

369 MiB

ram_used

139 MiB

ram_total

494 MiB

swap_total

255 MiB

swap_used

0 MiB

dev_root_used_space

658 MiB

dev_root_total_space

976 MiB

dev_root_linked_on

/dev/mmcblk0p3

data_used_space

249 MiB

data_total_space

1296 MiB

zrin · 29.Декабрь.2022 06:22:56

df

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/root 999320 673520 256988 73% /
devtmpfs 244696 0 244696 0% /dev
tmpfs 253400 0 253400 0% /dev/shm
tmpfs 253400 520 252880 1% /run
tmpfs 5120 0 5120 0% /run/lock
tmpfs 253400 0 253400 0% /sys/fs/cgroup
/dev/mmcblk0p6 1326868 254756 986660 21% /mnt/data
tmpfs 50680 0 50680 0% /run/user/0

zrin · 29.Декабрь.2022 06:24:35

Почему должен забиться диск если только переустановил прошивку с возвратом на заводские настройки?

zrin · 29.Декабрь.2022 06:27:19

Почему переустанавливал?
NodeRed начал глючить тормозить

Alexander_Rakhman · 29.Декабрь.2022 06:59:51

Про возврат на заводские настройки ничего не было
В любом случае, места достаточно.

Это довольно распространённая ошибка при установке Node-RED (да и других пакетов nodejs) на что угодно.

Попробуйте для начала сделать npm clean cache --force.

zrin · 29.Декабрь.2022 07:08:06

npm clean cache --force

npm WARN using --force I sure hope you know what you are doing.

Usage: npm

where is one of:
access, adduser, audit, bin, bugs, c, cache, ci, cit,
clean-install, clean-install-test, completion, config,
create, ddp, dedupe, deprecate, dist-tag, docs, doctor,
edit, explore, fund, get, help, help-search, hook, i, init,
install, install-ci-test, install-test, it, link, list, ln,
login, logout, ls, org, outdated, owner, pack, ping, prefix,
profile, prune, publish, rb, rebuild, repo, restart, root,
run, run-script, s, se, search, set, shrinkwrap, star,
stars, start, stop, t, team, test, token, tst, un,
uninstall, unpublish, unstar, up, update, v, version, view,
whoami

npm -h quick help on
npm -l display full usage info
npm help search for help on
npm help npm involved overview

Specify configs in the ini-formatted file:
/root/.npmrc
or on the command line via: npm --key value
Config info can be viewed via: npm help config

npm@6.14.8 /usr/lib/node_modules/npm

Alexander_Rakhman · 29.Декабрь.2022 07:21:54

Так. Пробовали ещё раз запустить установку нодреда?

zrin · 29.Декабрь.2022 07:23:48

тоже самое

npm install -g --unsafe-perm node-red@2.2

npm WARN deprecated multer@1.4.4: 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.
npm ERR! Unexpected end of JSON input while parsing near ‘…id":"SHA256:jl3bwswu8’

npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2022-12-29T07_10_36_917Z-debug.log

zrin · 29.Декабрь.2022 07:33:58

В принципе написано же что делать
Только как я могу это сделать пока не представляю

zrin · 29.Декабрь.2022 09:35:47

вот в этой теме была аналогичная ошибка

только как был решен вопрос до конца не понятен
особенно не понятны слова

…он не нашёл пакет в одном из мест, потом нашёл его в другом…

zrin · 29.Декабрь.2022 11:47:25

Прием

zrin · 29.Декабрь.2022 15:49:35

Пожалуйста, обновите как минимум Node.js 6 и версию 1.4.4-lts.1 Multer.

Как это сделать?

zrin · 29.Декабрь.2022 17:46:03

Как перейти

Этот релиз прошивки контроллера основан на новом Debian Linux 11 (Bullseye).

Команды для перехода:

Обновите пакеты используемого вами дистрибутива — это должен быть testing:

apt update && apt upgrade

Запустите переход на Bullseye, в разделе /root должно быть не меньше 300 Мбайт свободного места, процедура продлится около 45 минут:

wb-release --update-debian-release

Почему последнее не работает?

Alexander_Rakhman · 29.Декабрь.2022 18:16:46

Пытаюсь воспроизвести проблему с установкой нодреда у себя.
Чтобы перейти на Bullseye, надо предварительно перейти в ветку testing. Вы это сделали?

zrin · 29.Декабрь.2022 18:38:23

не найду на сайте testing