Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. Iobroker startet nicht mehr nach Ubuntu 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

    Iobroker startet nicht mehr nach Ubuntu update

    This topic has been deleted. Only users with topic management privileges can see it.
    • Dutchman
      Dutchman Developer Most Active Administrators last edited by

      Und wenn du in den Verzeichnis bist und das ./ Mal weck läst?

      –-----------------------

      Send from mobile device

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

        Wie man an der Dateigröße (688 Byte) sieht, hat reinstall.sh DOS-Format (CR/LF anstelle LF) und muss erst in das http://forum.iobroker.net/viewtopic.php?f=17&t=8530&p=94147#p94110.

        1 Reply Last reply Reply Quote 0
        • S
          sveni_lee last edited by

          funktioniert bei mir nicht…

          nach

          tr -d '\r' < /opt/iobroker/reinstall.sh > /opt/iobroker/reinstall.sh
          

          ist die Größe null

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

            Evtl. weil Du die Datei überschreibst?

            Mal mit einem neuen Ziel-Dateinamen probiert?

            Gruß,

            Eric

            1 Reply Last reply Reply Quote 0
            • S
              sveni_lee last edited by

              Yeep… das wars

              Dann mach ich mal nen reinstall.

              Gesendet von iPhone mit Tapatalk Pro

              1 Reply Last reply Reply Quote 0
              • S
                sveni_lee last edited by

                ist nicht ganz sauber durchgelaufen…

                DONE iobroker.javascript
                npm WARN deprecated tar.gz@1.0.7: ⚠️  WARNING ⚠️ tar.gz module has been deprecated and your application is vulnerable. Please use tar module instead: https://npmjs.com/tar
                npm WARN deprecated localhost.daplie.me-certificates@1.3.5: this package has been deprecated
                npm WARN prefer global npm@2.15.12 should be installed with -g
                
                > unix-dgram@0.2.3 install /opt/iobroker/node_modules/unix-dgram
                > node-gyp rebuild
                
                gyp WARN EACCES user "root" does not have permission to access the dev dir "/home/svenilee/.node-gyp/6.12.0"
                gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/node_modules/unix-dgram/.node-gyp"
                make: Verzeichnis „/opt/iobroker/node_modules/unix-dgram/build“ wird betreten
                  CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o
                  SOLINK_MODULE(target) Release/obj.target/unix_dgram.node
                  COPY Release/unix_dgram.node
                make: Verzeichnis „/opt/iobroker/node_modules/unix-dgram/build“ wird verlassen
                
                > ursa@0.9.4 install /opt/iobroker/node_modules/ursa
                > node-gyp rebuild
                
                gyp WARN EACCES user "root" does not have permission to access the dev dir "/home/svenilee/.node-gyp/6.12.0"
                gyp WARN EACCES attempting to reinstall using temporary dev dir "/opt/iobroker/node_modules/ursa/.node-gyp"
                make: Verzeichnis „/opt/iobroker/node_modules/ursa/build“ wird betreten
                  CXX(target) Release/obj.target/ursaNative/src/ursaNative.o
                  SOLINK_MODULE(target) Release/obj.target/ursaNative.node
                  COPY Release/ursaNative.node
                make: Verzeichnis „/opt/iobroker/node_modules/ursa/build“ wird verlassen
                
                
                npm ERR! code 1
                FAIL iobroker.socketio
                iobroker@1.0.0 /opt/iobroker
                └─┬ iobroker.tankerkoenig@1.0.4
                  └─┬ xml2js@0.2.8
                    └── sax@0.5.8
                
                DONE iobroker.tankerkoenig
                npm WARN deprecated to-iso-string@0.0.2: to-iso-string has been deprecated, use @segment/to-iso-string instead.
                npm WARN deprecated jade@0.26.3: Jade has been renamed to pug, please install the latest version of pug instead of jade
                npm WARN deprecated minimatch@0.3.0: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
                npm WARN deprecated node-uuid@1.4.8: Use uuid module instead
                npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130
                
                
                ./reinstall.sh: Zeile 34: Dateiende beim Suchen nach »"« erreicht.
                ./reinstall.sh: Zeile 37: Syntaxfehler: Unerwartetes Dateiende.
                svenilee@Gotham-City:/opt/iobroker$
                
                
                1 Reply Last reply Reply Quote 0
                • eric2905
                  eric2905 last edited by

                  Ggf. das Original-reinstall.sh mal mit einem FTP vom Linux ziehen und die Datei mit einem "vernünftiges" Editor wieder umkonvertierten.

                  Gruß,

                  Eric

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

                    Nimm diese Datei, nach dem Entfernen von .txt am Ende des Dateinamen.
                    493_reinstall.sh.txt

                    1 Reply Last reply Reply Quote 0
                    • S
                      sveni_lee last edited by

                      so, alles gemacht aber noch kein erfolg…

                      2017-11-17 22:05:40.282  - ^[[32minfo^[[39m: host.Gotham-City iobroker.js-controller version 1.2.0 js-controller starting
                      2017-11-17 22:05:40.288  - ^[[32minfo^[[39m: host.Gotham-City Copyright (c) 2014-2017 bluefox, hobbyquaker
                      2017-11-17 22:05:40.288  - ^[[32minfo^[[39m: host.Gotham-City hostname: Gotham-City, node: v6.12.0
                      2017-11-17 22:05:40.289  - ^[[32minfo^[[39m: host.Gotham-City ip addresses: 192.168.1.142 xxxxx
                      2017-11-17 22:05:40.337  - ^[[32minfo^[[39m: host.Gotham-City  inMem-states listening on port 9000
                      2017-11-17 22:05:40.358  - ^[[32minfo^[[39m: host.Gotham-City  inMem-objects listening on port 9001
                      2017-11-17 22:05:40.365  - ^[[32minfo^[[39m: host.Gotham-City InMemoryDB connected
                      2017-11-17 22:05:40.367  - ^[[33mwarn^[[39m: Host on this system is not possible, because IP address is for states is 0.0.0.0
                      2017-11-17 22:05:40.371  - ^[[32minfo^[[39m: host.Gotham-City no instances found
                      2017-11-17 22:05:40.381  - ^[[31merror^[[39m: uncaught exception: logger is not defined
                      2017-11-17 22:05:40.383  - ^[[31merror^[[39m: ReferenceError: logger is not defined
                          at Object.decryptPhrase (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:77:9)
                          at /opt/iobroker/node_modules/iobroker.js-controller/controller.js:128:27
                          at Timeout._onTimeout (/opt/iobroker/node_modules/iobroker.js-controller/lib/objects/objectsInMemServer.js:2102:21)
                          at ontimeout (timers.js:386:11)
                          at tryOnTimeout (timers.js:250:5)
                          at Timer.listOnTimeout (timers.js:214:5)
                      2017-11-17 22:05:40.388  - ^[[32minfo^[[39m: host.Gotham-City terminated
                      2017-11-17 22:05:40.396  - ^[[32minfo^[[39m: iobroker _restart
                      2017-11-17 22:05:40.652  - ^[[32minfo^[[39m: iobroker Starting node restart.js
                      2017-11-17 22:05:40.662  - ^[[32minfo^[[39m: iobroker exit 0
                      2017-11-17 22:05:40.776  - ^[[32minfo^[[39m: host.Gotham-City received SIGTERM
                      2017-11-17 22:05:40.777  - ^[[32minfo^[[39m: host.Gotham-City terminated
                      
                      

                      einen Fehler gab es doch beim reinstall

                      iobroker.core@0.1.0 /opt/iobroker
                      └── (empty)
                      
                      npm ERR! code 1
                      FAIL iobroker.socketio
                      iobroker.core@0.1.0 /opt/iobroker
                      
                      
                      1 Reply Last reply Reply Quote 0
                      • S
                        sveni_lee last edited by

                        kannes sein, das das Problem der iobroker.core ist?

                        iobroker.core@0.1.0 /opt/iobroker
                        └── (empty)
                        
                        npm ERR! code 1
                        
                        
                        1 Reply Last reply Reply Quote 0
                        • S
                          sveni_lee last edited by

                          Also ich bekomme iobroker einfach nicht mehr ans laufen… es läuft immer wieder auf den selben Fehler hinaus.

                          Da bei reinstall immer wieder der Fehler bei socketio auftritt habe ich versucht dieses Modul per Hand zu installieren-

                          Leider auch ohne erfolg

                          ! svenilee@Gotham-City:/opt/iobroker$ sudo npm install iobroker.socketio --loglevel verbose npm info it worked if it ends with ok npm verb cli [ '/usr/bin/node', npm verb cli '/usr/bin/npm', npm verb cli 'install', npm verb cli 'iobroker.socketio', npm verb cli '--loglevel', npm verb cli 'verbose' ] npm info using npm@3.10.10 npm info using node@v6.12.0 npm verb request uri https://registry.npmjs.org/iobroker.socketio npm verb request no auth needed npm info attempt registry request try #1 at 17:24:10 npm verb request id 7d087b006a900a50 npm verb etag W/"59f82d29-1200c" npm verb lastModified Tue, 31 Oct 2017 07:58:33 GMT npm http request GET https://registry.npmjs.org/iobroker.socketio npm http 304 https://registry.npmjs.org/iobroker.socketio npm verb headers { date: 'Sun, 19 Nov 2017 16:24:10 GMT', npm verb headers via: '1.1 varnish', npm verb headers 'cache-control': 'max-age=300', npm verb headers etag: 'W/"59f82d29-1200c"', npm verb headers age: '232', npm verb headers connection: 'keep-alive', npm verb headers 'x-served-by': 'cache-hhn1533-HHN', npm verb headers 'x-cache': 'HIT', npm verb headers 'x-cache-hits': '1', npm verb headers 'x-timer': 'S1511108650.285039,VS0,VE1', npm verb headers vary: 'Accept-Encoding, Accept' } npm verb etag https://registry.npmjs.org/iobroker.socketio from cache npm verb get saving iobroker.socketio to /home/svenilee/.npm/registry.npmjs.org/iobroker.socketio/.cache.json npm verb correctMkdir /home/svenilee/.npm correctMkdir not in flight; initializing npm verb cache add spec iobroker.socketio npm verb addNamed "latest" is being treated as a dist-tag for iobroker.socketio npm info addNameTag [ 'iobroker.socketio', 'latest' ] npm verb addNameTag registry:https://registry.npmjs.org/iobroker.socketio not in flight; fetching npm verb get https://registry.npmjs.org/iobroker.socketio not expired, no request npm verb addNamed "1.8.6" is a plain semver version for iobroker.socketio npm verb afterAdd /home/svenilee/.npm/iobroker.socketio/1.8.6/package/package.json not in flight; writing npm verb correctMkdir /home/svenilee/.npm correctMkdir not in flight; initializing npm verb afterAdd /home/svenilee/.npm/iobroker.socketio/1.8.6/package/package.json written npm verb correctMkdir /home/svenilee/.npm/_locks correctMkdir not in flight; initializing npm verb lock using /home/svenilee/.npm/_locks/staging-66d2468782e8ffc7.lock for /opt/iobroker/node_modules/.staging npm verb unbuild node_modules/.staging/iobroker.socketio-0c17e29c npm verb gentlyRm don't care about contents; nuking /opt/iobroker/node_modules/.staging/iobroker.socketio-0c17e29c npm verb tar unpack /home/svenilee/.npm/iobroker.socketio/1.8.6/package.tgz npm verb tar unpacking to /opt/iobroker/node_modules/.staging/iobroker.socketio-0c17e29c npm verb gentlyRm don't care about contents; nuking /opt/iobroker/node_modules/.staging/iobroker.socketio-0c17e29c npm verb gentlyRm don't care about contents; nuking /opt/iobroker/node_modules/.staging/iobroker.socketio-0c17e29c/node_modules npm info lifecycle iobroker.socketio@1.8.6~preinstall: iobroker.socketio@1.8.6 npm verb unbuild node_modules/iobroker.socketio npm info lifecycle iobroker.socketio@1.8.6~preuninstall: iobroker.socketio@1.8.6 npm info lifecycle iobroker.socketio@1.8.6~uninstall: iobroker.socketio@1.8.6 npm verb unbuild rmStuff iobroker.socketio@1.8.6 from /opt/iobroker/node_modules npm info lifecycle iobroker.socketio@1.8.6~postuninstall: iobroker.socketio@1.8.6 npm verb gentlyRm don't care about contents; nuking /opt/iobroker/node_modules/iobroker.socketio npm info linkStuff iobroker.socketio@1.8.6 npm verb linkBins iobroker.socketio@1.8.6 npm verb linkMans iobroker.socketio@1.8.6 npm info lifecycle iobroker.socketio@1.8.6~install: iobroker.socketio@1.8.6 npm info lifecycle iobroker.socketio@1.8.6~postinstall: iobroker.socketio@1.8.6 npm verb unlock done using /home/svenilee/.npm/_locks/staging-66d2468782e8ffc7.lock for /opt/iobroker/node_modules/.staging iobroker.core@0.1.0 /opt/iobroker └── (empty) ! npm verb exit [ 0, true ] npm ERR! code 1 svenilee@Gotham-City:/opt/iobroker$ !

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

                            Ich empfehle die neuste js-controller vom github zu installieren:

                            
                            cd /opt/iobroker
                            iobroker stop
                            npm i https://github.com/ioBroker/ioBroker.js-controller/tarball/master --production
                            iobroker start
                            
                            

                            Danach sollte js-controller alle fehlende Pakete selbst nachinstallieren.

                            1 Reply Last reply Reply Quote 0
                            • S
                              sveni_lee last edited by

                              hallo Bluefox,

                              hab ich Probiert:

                              ` > svenilee@Gotham-City:/opt/iobroker$ sudo iobroker stop

                              [sudo] Passwort für svenilee:

                              iobroker controller daemon is not running

                              svenilee@Gotham-City:/opt/iobroker$ sudo npm i https://github.com/ioBroker/ioBroker.js … all/master --production

                              npm WARN deprecated tar.gz@1.0.7: <emoji seq="26a0">⚠️</emoji> WARNING <emoji seq="26a0">⚠️</emoji> tar.gz module has been deprecated and your application is vulnerable. Please use tar module instead: https://npmjs.com/tar

                              npm WARN deprecated localhost.daplie.me-certificates@1.3.5: this package has been deprecated

                              iobroker.js-controller@1.2.1 install /opt/iobroker/node_modules/iobroker.js-controller

                              node iobroker.js setup first

                              iobroker.core@0.1.0 /opt/iobroker

                              └── iobroker.js-controller@1.2.1

                              svenilee@Gotham-City:/opt/iobroker$ sudo iobroker start

                              Starting iobroker controller daemon...

                              iobroker controller daemon started. PID: 13515 `

                              log:
                              ` > 2017-11-19 20:45:53.635 - ^[[32minfo^[[39m: host.Gotham-City iobroker.js-controller version 1.2.1 js-controller starting

                              2017-11-19 20:45:53.640 - ^[[32minfo^[[39m: host.Gotham-City Copyright © 2014-2017 bluefox, 2014 hobbyquaker

                              2017-11-19 20:45:53.640 - ^[[32minfo^[[39m: host.Gotham-City hostname: Gotham-City, node: v6.12.0

                              2017-11-19 20:45:53.641 - ^[[32minfo^[[39m: host.Gotham-City ip addresses: 192.168.1.142 fd2d:5cf3:5594:0:be5f:f4ff:fe7d:a73c fe80::be5f:f4ff:fe7d:a$

                              2017-11-19 20:45:53.691 - ^[[32minfo^[[39m: host.Gotham-City inMem-states listening on port 9000

                              2017-11-19 20:45:53.711 - ^[[32minfo^[[39m: host.Gotham-City inMem-objects listening on port 9001

                              2017-11-19 20:45:53.718 - ^[[32minfo^[[39m: host.Gotham-City InMemoryDB connected

                              2017-11-19 20:45:53.720 - ^[[33mwarn^[[39m: Host on this system is not possible, because IP address is for states is 0.0.0.0

                              2017-11-19 20:45:53.725 - ^[[32minfo^[[39m: host.Gotham-City no instances found

                              2017-11-19 20:45:53.746 - ^[[33mwarn^[[39m: host.Gotham-City multihost service started on 0.0.0.0:50005 `

                              sollte laufen…

                              ` > svenilee@Gotham-City:/opt/iobroker$ sudo iobroker status

                              iobroker is running `

                              ist aber unter port 8081 nicht erreichbar

                              muß ich noch einen reinstall ausführen?

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

                                @sveni_lee:

                                hallo Bluefox,

                                hab ich Probiert:

                                ` > svenilee@Gotham-City:/opt/iobroker$ sudo iobroker stop

                                [sudo] Passwort für svenilee:

                                iobroker controller daemon is not running

                                svenilee@Gotham-City:/opt/iobroker$ sudo npm i https://github.com/ioBroker/ioBroker.js … all/master --production

                                npm WARN deprecated tar.gz@1.0.7: <emoji seq="26a0">⚠️</emoji> WARNING <emoji seq="26a0">⚠️</emoji> tar.gz module has been deprecated and your application is vulnerable. Please use tar module instead: https://npmjs.com/tar

                                npm WARN deprecated localhost.daplie.me-certificates@1.3.5: this package has been deprecated

                                iobroker.js-controller@1.2.1 install /opt/iobroker/node_modules/iobroker.js-controller

                                node iobroker.js setup first

                                iobroker.core@0.1.0 /opt/iobroker

                                └── iobroker.js-controller@1.2.1

                                svenilee@Gotham-City:/opt/iobroker$ sudo iobroker start

                                Starting iobroker controller daemon...

                                iobroker controller daemon started. PID: 13515 `

                                log:
                                ` > 2017-11-19 20:45:53.635 - ^[[32minfo^[[39m: host.Gotham-City iobroker.js-controller version 1.2.1 js-controller starting

                                2017-11-19 20:45:53.640 - ^[[32minfo^[[39m: host.Gotham-City Copyright © 2014-2017 bluefox, 2014 hobbyquaker

                                2017-11-19 20:45:53.640 - ^[[32minfo^[[39m: host.Gotham-City hostname: Gotham-City, node: v6.12.0

                                2017-11-19 20:45:53.641 - ^[[32minfo^[[39m: host.Gotham-City ip addresses: 192.168.1.142 fd2d:5cf3:5594:0:be5f:f4ff:fe7d:a73c fe80::be5f:f4ff:fe7d:a$

                                2017-11-19 20:45:53.691 - ^[[32minfo^[[39m: host.Gotham-City inMem-states listening on port 9000

                                2017-11-19 20:45:53.711 - ^[[32minfo^[[39m: host.Gotham-City inMem-objects listening on port 9001

                                2017-11-19 20:45:53.718 - ^[[32minfo^[[39m: host.Gotham-City InMemoryDB connected

                                2017-11-19 20:45:53.720 - ^[[33mwarn^[[39m: Host on this system is not possible, because IP address is for states is 0.0.0.0

                                2017-11-19 20:45:53.725 - ^[[32minfo^[[39m: host.Gotham-City no instances found

                                2017-11-19 20:45:53.746 - ^[[33mwarn^[[39m: host.Gotham-City multihost service started on 0.0.0.0:50005 `

                                sollte laufen…

                                ` > svenilee@Gotham-City:/opt/iobroker$ sudo iobroker status

                                iobroker is running `

                                ist aber unter port 8081 nicht erreichbar

                                muß ich noch einen reinstall ausführen? `
                                Wo sind deine Einstellungen? Die datei /opt/iobroker-data/objects.json lehr oder default.

                                1 Reply Last reply Reply Quote 0
                                • S
                                  sveni_lee last edited by

                                  ich würde sagen default…

                                  steht fast überall was drin

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

                                    Ich wollte damit sagen, dass die Einstellungen weg sind.

                                    1 Reply Last reply Reply Quote 0
                                    • S
                                      sveni_lee last edited by

                                      sorry… versteh nicht was Du meinst?

                                      die Datei ist doch da?

                                      oder Anders... wie bekomme ich diese wieder?

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        sveni_lee last edited by

                                        so, ich habe jetzt eine Image-Sicherung vom Server genommen und den iobroker-ordner in

                                        mein aktuelles Image kopiert. Danach funktioniert es schon einmal wieder…

                                        Aber wie bekomme ich jetzt meinen aktuellen Datenstand dort rein, einfach den iobroker-data ordner wieder zurück

                                        kopieren?

                                        1 Reply Last reply Reply Quote 0
                                        • Dutchman
                                          Dutchman Developer Most Active Administrators last edited by

                                          @sveni_lee:

                                          Aber wie bekomme ich jetzt meinen aktuellen Datenstand dort rein, einfach den iobroker-data ordner wieder zurück

                                          kopieren? `

                                          Definiere Datenstand, history Daten oder?

                                          –-----------------------

                                          Send from mobile device

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            sveni_lee last edited by

                                            Objektpunkte, Skripte, Adaptereinstellungen

                                            Edit: hat nicht funktioniert…

                                            Gibt es einen Ordner in dem die Skripte abgelegt werden, do das ich wenigstens diese wieder herstellen kann?

                                            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

                                            847
                                            Online

                                            31.9k
                                            Users

                                            80.2k
                                            Topics

                                            1.3m
                                            Posts

                                            6
                                            31
                                            2753
                                            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