Node.js update
-
@homoran said in Node.js update:
iob start admin
Thank you, I am back in business (till the next time)...
-
@ap2017 sagte in Node.js update:
@homoran said in Node.js update:
iob start admin
Thank you, I am back in business (till the next time)...
please read my edit!
-
Now check how to upgrade your operating system to the current release.
'Tessa' is out of any support.
19.1 'Tessa' (LTS) Security Support Ended 2 months and 2 weeks ago (01 Apr 2023)And run your iob on 'stable' not beta-stage.
-
@thomas-braun Here is what I received from Mint support:
Linux Mint 19.1 has reached end of life 2 months ago, so it's good to upgrade it. SO you'll keep getting security updates again for your software. The newest version of node.js on Linux Mint is 12 but you can add the NodeSource PPA on Linux Mint 20.x or 21.x to get node.js 18 (or newer). The instructions are here: https://github.com/nodesource/distribut ... /README.md. Use the Ubuntu instructions. So on Linux Mint 20.x or 21.x you would run this to add node.js 18.x: CODE: SELECT ALL curl -fsSL https://deb.nodesource.com/setup_18.x | sudo -E bash - &&\ sudo apt-get install -y nodejs To upgrade from Linux Mint 19.1 to 20.x or 21.x you can follow the instructions here: viewtopic.php?t=235992. First upgrade to 19.3, then to 20 and if you want upgrade further to 20.3 and then 21. You can see till when each release is supported here: https://linuxmint.com/download_all.php. It will be some work to upgrade, and especially going from 19.3 to 20 is a hassle. Upgrading between major releases is easier and more reliable from 20 to 21. Still, because you're 2 major releases behind it may be recommended to instead do a fresh install of Linux Mint 21.x.I am wondering if it will be better to switch to different Linux version like Ubuntu. How difficult is to port ioBroker to new Linux installation?
-
@ap2017 sagte in Node.js update:
How difficult is to port ioBroker to new Linux installation?
Easy. Backup your current installation, change your OS to a current distribution (I recommend Debian 12 'Bookworm' for running a server), install a plain ioBroker and install your backup. Very easy with the Backitup-Adapter.
-
@ap2017 sagte in Node.js update:
How difficult is to port ioBroker to new Linux installation?
diffi...what?
backup with backitup
install new OS
install iobroker and the latest recommended node with one line
install vis if you use it, because of an actual bug
restore the backup
drink a cup of coffee or what you prefer
ready -
@thomas-braun Sounds doable. Just to be safe I will do it on differed solid state drive in my controller.
My system recovered but I see two issues:
- Not able to start VIS, getting message
File edit.html not found: {}- When updating adapters getting error 25. Tried to follow https://forum.iobroker.net/topic/57337/fehler-25-217-oder-enotempty-bei-adapter-install-update/2 still having error 25
Here is additional info:
ap@AP-Tiny:/opt/iobroker$ iobroker list instances system.adapter.accuweather.0 : accuweather : AP-Tiny - disabled + system.adapter.admin.0 : admin : AP-Tiny - enabled, port: 8081, bind: 0.0.0.0, run as: admi n system.adapter.backitup.0 : backitup : AP-Tiny - disabled system.adapter.cloud.0 : cloud : AP-Tiny - disabled system.adapter.deconz.0 : deconz : AP-Tiny - disabled, port: 8080 + system.adapter.discovery.0 : discovery : AP-Tiny - enabled system.adapter.echarts.0 : echarts : AP-Tiny - enabled system.adapter.flot.0 : flot : AP-Tiny - enabled + system.adapter.history.0 : history : AP-Tiny - enabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : AP-Tiny - enabled + system.adapter.info.0 : info : AP-Tiny - enabled + system.adapter.javascript.0 : javascript : AP-Tiny - enabled system.adapter.mysensors.0 : mysensors : AP-Tiny - disabled, port: 5003, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : AP-Tiny - enabled, port: 8087, bind: 0.0.0.0, run as: admi n + system.adapter.socketio.0 : socketio : AP-Tiny - enabled, port: 8084, bind: 192.168.1.74, run as: admin system.adapter.sonoff.0 : sonoff : AP-Tiny - disabled, port: 1883, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : AP-Tiny - enabled, port: 8443, bind: 0.0.0.0 system.adapter.vis-google-fonts.0 : vis-google-fonts : AP-Tiny - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : AP-Tiny - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : AP-Tiny - enabled system.adapter.vis-material-advanced.0 : vis-material-advanced : AP-Tiny - enabled system.adapter.vis-material-webfont.0 : vis-material-webfont : AP-Tiny - enabled system.adapter.vis-material.0 : vis-material : AP-Tiny - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : AP-Tiny - enabled system.adapter.vis-metro.0 : vis-metro : AP-Tiny - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : AP-Tiny - enabled system.adapter.vis.0 : vis : AP-Tiny - enabled + system.adapter.web.0 : web : AP-Tiny - enabled, port: 8082, bind: 0.0.0.0, run as: admi n + system.adapter.zigbee.0 : zigbee : AP-Tiny - enabled, port: /dev/serial/by-id/usb-ITead_Sonof f_Zigbee_3.0_USB_Dongle_Plus_ba5ba26a021aec119f4c76e5f01c6278-if00-port0 + system.adapter.zwave2.0 : zwave2 : AP-Tiny - enabled + instance is alive -
i stall vis if you use it, because of an actual bug
You have to install vis prior to restoring your backup. Known issue.
- Error 25 ist very generic, it can have a lot of causes for this error.
Try
iob stop iob fix iob start -
- Assuming that I have to delete VIS adapter and add it back. Will all my screens stay in the system?
- Tried this, did not help.
iob stop iob fix iob startHere is detailed error message
$ ./iobroker upgrade echarts Update echarts from @1.4.15 to @1.5.1 NPM version: 8.19.4 Installing iobroker.echarts@1.5.1... (System call) ERROR: npm ERR! code 6npm ERR! path /opt/iobroker/node_modules/iobroker.visnpm ERR! command failednpm ERR! command sh -c -- node main.js --installnpm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2023-06-14T20_57_44_562Z-debug-0.log ERROR: host.AP-Tiny Cannot install iobroker.echarts@1.5.1: 6 ERROR: process exited with code 25 -
@ap2017
Do it via command line interface and debug option:iobroker upgrade echarts --debug -
ap@AP-Tiny:/opt/iobroker$ iobroker upgrade echarts --debug This upgrade of "echarts" will introduce the following changes: ========================================================================== -> 1.5.1: Error handling in JSON data was improved -> 1.5.0: Implemented raw data export ========================================================================== Would you like to upgrade echarts from @1.4.15 to @1.5.1 now? [(y)es, (n)o]: y Update echarts from @1.4.15 to @1.5.1 NPM version: 8.19.4 Installing iobroker.echarts@1.5.1... (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 json3@3.3.2: Please use the native JSON object instead of JSON 3 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 ERR! code 6 npm ERR! path /opt/iobroker/node_modules/iobroker.vis npm ERR! command failed npm ERR! command sh -c -- node main.js --install npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2023-06-14T21_31_07_618Z-debug-0.log 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 json3@3.3.2: Please use the native JSON object instead of JSON 3 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 ERR! code 6 npm ERR! path /opt/iobroker/node_modules/iobroker.vis npm ERR! command failed npm ERR! command sh -c -- node main.js --install npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2023-06-14T21_31_07_618Z-debug-0.log host.AP-Tiny Cannot install iobroker.echarts@1.5.1: 6 ap@AP-Tiny:/opt/iobroker$open 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
open 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
-
@ap2017 sagte in Node.js update:
npm ERR! code 6 npm ERR! path /opt/iobroker/node_modules/iobroker.vis npm ERR! command failed npm ERR! command sh -c -- node main.js --installThe broken vis install blocks any other npm actions.
Tryiobroker upgrade vis@1.4.10Restore your backup again.
And avoid the beta Repository! -
ap@AP-Tiny:~$ iobroker upgrade vis@1.4.10 This downgrade of "vis" will at least remove the following changes: ========================================================================== -> 1.4.16 Corrected connection with "only port" URLs -> 1.4.15 Better check of the offline license -> 1.4.14 Corrected GUI bug -> 1.4.13 The group attributes will be replaced recursively -> 1.4.12 Fixed bug with the export of specific widgets -> 1.4.11 Removed ES6 commands to be supported by older browsers Fixed problem with update of grouped widgets Added web manifest to be able to handle vis as the web app ========================================================================== Would you like to downgrade vis from @1.4.16 to @1.4.10 now? [(y)es, (n)o]: y Update vis from @1.4.16 to @1.4.10 NPM version: 8.19.4 Installing iobroker.vis@1.4.10... (System call) npm ERR! code 6 npm ERR! path /opt/iobroker/node_modules/iobroker.vis npm ERR! command failed npm ERR! command sh -c -- node main.js --install npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2023-06-14T22_28_10_906Z-debug-0.log host.AP-Tiny Cannot install iobroker.vis@1.4.10: 6 ap@AP-Tiny:~$ -
@thomas-braun said in Node.js update:
Restore your backup again.
What do you mean by "Restore your backup again."? I did not do nor restore backup
-
I thought you did change your operating system?
-
@thomas-braun Not yet, it will take me a while
-
Then take your time and come again when done.
-
@ap2017 sagte in Node.js update:
Assuming that I have to delete VIS adapter and add it back
NO!!
Don't delete the vis adapter!Just install a "blank" version before restoring.
-
@thomas-braun Installed latest Ubuntu, restored ioBroker from backup (had to use latest beta controller to match with backup), but new installation of ioBroker is set for stable repositories. Everything seems to be working, including VIS. Having a bit of an issue with info adapter. It works for few seconds then turns red with error messages
2023-06-16 16:09:19.354 - info: info.0 (3352) Plugin sentry Sentry Plugin disabled for this process because sending of statistic data is disabled for the system 2023-06-16 16:09:20.660 - info: info.0 (3352) starting. Version 1.9.26 in /opt/iobroker/node_modules/iobroker.info, node: v18.16.0, js-controller: 5.0.4 2023-06-16 16:09:21.033 - info: info.0 (3352) Reading/updating systemdata. 2023-06-16 16:09:22.167 - info: info.0 (3352) State value to set for "info.0.sysinfo.cpu.info.speed" has to be type "string" but received type "number" 2023-06-16 16:09:22.323 - info: info.0 (3352) State value to set for "info.0.sysinfo.cpu.info.cache-l3" has to be type "number" but received type "string" 2023-06-16 16:09:22.583 - info: info.0 (3352) cpu Temp res = {"main":62,"cores":[62,61],"max":62,"socket":[],"chipset":null} 2023-06-16 16:09:25.284 - info: admin.0 (1913) ==> Connected system.user.admin from ::ffff:192.168.1.244 2023-06-16 16:09:27.785 - info: host.ap-EB1033 Updating repository "Stable (default)" under "http://download.iobroker.net/sources-dist.json" 2023-06-16 16:09:31.423 - info: info.0 (3352) State value to set for "info.0.sysinfo.disks.diskLayout.dev0.size" has to be type "string" but received type "number"Should I change Info objects types to match received vs. set?
-
Usually this would be reported as 'Issue' at the GitHub:
https://github.com/iobroker-community-adapters/ioBroker.info/issues
This may be due to the beta-version of the js-controller. Have seen similar errors with different adapters.
