Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. [gelöst] iobroker offline nach admin 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

    [gelöst] iobroker offline nach admin update

    This topic has been deleted. Only users with topic management privileges can see it.
    • J
      JRiddim @Guest last edited by JRiddim

      @HeinrichB danke dir, den Thread habe ich gesehen, habe alles auch durchprobiert...

      ? 1 Reply Last reply Reply Quote 0
      • ?
        A Former User @JRiddim last edited by

        @JRiddim verzeih meine Einmischung

        J 1 Reply Last reply Reply Quote 0
        • J
          JRiddim @Guest last edited by

          @HeinrichB ich bin für jede Hilfe dankbar!

          haselchen 1 Reply Last reply Reply Quote 0
          • haselchen
            haselchen Most Active @JRiddim last edited by

            @JRiddim

            was kommt unter

            ps -A | grep iobroker

            raus

            J 1 Reply Last reply Reply Quote 0
            • J
              JRiddim @haselchen last edited by JRiddim

              @haselchen

              ps -A | grep iobroker
  541 ?        00:19:16 iobroker.js-con
              haselchen 1 Reply Last reply Reply Quote 0
              • haselchen
                haselchen Most Active @JRiddim last edited by

                @JRiddim
                ok
                erst den befehl eingeben
                cd /opt/iobroker

                dann den
                node node_modules/iobroker.js-controller/controller.js --logs

                J 1 Reply Last reply Reply Quote 0
                • J
                  JRiddim @haselchen last edited by

                  @haselchen sagte in iobroker nicht mehr erreichbar nach admin update:

                  node node_modules/iobroker.js-controller/controller.js --logs

                  node node_modules/iobroker.js-controller/controller.js --logs
2020-01-29 22:32:59.327  - info: host.raspberrypi iobroker.js-controller version 2.2.8 js-controller starting
2020-01-29 22:32:59.336  - info: host.raspberrypi Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-01-29 22:32:59.337  - info: host.raspberrypi hostname: raspberrypi, node: v10.18.1
2020-01-29 22:32:59.339  - info: host.raspberrypi ip addresses: 192.168.100.50 fe80::dea6:32ff:fe0a:7cb6 fe80::fc97:c0ff:fef0:a5a8
2020-01-29 22:32:59.803  - info: host.raspberrypi  Error inMem-objects listening on port 9001
2020-01-29 22:33:00.351  - info: host.raspberrypi  Error inMem-states listening on port 9000
2020-01-29 22:33:00.405  - info: host.raspberrypi connected to Objects and States
2020-01-29 22:33:00.551  - info: host.raspberrypi 33 instances found
host.raspberrypi check instance "system.adapter.discovery.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.info.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.mihome-vacuum.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.telegram.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.hue.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.hm-rpc.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.hm-rega.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.hm-rpc.1" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.ping.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.web.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.vis.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.vis-hqwidgets.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.vis-timeandweather.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.vis-jqui-mfd.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.vis-metro.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.spotify-premium.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.vis-google-fonts.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.vis-fancyswitch.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.vis-bars.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.vis-history.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.ical.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.vis-justgage.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.weatherunderground.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.yr.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.backitup.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.terminal.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.zigbee.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.javascript.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.yahka.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.youtube.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.admin.0" for host "raspberrypi"
host.raspberrypi check instance "system.adapter.admin.1" for host "raspberrypi"
2020-01-29 22:33:00.615  - info: host.raspberrypi starting 30 instances
2020-01-29 22:33:00.665  - info: host.raspberrypi instance system.adapter.admin.0 started with pid 19462
================================== > LOG REDIRECT system.adapter.admin.0 => false [Process stopped]
2020-01-29 22:33:02.894  - error: host.raspberrypi instance system.adapter.admin.0 terminated by request of the instance itself and will not be restarted, before user restarts it.
2020-01-29 22:33:02.894  - info: host.raspberrypi Do not restart adapter system.adapter.admin.0 because desired by instance
================================== > LOG REDIRECT system.adapter.admin.0 => false [system.adapter.admin.0.logging]
2020-01-29 22:33:04.633  - info: host.raspberrypi instance system.adapter.admin.1 started with pid 19655
================================== > LOG REDIRECT system.adapter.admin.1 => false [Process stopped]
2020-01-29 22:33:06.831  - error: host.raspberrypi instance system.adapter.admin.1 terminated by request of the instance itself and will not be restarted, before user restarts it.
2020-01-29 22:33:06.832  - info: host.raspberrypi Do not restart adapter system.adapter.admin.1 because desired by instance
================================== > LOG REDIRECT system.adapter.admin.1 => false [system.adapter.admin.1.logging]
2020-01-29 22:33:08.633  - info: host.raspberrypi instance system.adapter.discovery.0 started with pid 19684
2020-01-29 22:33:10.198  - error: host.raspberrypi instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-01-29 22:33:10.199  - info: host.raspberrypi Restart adapter system.adapter.discovery.0 because enabled
2020-01-29 22:33:12.632  - info: host.raspberrypi instance system.adapter.info.0 started with pid 19861
2020-01-29 22:33:14.750  - error: host.raspberrypi instance system.adapter.info.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-01-29 22:33:14.751  - info: host.raspberrypi Restart adapter system.adapter.info.0 because enabled
2020-01-29 22:33:16.630  - info: host.raspberrypi instance system.adapter.mihome-vacuum.0 started with pid 19893
2020-01-29 22:33:18.147  - error: host.raspberrypi instance system.adapter.mihome-vacuum.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2020-01-29 22:33:18.148  - info: host.raspberrypi Restart adapter system.adapter.mihome-vacuum.0 because enabled
2020-01-29 22:33:20.631  - info: host.raspberrypi instance system.adapter.telegram.0 started with pid 20087

                  das will nicht mehr aufhören geht ewig weiter

                  haselchen 1 Reply Last reply Reply Quote 0
                  • haselchen
                    haselchen Most Active @JRiddim last edited by haselchen

                    @JRiddim

                    gib iobroker stop ein
                    dann
                    npm install iobroker.js-controller
                    dann
                    iobroker start

                    J 2 Replies Last reply Reply Quote 0
                    • J
                      JRiddim @haselchen last edited by JRiddim

                      @haselchen sagte in iobroker nicht mehr erreichbar nach admin update:

                      gib iobroker stop ein

                      tut sich nichts läuft munter weiter. Kann ich die Konsole einfach schließen?

                      haselchen 1 Reply Last reply Reply Quote 0
                      • haselchen
                        haselchen Most Active @JRiddim last edited by

                        @JRiddim

                        Ich mach das immer nach try and error.
                        Auf eigene Gefahr.
                        Ich hatte das Problem auch.
                        Und bin die Befehle durchgegangen.
                        Versuch mal iobroker neu zu starten. Also das Gerät.

                        1 Reply Last reply Reply Quote 0
                        • J
                          JRiddim @haselchen last edited by

                          @haselchen sagte in iobroker nicht mehr erreichbar nach admin update:

                          @JRiddim

                          gib iobroker stop ein
                          dann
                          npm install iobroker.js-controller
                          dann
                          iobroker start

                          auf der Ebene opt/iobroker oder?

                          haselchen 1 Reply Last reply Reply Quote 0
                          • haselchen
                            haselchen Most Active @JRiddim last edited by

                            @JRiddim

                            richtig.

                            J 1 Reply Last reply Reply Quote 0
                            • J
                              JRiddim @haselchen last edited by

                              @haselchen

                              erhalte diese Meldung dabei.

                              npm install iobroker.js-controller
npm WARN deprecated circular-json@0.3.3: CircularJSON is in maintenance only, flatted is its successor.

> iobroker.js-controller@2.2.8 preinstall /opt/iobroker/node_modules/iobroker.js-controller
> node lib/preinstallCheck.js

NPM version: 6.13.4

> iobroker.js-controller@2.2.8 install /opt/iobroker/node_modules/iobroker.js-controller
> node iobroker.js setup first

npm WARN bl@0.7.0 requires a peer of stream-browserify@* but none is installed. You must install peer dependencies yourself.
npm WARN ajv-keywords@2.1.1 requires a peer of ajv@^5.0.0 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.2 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@1.0.5 (node_modules/osx-temperature-sensor):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"})

+ iobroker.js-controller@2.2.8
updated 1 package and audited 4821 packages in 35.829s

12 packages are looking for funding
  run `npm fund` for details

found 57 vulnerabilities (40 low, 3 moderate, 14 high)
  run `npm audit fix` to fix them, or `npm audit` for details
                              haselchen 1 Reply Last reply Reply Quote 0
                              • haselchen
                                haselchen Most Active @JRiddim last edited by

                                @JRiddim

                                Viele Wege führen hier nach Rom.
                                Kommste mit iobroker start oder iobroker start admin.0 jetzt auf die Oberfläche?

                                Ansonsten kannst du noch den Fixer laufen lassen oder clever wäre auch beim raspi ein
                                sudo apt update und dann ein
                                sudo apt full-upgrade
                                zu machen.
                                dann ist der raspberry erstmal auf dem neuesten stand.

                                J 1 Reply Last reply Reply Quote 0
                                • J
                                  JRiddim @haselchen last edited by JRiddim

                                  @haselchen

                                  habe den rpi jetzt aktualisiert. port: 8081 funktioniert immer noch nicht.
                                  Wie kann ich den Fixer laufen lassen? 🙂

                                  haselchen 1 Reply Last reply Reply Quote 0
                                  • haselchen
                                    haselchen Most Active @JRiddim last edited by

                                    @JRiddim

                                    curl -sL https://iobroker.net/fix.sh | bash -

                                    J 1 Reply Last reply Reply Quote 0
                                    • T
                                      timtig @JRiddim last edited by

                                      @JRiddim
                                      bis jetzt war ich stiller beobachter und leser hier. Aber weil es mir immer wieder geholfen hat, wollte ich es hier auch zurück geben und versuchen zu helfen. Hatte den gleiche Fehler. War auch sehr verzweifelt. Alle adapter waren weg, nichts ging mehr. Verwende aber mein Haupt iobroker unter Sysnology mit portainer, den zweiten als slave auf RPI.
                                      Hatte auch ohne drauf zu schauen den admin adapter upgedatet und dann war alles weg. Bis in die nacht oder morgen früh war ich am Rechner, aber erst am zweiten Abend hatte ich alles reparieren können. Mein vorgehen war:
                                      container starten, natürlich startet iobroker nicht. Mit portainer auf die console und schauen ob da noch was von iobroker läuft:

                                      ps auxww|grep io
#killen wenn noch was läuft

                                      dann

                                      npm install iobroker.js-controller@2.2.8
#und
iobroker upgrade self

                                      wichtig ist natürlich, dass du den aktuellen node und so hast:
                                      link text

                                      dann container neustarten. Dann waren alle adapter erst mal da, aber dann schreck, die sind alle rot und starten nicht. Keine panik, die werden jetzt nach und nach neu installiert. Evtl. muss du ein oder anderen adapter neu starten. Kannst im log beobachten wie die installiert werden. Viel erfolg!
                                      sonst hier noch ein paar links dazu:
                                      link text
                                      link text
                                      Gruß

                                      J 1 Reply Last reply Reply Quote 0
                                      • J
                                        JRiddim @haselchen last edited by

                                        @haselchen sagte in iobroker nicht mehr erreichbar nach admin update:

                                        curl -sL https://iobroker.net/fix.sh | bash -

                                        brachte leider noch keinen Erfolg.
                                        ist es normal das unter Biobroker list instances der admin mit 0.0.0.0 angegeben wird?

                                        system.adapter.admin.0 : admin - enabled, port: 8081, bind: 0.0.0.0, run as: admin

                                        haselchen 1 Reply Last reply Reply Quote 0
                                        • J
                                          JRiddim @timtig last edited by JRiddim

                                          @timtig

                                          bei ps auxww|grep io kommt.

                                          root        12  0.0  0.0      0     0 ?        S    20:08   0:00 [migration/0]
root        15  0.0  0.0      0     0 ?        S    20:08   0:00 [migration/1]
root        20  0.0  0.0      0     0 ?        S    20:08   0:00 [migration/2]
root        25  0.0  0.0      0     0 ?        S    20:08   0:00 [migration/3]
root        42  0.0  0.0      0     0 ?        I<   20:08   0:00 [rpciod]
root        44  0.0  0.0      0     0 ?        I<   20:08   0:00 [xprtiod]
root        48  0.0  0.0      0     0 ?        I<   20:08   0:00 [nfsiod]
root        64  0.0  0.0      0     0 ?        I<   20:08   0:00 [DWC Notificatio]
message+   333  0.0  0.0   6644  3548 ?        Ss   20:08   0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
root      1789  0.3  2.0 269844 82356 ?        Sl   20:08   0:39 java -Xmx128m -Dos.arch=arm -Dlog4j.configuration=file:///etc/config/log4j.xml -Dfile.encoding=ISO-8859-1 -Dgnu.io.rxtx.SerialPorts=/dev/mmd_hmip -jar /opt/HMServer/HMIPServer.jar /etc/crRFD.conf /etc/HMServer.conf
iobroker 12828 18.0  2.8 199400 114016 ?       Ssl  22:55   0:58 iobroker.js-controller
iobroker 12881  0.4  1.1 136028 47856 ?        Sl   22:56   0:01 io.discovery.0
iobroker 12896  3.2  1.3 155804 55184 ?        Sl   22:56   0:10 io.info.0
iobroker 12917  1.1  1.0 144536 41024 ?        Sl   22:56   0:03 io.mihome-vacuum.0
iobroker 13344  1.4  1.2 153408 49440 ?        Sl   22:56   0:04 io.telegram.0
iobroker 13365  1.8  1.1 148252 44392 ?        Sl   22:56   0:05 io.hue.0
iobroker 13511  1.2  1.0 144764 42460 ?        Sl   22:56   0:03 io.hm-rpc.0
iobroker 13572  1.3  1.1 148148 46580 ?        Sl   22:56   0:04 io.hm-rega.0
iobroker 13735  1.3  1.2 149256 48172 ?        Sl   22:56   0:03 io.hm-rpc.1
iobroker 13797  0.7  1.0 136372 41596 ?        Sl   22:56   0:02 io.ping.0
iobroker 13999  0.7  1.3 148360 54868 ?        Sl   22:56   0:02 io.web.0
iobroker 14203  3.3  1.4 163012 59532 ?        Sl   22:56   0:09 io.spotify-premium.0
iobroker 14635  0.7  1.3 148708 53304 ?        Sl   22:57   0:01 io.terminal.0
iobroker 14673  1.6  1.1 150376 45628 ?        Sl   22:57   0:04 io.zigbee.0
iobroker 14820  4.9  2.3 199452 92496 ?        Sl   22:57   0:12 io.javascript.0
iobroker 14906  0.8  1.1 148136 44420 ?        Sl   22:57   0:02 io.yahka.0
juju     20733  0.0  0.0   7360   484 pts/1    S+   23:01   0:00 grep --color=auto io

                                          node -v
                                          v10.18.1

                                          nodejs -v
                                          v10.18.1

                                          npm -v
                                          6.13.4

                                          1 Reply Last reply Reply Quote 0
                                          • haselchen
                                            haselchen Most Active @JRiddim last edited by

                                            @JRiddim

                                            das ist richtig so.
                                            und normal sollte alles gehen.
                                            du kannst mal
                                            iobroker stop admin.0 eingeben

                                            und dann wieder starten

                                            J 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

                                            674
                                            Online

                                            31.7k
                                            Users

                                            79.9k
                                            Topics

                                            1.3m
                                            Posts

                                            adapter admin frage js.controller update
                                            8
                                            86
                                            8277
                                            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