[gelöst] Jeelink funktioniert nach Update nicht mehr
-
schau mal , ehrlich gesagt auch überlesen
https://forum.iobroker.net/topic/44566/how-to-node-js-iobroker-richtig-updaten-2021-22-edition
-
@glasfaser
Jeelink läuft aber seit gestern absturzfrei und ohne Probleme -
-
@glasfaser
War eine Top-Hilfe von Euch
Ich wäre daran verzweifelt und hätte die Sensoren entsorgt. -
Nach 89 Versuchen ist es durchgelaufen, aber keine Installation
Update sourceanalytix from @0.4.8 to @0.4.14 NPM version: 8.11.0 Installing iobroker.sourceanalytix@0.4.14... (System call) npm WARN deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated uuid@3.4.0: 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 WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated coffee-script@1.12.7: CoffeeScript on NPM has moved to "coffeescript" (no hyphen) npm ERR! code ENOMEM npm ERR! syscall spawn npm ERR! errno -12 npm ERR! spawn ENOMEM npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-08-16T13_58_27_978Z-debug-0.log host.TinkerboardS Cannot install iobroker.sourceanalytix@0.4.14: 244open Request’s Past, Present and Future #3142
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
-
@thomas-braun
Reicht das nicht?
freier Festplattenspeicher: 53%, Gesamte RAM-Auslastung: 802 Mb / Frei: 43% = 870 Mb [Server: TinkerboardS - 37 Prozesse] -
-
pi@TinkerboardS:~$ free -ht total used free shared buff/cache available Mem: 2,0G 1,6G 168M 3,0M 235M 427M Swap: 1,0G 134M 867M Total: 2,9G 1,7G 1,0G -
Ich glaube, ich habe den Übeltäter für den Jeelink-Fehler.
Im Log stand drin, dass man den Fixer laufen lassen soll.
Habe ich gemacht, danach der geliche Fehler mit dem serialport binding.
Die Schritte von gestern wiederholt, jetz läuft er wieder.
