Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Error/Bug
    4. iobroker exit 25 bei Adapter-Update

    NEWS

    • Beta-Start ioBroker-Matter Adapter

    • JAHRESRÜCKBLICK 2024 ✨

    • NEWS von ioBroker im Blog!

    iobroker exit 25 bei Adapter-Update

    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      Siggi0904 last edited by

      @thomas-braun

      login as: mario
mario@192.168.178.64's password:
Linux iobroker 6.1.0-18-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.76-1 (2024-02-01) x86_64

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Fri Mar 29 20:42:04 2024 from 192.168.178.41
mario@iobroker:~$ cd /opt/iobroker
mario@iobroker:/opt/iobroker$ npm ls -a | grep xmlbuilder
[sudo] Passwort für mario:
npm ERR! code ELSPROBLEMS
npm ERR! extraneous: @types/caseless@0.12.5 /opt/iobroker/node_modules/@types/caseless
npm ERR! extraneous: @types/request@2.48.12 /opt/iobroker/node_modules/@types/request
npm ERR! extraneous: @types/tough-cookie@4.0.5 /opt/iobroker/node_modules/@types/tough-cookie
npm ERR! extraneous: coffeescript@2.7.0 /opt/iobroker/node_modules/coffeescript
npm ERR! extraneous: jsonata@2.0.4 /opt/iobroker/node_modules/jsonata
npm ERR! extraneous: node-inspect@2.0.0 /opt/iobroker/node_modules/node-inspect
npm ERR! extraneous: picocolors@1.0.0 /opt/iobroker/node_modules/picocolors
npm ERR! extraneous: typescript@5.3.3 /opt/iobroker/node_modules/typescript
npm ERR! extraneous: virtual-tsc@0.6.2 /opt/iobroker/node_modules/virtual-tsc
npm ERR! extraneous: wake_on_lan@1.0.0 /opt/iobroker/node_modules/wake_on_lan
npm ERR! extraneous: form-data@2.5.1 /opt/iobroker/node_modules/@types/request/node_modules/form-data
npm ERR! extraneous: debug@4.3.4 /opt/iobroker/node_modules/virtual-tsc/node_modules/debug
npm ERR! extraneous: ms@2.1.2 /opt/iobroker/node_modules/virtual-tsc/node_modules/ms
npm ERR! invalid: xmlbuilder@0.4.2 /opt/iobroker/node_modules/xmlbuilder
│   └── xmlbuilder@11.0.1
│   └── xmlbuilder@0.4.2 invalid: "https://github.com/hobbyquaker/xmlbuilder-js/tarball/29fe5030dc6852007dc8d1bfd5109d75f8da58d5" from node_modules/homematic-xmlrpc
│ └── xmlbuilder@15.1.1
│   └── xmlbuilder@11.0.1

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-03-29T20_04_01_416Z-debug-0.log
mario@iobroker:/opt/iobroker$
      Thomas Braun 1 Reply Last reply Reply Quote 0
      • Thomas Braun
        Thomas Braun Most Active @Siggi0904 last edited by

        @siggi0904

        cd /opt/iobroker
npm ls xmlbuilder
        S 1 Reply Last reply Reply Quote 0
        • S
          Siggi0904 @Thomas Braun last edited by

          @thomas-braun

          mario@iobroker:/opt/iobroker$ npm ls xmlbuilder
npm ERR! code ELSPROBLEMS
npm ERR! invalid: xmlbuilder@0.4.2 /opt/iobroker/node_modules/xmlbuilder
iobroker.inst@2.0.3 /opt/iobroker
├─┬ iobroker.hm-rega@4.0.0
│ └─┬ xml2js@0.6.2
│   └── xmlbuilder@11.0.1
├─┬ iobroker.hm-rpc@1.16.0
│ └─┬ homematic-xmlrpc@1.0.2
│   └── xmlbuilder@0.4.2 invalid: "https://github.com/hobbyquaker/xmlbuilder-js/tarball/29fe5030dc6852007dc8d1bfd5109d75f8da58d5" from node_modules/homematic-xmlrpc
├─┬ iobroker.shelly@6.8.0
│ └── xmlbuilder@15.1.1
└─┬ iobroker.tr-064@4.2.18
  └─┬ xml2js@0.4.23
    └── xmlbuilder@11.0.1


npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-03-29T20_12_39_266Z-debug-0.log
mario@iobroker:/opt/iobroker$
          Thomas Braun 1 Reply Last reply Reply Quote 0
          • Thomas Braun
            Thomas Braun Most Active @Siggi0904 last edited by Thomas Braun

            @siggi0904 sagte in iobroker exit 25 bei Adapter-Update:

            iobroker.hm-rpc

            Installier den nochmal. Ich vermute die Abhängigkeit ist da falsch.

            S 1 Reply Last reply Reply Quote 0
            • S
              Siggi0904 @Thomas Braun last edited by

              @thomas-braun Hallo, wie? ggf. mit Debug, dass man sieht was da passiert.

              Wundert mich aber, weil der schon ewig läuft.

              Thomas Braun 2 Replies Last reply Reply Quote 0
              • Thomas Braun
                Thomas Braun Most Active @Siggi0904 last edited by

                @siggi0904

                Du hast da irgendein steinaltes Modul im Setup, das mit node-waf gebaut werden soll. Nur ist das seit mehreren Jahren obsolet und durch node-gyp ersetzt worden. Man müsste mal irgendwie schauen was das sein könnte. Vermutlich der xmlbuilder@0.4.2, der ist ja auch komplett veraltet und nicht mehr verlinkt.

                1 Reply Last reply Reply Quote 0
                • Thomas Braun
                  Thomas Braun Most Active @Siggi0904 last edited by

                  @siggi0904

                  iob update
iob upgrade hm-rpc@1.16.0
iob upgrade all
                  S 1 Reply Last reply Reply Quote 0
                  • S
                    Siggi0904 last edited by

                    @thomas-braun oh, wie kommt das da hin?

                    Wie kann ich iobroker.hm-rpc nochmal installieren?

                    1 Reply Last reply Reply Quote 0
                    • S
                      Siggi0904 @Thomas Braun last edited by

                      @thomas-braun sagte in iobroker exit 25 bei Adapter-Update:

                      iob upgrade hm-rpc@1.16.0

                      hm, misst. Bleibt auch so erhalten, der Fehler.

                      mario@iobroker:/opt/iobroker$ iob update
Used repository: stable
Adapter    "admin"        : 6.13.16  , installed 6.13.16
Adapter    "alarm"        : 3.6.0    , installed 3.6.0
Adapter    "alexa-timer-vis": 0.3.0  , installed 0.3.0
Adapter    "alexa2"       : 3.26.4   , installed 3.26.4
Adapter    "awtrix-light" : 0.16.0   , installed 0.16.0
Adapter    "backitup"     : 2.10.11  , installed 2.10.11
Adapter    "cloud"        : 5.0.1    , installed 4.4.1  [Updatable]
Adapter    "daswetter"    : 3.1.13   , installed 3.1.13
Adapter    "deconz"       : 1.4.0    , installed 1.4.0
Adapter    "discovery"    : 4.4.0    , installed 4.4.0
Adapter    "dwd"          : 2.8.5    , installed 2.8.5
Adapter    "email"        : 1.2.2    , installed 1.2.2
Adapter    "feiertage"    : 1.1.4    , installed 1.1.4
Adapter    "flot"         : 1.12.0   , installed 1.12.0
Adapter    "heatingcontrol": 2.12.5  , installed 2.12.5
Adapter    "hm-rega"      : 4.0.0    , installed 4.0.0
Adapter    "hm-rpc"       : 1.16.0   , installed 1.16.0
Adapter    "ical"         : 1.14.3   , installed 1.13.3 [Updatable]
Adapter    "icons-mfd-svg": 1.2.0    , installed 1.2.0
Adapter    "iot"          : 2.0.11   , installed 2.0.11
Adapter    "javascript"   : 7.8.0    , installed 7.8.0
Controller "js-controller": 5.0.19   , installed 5.0.19
Adapter    "mihome-vacuum": 4.1.1    , installed 4.1.1
Adapter    "openweathermap": 1.0.4   , installed 1.0.4
Adapter    "ping"         : 1.6.2    , installed 1.6.2
Adapter    "scenes"       : 2.3.9    , installed 2.3.9
Adapter    "shelly"       : 6.8.0    , installed 6.8.0
Adapter    "simple-api"   : 2.7.2    , installed 2.7.2
Adapter    "socketio"     : 6.6.1    , installed 6.6.0  [Updatable]
Adapter    "sonoff"       : 3.0.3    , installed 3.0.3
Adapter    "sql"          : 2.2.0    , installed 2.2.0
Adapter    "tankerkoenig" : 3.3.7    , installed 3.3.7
Adapter    "tr-064"       : 4.2.18   , installed 4.2.18
Adapter    "trashschedule": 3.2.0    , installed 3.2.0
Adapter    "vis"          : 1.5.4    , installed 1.5.4
Adapter    "web"          : 6.2.3    , installed 6.2.3
Adapter    "ws"           : 2.5.11   , installed 2.5.10 [Updatable]
mario@iobroker:/opt/iobroker$ iob upgrade hm-rpc@1.16.0
Would you like to reinstall version 1.16.0 of hm-rpc now? [(y)es, (n)o]: y
Update hm-rpc from @1.16.0 to @1.16.0
NPM version: 10.5.0
Installing iobroker.hm-rpc@1.16.0... (System call)
npm ERR! code 127
npm ERR! path /opt/iobroker/node_modules/zlib
npm ERR! command failed
npm ERR! command sh -c node-waf clean || true; node-waf configure build
npm ERR! sh: 1: node-waf: not found
npm ERR! sh: 1: node-waf: not found

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-03-29T20_31_44_159Z-debug-0.log
host.iobroker Cannot install iobroker.hm-rpc@1.16.0: 127
mario@iobroker:/opt/iobroker$
                      Thomas Braun 1 Reply Last reply Reply Quote 0
                      • Thomas Braun
                        Thomas Braun Most Active @Siggi0904 last edited by

                        @siggi0904 sagte in iobroker exit 25 bei Adapter-Update:

                        zlib

                        npm ls zlib
                        S 1 Reply Last reply Reply Quote 0
                        • S
                          Siggi0904 @Thomas Braun last edited by

                          @thomas-braun

                          mario@iobroker:/opt/iobroker$ npm ls zlib
iobroker.inst@2.0.3 /opt/iobroker
└─┬ iobroker.mihome-vacuum@4.1.1
  └── zlib@1.0.5

mario@iobroker:/opt/iobroker$
                          Thomas Braun 1 Reply Last reply Reply Quote 0
                          • Thomas Braun
                            Thomas Braun Most Active @Siggi0904 last edited by

                            @siggi0904

                            npm prune
npm ls
                            S 3 Replies Last reply Reply Quote 0
                            • S
                              Siggi0904 @Thomas Braun last edited by

                              @thomas-braun

                              mario@iobroker:/opt/iobroker$ npm ls zlib
iobroker.inst@2.0.3 /opt/iobroker
└─┬ iobroker.mihome-vacuum@4.1.1
  └── zlib@1.0.5

mario@iobroker:/opt/iobroker$ npm prune
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 @types/bl@5.1.0: This is a stub types definition. bl provides its own type definitions, so you do not need this installed.
npm WARN deprecated @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3
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 @azure/msal-node@1.18.4: A newer major version of this library is available. Please upgrade to the latest available version.
npm ERR! code 127
npm ERR! path /opt/iobroker/node_modules/zlib
npm ERR! command failed
npm ERR! command sh -c node-waf clean || true; node-waf configure build
npm ERR! sh: 1: node-waf: not found
npm ERR! sh: 1: node-waf: not found

npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-03-29T20_48_34_023Z-debug-0.log
mario@iobroker:/opt/iobroker$
                              Qix- created this issue in visionmedia/debug

                              closed ReDos Vulnerability Regression Visibility Notice #797

                              Qix- created this issue in visionmedia/debug

                              closed ReDos Vulnerability Regression Visibility Notice #797

                              Qix- created this issue in visionmedia/debug

                              closed ReDos Vulnerability Regression Visibility Notice #797

                              mikeal created this issue in request/request

                              open Request’s Past, Present and Future #3142

                              1 Reply Last reply Reply Quote 0
                              • S
                                Siggi0904 @Thomas Braun last edited by

                                @thomas-braun

                                mario@iobroker:/opt/iobroker$ npm ls
iobroker.inst@2.0.3 /opt/iobroker
├── @types/caseless@0.12.5 extraneous
├── @types/request@2.48.12 extraneous
├── @types/tough-cookie@4.0.5 extraneous
├── coffeescript@2.7.0 extraneous
├── colors@1.4.0
├── fs-extra@7.0.1
├── iobroker.admin@6.13.16
├── iobroker.alarm@3.6.0
├── iobroker.alexa-timer-vis@0.3.0
├── iobroker.alexa2@3.26.4
├── iobroker.awtrix-light@0.16.0
├── iobroker.backitup@2.10.11
├── iobroker.cloud@4.4.1
├── iobroker.daswetter@3.1.13
├── iobroker.deconz@1.4.0
├── iobroker.discovery@4.4.0
├── iobroker.dwd@2.8.5
├── iobroker.email@1.2.2
├── iobroker.feiertage@1.1.4
├── iobroker.flot@1.12.0
├── iobroker.heatingcontrol@2.12.5
├── iobroker.hm-rega@4.0.0
├── iobroker.hm-rpc@1.16.0
├── iobroker.ical@1.13.3
├── iobroker.icons-mfd-svg@1.2.0
├── iobroker.iot@2.0.11
├── iobroker.javascript@7.8.0
├── iobroker.js-controller@5.0.19
├── iobroker.mihome-vacuum@4.1.1
├── iobroker.openweathermap@1.0.4
├── iobroker.ping@1.6.2
├── iobroker.scenes@2.3.9
├── iobroker.shelly@6.8.0
├── iobroker.simple-api@2.7.2
├── iobroker.socketio@6.6.0
├── iobroker.sonoff@3.0.3
├── iobroker.sql@2.2.0
├── iobroker.tankerkoenig@3.3.7
├── iobroker.tr-064@4.2.18
├── iobroker.trashschedule@3.2.0
├── iobroker.vis@1.5.4
├── iobroker.web@6.2.3
├── iobroker.ws@2.5.10
├── iobroker@2.0.3
├── jsonata@2.0.4 extraneous
├── node-inspect@2.0.0 extraneous
├── picocolors@1.0.0 extraneous
├── semver@5.7.2
├── typescript@5.3.3 extraneous
├── virtual-tsc@0.6.2 extraneous
├── wake_on_lan@1.0.0 extraneous
└── yargs@7.1.2

mario@iobroker:/opt/iobroker$
                                1 Reply Last reply Reply Quote 0
                                • S
                                  Siggi0904 @Thomas Braun last edited by

                                  @thomas-braun

                                  In der Datei /opt/iobroker/node_modules/zlib/configure steht node-waf configure
                                  Also ist zlib schuld?

                                  Thomas Braun 2 Replies Last reply Reply Quote 0
                                  • Thomas Braun
                                    Thomas Braun Most Active @Siggi0904 last edited by

                                    @siggi0904 sagte in iobroker exit 25 bei Adapter-Update:

                                    node-waf configure

                                    Möglich. Auf meinem System schaut es so aus:

                                    echad@chet:/opt/iobroker $ grep -r node-waf           
node_modules/reinterval/.npmignore:# node-waf configuration
node_modules/bindings/bindings.js:      // node-waf and gyp_addon (a.k.a node-gyp)
node_modules/bindings/bindings.js:      // Legacy from node-waf, node <= 0.4.x
node_modules/zlib/configure:node-waf configure
node_modules/zlib/Makefile:     node-waf build
node_modules/zlib/Makefile:     node-waf clean
echad@chet:/opt/iobroker $

                                    Ich habe aber keine Fehler, wenn npm loslegt.

                                    S 1 Reply Last reply Reply Quote 0
                                    • S
                                      Siggi0904 @Thomas Braun last edited by

                                      @thomas-braun in den Releases zu node-js 18.20 ist aber auch viel zlib Zeug dabei.
                                      https://nodejs.org/en/blog/release/v18.20.0

                                      Bei mir auch so:

                                      mario@iobroker:/opt/iobroker$ grep -r node-waf
log/iobroker.2024-03-29.log:2024-03-29 18:56:47.899  - error: host.iobroker iobroker npm ERR! code 127npm ERR! path /opt/iobroker/node_modules/zlibnpm ERR! command failednpm ERR! command sh -c node-waf clean || true; node-waf configure buildnpm ERR! sh: 1: node-waf: not foundnpm ERR! sh: 1: node-waf: not foundnpm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-03-29T17_50_31_979Z-debug-0.log
log/iobroker.2024-03-29.log:2024-03-29 19:09:10.732  - error: host.iobroker iobroker npm ERR! code 127npm ERR! path /opt/iobroker/node_modules/zlibnpm ERR! command failednpm ERR! command sh -c node-waf clean || true; node-waf configure buildnpm ERR! sh: 1: node-waf: not foundnpm ERR! sh: 1: node-waf: not foundnpm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-03-29T18_03_29_073Z-debug-0.log
log/iobroker.2024-03-29.log:2024-03-29 20:25:32.516  - error: host.iobroker iobroker npm ERR! code 127npm ERR! path /opt/iobroker/node_modules/zlibnpm ERR! command failednpm ERR! command sh -c node-waf clean || true; node-waf configure buildnpm ERR! sh: 1: node-waf: not foundnpm ERR! sh: 1: node-waf: not foundnpm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-03-29T19_19_31_663Z-debug-0.log
log/iobroker.2024-03-29.log:2024-03-29 20:58:12.865  - error: host.iobroker iobroker npm ERR! code 127npm ERR! path /opt/iobroker/node_modules/zlibnpm ERR! command failednpm ERR! command sh -c node-waf clean || true; node-waf configure buildnpm ERR! sh: 1: node-waf: not foundnpm ERR! sh: 1: node-waf: not foundnpm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-03-29T19_52_59_224Z-debug-0.log
node_modules/zlib/configure:node-waf configure
node_modules/zlib/Makefile:     node-waf build
node_modules/zlib/Makefile:     node-waf clean
node_modules/bindings/bindings.js:      // node-waf and gyp_addon (a.k.a node-gyp)
node_modules/bindings/bindings.js:      // Legacy from node-waf, node <= 0.4.x
node_modules/node-rest-client/readme.md:**NOTE:** _Since version 0.8.0 node does not contain node-waf anymore. The node-zlib package which node-rest-client make use of, depends on node-waf.Fortunately since version 0.8.0 zlib is a core dependency of node, so since version 1.0 of node-rest-client the explicit dependency to "zlib" has been removed from package.json. therefore if you are using a version below 0.8.0 of node please use a versión below 1.0.0 of "node-rest-client". _
node_modules/reinterval/.npmignore:# node-waf configuration
mario@iobroker:/opt/iobroker$
                                      1 Reply Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @Siggi0904 last edited by

                                        @siggi0904

                                        Kommt aus dem Modul:

                                        https://github.com/kkaefer/DEPRECATED-node-zlib

                                        Das ist aber wie gesagt seit Jahren überholt.

                                        S 1 Reply Last reply Reply Quote 0
                                        • S
                                          Siggi0904 @Thomas Braun last edited by Siggi0904

                                          @thomas-braun ja.

                                          Deine Reihenfolge in der grep Ausgabe ist aber anders.
                                          das npmignore kommt bei mir am Ende, bei dir als erstes.

                                          Kann man die Verwendung irgendwie deaktivieren, dass das sauber durchläuft?

                                          Thomas Braun 1 Reply Last reply Reply Quote 0
                                          • Thomas Braun
                                            Thomas Braun Most Active @Siggi0904 last edited by

                                            @siggi0904 sagte in iobroker exit 25 bei Adapter-Update:

                                            Kann man die Verwendung irgendwie deaktivieren, dass das sauber durchläuft?

                                            Der mihome-vacuum schleppt wohl zlib an. Keine Ahnung, ob man die Dependency dort herausnehmen kann/soll/muss.

                                            S 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            1.1k
                                            Online

                                            31.0k
                                            Users

                                            78.0k
                                            Topics

                                            1.2m
                                            Posts

                                            8
                                            113
                                            3576
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo