ioBroker Backup wieder einspielen
-
@thomas-braun said in ioBroker Backup wieder einspielen:
load average: 12.11, 9.94, 6.40Was ist denn da los? Bei 4 ist die Kiste eigentlich dicht.
ich verstehe es leider nicht
-
@federal sagte in ioBroker Backup wieder einspielen:
ich verstehe es leider nicht
Ich auch nicht.
Die drei Zahlen sind die Auslastung der CPU im Moment, der letzten 5 und der letzten 15 Minuten. 1 ist dabei ein Kern, da dein RPI derer 4 hat ist 4 halt = 100%.
Irgendwas zieht da bei dir massiv Ressourcen, insbesondere da da vom iobroker her eigentlich nicht viel läuft macht das stutzig.Mit
topschauen was da los ist.
Edit: Mal zum Vergleich mein Rpi 4 / 8 GB:
echad@chet:~ $ uptime 20:42:40 up 8 days, 20:36, 2 users, load average: 0.42, 0.37, 0.35 -
@federal sagte in ioBroker Backup wieder einspielen:
ich verstehe es leider nicht
Ich auch nicht.
Die drei Zahlen sind die Auslastung der CPU im Moment, der letzten 5 und der letzten 15 Minuten. 1 ist dabei ein Kern, da dein RPI derer 4 hat ist 4 halt = 100%.
Irgendwas zieht da bei dir massiv Ressourcen, insbesondere da da vom iobroker her eigentlich nicht viel läuft macht das stutzig.Mit
topschauen was da los ist.
Edit: Mal zum Vergleich mein Rpi 4 / 8 GB:
echad@chet:~ $ uptime 20:42:40 up 8 days, 20:36, 2 users, load average: 0.42, 0.37, 0.35@thomas-braun said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
ich verstehe es leider nicht
Ich auch nicht.
Die drei Zahlen sind die Auslastung der CPU im Moment, der letzten 5 und der letzten 15 Minuten. 1 ist dabei ein Kern, da dein RPI derer 4 hat ist 4 halt = 100%.
Irgendwas zieht da bei dir massiv Ressourcen, insbesondere da da vom iobroker her eigentlich nicht viel läuft macht das stutzig.Mit
topschauen was da los ist.
Edit: Mal zum Vergleich mein Rpi 4 / 8 GB:
echad@chet:~ $ uptime 20:42:40 up 8 days, 20:36, 2 users, load average: 0.42, 0.37, 0.35
-
@thomas-braun said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
ich verstehe es leider nicht
Ich auch nicht.
Die drei Zahlen sind die Auslastung der CPU im Moment, der letzten 5 und der letzten 15 Minuten. 1 ist dabei ein Kern, da dein RPI derer 4 hat ist 4 halt = 100%.
Irgendwas zieht da bei dir massiv Ressourcen, insbesondere da da vom iobroker her eigentlich nicht viel läuft macht das stutzig.Mit
topschauen was da los ist.
Edit: Mal zum Vergleich mein Rpi 4 / 8 GB:
echad@chet:~ $ uptime 20:42:40 up 8 days, 20:36, 2 users, load average: 0.42, 0.37, 0.35Nach dem reboot schaut es gesünder aus.
-
Nach dem reboot schaut es gesünder aus.
@thomas-braun said in ioBroker Backup wieder einspielen:
Nach dem reboot schaut es gesünder aus.
iob ist immer noch nicht erreichbar.
Ich muss mich ausklinken. Danke an alle. -
@thomas-braun said in ioBroker Backup wieder einspielen:
Nach dem reboot schaut es gesünder aus.
iob ist immer noch nicht erreichbar.
Ich muss mich ausklinken. Danke an alle.@federal sagte in ioBroker Backup wieder einspielen:
iob ist immer noch nicht erreichbar.
Er läuft ja auch nicht.
-
@federal sagte in ioBroker Backup wieder einspielen:
iob ist immer noch nicht erreichbar.
Er läuft ja auch nicht.
@thomas-braun said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
iob ist immer noch nicht erreichbar.
Er läuft ja auch nicht.
lässt sich auch nicht starten. Was kann ich noch tun?
das zeigt die Statusanzeige
pi@raspberrypi:~ $ iobroker status node:internal/modules/cjs/loader:1024 throw err; ^ Error: Cannot find module 'buffer-equal-constant-time' Require stack: - /opt/iobroker/node_modules/jwa/index.js - /opt/iobroker/node_modules/jws/lib/sign-stream.js - /opt/iobroker/node_modules/jws/index.js - /opt/iobroker/node_modules/jsonwebtoken/decode.js - /opt/iobroker/node_modules/jsonwebtoken/index.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1021:15) at Function.Module._load (node:internal/modules/cjs/loader:866:27) at Module.require (node:internal/modules/cjs/loader:1093:19) at require (node:internal/modules/cjs/helpers:108:18) at Object.<anonymous> (/opt/iobroker/node_modules/jwa/index.js:1:19) at Module._compile (node:internal/modules/cjs/loader:1191:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1245:10) at Module.load (node:internal/modules/cjs/loader:1069:32) at Function.Module._load (node:internal/modules/cjs/loader:904:12) at Module.require (node:internal/modules/cjs/loader:1093:19) { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/jwa/index.js', '/opt/iobroker/node_modules/jws/lib/sign-stream.js', '/opt/iobroker/node_modules/jws/index.js', '/opt/iobroker/node_modules/jsonwebtoken/decode.js', '/opt/iobroker/node_modules/jsonwebtoken/index.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/index.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' -
@thomas-braun said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
iob ist immer noch nicht erreichbar.
Er läuft ja auch nicht.
lässt sich auch nicht starten. Was kann ich noch tun?
das zeigt die Statusanzeige
pi@raspberrypi:~ $ iobroker status node:internal/modules/cjs/loader:1024 throw err; ^ Error: Cannot find module 'buffer-equal-constant-time' Require stack: - /opt/iobroker/node_modules/jwa/index.js - /opt/iobroker/node_modules/jws/lib/sign-stream.js - /opt/iobroker/node_modules/jws/index.js - /opt/iobroker/node_modules/jsonwebtoken/decode.js - /opt/iobroker/node_modules/jsonwebtoken/index.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1021:15) at Function.Module._load (node:internal/modules/cjs/loader:866:27) at Module.require (node:internal/modules/cjs/loader:1093:19) at require (node:internal/modules/cjs/helpers:108:18) at Object.<anonymous> (/opt/iobroker/node_modules/jwa/index.js:1:19) at Module._compile (node:internal/modules/cjs/loader:1191:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1245:10) at Module.load (node:internal/modules/cjs/loader:1069:32) at Function.Module._load (node:internal/modules/cjs/loader:904:12) at Module.require (node:internal/modules/cjs/loader:1093:19) { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/jwa/index.js', '/opt/iobroker/node_modules/jws/lib/sign-stream.js', '/opt/iobroker/node_modules/jws/index.js', '/opt/iobroker/node_modules/jsonwebtoken/decode.js', '/opt/iobroker/node_modules/jsonwebtoken/index.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/index.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'Last login: Tue Apr 4 15:43:58 2023 from 100.75.198.95 echad@chet:~ $ cd /opt/iobroker/ echad@chet:/opt/iobroker $ npm ls buffer-equal-constant-time iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.backitup@2.6.16 │ └─┬ google-auth-library@8.7.0 │ └─┬ jws@4.0.0 │ └─┬ jwa@2.0.0 │ └── buffer-equal-constant-time@1.0.1 └─┬ iobroker.js-controller@5.0.1-alpha.0-20230403-fd495c2e └─┬ jsonwebtoken@9.0.0 └─┬ jws@3.2.2 └─┬ jwa@1.4.1 └── buffer-equal-constant-time@1.0.1 deduped echad@chet:/opt/iobroker $Ich würde den js-controller nochmal installieren.
-
Last login: Tue Apr 4 15:43:58 2023 from 100.75.198.95 echad@chet:~ $ cd /opt/iobroker/ echad@chet:/opt/iobroker $ npm ls buffer-equal-constant-time iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.backitup@2.6.16 │ └─┬ google-auth-library@8.7.0 │ └─┬ jws@4.0.0 │ └─┬ jwa@2.0.0 │ └── buffer-equal-constant-time@1.0.1 └─┬ iobroker.js-controller@5.0.1-alpha.0-20230403-fd495c2e └─┬ jsonwebtoken@9.0.0 └─┬ jws@3.2.2 └─┬ jwa@1.4.1 └── buffer-equal-constant-time@1.0.1 deduped echad@chet:/opt/iobroker $Ich würde den js-controller nochmal installieren.
@thomas-braun said in ioBroker Backup wieder einspielen:
Last login: Tue Apr 4 15:43:58 2023 from 100.75.198.95 echad@chet:~ $ cd /opt/iobroker/ echad@chet:/opt/iobroker $ npm ls buffer-equal-constant-time iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.backitup@2.6.16 │ └─┬ google-auth-library@8.7.0 │ └─┬ jws@4.0.0 │ └─┬ jwa@2.0.0 │ └── buffer-equal-constant-time@1.0.1 └─┬ iobroker.js-controller@5.0.1-alpha.0-20230403-fd495c2e └─┬ jsonwebtoken@9.0.0 └─┬ jws@3.2.2 └─┬ jwa@1.4.1 └── buffer-equal-constant-time@1.0.1 deduped echad@chet:/opt/iobroker $Ich würde den js-controller nochmal installieren.
wie mache ich das?
-
@thomas-braun said in ioBroker Backup wieder einspielen:
Last login: Tue Apr 4 15:43:58 2023 from 100.75.198.95 echad@chet:~ $ cd /opt/iobroker/ echad@chet:/opt/iobroker $ npm ls buffer-equal-constant-time iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.backitup@2.6.16 │ └─┬ google-auth-library@8.7.0 │ └─┬ jws@4.0.0 │ └─┬ jwa@2.0.0 │ └── buffer-equal-constant-time@1.0.1 └─┬ iobroker.js-controller@5.0.1-alpha.0-20230403-fd495c2e └─┬ jsonwebtoken@9.0.0 └─┬ jws@3.2.2 └─┬ jwa@1.4.1 └── buffer-equal-constant-time@1.0.1 deduped echad@chet:/opt/iobroker $Ich würde den js-controller nochmal installieren.
wie mache ich das?
@federal sagte in ioBroker Backup wieder einspielen:
wie mache ich das?
-
@thomas-braun said in ioBroker Backup wieder einspielen:
Last login: Tue Apr 4 15:43:58 2023 from 100.75.198.95 echad@chet:~ $ cd /opt/iobroker/ echad@chet:/opt/iobroker $ npm ls buffer-equal-constant-time iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.backitup@2.6.16 │ └─┬ google-auth-library@8.7.0 │ └─┬ jws@4.0.0 │ └─┬ jwa@2.0.0 │ └── buffer-equal-constant-time@1.0.1 └─┬ iobroker.js-controller@5.0.1-alpha.0-20230403-fd495c2e └─┬ jsonwebtoken@9.0.0 └─┬ jws@3.2.2 └─┬ jwa@1.4.1 └── buffer-equal-constant-time@1.0.1 deduped echad@chet:/opt/iobroker $Ich würde den js-controller nochmal installieren.
wie mache ich das?
iob stop iob fix cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller iob start -
iob stop iob fix cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller iob start@thomas-braun said in ioBroker Backup wieder einspielen:
iob stop iob fix cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller iob start -
@thomas-braun said in ioBroker Backup wieder einspielen:
iob stop iob fix cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller iob startWie immer bei Linux:
Warten bis wieder eine Eingabezeile erscheint, erst dann ist der Task erledigt. -
Wie immer bei Linux:
Warten bis wieder eine Eingabezeile erscheint, erst dann ist der Task erledigt.@thomas-braun said in ioBroker Backup wieder einspielen:
Wie immer bei Linux:
Warten bis wieder eine Eingabezeile erscheint, erst dann ist der Task erledigt.Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-contr oller npm WARN deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the o ne that's built-in. npm WARN deprecated @types/bl@5.1.0: This is a stub types definition. bl provide s its own type definitions, so you do not need this installed. npm WARN deprecated request-promise-native@1.0.9: request-promise-native has bee n deprecated because it extends the now deprecated request package, see https:// github.com/request/request/issues/3142 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 b ecause it extends the now deprecated request package, see https://github.com/req uest/request/issues/3142 npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JS ON 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 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://git hub.com/request/request/issues/3142 npm WARN deprecated axios@0.19.2: Critical security vulnerability fixed in v0.21 .1. For more information, see https://github.com/axios/axios/pull/3410 (##################) ⠸ reify:aws-sdk: timing reifyNode:node_modules/typescript (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C npm ERR! path /opt/iobroker/node_modules/iobroker.javascript npm ERR! command failed npm ERR! signal SIGINT npm ERR! command sh -c -- node ./install/installTypings.js npm ERR! Installing NodeJS typings... npm ERR! latest @types: 18, installed node: 16 npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2023-04-04T16_30_22_609Z-debug-0.log pi@raspberrypi:/opt/iobroker $ iob start pi@raspberrypi:/opt/iobroker $ iob protokol node:internal/modules/cjs/loader:1024 throw err; ^ Error: Cannot find module 'buffer-equal-constant-time' Require stack: - /opt/iobroker/node_modules/jwa/index.js - /opt/iobroker/node_modules/jws/lib/sign-stream.js - /opt/iobroker/node_modules/jws/index.js - /opt/iobroker/node_modules/jsonwebtoken/decode.js - /opt/iobroker/node_modules/jsonwebtoken/index.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1021:15) at Function.Module._load (node:internal/modules/cjs/loader:866:27) at Module.require (node:internal/modules/cjs/loader:1093:19) at require (node:internal/modules/cjs/helpers:108:18) at Object.<anonymous> (/opt/iobroker/node_modules/jwa/index.js:1:19) at Module._compile (node:internal/modules/cjs/loader:1191:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1245:10) at Module.load (node:internal/modules/cjs/loader:1069:32) at Function.Module._load (node:internal/modules/cjs/loader:904:12) at Module.require (node:internal/modules/cjs/loader:1093:19) { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/jwa/index.js', '/opt/iobroker/node_modules/jws/lib/sign-stream.js', '/opt/iobroker/node_modules/jws/index.js', '/opt/iobroker/node_modules/jsonwebtoken/decode.js', '/opt/iobroker/node_modules/jsonwebtoken/index.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/index.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' ] } pi@raspberrypi:/opt/iobroker $ -
@thomas-braun said in ioBroker Backup wieder einspielen:
iob stop iob fix cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller iob start -
@thomas-braun said in ioBroker Backup wieder einspielen:
Wie immer bei Linux:
Warten bis wieder eine Eingabezeile erscheint, erst dann ist der Task erledigt.Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-contr oller npm WARN deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the o ne that's built-in. npm WARN deprecated @types/bl@5.1.0: This is a stub types definition. bl provide s its own type definitions, so you do not need this installed. npm WARN deprecated request-promise-native@1.0.9: request-promise-native has bee n deprecated because it extends the now deprecated request package, see https:// github.com/request/request/issues/3142 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 b ecause it extends the now deprecated request package, see https://github.com/req uest/request/issues/3142 npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JS ON 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 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://git hub.com/request/request/issues/3142 npm WARN deprecated axios@0.19.2: Critical security vulnerability fixed in v0.21 .1. For more information, see https://github.com/axios/axios/pull/3410 (##################) ⠸ reify:aws-sdk: timing reifyNode:node_modules/typescript (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C npm ERR! path /opt/iobroker/node_modules/iobroker.javascript npm ERR! command failed npm ERR! signal SIGINT npm ERR! command sh -c -- node ./install/installTypings.js npm ERR! Installing NodeJS typings... npm ERR! latest @types: 18, installed node: 16 npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2023-04-04T16_30_22_609Z-debug-0.log pi@raspberrypi:/opt/iobroker $ iob start pi@raspberrypi:/opt/iobroker $ iob protokol node:internal/modules/cjs/loader:1024 throw err; ^ Error: Cannot find module 'buffer-equal-constant-time' Require stack: - /opt/iobroker/node_modules/jwa/index.js - /opt/iobroker/node_modules/jws/lib/sign-stream.js - /opt/iobroker/node_modules/jws/index.js - /opt/iobroker/node_modules/jsonwebtoken/decode.js - /opt/iobroker/node_modules/jsonwebtoken/index.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1021:15) at Function.Module._load (node:internal/modules/cjs/loader:866:27) at Module.require (node:internal/modules/cjs/loader:1093:19) at require (node:internal/modules/cjs/helpers:108:18) at Object.<anonymous> (/opt/iobroker/node_modules/jwa/index.js:1:19) at Module._compile (node:internal/modules/cjs/loader:1191:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1245:10) at Module.load (node:internal/modules/cjs/loader:1069:32) at Function.Module._load (node:internal/modules/cjs/loader:904:12) at Module.require (node:internal/modules/cjs/loader:1093:19) { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/jwa/index.js', '/opt/iobroker/node_modules/jws/lib/sign-stream.js', '/opt/iobroker/node_modules/jws/index.js', '/opt/iobroker/node_modules/jsonwebtoken/decode.js', '/opt/iobroker/node_modules/jsonwebtoken/index.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/index.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' ] } pi@raspberrypi:/opt/iobroker $@federal sagte in ioBroker Backup wieder einspielen:
npm ERR! latest @types: 18, installed node: 16
Geh mal auf nodejs 18.
-
@federal sagte in ioBroker Backup wieder einspielen:
npm ERR! latest @types: 18, installed node: 16
Geh mal auf nodejs 18.
@thomas-braun said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
npm ERR! latest @types: 18, installed node: 16
Geh mal auf nodejs 18.
kann ich die Eingabe dazu haben?
-
@thomas-braun said in ioBroker Backup wieder einspielen:
Wie immer bei Linux:
Warten bis wieder eine Eingabezeile erscheint, erst dann ist der Task erledigt.Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@raspberrypi:~ $ cd /opt/iobroker pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-contr oller npm WARN deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the o ne that's built-in. npm WARN deprecated @types/bl@5.1.0: This is a stub types definition. bl provide s its own type definitions, so you do not need this installed. npm WARN deprecated request-promise-native@1.0.9: request-promise-native has bee n deprecated because it extends the now deprecated request package, see https:// github.com/request/request/issues/3142 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 b ecause it extends the now deprecated request package, see https://github.com/req uest/request/issues/3142 npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JS ON 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 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 hav e a low-severity ReDos regression when used in a Node.js environment. It is reco mmended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/iss ues/797) npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older v ersions may use Math.random() in certain circumstances, which is known to be pro blematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://git hub.com/request/request/issues/3142 npm WARN deprecated axios@0.19.2: Critical security vulnerability fixed in v0.21 .1. For more information, see https://github.com/axios/axios/pull/3410 (##################) ⠸ reify:aws-sdk: timing reifyNode:node_modules/typescript (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C (##################) ⠼ reify:aws-sdk: timing reifyNode:node_modules/typescript C npm ERR! path /opt/iobroker/node_modules/iobroker.javascript npm ERR! command failed npm ERR! signal SIGINT npm ERR! command sh -c -- node ./install/installTypings.js npm ERR! Installing NodeJS typings... npm ERR! latest @types: 18, installed node: 16 npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2023-04-04T16_30_22_609Z-debug-0.log pi@raspberrypi:/opt/iobroker $ iob start pi@raspberrypi:/opt/iobroker $ iob protokol node:internal/modules/cjs/loader:1024 throw err; ^ Error: Cannot find module 'buffer-equal-constant-time' Require stack: - /opt/iobroker/node_modules/jwa/index.js - /opt/iobroker/node_modules/jws/lib/sign-stream.js - /opt/iobroker/node_modules/jws/index.js - /opt/iobroker/node_modules/jsonwebtoken/decode.js - /opt/iobroker/node_modules/jsonwebtoken/index.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js - /opt/iobroker/node_modules/@iobroker/js-controller-common/index.js - /opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js - /opt/iobroker/node_modules/iobroker.js-controller/iobroker.js at Function.Module._resolveFilename (node:internal/modules/cjs/loader:1021:15) at Function.Module._load (node:internal/modules/cjs/loader:866:27) at Module.require (node:internal/modules/cjs/loader:1093:19) at require (node:internal/modules/cjs/helpers:108:18) at Object.<anonymous> (/opt/iobroker/node_modules/jwa/index.js:1:19) at Module._compile (node:internal/modules/cjs/loader:1191:14) at Object.Module._extensions..js (node:internal/modules/cjs/loader:1245:10) at Module.load (node:internal/modules/cjs/loader:1069:32) at Function.Module._load (node:internal/modules/cjs/loader:904:12) at Module.require (node:internal/modules/cjs/loader:1093:19) { code: 'MODULE_NOT_FOUND', requireStack: [ '/opt/iobroker/node_modules/jwa/index.js', '/opt/iobroker/node_modules/jws/lib/sign-stream.js', '/opt/iobroker/node_modules/jws/index.js', '/opt/iobroker/node_modules/jsonwebtoken/decode.js', '/opt/iobroker/node_modules/jsonwebtoken/index.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/lib/common/tools.js', '/opt/iobroker/node_modules/@iobroker/js-controller-common/index.js', '/opt/iobroker/node_modules/iobroker.js-controller/lib/setup.js', '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' ] } pi@raspberrypi:/opt/iobroker $ -
@federal sagte in ioBroker Backup wieder einspielen:
pi@raspberrypi:/opt/iobroker $ iob protokol
wo hast du denn diesen Befehl her !?
@glasfaser said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
pi@raspberrypi:/opt/iobroker $ iob protokol
wo hast du denn diesen Befehl her !?
sorry. Habe mit iobroker status verwechselt
-
@thomas-braun said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
npm ERR! latest @types: 18, installed node: 16
Geh mal auf nodejs 18.
kann ich die Eingabe dazu haben?
@federal sagte in ioBroker Backup wieder einspielen:
@thomas-braun said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
npm ERR! latest @types: 18, installed node: 16
Geh mal auf nodejs 18.
kann ich die Eingabe dazu haben?
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
267
Online32.7k
Benutzer82.6k
Themen1.3m
Beiträge