NEWS
Nach Update läuft nichts mehr!
ioBroker Allgemein
416
Beiträge
18
Kommentatoren
68.0k
Aufrufe
9
Watching
-
@SaschaS
Schau mal ob der IOBroker erreichbar ist. Wenn ja, würde ich die Adapter über den Admin updaten, wobei noch ein npm rebuild wegen des Node Updates anstehen dürfte.
Das soll aber Thomas mal dirigieren. -
@Thomas-Braun said in Nach Update läuft nichts mehr!:
@SaschaS Nein.
groupszeigen.
pi@raspberrypi:/opt/iobroker $ groups pi adm dialout cdrom sudo audio video plugdev games users input netdev bluetooth gpio i2c spi -
@Jan1 IoBroker war kurzzeitig über die Weboberfläche erreichbar. Zeit mir auch an, dass 9 Adapter aktualisiert werden können.
-
@Thomas-Braun said in Nach Update läuft nichts mehr!:
@SaschaS Nein.
groupszeigen.
pi@raspberrypi:/opt/iobroker $ groups pi adm dialout cdrom sudo audio video plugdev games users input netdev bluetooth gpio i2c spisudo usermod -aG iobroker piDann den user 'pi' einmal ausloggen und wieder als 'pi' einloggen.
-
sudo usermod -aG iobroker piDann den user 'pi' einmal ausloggen und wieder als 'pi' einloggen.
@Thomas-Braun said in Nach Update läuft nichts mehr!:
sudo usermod -aG iobroker pi
Ich frage lieber nach. Ausloggen mit exit, logout ? peinlich?
-
@Thomas-Braun said in Nach Update läuft nichts mehr!:
sudo usermod -aG iobroker pi
Ich frage lieber nach. Ausloggen mit exit, logout ? peinlich?
@SaschaS Ja, mit
exit -
@SaschaS Ja, mit
exitpi@raspberrypi:/opt/iobroker $ groups pi adm dialout cdrom sudo audio video plugdev games users input netdev bluetooth gpio i2c spi iobrokerda hier jetzt iobroker in der Liste aufgeführt ist, gehe ich mal davon aus, dass jetzt mehr Rechte da sind und ich noch einmal das upgrade anstoßen kann.
-
pi@raspberrypi:/opt/iobroker $ groups pi adm dialout cdrom sudo audio video plugdev games users input netdev bluetooth gpio i2c spi iobrokerda hier jetzt iobroker in der Liste aufgeführt ist, gehe ich mal davon aus, dass jetzt mehr Rechte da sind und ich noch einmal das upgrade anstoßen kann.
@SaschaS Richtig, das war der Plan...
-
@SaschaS Richtig, das war der Plan...
@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 -
@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 -
@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 Jag den Fixer nochmal drüber:
curl -sL https://iobroker.net/fix.sh | bash - -
@SaschaS
das riecht nach "den Fixer noch mal laufen lassen"
Wobei ich die Updates lieber direkt aus IOBroker Admin raus starten würde.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 runningWie kille ich die jetzt am saubersten?
-
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 runningWie kille ich die jetzt am saubersten?
sudo pkill io -
sudo pkill ionach
sudo pkill iolaufen 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 -
nach
sudo pkill iolaufen 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 $sudo kill 16869 16920 16990 -
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 -
@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 ioUnd 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 iobrokerWenn das nicht fruchtet:
sudo kill -9 PIDPID weißt du ja wie du die bekommst.
389
Online32.5k
Benutzer81.8k
Themen1.3m
Beiträge