Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Nodejs und npm Update

    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

    Nodejs und npm Update

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

      leider nein

      2018-05-12 20:01:30.051  - [32minfo[39m: host.IoBrocker iobroker.js-controller version 1.4.2 js-controller starting
      2018-05-12 20:01:30.055  - [32minfo[39m: host.IoBrocker Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
      2018-05-12 20:01:30.055  - [32minfo[39m: host.IoBrocker hostname: IoBrocker, node: v6.14.2
      2018-05-12 20:01:30.055  - [32minfo[39m: host.IoBrocker ip addresses: 192.168.178.152 fe80::20c:29ff:fe45:b018
      2018-05-12 20:01:30.122  - [32minfo[39m: host.IoBrocker  inMem-states listening on port 9000
      2018-05-12 20:01:30.289  - [32minfo[39m: host.IoBrocker  inMem-objects listening on port 9001
      2018-05-12 20:01:30.295  - [32minfo[39m: host.IoBrocker InMemoryDB connected
      2018-05-12 20:01:30.308  - [32minfo[39m: host.IoBrocker 40 instances found
      2018-05-12 20:01:30.319  - [32minfo[39m: host.IoBrocker starting 35 instances
      2018-05-12 20:01:30.339  - [32minfo[39m: host.IoBrocker instance system.adapter.admin.2 started with pid 5250
      2018-05-12 20:01:31.566  - [33mwarn[39m: sayit.0 Reconnection to DB.
      2018-05-12 20:01:31.576  - [33mwarn[39m: sayit.0 Reconnection to DB.
      2018-05-12 20:01:31.570  - [33mwarn[39m: hm-rpc.2 Reconnection to DB.
      2018-05-12 20:01:31.583  - [33mwarn[39m: hm-rpc.2 Reconnection to DB.
      2018-05-12 20:01:32.125  - [31merror[39m: sayit.0 already running
      2018-05-12 20:01:32.520  - [32minfo[39m: host.IoBrocker Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
      2018-05-12 20:01:32.708  - [31merror[39m: Caught by controller[0]: 2018-05-12 20:01:32.676  -  admin.2 port 8081 already in use
      2018-05-12 20:01:32.709  - [31merror[39m: host.IoBrocker instance system.adapter.admin.2 terminated with code 1 ()
      2018-05-12 20:01:32.709  - [32minfo[39m: host.IoBrocker Restart adapter system.adapter.admin.2 because enabled
      2018-05-12 20:01:32.736  - [31merror[39m: hm-rpc.2 already running
      2018-05-12 20:01:32.866  - [33mwarn[39m: hm-rpc.0 Reconnection to DB.
      2018-05-12 20:01:32.876  - [33mwarn[39m: hm-rpc.0 Reconnection to DB.
      2018-05-12 20:01:33.392  - [33mwarn[39m: web.0 Reconnection to DB.
      2018-05-12 20:01:33.401  - [33mwarn[39m: web.0 Reconnection to DB.
      2018-05-12 20:01:33.781  - [31merror[39m: web.0 already running
      2018-05-12 20:01:33.879  - [33mwarn[39m: admin.2 Reconnection to DB.
      2018-05-12 20:01:33.888  - [33mwarn[39m: admin.2 Reconnection to DB.
      2018-05-12 20:01:34.147  - [33mwarn[39m: ping.0 Reconnection to DB.
      2018-05-12 20:01:34.154  - [33mwarn[39m: ping.0 Reconnection to DB.
      2018-05-12 20:01:34.379  - [32minfo[39m: host.IoBrocker instance scheduled system.adapter.ical.0 0,30 * * * *
      2018-05-12 20:01:34.387  - [32minfo[39m: host.IoBrocker instance system.adapter.ical.0 started with pid 5271
      2018-05-12 20:01:34.557  - [31merror[39m: hm-rpc.0 already running
      2018-05-12 20:01:35.053  - [31merror[39m: admin.2 already running
      2018-05-12 20:01:35.149  - [31merror[39m: ping.0 already running
      2018-05-12 20:01:38.343  - [32minfo[39m: host.IoBrocker instance system.adapter.simple-api.0 started with pid 5281
      2018-05-12 20:01:38.690  - [31merror[39m: Caught by controller[0]: 2018-05-12 20:01:38.679  -  simple-api.0 already running
      2018-05-12 20:01:38.690  - [31merror[39m: host.IoBrocker instance system.adapter.simple-api.0 terminated with code 7 (Adapter already running)
      2018-05-12 20:01:38.690  - [32minfo[39m: host.IoBrocker Restart adapter system.adapter.simple-api.0 because enabled
      2018-05-12 20:01:41.987  - [32minfo[39m: host.IoBrocker instance system.adapter.ical.0 terminated with code 0 (OK)
      2018-05-12 20:01:42.325  - [32minfo[39m: host.IoBrocker instance system.adapter.web.0 started with pid 5291
      2018-05-12 20:01:42.730  - [31merror[39m: Caught by controller[0]: 2018-05-12 20:01:42.721  -  web.0 already running
      2018-05-12 20:01:42.730  - [31merror[39m: host.IoBrocker instance system.adapter.web.0 terminated with code 7 (Adapter already running)
      2018-05-12 20:01:42.730  - [32minfo[39m: host.IoBrocker Restart adapter system.adapter.web.0 because enabled
      2018-05-12 20:01:46.325  - [32minfo[39m: host.IoBrocker instance system.adapter.hm-rega.0 started with pid 5301
      2018-05-12 20:01:46.645  - [31merror[39m: Caught by controller[0]: 2018-05-12 20:01:46.635  -  hm-rega.0 already running
      2018-05-12 20:01:46.645  - [31merror[39m: host.IoBrocker instance system.adapter.hm-rega.0 terminated with code 7 (Adapter already running)
      2018-05-12 20:01:46.645  - [32minfo[39m: host.IoBrocker Restart adapter system.adapter.hm-rega.0 because enabled
      2018-05-12 20:01:50.327  - [32minfo[39m: host.IoBrocker instance system.adapter.hm-rpc.0 started with pid 5311
      2018-05-12 20:01:50.674  - [31merror[39m: Caught by controller[0]: 2018-05-12 20:01:50.666  -  hm-rpc.0 already running
      2018-05-12 20:01:50.674  - [31merror[39m: host.IoBrocker instance system.adapter.hm-rpc.0 terminated with code 7 (Adapter already running)
      2018-05-12 20:01:50.674  - [32minfo[39m: host.IoBrocker Restart adapter system.adapter.hm-rpc.0 because enabled
      2018-05-12 20:01:54.328  - [32minfo[39m: host.IoBrocker instance system.adapter.hm-rpc.1 started with pid 5321
      2018-05-12 20:01:58.323  - [32minfo[39m: host.IoBrocker instance system.adapter.hm-rpc.2 started with pid 5331
      2018-05-12 20:02:02.326  - [32minfo[39m: host.IoBrocker instance system.adapter.sayit.0 started with pid 5341
      2018-05-12 20:02:02.715  - [32minfo[39m: host.IoBrocker instance system.adapter.admin.2 started with pid 5347
      2018-05-12 20:02:05.469  - [32minfo[39m: host.IoBrocker Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
      2018-05-12 20:02:07.639  - [32minfo[39m: host.IoBrocker instance system.adapter.vis.0 terminated while should be started once
      2018-05-12 20:02:08.698  - [32minfo[39m: host.IoBrocker instance system.adapter.simple-api.0 started with pid 5371
      2018-05-12 20:02:12.736  - [32minfo[39m: host.IoBrocker instance system.adapter.web.0 started with pid 5388
      2018-05-12 20:02:16.651  - [32minfo[39m: host.IoBrocker instance system.adapter.hm-rega.0 started with pid 5398
      2018-05-12 20:02:20.681  - [32minfo[39m: host.IoBrocker instance system.adapter.hm-rpc.0 started with pid 5408
      2018-05-12 20:02:22.325  - [32minfo[39m: host.IoBrocker instance system.adapter.rpi2.0 started with pid 5418
      2018-05-12 20:02:26.330  - [32minfo[39m: host.IoBrocker instance scheduled system.adapter.dwd.0 5 * * * *
      2018-05-12 20:02:26.338  - [32minfo[39m: host.IoBrocker instance system.adapter.dwd.0 started with pid 5436
      2018-05-12 20:02:27.576  - [32minfo[39m: host.IoBrocker instance system.adapter.dwd.0 terminated with code 0 (OK)
      2018-05-12 20:02:30.328  - [32minfo[39m: host.IoBrocker instance system.adapter.ping.0 started with pid 5446
      2018-05-12 20:02:34.325  - [32minfo[39m: host.IoBrocker instance system.adapter.node-red.0 started with pid 5458
      2018-05-12 20:02:34.736  - [31merror[39m: node-red.0 setObject id missing!!
      2018-05-12 20:02:37.141  - [33mwarn[39m: node-red.0 12 May 20:02:37 - [warn] ------------------------------------------------------
      
      2018-05-12 20:02:37.143  - [33mwarn[39m: node-red.0 12 May 20:02:37 - [warn] [node-red/rpi-gpio] Info : Ignoring Raspberry Pi specific node
      
      2018-05-12 20:02:37.144  - [33mwarn[39m: node-red.0 12 May 20:02:37 - [warn] ------------------------------------------------------
      
      2018-05-12 20:02:37.145  - [33mwarn[39m: node-red.0 12 May 20:02:37 - [info] User directory : /opt/iobroker/iobroker-data/node-red/
      12 May 20:02:37 - [warn] Projects disabled : set editorTheme.projects.enabled=true to enable
      
      2018-05-12 20:02:37.219  - [33mwarn[39m: node-red.0 12 May 20:02:37 - [warn] 
      
      ---------------------------------------------------------------------
      Your flow credentials file is encrypted using a system-generated key.
      
      If the system-generated key is lost for any reason, your credentials
      file will not be recoverable, you will have to delete it and re-enter
      your credentials.
      
      You should set your own key using the 'credentialSecret' option in
      your settings file. Node-RED will then re-encrypt your credentials
      file using your chosen key the next time you deploy a change.
      ---------------------------------------------------------------------
      
      2018-05-12 20:02:42.325  - [32minfo[39m: host.IoBrocker instance system.adapter.samsung.0 started with pid 5487
      2018-05-12 20:02:54.329  - [32minfo[39m: host.IoBrocker instance scheduled system.adapter.yr.0 0 * * * *
      2018-05-12 20:02:54.335  - [32minfo[39m: host.IoBrocker instance system.adapter.yr.0 started with pid 5500
      2018-05-12 20:02:58.231  - [32minfo[39m: host.IoBrocker object change system.adapter.synology.0
      2018-05-12 20:02:58.231  - [32minfo[39m: host.IoBrocker "system.adapter.synology.0" disabled
      2018-05-12 20:02:58.325  - [32minfo[39m: host.IoBrocker instance system.adapter.nut.1 started with pid 5510
      2018-05-12 20:02:59.094  - [32minfo[39m: host.IoBrocker object change system.adapter.telegram.0
      2018-05-12 20:02:59.094  - [32minfo[39m: host.IoBrocker "system.adapter.telegram.0" disabled
      2018-05-12 20:02:59.997  - [32minfo[39m: host.IoBrocker instance system.adapter.yr.0 terminated with code 0 (OK)
      2018-05-12 20:03:14.327  - [32minfo[39m: host.IoBrocker instance scheduled system.adapter.tvspielfilm.0 */30 * * * *
      2018-05-12 20:03:14.332  - [32minfo[39m: host.IoBrocker instance system.adapter.tvspielfilm.0 started with pid 5532
      2018-05-12 20:03:18.326  - [32minfo[39m: host.IoBrocker instance system.adapter.yahka.0 started with pid 5544
      2018-05-12 20:03:22.331  - [32minfo[39m: host.IoBrocker instance system.adapter.yahka.1 started with pid 5580
      
      
      1 Reply Last reply Reply Quote 0
      • wendy2702
        wendy2702 last edited by

        @chka:

        leider nein `

        Heißt jetzt was? Du kannst/willst es nicht probieren oder ???

        Das logfile sieht doch schon besser aus bis auf das NodeRed Problem.

        1 Reply Last reply Reply Quote 0
        • C
          chka last edited by

          sorry habe nicht zu Ende geschrieben, es hat leider nichts gebracht anbei die log mit deaktiviertem java, nodered und noch diversen anderen.

          allerdings da gleiche

          <code>2018-05-12 20:14:07.342  - [32minfo[39m: host.IoBrocker iobroker.js-controller version 1.4.2 js-controller starting
          2018-05-12 20:14:07.345  - [32minfo[39m: host.IoBrocker Copyright (c) 2014-2018 bluefox, 2014 hobbyquaker
          2018-05-12 20:14:07.345  - [32minfo[39m: host.IoBrocker hostname: IoBrocker, node: v6.14.2
          2018-05-12 20:14:07.346  - [32minfo[39m: host.IoBrocker ip addresses: 192.168.178.152 fe80::20c:29ff:fe45:b018
          2018-05-12 20:14:07.431  - [32minfo[39m: host.IoBrocker  inMem-states listening on port 9000
          2018-05-12 20:14:07.603  - [32minfo[39m: host.IoBrocker  inMem-objects listening on port 9001
          2018-05-12 20:14:07.610  - [32minfo[39m: host.IoBrocker InMemoryDB connected
          2018-05-12 20:14:07.621  - [32minfo[39m: host.IoBrocker 40 instances found
          2018-05-12 20:14:07.632  - [32minfo[39m: host.IoBrocker starting 32 instances
          2018-05-12 20:14:07.661  - [32minfo[39m: host.IoBrocker instance system.adapter.admin.2 started with pid 1054
          2018-05-12 20:14:09.906  - [32minfo[39m: host.IoBrocker Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"
          2018-05-12 20:14:11.643  - [32minfo[39m: host.IoBrocker instance scheduled system.adapter.ical.0 0,30 * * * *
          2018-05-12 20:14:11.647  - [32minfo[39m: host.IoBrocker instance system.adapter.ical.0 started with pid 1074
          2018-05-12 20:14:15.642  - [32minfo[39m: host.IoBrocker instance system.adapter.simple-api.0 started with pid 1084
          2018-05-12 20:14:19.130  - [32minfo[39m: host.IoBrocker instance system.adapter.ical.0 terminated with code 0 (OK)
          2018-05-12 20:14:19.642  - [32minfo[39m: host.IoBrocker instance system.adapter.web.0 started with pid 1094
          2018-05-12 20:14:23.641  - [32minfo[39m: host.IoBrocker instance system.adapter.hm-rega.0 started with pid 1105
          2018-05-12 20:14:27.646  - [32minfo[39m: host.IoBrocker instance system.adapter.hm-rpc.0 started with pid 1115
          2018-05-12 20:14:31.644  - [32minfo[39m: host.IoBrocker instance system.adapter.hm-rpc.1 started with pid 1125
          2018-05-12 20:14:35.642  - [32minfo[39m: host.IoBrocker instance system.adapter.hm-rpc.2 started with pid 1142
          2018-05-12 20:14:39.643  - [32minfo[39m: host.IoBrocker instance system.adapter.sayit.0 started with pid 1152
          2018-05-12 20:14:45.180  - [32minfo[39m: host.IoBrocker instance system.adapter.vis.0 terminated while should be started once
          2018-05-12 20:14:59.642  - [32minfo[39m: host.IoBrocker instance system.adapter.rpi2.0 started with pid 1172
          2018-05-12 20:15:03.651  - [32minfo[39m: host.IoBrocker instance scheduled system.adapter.dwd.0 5 * * * *
          2018-05-12 20:15:03.655  - [32minfo[39m: host.IoBrocker instance system.adapter.dwd.0 started with pid 1198
          2018-05-12 20:15:04.897  - [32minfo[39m: host.IoBrocker instance system.adapter.dwd.0 terminated with code 0 (OK)
          2018-05-12 20:15:07.642  - [32minfo[39m: host.IoBrocker instance system.adapter.ping.0 started with pid 1215
          2018-05-12 20:15:15.643  - [32minfo[39m: host.IoBrocker instance system.adapter.samsung.0 started with pid 1227
          2018-05-12 20:15:27.645  - [32minfo[39m: host.IoBrocker instance scheduled system.adapter.yr.0 0 * * * *
          2018-05-12 20:15:27.650  - [32minfo[39m: host.IoBrocker instance system.adapter.yr.0 started with pid 1240
          2018-05-12 20:15:31.643  - [32minfo[39m: host.IoBrocker instance system.adapter.nut.1 started with pid 1252
          2018-05-12 20:15:33.212  - [32minfo[39m: host.IoBrocker instance system.adapter.yr.0 terminated with code 0 (OK)
          2018-05-12 20:15:47.640  - [32minfo[39m: host.IoBrocker instance scheduled system.adapter.tvspielfilm.0 */30 * * * *
          2018-05-12 20:15:47.643  - [32minfo[39m: host.IoBrocker instance system.adapter.tvspielfilm.0 started with pid 1264
          2018-05-12 20:15:51.642  - [32minfo[39m: host.IoBrocker instance system.adapter.yahka.0 started with pid 1276
          2018-05-12 20:15:52.303  - [33mwarn[39m: tvspielfilm.0 Error: read ECONNRESET
          2018-05-12 20:15:55.651  - [32minfo[39m: host.IoBrocker instance system.adapter.yahka.1 started with pid 1286[/code]</code>
          
          1 Reply Last reply Reply Quote 0
          • C
            chka last edited by

            ich schalte jetzt mal nach und nach alles ab und schau dann mal wo es ua. harkt

            1 Reply Last reply Reply Quote 0
            • wendy2702
              wendy2702 last edited by

              Das sieht nur nach restart log aus…

              Wie sieht es denn im Fehler Fall aus bzw. Was genau passiert da?

              Gesendet von iPhone mit Tapatalk Pro

              1 Reply Last reply Reply Quote 0
              • C
                chka last edited by

                iobroker geht im Fehlerfall aus.

                danach kann ich es wieder starten und er geht nach einer zeit wieder aus.

                die restart log ist lehr

                ich installiere jetzt mal alle deaktivierten adapter neu.

                was mir aufgefallen ist bei der neu Installation kommt immer wieder das hier:

                deprecated node-uuid@1.4.8: Use uuid module instead
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4 (node_modules/iobroker.ble/node_modules/noble/node_modules/xpc-connection):npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
                npm WARN optional SKIPPING OPTIONAL DEPENDENCY: xpc-connection@~0.1.4 (node_modules/noble/node_modules/xpc-connection):
                npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for xpc-connection@0.1.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
                
                
                1 Reply Last reply Reply Quote 0
                • wendy2702
                  wendy2702 last edited by

                  Du hast nicht zufällig noch die Logs vom Node/Npm Upgrade?

                  Gesendet von iPhone mit Tapatalk Pro

                  1 Reply Last reply Reply Quote 0
                  • C
                    chka last edited by

                    leider nein aber ich habe vorher ein snapshot gemacht von der vm. oder liegt irgendwo die log

                    ich bin weiter, java mag einfach nicht starten

                    2018-05-12 20:59:00.580  - [34mdebug[39m: javascript.0 objectDB connected
                    2018-05-12 20:59:00.596  - [34mdebug[39m: javascript.0 statesDB connected
                    2018-05-12 20:59:00.613  - [32minfo[39m: javascript.0 starting. Version 3.6.4 in /opt/iobroker/node_modules/iobroker.javascript, node: v6.14.2
                    2018-05-12 20:59:00.617  - [32minfo[39m: javascript.0 requesting all states
                    2018-05-12 20:59:00.618  - [32minfo[39m: javascript.0 requesting all objects
                    2018-05-12 20:59:01.305  - [32minfo[39m: javascript.0 received all states
                    
                    

                    yahka gibt iobroker dann den rest

                    1 Reply Last reply Reply Quote 0
                    • wendy2702
                      wendy2702 last edited by

                      Was genau machst du jetzt eigentlich?

                      Aus deinem ersten log:

                      @chka:

                      2018-05-04 20:52:46.221 - info: host.IoBrocker hostname: IoBrocker, node: v8.11.1 `

                      Dann aus den anderen:

                      @chka:

                      2018-05-12 20:14:07.345 - [32minfo[39m: host.IoBrocker hostname: IoBrocker, node: v6.14.2 `

                      1 Reply Last reply Reply Quote 0
                      • C
                        chka last edited by

                        ich habe es mit beiden versucht einmal die Anleitung von deinem post vom 30.04.2018 dan auch von BuZZy 02.05.2018, durch die snapshots kann ich Gott sei dank immer wieder von vorne es versuchen.

                        das Problem ist aber bei beiden das gleiche egal ob node 6 oder 8

                        1 Reply Last reply Reply Quote 0
                        • wendy2702
                          wendy2702 last edited by

                          @chka:

                          ich habe es mit beiden versucht einmal die Anleitung von deinem post vom 30.04.2018 dan auch von BuZZy 02.05.2018, durch die snapshots kann ich `

                          Wird echt Zeit für einen neuen Avatar… :roll:

                          Wenn du es immer wieder neu machen kannst...

                          dann logge doch mal den Node/NPM Upgrade und reinstall komplett mit.

                          1 Reply Last reply Reply Quote 0
                          • C
                            chka last edited by

                            ups sorry 😄

                            wie kann ich das am besten in eine log schreiben geht das mit hinten dran - log.log also

                            curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash - log.log

                            1 Reply Last reply Reply Quote 0
                            • wendy2702
                              wendy2702 last edited by

                              Mit welchem Tool bit du auf der VM verbunden, wo tippelst du deine Befehle ein?

                              Putty? Falls ja am einfachsten da das logging aktivieren.

                              1 Reply Last reply Reply Quote 0
                              • C
                                chka last edited by

                                ne über Mac OS terminal, habe aber was gefunden:

                                /usr/bin/script ~/Desktop/Terminal.log
                                

                                nicht wundern ich habe den Befehl für node Installation doppelt geschickt: 883_terminal.log

                                1 Reply Last reply Reply Quote 0
                                • wendy2702
                                  wendy2702 last edited by

                                  Hast du vor der neu installation mal ein Linux update gemacht?

                                  apt update && apt upgrade
                                  

                                  Auch bei der Installation nur "apt" verwenden seit Jessie.

                                  Hast du nach Ausführen von:````
                                  curl -sL https://deb.nodesource.com/setup_6.x | sudo -E bash

                                  
                                  Auch das gemacht wie am Ende der Ausführung gefordert:
                                  
                                  

                                  sudo apt-get install -y nodejs ` to install Node.js 6.x LTS Boron and npm

                                  
                                  War das mal ein Wheezy welches du upgegraded hast?
                                  1 Reply Last reply Reply Quote 0
                                  • C
                                    chka last edited by

                                    ja apt update && apt upgrade ist recht aktuell, von letzter Woche

                                    dachte mit````
                                    apt-get install -y build-essential libavahi-compat-libdnssd-dev libudev-dev libpam0g-dev nodejs

                                    ist
                                    

                                    sudo apt-get install -y nodejs

                                    
                                    ja es ist Debian Wheezy
                                    
                                    nachtrag:
                                    
                                    cat /etc/os-release
                                    
                                    PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
                                    
                                    NAME="Debian GNU/Linux"
                                    
                                    VERSION_ID="8"
                                    
                                    VERSION="8 (jessie)"
                                    
                                    ID=debian
                                    
                                    HOME_URL="[http://www.debian.org/](http://www.debian.org/)"
                                    
                                    SUPPORT_URL="[http://www.debian.org/support](http://www.debian.org/support)"
                                    
                                    BUG_REPORT_URL="[https://bugs.debian.org/](https://bugs.debian.org/)"
                                    [883_iobroker.2018-05-13.log](/assets/uploads/files/883_iobroker.2018-05-13.log)
                                    [883_terminal.log](/assets/uploads/files/883_terminal.log)
                                    1 Reply Last reply Reply Quote 0
                                    • wendy2702
                                      wendy2702 last edited by

                                      Aktuell nur Ipad verfügbar zum log schauen.

                                      Würde in erster Linie glaube ich immer noch auf ein JavaScript problem tippen wenn ich das richtig gesehen habe.

                                      Mal lust auf einen anderen Versuch?

                                      Dann iobroker backup machen

                                      Iobroker von der VM komplett löschen inklusive Node/NPM etc.

                                      Dann direkt mit Node 6 oder 8 installieren und dann iobroker neu installieren und anschließend ein restore vom backup.

                                      1 Reply Last reply Reply Quote 0
                                      • C
                                        chka last edited by

                                        ja das kann ich mal machen, muss das nur auf Dienstag verschieben.

                                        Danke dir und Glückwunsch zum neuen avatar 😉

                                        1 Reply Last reply Reply Quote 0
                                        • wendy2702
                                          wendy2702 last edited by

                                          @chka:

                                          Danke dir und Glückwunsch zum neuen avatar 😉 `

                                          Danke! Jetzt weiß jeder welche Comics und Filme ich mag :mrgreen:

                                          1 Reply Last reply Reply Quote 0
                                          • C
                                            chka last edited by

                                            so backup habe ich schon mal gemacht

                                            root@IoBrocker:/opt/iobroker# ./iobroker backup
                                            Backup created: /opt/iobroker/backups/2018_05_15-19_03_40_backupiobroker.tar.gz
                                            
                                            

                                            allerdings stehe ich auf dem schlauch wie deinstalliere ich iobroker?

                                            rm /opt/iobroker/*
                                            ````und vorher das backup wo anders hinschieben, reicht dies?
                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            854
                                            Online

                                            31.9k
                                            Users

                                            80.1k
                                            Topics

                                            1.3m
                                            Posts

                                            21
                                            124
                                            30008
                                            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