ioBroker nicht mehr erreichbar
-
@berti69 sagte in ioBroker nicht mehr erreichbar:
Hmmm. Sieht alles sehr krumm aus.
dmesg -T | grep -i ext4liefert?
-
@thomas-braun sagte in ioBroker nicht mehr erreichbar:
dmesg -T | grep -i ext4
pi@iobroker:~ $ dmesg -T | grep -i ext4 [Mi Jul 14 18:07:15 2021] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 bcm2708_fb.fbwidth=65 6 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem. mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=596b8f27-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait [Mi Jul 14 18:07:18 2021] EXT4-fs (mmcblk0p2): INFO: recovery required on readon ly filesystem [Mi Jul 14 18:07:18 2021] EXT4-fs (mmcblk0p2): write access will be enabled duri ng recovery [Mi Jul 14 18:07:19 2021] EXT4-fs (mmcblk0p2): recovery complete [Mi Jul 14 18:07:19 2021] EXT4-fs (mmcblk0p2): mounted filesystem with ordered d ata mode. Opts: (null) [Mi Jul 14 18:07:19 2021] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Mi Jul 14 18:07:22 2021] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) pi@iobroker:~ $Bin jetzt auf Firefox gewechselt und schon geht das mit dem Code.
-
iobroker stop sudo rebootUnd wenn die Kiste wieder hochgekommen ist als erstes nochmal
dmesg -T | grep -i ext4 -
pi@iobroker:~ $ dmesg -T | grep -i ext4 [Mi Jul 14 18:24:48 2021] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_ hdmi=1 bcm2708_fb.fbwidth=656 bcm2708_fb.fbheight=416 bcm2708_fb.fbswap=1 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 con sole=ttyS0,115200 console=tty1 root=PARTUUID=596b8f27-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait [Mi Jul 14 18:24:51 2021] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Mi Jul 14 18:24:51 2021] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Mi Jul 14 18:24:55 2021] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) pi@iobroker:~ $ -
@berti69 Dann nochmal versuchen zu installieren.
-
@thomas-braun
Komplett neu installieren ?
oder nur iobroker? -
@berti69 Zunächst Mal nur den js-controller.
Siehe oben -
@thomas-braun
das geht nicht. Gleiche Meldungen wie vorhinpi@iobroker:~ $ cd /opt/iobroker pi@iobroker:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm ERR! code EJSONPARSE npm ERR! file /opt/iobroker/package.json npm ERR! JSON.parse Failed to parse json npm ERR! JSON.parse Unexpected token in JSON at position 320 while parsing near '...{ npm ERR! JSON.parse "colors": "^1., npm ERR! JSON.parse "fs-extra"...' npm ERR! JSON.parse Failed to parse package.json data. npm ERR! JSON.parse package.json must be actual JSON, not just JavaScript. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-07-14T17_08_41_354Z-debug.log pi@iobroker:/opt/iobroker $ -
@berti69 sagte in ioBroker nicht mehr erreichbar:
opt/iobroker/package.json
Die Datei ist wohl defekt. Keine Ahnung ob man die wiederherstellen kann.
Ich würde wohl jetzt ein Backup einspielen. -
@thomas-braun
kann das sein das ich ins falsche verzeichnis installiert habe ? Ein Backup habe ich gemacht.pi@iobroker:/opt/iobroker $ npm install iobroker.js-controller npm ERR! code EJSONPARSE npm ERR! file /opt/iobroker/package.json npm ERR! JSON.parse Failed to parse json npm ERR! JSON.parse Unexpected token in JSON at position 320 while parsing near '...{ npm ERR! JSON.parse "colors": "^1., npm ERR! JSON.parse "fs-extra"...' npm ERR! JSON.parse Failed to parse package.json data. npm ERR! JSON.parse package.json must be actual JSON, not just JavaScript. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-07-14T17_19_21_407Z-debug.log pi@iobroker:/opt/iobroker $ cd pi@iobroker:~ $ npm install iobroker.js-controller npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported > iobroker.js-controller@3.3.14 preinstall /home/pi/node_modules/iobroker.js-controller > node lib/preinstallCheck.js NPM version: 6.14.13 > unix-dgram@2.0.3 install /home/pi/node_modules/unix-dgram > node-gyp rebuild make: Verzeichnis â/home/pi/node_modules/unix-dgram/buildâ wird betreten CXX(target) Release/obj.target/unix_dgram/src/unix_dgram.o In file included from ../../nan/nan.h:56, from ../src/unix_dgram.cc:5: /home/pi/.cache/node-gyp/12.22.2/include/node/node.h:736:43: warning: cast between incompatible function types from âvoid (*)(v8::Local<v8::Object>)â to ânode::addon_register_funcâ {aka âvoid (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)â} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^ /home/pi/.cache/node-gyp/12.22.2/include/node/node.h:770:3: note: in expansion of macro âNODE_MODULE_Xâ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^~~~~~~~~~~~~ ../src/unix_dgram.cc:404:1: note: in expansion of macro âNODE_MODULEâ NODE_MODULE(unix_dgram, Initialize) ^~~~~~~~~~~ SOLINK_MODULE(target) Release/obj.target/unix_dgram.node COPY Release/unix_dgram.node make: Verzeichnis â/home/pi/node_modules/unix-dgram/buildâ wird verlassen > ursa-optional@0.9.10 install /home/pi/node_modules/ursa-optional > node rebuild.js ursaNative bindings compilation fail. This is not an issue. Modules that depend on it will use fallbacks. > diskusage@1.1.3 install /home/pi/node_modules/diskusage > node-gyp rebuild make: Verzeichnis â/home/pi/node_modules/diskusage/buildâ wird betreten CXX(target) Release/obj.target/diskusage/src/main.o In file included from ../../nan/nan.h:56, from ../src/main.cpp:3: /home/pi/.cache/node-gyp/12.22.2/include/node/node.h:736:43: warning: cast between incompatible function types from âvoid (*)(v8::Local<v8::Object>)â to ânode::addon_register_funcâ {aka âvoid (*)(v8::Local<v8::Object>, v8::Local<v8::Value>, void*)â} [-Wcast-function-type] (node::addon_register_func) (regfunc), \ ^ /home/pi/.cache/node-gyp/12.22.2/include/node/node.h:770:3: note: in expansion of macro âNODE_MODULE_Xâ NODE_MODULE_X(modname, regfunc, NULL, 0) // NOLINT (readability/null_usage) ^~~~~~~~~~~~~ ../src/main.cpp:42:1: note: in expansion of macro âNODE_MODULEâ NODE_MODULE(diskusage, Init) ^~~~~~~~~~~ CXX(target) Release/obj.target/diskusage/src/diskusage_posix.o SOLINK_MODULE(target) Release/obj.target/diskusage.node COPY Release/diskusage.node make: Verzeichnis â/home/pi/node_modules/diskusage/buildâ wird verlassen > iobroker.js-controller@3.3.14 install /home/pi/node_modules/iobroker.js-controller > node iobroker.js setup first creating conf/iobroker.json Server Cannot load /home/pi/iobroker-data/objects.json: Database file /home/pi/iobroker-data/objects.json does not exists.. We try last Backup! Server Cannot load /home/pi/iobroker-data/states.json: Database file /home/pi/iobroker-data/states.json does not exists.. We try last Backup! Server Cannot load /home/pi/iobroker-data/objects.json.bak: Database file /home/pi/iobroker-data/objects.json.bak does not exists.. Continue with empty dataset! Server If this is no Migration or initial start please restore the last backup from /home/pi/iobroker-data/backup-objects Server Cannot load /home/pi/iobroker-data/states.json.bak: Database file /home/pi/iobroker-data/states.json.bak does not exists.. Continue with empty dataset! Server If this is no Migration or initial start please restore the last backup from /home/pi/iobroker-data/backup-objects Cannot read system.config: null (OK when migrating or restoring) object 0_userdata.0.example_state created object 0_userdata.0 created object alias.0 created object system.certificates created object system.repositories created object system.config created object enum.functions created object enum.rooms created object system.group.user created object system.group.administrator created object _design/custom created object _design/system created object system.meta.uuid created: 88674e08-15f5-d7d6-3be0-6846412b9edd object system.user.admin created ATTENTION: Error reporting via Sentry will be activated on next start of ioBroker ioBroker wants to make sure to deliver the most stable smart home system. To allow this we decided to implement an automatic error and crash reporting solution into the js-controller and also into adapters. THIS REPORTING WILL BE ENABLED WITH THE NEXT START OF YOUR IOBROKER! For any error that leads to the crash of the js-controller or one of the relevant adapters the error details are send to a server. For the js-controller and core adapters this server is located and operated in germany. For community adapters please check the Github Readme of the affected adapter for details which Sentry server is used. If you want to disable the error reporting you can use the command 'iobroker plugin disable sentry' This command will also make sure that no adapter that runs on this host will send crash reporting data to sentry. { "defaultPrivate": "-----BEGIN RSA PRIVATE KEY-----\r\nMIIEpgIBAAKCAQEAvxJJ4ClaW2NB92cPGg/wmN40DyKWP9EEEh4PiSPDv2vXC2rO\r\nSqETE3A5AMIEDwJlr0rq4Mtam1VT8yPjda+565LQy1QoqX7ZoAs7+ykxrIJfu3Sx\r\nkFcTtAQyG+EpWtmd6sja3dYE23psJ/T4R1sGgr6PnjPH7Pa1U8f6DptVphH50/G/\r\n1OJMD+NSXj7/g6pP68M2ID2vyJpWQw23zKsRwVJ9uw87lY5yopGqnr1uegqWcQuE\r\n35gRXTlRKIGegLnDQs7HypWcCMdRcrIazmpNY4dW3i6Mmv3N3aSiuMTR88z0Yano\r\nWMzCmgh98v4Z5VCPINzAOa8b07KovigHjVOZfwIDAQABAoIBAQCZ91jEY05GWgNs\r\nIwXOUI3mARgeIhbEsd7/4m1Oax1vgKy2rIgzJvzCKyoj7DNtDNd3m30NS5BlnyqY\r\nwJCn4sSEibfqQJTLkEY5axQYXaeDhUMzQONclm5wHvlp8dRrOvS/nr6PB8i+OzYw\r\nNHxks3rZnEkKiFtQHbUcIAbmAlHQEULDzJz08Xbfj0FR+F9AH1ZIDolSJx6+boP6\r\ntaioRJdbmWNQUlttFZrLZdcNC/cg1/Bty3fGlZuraJA43nEOH793k8ONNNTPZ+tq\r\nK1BMaD12GhTGPwbTz5NbEQcTDc02T2k5N4CzO8fEkoo0LHBRnpq1MRPSbvAyQ83o\r\n3Y7iQMbRAoGBAO3/SYC8FZDmTwz/tyj39VVhIkS/blz9IWBMi7GBBj3sBc+PHyOw\r\n1l8d8L5M3gdmJf1qIM6MoA+4wEeHe8WF6lQvP8BD6EOw0hTE+giiGBSx0toJpnq7\r\nM/f5Mm7ggjeSI7Ogyut3tHMiYmsgyI7YQX7Pt4f/WAmn8MzLQo02oGPFAoGBAM2G\r\nTd1hu/MgoUST+MBZ5nNz1NqIeHNfZQ4AO9+pJbng3zVLSyQ88JR/TYr0/QU7AfVJ\r\nhd2R2rnTYHFeoxVoIPPawjbX5DM4QtK9S6rc9sIaBGZ9s+9icCZeWdGOG4fGpv8J\r\naBFVGscffUhG0bDLO+5lCnTGwEUTAW3n4qNv8ChzAoGBAMIG7zChpd9Us7vAOd2P\r\nkRZDM0Hi4yGySGSO4xAaRTF0WyRk5Rke0RYIfb1XQ2e60lvwCsD5ioBmuXNXNAPL\r\nckehoZKoihGtdQfzsngZVhKBCooxdeT2+549Le2Q4PhXDv4hp20iUR3QOXZm6rrx\r\n+SteQp0AAhEVNk5vo1km4MmVAoGBAJgjIAaNr3SFJfu+0XeJ1OaHyvvN4+P7rLGV\r\niLzC2FNlW7V2u/PiTHCQX9VKDvZNPODXAQoISvIdv5mMZYqWHzaELBou7BTiQ8z+\r\nJUIg+WSrn7BCwuykYMJ2O2S9HjH+4mWOEAQsjHr0G2hiTBzkBMQu9XOGIJPBQuCZ\r\ns5IqbYtzAoGBAIwR0S8EwEjRqoJTPdG5HpnXYRTDFw+zVSdzE+EZ2hH2Tdhtr+18\r\naNdBbAeg/7HIKjBc/kYGtIP2I6pWnErNhnOY+CTtSwFKtgw3iufzNStPTm0QU/Sj\r\nh2iQgE8LNxYpQU04Xg2xIRbKSSnuqsVt5grrbhwGVcbnWqcr1wdpaVmv\r\n-----END RSA PRIVATE KEY-----\r\n", "defaultPublic": "-----BEGIN CERTIFICATE-----\r\nMIIDfjCCAmagAwIBAgIJAQ4nK6xRTwWiMA0GCSqGSIb3DQEBCwUAMD4xETAPBgNV\r\nBAMTCGlvYnJva2VyMRYwFAYDVQQKEw1pb0Jyb2tlciBHbWJIMREwDwYDVQQLEwhp\r\nb2Jyb2tlcjAeFw0yMTA3MTQxNzIxNDdaFw0yMjA3MTQxNzIxNDdaMD4xETAPBgNV\r\nBAMTCGlvYnJva2VyMRYwFAYDVQQKEw1pb0Jyb2tlciBHbWJIMREwDwYDVQQLEwhp\r\nb2Jyb2tlcjCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBAL8SSeApWltj\r\nQfdnDxoP8JjeNA8ilj/RBBIeD4kjw79r1wtqzkqhExNwOQDCBA8CZa9K6uDLWptV\r\nU/Mj43WvueuS0MtUKKl+2aALO/spMayCX7t0sZBXE7QEMhvhKVrZnerI2t3WBNt6\r\nbCf0+EdbBoK+j54zx+z2tVPH+g6bVaYR+dPxv9TiTA/jUl4+/4OqT+vDNiA9r8ia\r\nVkMNt8yrEcFSfbsPO5WOcqKRqp69bnoKlnELhN+YEV05USiBnoC5w0LOx8qVnAjH\r\nUXKyGs5qTWOHVt4ujJr9zd2korjE0fPM9GGp6FjMwpoIffL+GeVQjyDcwDmvG9Oy\r\nqL4oB41TmX8CAwEAAaN/MH0wDAYDVR0TAQH/BAIwADAPBgNVHQ8BAf8EBQMDB7+A\r\nMBMGA1UdEQQMMAqCCGlvYnJva2VyMB0GA1UdDgQWBBRETtzMsjRG8SM1ObmOOiqp\r\nN9EC1jAdBgNVHSUEFjAUBggrBgEFBQcDAQYIKwYBBQUHAwIwCQYDVR0jBAIwADAN\r\nBgkqhkiG9w0BAQsFAAOCAQEAqA7YDgEobps6NutBDlY/dKqPIEBgaKZQVDODPJuf\r\nWIvi/GDOin+oy+gZo3OCWykE8eiuMwmZreKn8Div4PZh5TR6ofAbZR9YC6hRxTKu\r\nPcF8x+GK8JhDwCq9FMMD53BSnOh/eGu2sbQoQ7BOa3PhVZZbML0fv8tXujVIbXpK\r\n3rNIuWS6WjpsC8sgY0npUFUTIqNnrpse6+jfi+7U8F8m47UcMaoS2AXGQaT9bzq/\r\nFAPrXyuRf5rB66f/vGLtnCQrJXRPF5gW602UnbdRhdiuMkY1+jvnX4OdnfOHdWzW\r\nksJ+fG2myONLYlbJptbALPof4uuVAGYdVaN9woshaLLbBQ==\r\n-----END CERTIFICATE-----\r\n" } The object "system.certificates" was updated successfully. > @root/acme@3.1.0 postinstall /home/pi/node_modules/@root/acme > node scripts/postinstall > esbuild@0.11.23 postinstall /home/pi/node_modules/esbuild > node install.js npm WARN saveError ENOENT: no such file or directory, open '/home/pi/package.json' npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN enoent ENOENT: no such file or directory, open '/home/pi/package.json' npm WARN pi No description npm WARN pi No repository field. npm WARN pi No README data npm WARN pi No license field. + iobroker.js-controller@3.3.14 added 298 packages from 282 contributors and audited 306 packages in 145.393s 11 packages are looking for funding run `npm fund` for details found 1 high severity vulnerability run `npm audit fix` to fix them, or `npm audit` for detailsopen Request’s Past, Present and Future #3142
-
ins falsche verzeichnis installiert habe
Im zweiten Versuch, ja. Die Installation macht man nicht im Home des Users.
-
@thomas-braun
wie bekomme ich das gelöscht bzw wie spiele ich das Backup ein das im Ordner backups liegt ? -
@berti69 Kannst du einfach löschen.
rm -r datei-verzeichnisname -
@thomas-braun
wie geht das Backup einspielen ?
Danke
Wenn das nicht geht mach ich alles neu. -
@berti69 Wie angelegt?
Mit dem Backitup-Adapter? -
@thomas-braun
Über die Konsole bzw Putty -
@berti69 Da weiß ich den Befehl nicht. Musst du mal in der Dokumentation nachschauen.
-
@thomas-braun
Ok
Danke -
Mein iobroker läuft wieder. Habe mich durch die Doku gearbeitet.
Das was jetzt noch fehlt sind Adapter zum instalieren. Ich meine Neue
