NEWS
Nach Update läuft nichts mehr!
-
@Thomas-Braun Weniger erfolgreich..
pi@raspberrypi:/opt/iobroker $ iobroker upgrade Update admin from @3.7.8 to @4.0.10 NPM version: 6.14.2 npm install iobroker.admin@4.0.10 --loglevel error --prefix "/opt/iobroker" (System call) npm ERR! code EACCES npm ERR! syscall access npm ERR! path /opt/iobroker/node_modules/iobroker.admin npm ERR! errno -13 npm ERR! Error: EACCES: permission denied, access '/opt/iobroker/node_modules/iobroker.admin' npm ERR! { Error: EACCES: permission denied, access '/opt/iobroker/node_modules/iobroker.admin' npm ERR! stack: 'Error: EACCES: permission denied, access \'/opt/iobroker/node_modules/iobroker.admin\'', npm ERR! errno: -13, npm ERR! code: 'EACCES', npm ERR! syscall: 'access', npm ERR! path: '/opt/iobroker/node_modules/iobroker.admin' } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It is likely you do not have the permissions to access this file as the current user npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2020-05-21T08_58_31_749Z-debug.log host.raspberrypi Cannot install iobroker.admin@4.0.10: 243
-
@SaschaS
das riecht nach "den Fixer noch mal laufen lassen"
Wobei ich die Updates lieber direkt aus IOBroker Admin raus starten würde. -
@SaschaS Jag den Fixer nochmal drüber:
curl -sL https://iobroker.net/fix.sh | bash -
-
pi@raspberrypi:/opt/iobroker $ curl -sL https://iobroker.net/fix.sh | bash - library: loaded Library version=2020-04-12 ioBroker or some processes are still running: io.discovery.0 io.history.0 io.javascript.0 io.web.0 io.cloud.0 io.info.0 io.deconz.0 io.tankerkoenig.0 io.ble.0 Please stop them first and try again!
Wieso laufen denn da noch Dienste?
pi@raspberrypi:/opt/iobroker $ iobroker stop iobroker controller daemon is not running
Wie kille ich die jetzt am saubersten?
-
sudo pkill io
-
nach
sudo pkill io
laufen immer noch Dienste
pi@raspberrypi:/opt/iobroker $ ps auxww | grep io root 12 0.0 0.0 0 0 ? S 10:39 0:00 [migration/0] root 15 0.0 0.0 0 0 ? S 10:39 0:00 [migration/1] root 20 0.0 0.0 0 0 ? S 10:39 0:00 [migration/2] root 25 0.0 0.0 0 0 ? S 10:39 0:00 [migration/3] root 41 0.0 0.0 0 0 ? I< 10:39 0:00 [rpciod] root 43 0.0 0.0 0 0 ? I< 10:39 0:00 [xprtiod] root 47 0.0 0.0 0 0 ? I< 10:39 0:00 [nfsiod] root 62 0.0 0.0 0 0 ? I< 10:39 0:00 [DWC Notificatio] message+ 350 0.0 0.3 6512 3472 ? Ss 10:39 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation iobroker 16869 30.8 11.5 186284 109716 ? Dsl 11:04 0:08 iobroker.js-controller iobroker 16920 9.9 4.5 120552 42908 ? Sl 11:04 0:02 io.discovery.0 iobroker 16990 21.0 6.5 140452 62140 ? Sl 11:04 0:03 io.history.0 iobroker 17030 45.6 10.8 181700 103192 ? Sl 11:04 0:05 /usr/bin/node /opt/iobroker/node_modules/iobroker.javascript/main.js 0 info pi 17155 0.0 0.0 4772 576 pts/0 S+ 11:04 0:00 grep --color=auto io pi@raspberrypi:/opt/iobroker $
-
Und das werden immer mehr...wieso starten die denn jetzt alle durch?
pi@raspberrypi:/opt/iobroker $ ps auxww | grep io root 12 0.0 0.0 0 0 ? S 10:39 0:00 [migration/0] root 15 0.0 0.0 0 0 ? S 10:39 0:00 [migration/1] root 20 0.0 0.0 0 0 ? S 10:39 0:00 [migration/2] root 25 0.0 0.0 0 0 ? S 10:39 0:00 [migration/3] root 41 0.0 0.0 0 0 ? I< 10:39 0:00 [rpciod] root 43 0.0 0.0 0 0 ? I< 10:39 0:00 [xprtiod] root 47 0.0 0.0 0 0 ? I< 10:39 0:00 [nfsiod] root 62 0.0 0.0 0 0 ? I< 10:39 0:00 [DWC Notificatio] message+ 350 0.0 0.3 6512 3472 ? Ss 10:39 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation iobroker 16869 25.7 10.4 175232 99196 ? Dsl 11:04 0:22 iobroker.js-controller iobroker 16920 2.8 4.5 120552 42936 ? Sl 11:04 0:02 io.discovery.0 iobroker 16990 7.1 3.7 128760 35148 ? Sl 11:04 0:05 io.history.0 iobroker 17030 20.8 14.2 211672 134692 ? Sl 11:04 0:15 io.javascript.0 iobroker 17237 12.1 4.5 135500 42748 ? Rl 11:04 0:06 io.stiebel-isg.0 iobroker 17248 7.9 4.2 133872 40160 ? Sl 11:04 0:04 io.web.0 iobroker 17254 7.3 3.9 131960 37660 ? Sl 11:04 0:03 /usr/bin/node /opt/iobroker/node_modules/iobroker.cloud/main.js 0 info iobroker 17261 5.3 4.5 121004 43076 ? Sl 11:04 0:02 /usr/bin/node /opt/iobroker/node_modules/iobroker.info/main.js 0 info iobroker 17339 7.5 5.1 131932 49248 ? Sl 11:04 0:03 io.deconz.0 iobroker 17699 21.6 4.7 131708 45304 ? Sl 11:05 0:03 /usr/bin/node /opt/iobroker/node_modules/iobroker.tankerkoenig/main.js 0 info iobroker 17706 22.6 5.1 132704 49024 ? Sl 11:05 0:03 io.ical.0 iobroker 17716 21.6 4.0 131016 38792 ? Sl 11:05 0:03 io.ble.0 pi 17888 0.0 0.0 4772 524 pts/0 S+ 11:05 0:00 grep --color=auto io
-
sudo kill 16869 16920 16990
-
@Thomas-Braun said in Nach Update läuft nichts mehr!:
sudo kill 16869 16920 16990
Der scheint verdammt hartnäckig zu sein
pi@raspberrypi:/opt/iobroker $ sudo kill 16869 pi@raspberrypi:/opt/iobroker $ ps auxww | grep io root 12 0.0 0.0 0 0 ? S 10:39 0:00 [migration/0] root 15 0.0 0.0 0 0 ? S 10:39 0:00 [migration/1] root 20 0.0 0.0 0 0 ? S 10:39 0:00 [migration/2] root 25 0.0 0.0 0 0 ? S 10:39 0:00 [migration/3] root 41 0.0 0.0 0 0 ? I< 10:39 0:00 [rpciod] root 43 0.0 0.0 0 0 ? I< 10:39 0:00 [xprtiod] root 47 0.0 0.0 0 0 ? I< 10:39 0:00 [nfsiod] root 62 0.0 0.0 0 0 ? I< 10:39 0:00 [DWC Notificatio] message+ 350 0.0 0.3 6512 3472 ? Ss 10:39 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation iobroker 16869 16.7 10.2 199612 97400 ? Dsl 11:04 0:40 iobroker.js-controller pi 19863 0.0 0.0 4772 552 pts/0 S+ 11:08 0:00 grep --color=auto io
-
Und jetzt hat er eine neue PID...ich raff's nicht..wieso startet der denn immer wieder?
pi@raspberrypi:/opt/iobroker $ ps auxww | grep io root 12 0.0 0.0 0 0 ? S 10:39 0:00 [migration/0] root 15 0.0 0.0 0 0 ? S 10:39 0:00 [migration/1] root 20 0.0 0.0 0 0 ? S 10:39 0:00 [migration/2] root 25 0.0 0.0 0 0 ? S 10:39 0:00 [migration/3] root 41 0.0 0.0 0 0 ? I< 10:39 0:00 [rpciod] root 43 0.0 0.0 0 0 ? I< 10:39 0:00 [xprtiod] root 47 0.0 0.0 0 0 ? I< 10:39 0:00 [nfsiod] root 62 0.0 0.0 0 0 ? I< 10:39 0:00 [DWC Notificatio] message+ 350 0.0 0.3 6512 3472 ? Ss 10:39 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation iobroker 20224 20.6 14.5 229260 137796 ? Rsl 11:08 0:15 iobroker.js-controller iobroker 20266 3.2 4.5 120552 42844 ? Sl 11:08 0:02 io.discovery.0 iobroker 20341 7.1 3.9 130108 37164 ? Sl 11:09 0:04 io.history.0 iobroker 20380 14.9 9.5 184116 91028 ? Sl 11:09 0:09 io.javascript.0 iobroker 20708 11.9 5.1 132532 49252 ? Sl 11:09 0:04 /usr/bin/node /opt/iobroker/node_modules/iobroker.stiebel-isg/main.js 0 info iobroker 20714 7.0 4.4 120504 42040 ? Sl 11:09 0:02 /usr/bin/node /opt/iobroker/node_modules/iobroker.vis/main.js 0 info iobroker 20720 9.4 3.8 131212 36564 ? Sl 11:09 0:03 /usr/bin/node /opt/iobroker/node_modules/iobroker.web/main.js 0 info iobroker 20726 9.0 4.7 131444 45024 ? Sl 11:09 0:03 /usr/bin/node /opt/iobroker/node_modules/iobroker.cloud/main.js 0 info iobroker 20728 7.5 4.5 120544 43120 ? Sl 11:09 0:02 /usr/bin/node /opt/iobroker/node_modules/iobroker.info/main.js 0 info iobroker 20745 9.2 4.8 131288 45548 ? Sl 11:09 0:03 /usr/bin/node /opt/iobroker/node_modules/iobroker.deconz/main.js 0 info iobroker 20792 11.3 3.9 131792 37300 ? Sl 11:09 0:03 /usr/bin/node /opt/iobroker/node_modules/iobroker.tankerkoenig/main.js 0 info pi 21089 0.0 0.0 4772 548 pts/0 S+ 11:10 0:00 grep --color=auto io
-
@Jan1 Jetzt übrigens nicht mehr über die Weboberfläche erreichbar..Aber ist auch kein Wunder, da io.admin sich nicht wie aus Geisterhand von alleine startet..
-
iobroker stop sudo killall iobroker
Wenn das nicht fruchtet:
sudo kill -9 PID
PID weißt du ja wie du die bekommst.
-
Das Problem ist doch gerade, dass nach jedem kill der iobroker.js-controller wieder auftaucht..
pi@raspberrypi:/opt/iobroker $ sudo killall iobroker iobroker: Kein Prozess gefunden pi@raspberrypi:/opt/iobroker $ ps auxww | grep io root 12 0.0 0.0 0 0 ? S 10:39 0:00 [migration/0] root 15 0.0 0.0 0 0 ? S 10:39 0:00 [migration/1] root 20 0.0 0.0 0 0 ? S 10:39 0:00 [migration/2] root 25 0.0 0.0 0 0 ? S 10:39 0:00 [migration/3] root 41 0.0 0.0 0 0 ? I< 10:39 0:00 [rpciod] root 43 0.0 0.0 0 0 ? I< 10:39 0:00 [xprtiod] root 47 0.0 0.0 0 0 ? I< 10:39 0:00 [nfsiod] root 62 0.0 0.0 0 0 ? I< 10:39 0:00 [DWC Notificatio] message+ 350 0.0 0.3 6512 3472 ? Ss 10:39 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation iobroker 24294 11.6 7.7 170944 73416 ? Rsl 11:14 0:36 iobroker.js-controller iobroker 24334 0.9 4.4 120548 42532 ? Sl 11:14 0:02 io.discovery.0 iobroker 24405 3.0 3.7 129788 35732 ? Sl 11:14 0:09 io.history.0 iobroker 24447 8.1 11.5 200760 109760 ? Sl 11:14 0:24 io.javascript.0 iobroker 25571 6.2 6.4 145400 61484 ? Sl 11:15 0:15 io.stiebel-isg.0 iobroker 25582 1.8 4.2 134016 40080 ? Sl 11:15 0:04 io.web.0 iobroker 25588 3.1 7.8 155956 74028 ? Sl 11:15 0:07 io.cloud.0 iobroker 25591 1.1 4.5 120868 42888 ? Sl 11:15 0:02 /usr/bin/node /opt/iobroker/node_modules/iobroker.info/main.js 0 info iobroker 25602 2.4 4.3 134352 41060 ? Sl 11:15 0:06 io.deconz.0 iobroker 25613 1.5 4.0 132196 37988 ? Sl 11:15 0:03 /usr/bin/node /opt/iobroker/node_modules/iobroker.tankerkoenig/main.js 0 info iobroker 25620 5.8 4.6 135784 44408 ? Sl 11:15 0:14 io.ble.0 iobroker 28191 0.0 0.0 0 0 ? Z 11:19 0:00 [sh] <defunct> pi 28194 0.0 0.0 4772 560 pts/0 S+ 11:19 0:00 grep --color=auto io pi@raspberrypi:/opt/iobroker $ sudo kill -9 24294 pi@raspberrypi:/opt/iobroker $ ps auxww | grep io root 12 0.0 0.0 0 0 ? S 10:39 0:00 [migration/0] root 15 0.0 0.0 0 0 ? S 10:39 0:00 [migration/1] root 20 0.0 0.0 0 0 ? S 10:39 0:00 [migration/2] root 25 0.0 0.0 0 0 ? S 10:39 0:00 [migration/3] root 41 0.0 0.0 0 0 ? I< 10:39 0:00 [rpciod] root 43 0.0 0.0 0 0 ? I< 10:39 0:00 [xprtiod] root 47 0.0 0.0 0 0 ? I< 10:39 0:00 [nfsiod] root 62 0.0 0.0 0 0 ? I< 10:39 0:00 [DWC Notificatio] message+ 350 0.0 0.3 6512 3472 ? Ss 10:39 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation iobroker 24405 3.8 5.3 131160 50456 ? Sl 11:14 0:13 io.history.0 pi 28986 0.0 0.0 4772 536 pts/0 S+ 11:20 0:00 grep --color=auto io pi@raspberrypi:/opt/iobroker $ sudo kill -9 24405 kill: (24405): Kein passender Prozess gefunden pi@raspberrypi:/opt/iobroker $ ps auxww | grep io root 12 0.0 0.0 0 0 ? S 10:39 0:00 [migration/0] root 15 0.0 0.0 0 0 ? S 10:39 0:00 [migration/1] root 20 0.0 0.0 0 0 ? S 10:39 0:00 [migration/2] root 25 0.0 0.0 0 0 ? S 10:39 0:00 [migration/3] root 41 0.0 0.0 0 0 ? I< 10:39 0:00 [rpciod] root 43 0.0 0.0 0 0 ? I< 10:39 0:00 [xprtiod] root 47 0.0 0.0 0 0 ? I< 10:39 0:00 [nfsiod] root 62 0.0 0.0 0 0 ? I< 10:39 0:00 [DWC Notificatio] message+ 350 0.0 0.3 6512 3472 ? Ss 10:39 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation iobroker 29172 119 6.4 147356 61188 ? Rsl 11:20 0:03 iobroker.js-controller iobroker 29208 0.0 0.0 0 0 ? Z 11:20 0:00 [sh] <defunct> iobroker 29210 0.0 0.0 0 0 ? Z 11:20 0:00 [sh] <defunct> iobroker 29212 0.0 0.0 0 0 ? Z 11:20 0:00 [sh] <defunct> pi 29215 0.0 0.0 4772 524 pts/0 S+ 11:20 0:00 grep --color=auto io
-
sudo -u iobroker kill -15 -1
-
@Thomas-Braun said in Nach Update läuft nichts mehr!:
sudo -u iobroker kill -15 -1
pi@raspberrypi:/opt/iobroker $ sudo -u iobroker kill -15 -1 Speicherzugriffsfehler
-
@Thomas-Braun said in Nach Update läuft nichts mehr!:
sudo killall iobroker
Ich würde ja gerne wieder sudo systemctl stop iobroker verwenden. Aber das findet @Jan1 ja nicht so prickelnd bzw. veraltet
-
@SaschaS Das kannst du aber mal probieren.
-
@SaschaS said in Nach Update läuft nichts mehr!:
sudo systemctl stop iobroker
Das Stehaufmännchen ist besiegt! Warum das jetzt funktioniert, verstehe ich nicht. Vielleicht habt ihr Ideen.
Ich würde jetzt den Fixer laufen lassen.pi@raspberrypi:/opt/iobroker $ sudo systemctl stop iobroker pi@raspberrypi:/opt/iobroker $ ps auxww | grep io root 12 0.0 0.0 0 0 ? S 11:23 0:00 [migration/0] root 15 0.0 0.0 0 0 ? S 11:23 0:00 [migration/1] root 20 0.0 0.0 0 0 ? S 11:23 0:00 [migration/2] root 25 0.0 0.0 0 0 ? S 11:23 0:00 [migration/3] root 41 0.0 0.0 0 0 ? I< 11:23 0:00 [rpciod] root 43 0.0 0.0 0 0 ? I< 11:23 0:00 [xprtiod] root 47 0.0 0.0 0 0 ? I< 11:23 0:00 [nfsiod] root 62 0.0 0.0 0 0 ? I< 11:23 0:00 [DWC Notificatio] message+ 354 0.1 0.3 6516 3504 ? Ss 11:23 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation pi 4563 0.0 0.0 4772 544 pts/0 S+ 11:27 0:00 grep --color=auto io pi@raspberrypi:/opt/iobroker $ ps auxww | grep io root 12 0.0 0.0 0 0 ? S 11:23 0:00 [migration/0] root 15 0.0 0.0 0 0 ? S 11:23 0:00 [migration/1] root 20 0.0 0.0 0 0 ? S 11:23 0:00 [migration/2] root 25 0.0 0.0 0 0 ? S 11:23 0:00 [migration/3] root 41 0.0 0.0 0 0 ? I< 11:23 0:00 [rpciod] root 43 0.0 0.0 0 0 ? I< 11:23 0:00 [xprtiod] root 47 0.0 0.0 0 0 ? I< 11:23 0:00 [nfsiod] root 62 0.0 0.0 0 0 ? I< 11:23 0:00 [DWC Notificatio] message+ 354 0.1 0.3 6516 3504 ? Ss 11:23 0:00 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation pi 4650 0.0 0.0 4772 532 pts/0 S+ 11:27 0:00 grep --color=auto io
-
@SaschaS
Das war eben mal zwischen durch nötig, wobei Deine alte Installation da vielleicht immer noch drauf besteht -
@SaschaS Ja, lass den Fixer mal laufen.