<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[iobroker (buanet docker) adapter lassen sich nicht updaten]]></title><description><![CDATA[<p dir="auto">Hallo,<br />
ich habe momentan das Problem, dass sich Adapter nicht aktualisieren lassen, weder über das WEB-Frontend noch auf der Konsole.</p>
<p dir="auto">Beispiel</p>
<pre><code>root@iobroker:/opt/iobroker# iob update | grep sql
Adapter    "sql"          : 2.2.0    , installed 2.1.8  [Updatable]

root@iobroker:/opt/iobroker# iob upgrade

This upgrade of "sql" will introduce the following changes:
==========================================================================
-&gt; 2.2.0:
IMPORTANT: Node.js 14.x is now needed at minimum!
Fix potential crash cases with upcoming js-controller versions
==========================================================================

Would you like to upgrade sql from @2.1.8 to @2.2.0 now? [(y)es, (n)o]: y
Update sql from @2.1.8 to @2.2.0
host.iobroker Adapter "system.adapter.sql.1" is stopped.
NPM version: 8.15.0
Installing iobroker.sql@2.2.0... (System call)
upload [13] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/de/translations.json i18n/de/translations.json application/json
upload [12] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/en/translations.json i18n/en/translations.json application/json
upload [11] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/es/translations.json i18n/es/translations.json application/json
upload [10] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
upload [9] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/it/translations.json i18n/it/translations.json application/json
upload [8] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
upload [7] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
upload [6] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
upload [5] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
upload [4] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
upload [3] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/jsonConfig.json jsonConfig.json application/json
upload [2] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/jsonCustom.json jsonCustom.json application/json
upload [1] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/sql.png sql.png image/png
upload [0] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/words.js words.js application/javascript
host.iobroker Adapter "system.adapter.sql.1" is started

root@iobroker:/opt/iobroker# iob update | grep Updatable
Adapter    "history"      : 2.2.4    , installed 2.2.3  [Updatable]
Adapter    "influxdb"     : 3.2.0    , installed 3.1.8  [Updatable]
Adapter    "info"         : 1.9.21   , installed 1.9.19 [Updatable]
Adapter    "sql"          : 2.2.0    , installed 2.1.8  [Updatable]
</code></pre>
<p dir="auto">Das gleiche bei den anderen Adaptern.<br />
Im log stehen keinerlei Fehlermeldungen diesbezüglich.</p>
<p dir="auto">Docker Image-Version:<br />
"Image": "buanet/iobroker:latest-v7" (label "org.opencontainers.image.version": "v7.0.1")</p>
<p dir="auto">Node-Version: v16.17.0</p>
<p dir="auto">Ich bin vor einigen Tagen von der docker-image Version von latest-v6 auf latest-v7 gewechselt, da gab es das<br />
Problem noch nicht .</p>
<p dir="auto">Beim Starten des Containers fallen mir auch keine Fehlermeldungen auf, die auf Probleme diesbezüglich hinweisen.</p>
<pre><code>--------------------------------------------------------------------------------
-----             Step 2 of 5: Detecting ioBroker installation             -----
--------------------------------------------------------------------------------

Existing installation of ioBroker detected in /opt/iobroker.

--------------------------------------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------

(Re)Setting folder permissions (This might take a while! Please be patient!)... Done.

Fixing "sudo-bug" by replacing sudo in iobroker with gosu... Done.

--------------------------------------------------------------------------------
-----                Step 4 of 5: Applying special settings                -----
--------------------------------------------------------------------------------

Some adapters have special requirements/ settings which can be activated by the use of environment variables.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).

Checking multihost setup...
Multihost is set as "master" by ENV and no external objects db is set.
Setting host of objects db to "0.0.0.0" to allow external communication... Done.
Multihost is set as "master" by ENV and no external states db is set.
Setting host of states db to "0.0.0.0" to allow external communication... Done.
Done.

--------------------------------------------------------------------------------
-----                    Step 5 of 5: ioBroker startup                     -----
--------------------------------------------------------------------------------

Starting ioBroker...

2022-09-22 07:52:24.920  - ^[[32minfo^[[39m: host.iobroker iobroker.js-controller version 4.0.23 js-controller starting
2022-09-22 07:52:24.923  - ^[[32minfo^[[39m: host.iobroker Copyright (c) 2014-2022 bluefox, 2014 hobbyquaker
2022-09-22 07:52:24.923  - ^[[32minfo^[[39m: host.iobroker hostname: iobroker, node: v16.17.0
2022-09-22 07:52:24.923  - ^[[32minfo^[[39m: host.iobroker ip addresses: 192.168.0.6
</code></pre>
<p dir="auto">Kennt jemand das Problem bzw. hat jemand ggf. eine Lösung dafür ?</p>
]]></description><link>https://forum.iobroker.net/topic/58200/iobroker-buanet-docker-adapter-lassen-sich-nicht-updaten</link><generator>RSS for Node</generator><lastBuildDate>Mon, 18 May 2026 16:43:00 GMT</lastBuildDate><atom:link href="https://forum.iobroker.net/topic/58200.rss" rel="self" type="application/rss+xml"/><pubDate>Thu, 22 Sep 2022 06:24:37 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to iobroker (buanet docker) adapter lassen sich nicht updaten on Thu, 22 Sep 2022 07:55:11 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/glasfaser" aria-label="Profile: glasfaser">@<bdi>glasfaser</bdi></a> said in <a href="/post/861417">iobroker (buanet docker) adapter lassen sich nicht updaten</a>:</p>
<blockquote>
<p dir="auto">Was hast du gemacht ... weil du schreibst</p>
<p dir="auto">dann ging nix mehr.</p>
</blockquote>
<p dir="auto">ich habe</p>
<ol>
<li>erfolgreich versucht ruhig zu bleiben</li>
<li>einen Kaffee geholt</li>
<li>geschaut ob mein Backup gestern gelaufen ist</li>
</ol>
<p dir="auto">Nach der Installation von iobroker.js-controller dem Update und upgrade<br />
läuft jetzt alles wieder - soweit ich es sehen kann.<br />
Allerdings hat er nach dem Start alle Adapter neu installiert.</p>
<p dir="auto">Vielen lieben Dank - läuft alles und Adapter lassen sich wieder updaten.</p>
]]></description><link>https://forum.iobroker.net/post/861424</link><guid isPermaLink="true">https://forum.iobroker.net/post/861424</guid><dc:creator><![CDATA[ehome]]></dc:creator><pubDate>Thu, 22 Sep 2022 07:55:11 GMT</pubDate></item><item><title><![CDATA[Reply to iobroker (buanet docker) adapter lassen sich nicht updaten on Thu, 22 Sep 2022 07:42:32 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ehome" aria-label="Profile: ehome">@<bdi>ehome</bdi></a> sagte in <a href="/post/861413">iobroker (buanet docker) adapter lassen sich nicht updaten</a>:</p>
<blockquote>
<p dir="auto">habe daraufhin ein update eines Adapters probiert - dann ging nix mehr.</p>
</blockquote>
<p dir="auto">Was hast du gemacht ... weil du schreibst</p>
<blockquote>
<p dir="auto">dann ging nix mehr.</p>
</blockquote>
<p dir="auto">Fehler im Log oder .... !?</p>
]]></description><link>https://forum.iobroker.net/post/861417</link><guid isPermaLink="true">https://forum.iobroker.net/post/861417</guid><dc:creator><![CDATA[Glasfaser]]></dc:creator><pubDate>Thu, 22 Sep 2022 07:42:32 GMT</pubDate></item><item><title><![CDATA[Reply to iobroker (buanet docker) adapter lassen sich nicht updaten on Thu, 22 Sep 2022 07:41:06 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ehome" aria-label="Profile: ehome">@<bdi>ehome</bdi></a></p>
<pre><code>cd /opt/iobroker
sudo -H -u iobroker npm install iobroker.js-controller
iobroker update -i
iobroker upgrade
</code></pre>
<p dir="auto">Container danach wieder neu starten</p>
]]></description><link>https://forum.iobroker.net/post/861416</link><guid isPermaLink="true">https://forum.iobroker.net/post/861416</guid><dc:creator><![CDATA[Glasfaser]]></dc:creator><pubDate>Thu, 22 Sep 2022 07:41:06 GMT</pubDate></item><item><title><![CDATA[Reply to iobroker (buanet docker) adapter lassen sich nicht updaten on Thu, 22 Sep 2022 07:37:01 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/glasfaser" aria-label="Profile: glasfaser">@<bdi>glasfaser</bdi></a><br />
alles startete, habe daraufhin ein update eines Adapters probiert - dann ging nix mehr.<br />
Habe daraufhin Container wieder neu gestartet:</p>
<pre><code>--------------------------------------------------------------------------------
-----             Step 2 of 5: Detecting ioBroker installation             -----
--------------------------------------------------------------------------------

Existing installation of ioBroker detected in /opt/iobroker.

--------------------------------------------------------------------------------
-----             Step 3 of 5: Checking ioBroker installation              -----
--------------------------------------------------------------------------------

(Re)Setting folder permissions (This might take a while! Please be patient!)... Done.

Fixing "sudo-bug" by replacing sudo in iobroker with gosu... Done.

node:internal/modules/cjs/loader:959
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
    at Function.Module._load (node:internal/modules/cjs/loader:804:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}
/opt/scripts/iobroker_startup.sh: line 212: [: !=: unary operator expected
--------------------------------------------------------------------------------
-----                Step 4 of 5: Applying special settings                -----
--------------------------------------------------------------------------------

Some adapters have special requirements/ settings which can be activated by the use of environment variables.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).

Checking multihost setup...
Multihost is set as "master" by ENV and no external objects db is set.
Setting host of objects db to "0.0.0.0" to allow external communication... Done.
Multihost is set as "master" by ENV and no external states db is set.
Setting host of states db to "0.0.0.0" to allow external communication... Done.
Done.

--------------------------------------------------------------------------------
-----                    Step 5 of 5: ioBroker startup                     -----
--------------------------------------------------------------------------------

Starting ioBroker...

node:internal/modules/cjs/loader:959
  throw err;
  ^

Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/controller.js'
    at Function.Module._resolveFilename (node:internal/modules/cjs/loader:956:15)
    at Function.Module._load (node:internal/modules/cjs/loader:804:27)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
    at node:internal/main/run_main_module:17:47 {
  code: 'MODULE_NOT_FOUND',
  requireStack: []
}

</code></pre>
<p dir="auto">jetzt starte nicht mal mehr iobroker</p>
]]></description><link>https://forum.iobroker.net/post/861413</link><guid isPermaLink="true">https://forum.iobroker.net/post/861413</guid><dc:creator><![CDATA[ehome]]></dc:creator><pubDate>Thu, 22 Sep 2022 07:37:01 GMT</pubDate></item><item><title><![CDATA[Reply to iobroker (buanet docker) adapter lassen sich nicht updaten on Thu, 22 Sep 2022 07:36:40 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ehome" aria-label="Profile: ehome">@<bdi>ehome</bdi></a> sagte in <a href="/post/861407">iobroker (buanet docker) adapter lassen sich nicht updaten</a>:</p>
<blockquote>
<p dir="auto">seems to be corrupted.</p>
</blockquote>
<p dir="auto">Den npm cache mal leeren und den Adapter mit den iobroker.icons-open-icon-library-png nochmal installieren.</p>
]]></description><link>https://forum.iobroker.net/post/861412</link><guid isPermaLink="true">https://forum.iobroker.net/post/861412</guid><dc:creator><![CDATA[Thomas Braun]]></dc:creator><pubDate>Thu, 22 Sep 2022 07:36:40 GMT</pubDate></item><item><title><![CDATA[Reply to iobroker (buanet docker) adapter lassen sich nicht updaten on Thu, 22 Sep 2022 07:26:16 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ehome" aria-label="Profile: ehome">@<bdi>ehome</bdi></a></p>
<pre><code>pkill -u iobroker
rm /opt/iobroker/package*
</code></pre>
<p dir="auto"><strong>danach den</strong> <strong>Container neu starten</strong> .</p>
]]></description><link>https://forum.iobroker.net/post/861410</link><guid isPermaLink="true">https://forum.iobroker.net/post/861410</guid><dc:creator><![CDATA[Glasfaser]]></dc:creator><pubDate>Thu, 22 Sep 2022 07:26:16 GMT</pubDate></item><item><title><![CDATA[Reply to iobroker (buanet docker) adapter lassen sich nicht updaten on Thu, 22 Sep 2022 07:22:15 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/glasfaser" aria-label="Profile: glasfaser">@<bdi>glasfaser</bdi></a><br />
ups, sorry.</p>
<p dir="auto">Also:</p>
<pre><code>iobroker upgrade iobroker.sql@2.2.0 --debug

This upgrade of "sql" will introduce the following changes:
==========================================================================
-&gt; 2.2.0:
IMPORTANT: Node.js 14.x is now needed at minimum!
Fix potential crash cases with upcoming js-controller versions
==========================================================================

Would you like to upgrade sql from @2.1.8 to @2.2.0 now? [(y)es, (n)o]: y
Update sql from @2.1.8 to @2.2.0
host.iobroker Adapter "system.adapter.sql.1" is stopped.
NPM version: 8.15.0
Installing iobroker.sql@2.2.0... (System call)
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm WARN tarball tarball data for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master (sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master (sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==) seems to be corrupted. Trying again.
npm WARN old lockfile Error: sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== integrity checksum failed when using sha512: wanted sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== but got sha512-ZH4lj95sM6IpZEL2H1HR0hXTo6GMqbUBPbQyylgdRd6TDEdU+fgohUVGW4gPI0UnrAzqM/kx5+mozLqCVh2DCg==. (64751136 bytes)
npm WARN old lockfile     at IntegrityStream.[_onEnd] (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:118:19)
npm WARN old lockfile     at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:88:19)
npm WARN old lockfile     at IntegrityStream.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:440:12)
npm WARN old lockfile     at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:484:25)
npm WARN old lockfile     at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:90:18)
npm WARN old lockfile     at IntegrityStream.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:318:12)
npm WARN old lockfile     at IntegrityStream.resume (/usr/lib/node_modules/npm/node_modules/minipass/index.js:322:24)
npm WARN old lockfile     at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/minipass-pipeline/index.js:105:19)
npm WARN old lockfile     at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/make-fetch-happen/lib/pipeline.js:37:18)
npm WARN old lockfile     at CachingMinipassPipeline.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:312:10)
npm WARN old lockfile  Could not fetch metadata for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master Error: sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== integrity checksum failed when using sha512: wanted sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== but got sha512-ZH4lj95sM6IpZEL2H1HR0hXTo6GMqbUBPbQyylgdRd6TDEdU+fgohUVGW4gPI0UnrAzqM/kx5+mozLqCVh2DCg==. (64751136 bytes)
npm WARN old lockfile     at IntegrityStream.[_onEnd] (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:118:19)
npm WARN old lockfile     at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:88:19)
npm WARN old lockfile     at IntegrityStream.[maybeEmitEnd] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:440:12)
npm WARN old lockfile     at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/minipass/index.js:484:25)
npm WARN old lockfile     at IntegrityStream.emit (/usr/lib/node_modules/npm/node_modules/ssri/lib/index.js:90:18)
npm WARN old lockfile     at IntegrityStream.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:318:12)
npm WARN old lockfile     at IntegrityStream.resume (/usr/lib/node_modules/npm/node_modules/minipass/index.js:322:24)
npm WARN old lockfile     at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/minipass-pipeline/index.js:105:19)
npm WARN old lockfile     at CachingMinipassPipeline.emit (/usr/lib/node_modules/npm/node_modules/make-fetch-happen/lib/pipeline.js:37:18)
npm WARN old lockfile     at CachingMinipassPipeline.[resume] (/usr/lib/node_modules/npm/node_modules/minipass/index.js:312:10) {
npm WARN old lockfile   code: 'EINTEGRITY',
npm WARN old lockfile   found: Integrity { sha512: [ [Hash] ] },
npm WARN old lockfile   expected: [
npm WARN old lockfile     Hash {
npm WARN old lockfile       source: 'sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==',
npm WARN old lockfile       digest: 'qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==',
npm WARN old lockfile       algorithm: 'sha512',
npm WARN old lockfile       options: []
npm WARN old lockfile     }
npm WARN old lockfile   ],
npm WARN old lockfile   algorithm: 'sha512',
npm WARN old lockfile   sri: Integrity { sha512: [ [Hash] ] }
npm WARN old lockfile }
npm WARN tarball tarball data for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master (sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==) seems to be corrupted. Trying again.
npm WARN tarball tarball data for iobroker.icons-open-icon-library-png@https://github.com/ioBroker/ioBroker.icons-open-icon-library-png/tarball/master (sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w==) seems to be corrupted. Trying again.
npm ERR! code EINTEGRITY
npm ERR! sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== integrity checksum failed when using sha512: wanted sha512-qGFFRFfv/uSaVT+z3v01bwdZYjfIES0YwaHNOgy+OO28NMa8/8fh2rkBKGHNeHfFPBTo3juTeH+p6ngZ6s//7w== but got sha512-ZH4lj95sM6IpZEL2H1HR0hXTo6GMqbUBPbQyylgdRd6TDEdU+fgohUVGW4gPI0UnrAzqM/kx5+mozLqCVh2DCg==. (64751136 bytes)

npm ERR! A complete log of this run can be found in:
npm ERR!     /opt/iobroker/.npm/_logs/2022-09-22T07_08_23_704Z-debug-0.log
upload [13] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/de/translations.json i18n/de/translations.json application/json
upload [12] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/en/translations.json i18n/en/translations.json application/json
upload [11] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/es/translations.json i18n/es/translations.json application/json
upload [10] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/fr/translations.json i18n/fr/translations.json application/json
upload [9] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/it/translations.json i18n/it/translations.json application/json
upload [8] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/nl/translations.json i18n/nl/translations.json application/json
upload [7] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/pl/translations.json i18n/pl/translations.json application/json
upload [6] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/pt/translations.json i18n/pt/translations.json application/json
upload [5] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/ru/translations.json i18n/ru/translations.json application/json
upload [4] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/i18n/zh-cn/translations.json i18n/zh-cn/translations.json application/json
upload [3] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/jsonConfig.json jsonConfig.json application/json
upload [2] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/jsonCustom.json jsonCustom.json application/json
upload [1] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/sql.png sql.png image/png
upload [0] sql.admin /opt/iobroker/node_modules/iobroker.sql/admin/words.js words.js application/javascript
host.iobroker Adapter "system.adapter.sql.1" is started
</code></pre>
<p dir="auto">jetzt sehe ich auch Fehlermeldungen - mit dem debug hätt ich auch selber drauf kommen können .... da gibt es bei mir meherere von:</p>
<pre><code>root@iobroker:/opt/iobroker# find . -name package-lock.json
./node_modules/@abandonware/bluetooth-hci-socket/package-lock.json
./node_modules/@abandonware/noble/package-lock.json
./node_modules/minipass-sized/package-lock.json
./node_modules/npm-normalize-package-bin/package-lock.json
./node_modules/iobroker.javascript/package-lock.json
./package-lock.json
</code></pre>
<p dir="auto">npm ls | grep -E 'github.com|ERR'</p>
<pre><code>root@iobroker:/opt/iobroker# npm ls | grep -E 'github.com|ERR'
├── iobroker.solaredge@0.2.0 (git+ssh://git@github.com/92lleo/ioBroker.solaredge.git#189bb28347e0cfeffaa6b2b0b21c2534d827fbf9)
</code></pre>
<p dir="auto">iobroker update -i</p>
<pre><code>root@iobroker:/opt/iobroker# iobroker update -i
Used repository: Stable (default)
Adapter    "admin"        : 6.2.22   , installed 6.2.22
Adapter    "alias-manager": 1.2.6    , installed 1.2.6
Adapter    "backitup"     : 2.4.12   , installed 2.4.12
Adapter    "daswetter"    : 3.1.4    , installed 3.1.4
Adapter    "device-watcher": 1.0.0   , installed 1.0.0
Adapter    "devices"      : 1.0.12   , installed 1.0.12
Adapter    "discovery"    : 3.0.5    , installed 3.0.5
Adapter    "echarts"      : 1.0.12   , installed 1.0.12
Adapter    "email"        : 1.1.3    , installed 1.1.3
Adapter    "eventlist"    : 1.0.1    , installed 1.0.1
Adapter    "feiertage"    : 1.1.0    , installed 1.1.0
Adapter    "flot"         : 1.11.0   , installed 1.11.0
Adapter    "fullybrowser" : 2.1.2    , installed 2.1.2
Adapter    "history"      : 2.2.4    , installed 2.2.3  [Updatable]
Adapter    "hm-rega"      : 3.0.43   , installed 3.0.43
Adapter    "hm-rpc"       : 1.15.15  , installed 1.15.15
Adapter    "homeconnect"  : 1.0.2    , installed 1.0.2
Adapter    "ical"         : 1.13.2   , installed 1.13.2
Adapter    "icons-addictive-flavour-png": 0.1.0, installed 0.1.0
Adapter    "icons-open-icon-library-png": 0.1.2, installed 0.1.3
Adapter    "icons-ultimate-png": 1.0.1, installed 1.0.1
Adapter    "influxdb"     : 3.2.0    , installed 3.1.8  [Updatable]
Adapter    "info"         : 1.9.21   , installed 1.9.19 [Updatable]
Adapter    "jarvis"       : 3.0.13   , installed 3.0.13
Adapter    "javascript"   : 6.0.3    , installed 6.0.3
Controller "js-controller": 4.0.23   , installed 4.0.23
Adapter    "kecontact"    : 1.4.1    , installed 1.4.1
Adapter    "lametric"     : 2.0.0    , installed 2.0.0
Adapter    "linkeddevices": 1.5.5    , installed 1.5.5
Adapter    "logparser"    : 1.1.0    , installed 1.1.0
Adapter    "lovelace"     : 2.2.0    , installed 2.2.0
Adapter    "modbus"       : 5.0.5    , installed 5.0.5
Adapter    "mqtt"         : 4.0.7    , installed 4.0.7
Adapter    "mqtt-client"  : 1.6.3    , installed 1.6.3
Adapter    "nut"          : 1.5.1    , installed 1.5.1
Adapter    "parser"       : 1.2.1    , installed 1.2.1
Adapter    "phantomjs"    : 1.1.3    , installed 1.1.3
Adapter    "ping"         : 1.5.3    , installed 1.5.3
Adapter    "pushover"     : 3.0.3    , installed 3.0.3
Adapter    "radar2"       : 2.0.3    , installed 2.0.3
Adapter    "renault"      : 0.0.14   , installed 0.0.14
Adapter    "rpi2"         : 1.3.2    , installed 1.3.2
Adapter    "schoolfree"   : 1.0.1    , installed 1.0.1
Adapter    "simple-api"   : 2.7.1    , installed 2.7.1
Adapter    "smartmeter"   : 3.3.4    , installed 3.3.4
Adapter    "socketio"     : 6.1.10   , installed 6.1.10
Adapter    "sonos"        : 2.2.3    , installed 2.2.3
Adapter    "spotify-premium": 1.2.2  , installed 1.2.2
Adapter    "sql"          : 2.2.0    , installed 2.1.8  [Updatable]
Adapter    "statistics"   : 2.2.0    , installed 2.2.0
Adapter    "systeminfo"   : 0.3.1    , installed 0.3.1
Adapter    "tankerkoenig" : 2.1.1    , installed 2.1.1
Adapter    "trashschedule": 2.0.3    , installed 2.0.3
Adapter    "unifi"        : 0.6.1    , installed 0.6.1
Adapter    "viessmann"    : 1.3.7    , installed 1.3.7
Adapter    "vis"          : 1.4.15   , installed 1.4.15
Adapter    "vis-material" : 0.1.3    , installed 0.1.3
Adapter    "vis-timeandweather": 1.2.2, installed 1.2.2
Adapter    "vis-weather"  : 2.5.6    , installed 2.5.6
Adapter    "web"          : 5.2.5    , installed 5.2.5
Adapter    "ws"           : 2.1.5    , installed 2.1.5
Adapter    "yahka"        : 0.13.1   , installed 0.13.1
Adapter    "zoe2"         : 0.2.5    , installed 0.2.5
</code></pre>
<p dir="auto">sudo ln -s /usr/bin/node /usr/bin/nodejs</p>
<pre><code>root@iobroker:/opt/iobroker# sudo ln -s /usr/bin/node /usr/bin/nodejs
ln: failed to create symbolic link '/usr/bin/nodejs': File exists
</code></pre>
<p dir="auto">uname -m &amp;&amp; type -P nodejs node npm &amp;&amp; nodejs -v &amp;&amp; node -v &amp;&amp; npm -v &amp;&amp; whoami &amp;&amp; pwd &amp;&amp; sudo apt update &amp;&gt; /dev/null &amp;&amp; sudo apt update &amp;&amp; apt policy nodejs</p>
<pre><code>root@iobroker:/opt/iobroker# uname -m &amp;&amp; type -P nodejs node npm &amp;&amp; nodejs -v &amp;&amp; node -v &amp;&amp; npm -v &amp;&amp; whoami &amp;&amp; pwd &amp;&amp; sudo apt update &amp;&gt; /dev/null &amp;&amp; sudo apt update &amp;&amp; apt policy nodejs
x86_64
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v16.17.0
v16.17.0
8.15.0
root
/opt/iobroker
Hit:1 http://security.debian.org/debian-security bullseye-security InRelease
Hit:2 http://deb.debian.org/debian bullseye InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
nodejs:
  Installed: 16.17.0-deb-1nodesource1
  Candidate: 16.17.0-deb-1nodesource1
  Version table:
 *** 16.17.0-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
     12.22.12~dfsg-1~deb11u1 500
        500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
     12.22.5~dfsg-2~11u1 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
</code></pre>
]]></description><link>https://forum.iobroker.net/post/861407</link><guid isPermaLink="true">https://forum.iobroker.net/post/861407</guid><dc:creator><![CDATA[ehome]]></dc:creator><pubDate>Thu, 22 Sep 2022 07:22:15 GMT</pubDate></item><item><title><![CDATA[Reply to iobroker (buanet docker) adapter lassen sich nicht updaten on Thu, 22 Sep 2022 07:07:13 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ehome" aria-label="Profile: ehome">@<bdi>ehome</bdi></a></p>
<blockquote>
<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/glasfaser" aria-label="Profile: glasfaser">@<bdi>glasfaser</bdi></a> sagte in <a href="/post/861396">iobroker (buanet docker) adapter lassen sich nicht updaten</a>:<br />
Zeige mal :<br />
iobroker upgrade iobroker.sql@2.2.0 --debug</p>
</blockquote>
<p dir="auto">???</p>
<p dir="auto">und der Rest fehlt auch</p>
<pre><code>iobroker update -i
</code></pre>
]]></description><link>https://forum.iobroker.net/post/861400</link><guid isPermaLink="true">https://forum.iobroker.net/post/861400</guid><dc:creator><![CDATA[Glasfaser]]></dc:creator><pubDate>Thu, 22 Sep 2022 07:07:13 GMT</pubDate></item><item><title><![CDATA[Reply to iobroker (buanet docker) adapter lassen sich nicht updaten on Thu, 22 Sep 2022 07:04:11 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/glasfaser" aria-label="Profile: glasfaser">@<bdi>glasfaser</bdi></a> said in <a href="/post/861396">iobroker (buanet docker) adapter lassen sich nicht updaten</a>:</p>
<blockquote>
<p dir="auto">uname -m &amp;&amp; type -P nodejs node npm &amp;&amp; nodejs -v &amp;&amp; node -v &amp;&amp; npm -v &amp;&amp; whoami &amp;&amp; pwd &amp;&amp; sudo apt update &amp;&gt; /dev/null &amp;&amp; sudo apt update &amp;&amp; apt policy nodejs</p>
</blockquote>
<p dir="auto">@glafaser Vielen Dank für deine Antwort,<br />
puh ehrlich gesagt weiss ich nicht, ob ich im alten Container den update irgendwann gemacht habe, werde wohl langsam vergesslich ...</p>
<p dir="auto">Hier der Output deiner Befehle:</p>
<pre><code>root@iobroker:/opt/iobroker# npm ls | grep -E 'github.com|ERR'
├── iobroker.solaredge@0.2.0 (git+ssh://git@github.com/92lleo/ioBroker.solaredge.git#189bb28347e0cfeffaa6b2b0b21c2534d827fbf9)
root@iobroker:/opt/iobroker# sudo ln -s /usr/bin/node /usr/bin/nodejs
root@iobroker:/opt/iobroker# uname -m &amp;&amp; type -P nodejs node npm &amp;&amp; nodejs -v &amp;&amp; node -v &amp;&amp; npm -v &amp;&amp; whoami &amp;&amp; pwd &amp;&amp; sudo apt update &amp;&gt; /dev/null &amp;&amp; sudo apt update &amp;&amp; apt policy nodejs
x86_64
/usr/bin/nodejs
/usr/bin/node
/usr/bin/npm
v16.17.0
v16.17.0
8.15.0
root
/opt/iobroker
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://security.debian.org/debian-security bullseye-security InRelease
Hit:3 http://deb.debian.org/debian bullseye-updates InRelease
Hit:4 https://deb.nodesource.com/node_16.x bullseye InRelease
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.
nodejs:
  Installed: 16.17.0-deb-1nodesource1
  Candidate: 16.17.0-deb-1nodesource1
  Version table:
 *** 16.17.0-deb-1nodesource1 500
        500 https://deb.nodesource.com/node_16.x bullseye/main amd64 Packages
        100 /var/lib/dpkg/status
     12.22.12~dfsg-1~deb11u1 500
        500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages
     12.22.5~dfsg-2~11u1 500
        500 http://deb.debian.org/debian bullseye/main amd64 Packages
</code></pre>
]]></description><link>https://forum.iobroker.net/post/861397</link><guid isPermaLink="true">https://forum.iobroker.net/post/861397</guid><dc:creator><![CDATA[ehome]]></dc:creator><pubDate>Thu, 22 Sep 2022 07:04:11 GMT</pubDate></item><item><title><![CDATA[Reply to iobroker (buanet docker) adapter lassen sich nicht updaten on Thu, 22 Sep 2022 06:55:20 GMT]]></title><description><![CDATA[<p dir="auto"><a class="plugin-mentions-user plugin-mentions-a" href="/user/ehome" aria-label="Profile: ehome">@<bdi>ehome</bdi></a> sagte in <a href="/post/861389">iobroker (buanet docker) adapter lassen sich nicht updaten</a>:</p>
<blockquote>
<p dir="auto">docker-image Version von latest-v6 auf latest-v7 gewechselt,</p>
</blockquote>
<p dir="auto">hast du vorher schon im alten Container ein upgrade auf Nodejs16 gemacht !?</p>
<p dir="auto">Zeige mal :</p>
<pre><code>iobroker upgrade iobroker.sql@2.2.0 --debug
</code></pre>
<pre><code>cd /opt/iobroker
npm ls | grep -E 'github.com|ERR' 

iobroker update -i
 
sudo ln -s /usr/bin/node /usr/bin/nodejs

uname -m &amp;&amp; type -P nodejs node npm &amp;&amp; nodejs -v &amp;&amp; node -v &amp;&amp; npm -v &amp;&amp; whoami &amp;&amp; pwd &amp;&amp; sudo apt update &amp;&gt; /dev/null &amp;&amp; sudo apt update &amp;&amp; apt policy nodejs
</code></pre>
]]></description><link>https://forum.iobroker.net/post/861396</link><guid isPermaLink="true">https://forum.iobroker.net/post/861396</guid><dc:creator><![CDATA[Glasfaser]]></dc:creator><pubDate>Thu, 22 Sep 2022 06:55:20 GMT</pubDate></item></channel></rss>