Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. Tester
    4. Beta-Test js-controller 2.2.x GitHub

    NEWS

    • Neuer Blog: Fotos und Eindrücke aus Solingen

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    Beta-Test js-controller 2.2.x GitHub

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

      Hey All,

      auf GitHub erwartet Euch die 2.2.4:

      • (Apollon77) create symlink to current logfile (fixes #578)
      • (Apollon77) add some logging for archiving logfiles on windows
      • (Apollon77) add warning messge for getMessage method to make deprecation more visible
      • (bluefox) Fix wrong error handling for adapter deletions; should work again! Fixes #576
      • (bluefox) Add Package installation by js-controller for Linux based systems (apt/yum package managers) via io-package common.osDependencies[process.platform]

      Bedeutet: Bitte Adapter Löschen neu testen. Sollte jetzt tun.

      Neuschwansteini E 2 Replies Last reply Reply Quote 1
      • Neuschwansteini
        Neuschwansteini @apollon77 last edited by

        @apollon77 2.2.4 läuft hier überall unauffällig. 👍 👍

        1 Reply Last reply Reply Quote 1
        • D
          darkiop Most Active last edited by

          So, auch hier noch schnell die 2.2.4 vor 0 Uhr installiert um Morgen dann direkt das current.log prüfen zu können 🙂

          apollon77 1 Reply Last reply Reply Quote 1
          • apollon77
            apollon77 @darkiop last edited by

            @darkiop Bei mir hats geklappt 🙂

            D 1 Reply Last reply Reply Quote 0
            • crunchip
              crunchip Forum Testing Most Active last edited by

              aktuell js-controller 2.1.1
              admin 3.7.2
              nodejs 10.17.0
              NPM 6.11.3
              iobroker in einer Proxmox VM

              ich habe es nun 2mal versucht, jeweils rund 20 min gewartet, aber es passiert nichts
              eingeloggt auf Putty
              ins Verzeichnis opt/iobroker
              iobroker stop
              npm install ioBroker/ioBroker.js-controller

              1 Reply Last reply Reply Quote 0
              • D
                darkiop Most Active @apollon77 last edited by darkiop

                @apollon77 Aufm master im Container bei mir auch:

                556051a0-3c4b-4d0a-9728-b0de913e7a44-grafik.png

                Aufm Raspi, also der Slave, nicht - den starte ich jetzt mal durch:

                900d767f-dc19-41a3-ad96-e0e37b5117a6-grafik.png

                apollon77 1 Reply Last reply Reply Quote 0
                • apollon77
                  apollon77 @darkiop last edited by

                  @darkiop Der hat aber auch noch nicht mal ein 30er logfile ... kann sein das der nix zu loggen hatte seit 23:41? 🙂

                  D Chaot 2 Replies Last reply Reply Quote 0
                  • D
                    darkiop Most Active @apollon77 last edited by

                    @apollon77 oh, das kann natürlich sein - ist ja der slave 😄 das war der wink das es zeit fürs bett ist g

                    1 Reply Last reply Reply Quote 0
                    • sigi234
                      sigi234 Forum Testing Most Active @apollon77 last edited by sigi234

                      @apollon77

                      Screenshot (1116).png

                      iobroker.2019-12-30.zip

                      Screenshot (1123).png

                      Chaot 1 Reply Last reply Reply Quote 0
                      • Chaot
                        Chaot @sigi234 last edited by

                        @apollon77 Ich habe eine Fehlermeldung aus Proxmox.
                        Aber ich denke mal das hat nichts mit der Controler Version zu tun sondern mit dem Adapter:

                        host.ioBroker	2019-12-30 04:06:00.115	error	Caught by controller[2]: at IncomingMessage.emit (events.js:203:15)
host.ioBroker	2019-12-30 04:06:00.115	error	Caught by controller[2]: at Object.onceWrapper (events.js:286:20)
host.ioBroker	2019-12-30 04:06:00.115	error	Caught by controller[2]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
host.ioBroker	2019-12-30 04:06:00.114	error	Caught by controller[2]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.114	error	Caught by controller[2]: at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
host.ioBroker	2019-12-30 04:06:00.114	error	Caught by controller[2]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.114	error	Caught by controller[2]: at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
host.ioBroker	2019-12-30 04:06:00.112	error	Caught by controller[2]: at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
host.ioBroker	2019-12-30 04:06:00.110	error	Caught by controller[2]: at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
host.ioBroker	2019-12-30 04:06:00.110	error	Caught by controller[2]: at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
host.ioBroker	2019-12-30 04:06:00.110	error	Caught by controller[2]: TypeError: Cannot read property 'name' of undefined
host.ioBroker	2019-12-30 04:06:00.110	error	Caught by controller[1]: at IncomingMessage.emit (events.js:203:15)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at Object.onceWrapper (events.js:286:20)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.109	error	Caught by controller[1]: at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[1]: at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[1]: at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[1]: at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[1]: TypeError: Cannot read property 'name' of undefined
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[0]: at IncomingMessage.emit (events.js:203:15)
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[0]: at Object.onceWrapper (events.js:286:20)
host.ioBroker	2019-12-30 04:06:00.108	error	Caught by controller[0]: at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
host.ioBroker	2019-12-30 04:06:00.107	error	Caught by controller[0]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.107	error	Caught by controller[0]: at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
host.ioBroker	2019-12-30 04:06:00.107	error	Caught by controller[0]: at Request.emit (events.js:198:13)
host.ioBroker	2019-12-30 04:06:00.107	error	Caught by controller[0]: at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
host.ioBroker	2019-12-30 04:06:00.106	error	Caught by controller[0]: at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
host.ioBroker	2019-12-30 04:06:00.106	error	Caught by controller[0]: at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
host.ioBroker	2019-12-30 04:06:00.106	error	Caught by controller[0]: at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
host.ioBroker	2019-12-30 04:06:00.105	error	Caught by controller[0]: TypeError: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.543	error	at IncomingMessage.emit (events.js:203:15)
proxmox.0	2019-12-30 04:05:59.543	error	at Object.onceWrapper (events.js:286:20)
proxmox.0	2019-12-30 04:05:59.543	error	at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
proxmox.0	2019-12-30 04:05:59.543	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.543	error	at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
proxmox.0	2019-12-30 04:05:59.543	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.543	error	at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
proxmox.0	2019-12-30 04:05:59.543	error	at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
proxmox.0	2019-12-30 04:05:59.543	error	at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
proxmox.0	2019-12-30 04:05:59.543	error	at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
proxmox.0	2019-12-30 04:05:59.543	error	(684) TypeError: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.542	error	(684) uncaught exception: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.530	error	at IncomingMessage.emit (events.js:203:15)
proxmox.0	2019-12-30 04:05:59.530	error	at Object.onceWrapper (events.js:286:20)
proxmox.0	2019-12-30 04:05:59.530	error	at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
proxmox.0	2019-12-30 04:05:59.530	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.530	error	at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
proxmox.0	2019-12-30 04:05:59.530	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.530	error	at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
proxmox.0	2019-12-30 04:05:59.530	error	at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
proxmox.0	2019-12-30 04:05:59.530	error	at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
proxmox.0	2019-12-30 04:05:59.530	error	at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
proxmox.0	2019-12-30 04:05:59.530	error	(684) TypeError: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.530	error	(684) uncaught exception: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.525	error	at IncomingMessage.emit (events.js:203:15)
proxmox.0	2019-12-30 04:05:59.525	error	at Object.onceWrapper (events.js:286:20)
proxmox.0	2019-12-30 04:05:59.525	error	at IncomingMessage.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1083:12)
proxmox.0	2019-12-30 04:05:59.525	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.525	error	at Request.<anonymous> (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:1161:10)
proxmox.0	2019-12-30 04:05:59.525	error	at Request.emit (events.js:198:13)
proxmox.0	2019-12-30 04:05:59.525	error	at Request.self.callback (/opt/iobroker/node_modules/iobroker.proxmox/node_modules/request/request.js:185:22)
proxmox.0	2019-12-30 04:05:59.525	error	at Request.request [as _callback] (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:166:21)
proxmox.0	2019-12-30 04:05:59.525	error	at _get.then.data (/opt/iobroker/node_modules/iobroker.proxmox/lib/proxmox.js:48:9)
proxmox.0	2019-12-30 04:05:59.525	error	at /opt/iobroker/node_modules/iobroker.proxmox/main.js:415:33
proxmox.0	2019-12-30 04:05:59.525	error	(684) TypeError: Cannot read property 'name' of undefined
proxmox.0	2019-12-30 04:05:59.500	error	(684) uncaught exception: Cannot read property 'name' of undefined

                        Ansonsten alles ohne weitere Fehlermeldungen.
                        Version 2.2.4 seit gestern kurz nach Veröffentlichung

                        crunchip apollon77 2 Replies Last reply Reply Quote 0
                        • E
                          Einstein67 @apollon77 last edited by

                          @apollon77 said in Beta-Test js-controller 2.2.x GitHub:

                          Bedeutet: Bitte Adapter Löschen neu testen. Sollte jetzt tun.

                          Bei mir immer noch das selbe verhalten wie bei 2.2.2

                          Nach dem (laut Log fehlerlosen) löschen von Adapter oder Instanz wird die dazugehörige Konfigseite geöffnet, und die Instanz ist immer noch da ...

                          apollon77 1 Reply Last reply Reply Quote 0
                          • crunchip
                            crunchip Forum Testing Most Active @Chaot last edited by

                            @Chaot kommt vom Adapter, kämpfe schon länger damit herum
                            https://github.com/iobroker-community-adapters/ioBroker.proxmox/issues/35

                            crunchip77 created this issue in iobroker-community-adapters/ioBroker.proxmox

                            closed restart des Adapters(error request) #35

                            Chaot 1 Reply Last reply Reply Quote 0
                            • Chaot
                              Chaot @crunchip last edited by

                              @crunchip Danke. Das habe ich mir schon fast gedacht.
                              Vermutlich lag das daran das Proxmox genau zu der Zeit das Backup der PVE gemacht hat. Ich habe jetzt das Requestintevall mal von 30 auf 120 Sekunden gesetzt und werde mal abwarten ob es nochmal kommt.
                              Falls ja, werde ich mich mal bei dir anhängen.

                              1 Reply Last reply Reply Quote 0
                              • L
                                lonsimbt last edited by

                                Die 2.2.4 läuft bei mir unauffällig keine Probleme oder Fehler im Log.

                                @crunchip : Die Probleme mit dem proxmox-Adapter (0.5.1) treten bei mir nicht auf.

                                Gruß Marco

                                1 Reply Last reply Reply Quote 0
                                • Chaot
                                  Chaot @apollon77 last edited by

                                  @apollon77 Mir fällt eine Besonderheit auf.
                                  Ich habe an einem Raspi einen Touchscreen hängen der auf VIS zugreift.
                                  Seit gestern fällt mir auf das der Browser zwischendurch einen Timeout beim Zugriff auf die Webseite bringt.
                                  Das war vorher nicht so.

                                  Kann ich von der Version auf 2.1.1 zurück mit dem vorhandenen Admin V3.7.5 oder geht dann der Admin flöten?

                                  apollon77 1 Reply Last reply Reply Quote 0
                                  • apollon77
                                    apollon77 @Chaot last edited by

                                    @Chaot bitte issue bei proxmox anlegen. Kann es sein das du nen proxmox node rebooten hast?

                                    E 1 Reply Last reply Reply Quote 0
                                    • apollon77
                                      apollon77 @Einstein67 last edited by

                                      @Einstein67 wie sieht das log jetzt aus? Dann bitte issue reopen. Muss ich mir wohl ansehen

                                      1 Reply Last reply Reply Quote 0
                                      • apollon77
                                        apollon77 @Chaot last edited by

                                        @Chaot an sich sollte keine Änderung in der 2.2 zu so einem Effekt führen. Was genau sind timeouts? Der Browser redet mit dem Web Adapter. Gibts im log irgendwas?

                                        Admin 3.7.5 sollte mit 2.1.1 tun soweit ich gelesen habe.

                                        1 Reply Last reply Reply Quote 0
                                        • E
                                          Einstein67 @apollon77 last edited by Einstein67

                                          @apollon77

                                          Die Logs sehen nicht so schlecht aus. Allerdings ist, im Vergleich zu den Logs von vor 2 Tagen, nun auch eine Fehlermeldung vorhanden: "ERROR: No packet manager found"

                                          Web-GUI - Entfernen einer Instanz

                                          $ ./iobroker del info.0
Delete adapter "info.0"
host.iob10b Counted 1 instances of info.0
host.iob10b Counted 1 devices of info.0
host.iob10b Counted 58 channels of info.0
ERROR: No packet manager found
host.iob10b Counted 294 states of info.0
host.iob10b Counted 14 states of system.adapter.info.0
host.iob10b Deleting 368 object(s).
host.iob10b: Only 200 objects left to be deleted.
process exited with code 0

                                          Web-GUI - Adapter löschen

                                          $ ./iobroker del info
Delete adapter "info"
host.iob10b Counted 1 instances of info
host.iob10b Counted 1 adapter for info
ERROR: No packet manager found
host.iob10b Deleting 2 object(s).
npm uninstall iobroker.info --silent --save --prefix "/opt/iobroker" (System call)
process exited with code 0

                                          Danach öffnet sich in beiden Fällen die AdapterKonfiguration ....

                                          Was mir noch aufgefallen ist: Das entfernen von Adaptern/Instanzen funktioniert mittels Konsole auch nur dann, wenn ioBroker vorher gestoppt wurde!

                                          Konsole - ioBroker läuft. Instanz wird nicht gelöscht (nach starten ist nach einiger Zeit der Adapter auch wieder da)

                                          iobroker@iob10b:~$ iobroker del info
Delete adapter "info"
host.iob10b Counted 1 instances of info
host.iob10b Counted 1 adapter for info
host.iob10b Counted 1 devices of info
host.iob10b Counted 58 channels of info
host.iob10b Counted 294 states of info
host.iob10b Counted 14 states of system.adapter.info
host.iob10b Deleting 369 object(s).
No packet manager found
host.iob10b: Only 200 objects left to be deleted.
npm uninstall iobroker.info --silent --save --prefix "/opt/iobroker" (System call)

                                          Konsole - ioBroker gestoppt und trotz der Fehlermeldung am Ende, wird die Instanz und der Adapter entfernt.

                                          iobroker@iob10b:~$ iobroker stop
iobroker@iob10b:~$ iobroker del info
Delete adapter "info"
host.iob10b Counted 1 instances of info
host.iob10b Counted 1 adapter for info
host.iob10b Counted 1 devices of info
host.iob10b Counted 58 channels of info
host.iob10b Counted 294 states of info
host.iob10b Counted 14 states of system.adapter.info
No packet manager found
host.iob10b Deleting 369 object(s).
host.iob10b: Only 200 objects left to be deleted.
npm uninstall iobroker.info --silent --save --prefix "/opt/iobroker" (System call)
 Cannot write files: /opt/iobroker/iobroker-data/files/info.admin/_data.json: ENOENT: no such file or directory, open '/opt/iobroker/iobroker-data/files/info.admin/_data.json'
                                          simatec 1 Reply Last reply Reply Quote 0
                                          • crunchip
                                            crunchip Forum Testing Most Active last edited by

                                            ich bekomm´s immer noch nicht gebacken, den Js-controller zu installieren

                                            root@IoBroker:~# cd /opt/iobroker
root@IoBroker:/opt/iobroker# iobroker stop
root@IoBroker:/opt/iobroker# npm install ioBroker/ioBroker.js-controller
[..................] / rollbackFailedOptional: verb npm-session cfd65c7e37e779d
                                            D 1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate

                                            898
                                            Online

                                            31.8k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            beta github js-controller
                                            18
                                            169
                                            15607
                                            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