NEWS
ioBroker Backup wieder einspielen
Installation
85
Beiträge
4
Kommentatoren
7.9k
Aufrufe
3
Watching
-
@federal sagte in ioBroker Backup wieder einspielen:
mit sudo iobroker restore
Kein sudo vor ioBroker Befehle !
Error: Cannot find module './lib/setup'
cd /opt/iobroker iobroker fix sudo -H -u iobroker npm install iobroker.js-controller========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm WARN deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in. npm WARN deprecated @types/bl@5.1.0: This is a stub types definition. bl provides its own type definitions, so you do not need this installed. npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated axios@0.19.2: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410 ^C(##################) ⠏ reify:aws-sdk: timing reifyNode:node_modules/iobroker.zigbee/node_module pi@raspberrypi:/opt/iobroker $ -
========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@raspberrypi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm WARN deprecated crypto@1.0.1: This package is no longer supported. It's now a built-in Node module. If you've depended on crypto, you should switch to the one that's built-in. npm WARN deprecated @types/bl@5.1.0: This is a stub types definition. bl provides its own type definitions, so you do not need this installed. npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated uuid@3.3.2: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated axios@0.19.2: Critical security vulnerability fixed in v0.21.1. For more information, see https://github.com/axios/axios/pull/3410 ^C(##################) ⠏ reify:aws-sdk: timing reifyNode:node_modules/iobroker.zigbee/node_module pi@raspberrypi:/opt/iobroker $ -
pi@raspberrypi:/opt/iobroker $ iobroker status iobroker is running on this host. Objects type: jsonl States type: jsonl pi@raspberrypi:/opt/iobroker $ iobroker start all The adapter "admin.0" was started. The adapter "tuya.0" was started. The adapter "backitup.0" was started. The adapter "vis-timeandweather.0" was started. The adapter "worx.0" was started. pi@raspberrypi:/opt/iobroker $ -
pi@raspberrypi:/opt/iobroker $ iobroker status iobroker is running on this host. Objects type: jsonl States type: jsonl pi@raspberrypi:/opt/iobroker $ iobroker start all The adapter "admin.0" was started. The adapter "tuya.0" was started. The adapter "backitup.0" was started. The adapter "vis-timeandweather.0" was started. The adapter "worx.0" was started. pi@raspberrypi:/opt/iobroker $ -
@federal sagte in ioBroker Backup wieder einspielen:
iobroker is running on this host.
The adapter .... was started.
Ja ... und was ist jetzt !?
-
@glasfaser
so wie ich es verstehe, wurden nur 5 Adapter gestartet.
iob läuft weiterhin nicht!
Wie soll ich weiter vorgehen?@federal sagte in ioBroker Backup wieder einspielen:
so wie ich es verstehe, wurden nur 5 Adapter gestartet.
Du hast doch ein Backup/Restore eingespielt ... und das dauert
Aber :
durch den krasch werden die anderen Adapter nicht mehr nachinstalliert .Wie soll ich weiter vorgehen?
Neues Backup/Restore einspielen .
-
@federal sagte in ioBroker Backup wieder einspielen:
so wie ich es verstehe, wurden nur 5 Adapter gestartet.
Du hast doch ein Backup/Restore eingespielt ... und das dauert
Aber :
durch den krasch werden die anderen Adapter nicht mehr nachinstalliert .Wie soll ich weiter vorgehen?
Neues Backup/Restore einspielen .
@glasfaser said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
so wie ich es verstehe, wurden nur 5 Adapter gestartet.
Du hast doch ein Backup/Restore eingespielt ... und das dauert
Aber :
durch den krasch werden die anderen Adapter nicht mehr nachinstalliert .Wie soll ich weiter vorgehen?
Neues Backup/Restore einspielen .
wie kann ich sicherstellen, dass PuTTY nicht aussteigt? Wenn man nichts eingibt, bricht die Verbindung weg.
Soll ich mit der letzten Sicherung probieren? Habe aber Chromecast Adapter v3.0.3 nicht zum laufen gebracht. -
@federal sagte in ioBroker Backup wieder einspielen:
@homoran
gehe davon aus, dass auf dem Stick gleiche abgespeichert sindhoffentlich!
dann könntest du eine Neuinstallation durchführen und ein funktionierendes Backup wieder einspielen. -
@glasfaser said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
so wie ich es verstehe, wurden nur 5 Adapter gestartet.
Du hast doch ein Backup/Restore eingespielt ... und das dauert
Aber :
durch den krasch werden die anderen Adapter nicht mehr nachinstalliert .Wie soll ich weiter vorgehen?
Neues Backup/Restore einspielen .
wie kann ich sicherstellen, dass PuTTY nicht aussteigt? Wenn man nichts eingibt, bricht die Verbindung weg.
Soll ich mit der letzten Sicherung probieren? Habe aber Chromecast Adapter v3.0.3 nicht zum laufen gebracht.@federal sagte in ioBroker Backup wieder einspielen:
wie kann ich sicherstellen, dass PuTTY nicht aussteigt?
Zwei Session mit Putty machen .
Wenn man nichts eingibt, bricht die Verbindung weg.
Dann liegt ein Netzwerkproblem bei dir vor !
Synology 918+ 16GB - ioBroker in Docker v9 , VISO auf Trekstor Primebook C13 13,3" , Hikvision Domkameras mit Surveillance Station .. CCU RaspberryMatic in Synology VM .. Zigbee CC2538+CC2592 .. Sonoff .. KNX .. Modbus ..
-
@glasfaser said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
so wie ich es verstehe, wurden nur 5 Adapter gestartet.
Du hast doch ein Backup/Restore eingespielt ... und das dauert
Aber :
durch den krasch werden die anderen Adapter nicht mehr nachinstalliert .Wie soll ich weiter vorgehen?
Neues Backup/Restore einspielen .
wie kann ich sicherstellen, dass PuTTY nicht aussteigt? Wenn man nichts eingibt, bricht die Verbindung weg.
Soll ich mit der letzten Sicherung probieren? Habe aber Chromecast Adapter v3.0.3 nicht zum laufen gebracht.@federal sagte in ioBroker Backup wieder einspielen:
wie kann ich sicherstellen, dass PuTTY nicht aussteigt?
was haben wir denn überhaupt als Basis?
was kommt bei
iob diag? -
@federal sagte in ioBroker Backup wieder einspielen:
wie kann ich sicherstellen, dass PuTTY nicht aussteigt?
Zwei Session mit Putty machen .
Wenn man nichts eingibt, bricht die Verbindung weg.
Dann liegt ein Netzwerkproblem bei dir vor !
@glasfaser sagte in ioBroker Backup wieder einspielen:
Dann liegt ein Netzwerkproblem bei dir vor !Dann passt meine Vermutung ... in einem anderen Thread von dir :
-
@federal sagte in ioBroker Backup wieder einspielen:
wie kann ich sicherstellen, dass PuTTY nicht aussteigt?
was haben wir denn überhaupt als Basis?
was kommt bei
iob diag?@homoran said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
wie kann ich sicherstellen, dass PuTTY nicht aussteigt?
was haben wir denn überhaupt als Basis?
was kommt bei
iob diag?======== Start marking the full check here =========
Skript v.2023-04-02 *** BASE SYSTEM *** Model : Raspberry Pi 4 Model B Rev 1.2 Architecture : armv7l Docker : false Virtualization : none Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" Systemuptime and Load: 18:54:45 up 41 days, 9:15, 2 users, load average: 2.40, 2.64, 2.80 CPU threads: 4 *** Time and Time Zones *** Local time: Mon 2023-04-03 18:54:45 CEST Universal time: Mon 2023-04-03 16:54:45 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input netdev lpadmin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 3.8G 1.6G 167M 190M 2.1G 2.3G Swap: 99M 37M 62M Total: 3.9G 1.6G 230M 3838 M total memory 1571 M used memory 853 M active memory 2584 M inactive memory 167 M free memory 264 M buffer memory 1836 M swap cache 99 M total swap 37 M used swap 62 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 29G 7.8G 21G 28% / devtmpfs devtmpfs 1.8G 0 1.8G 0% /dev tmpfs tmpfs 1.9G 16K 1.9G 1% /dev/shm tmpfs tmpfs 1.9G 209M 1.7G 11% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mmcblk0p1 vfat 253M 49M 204M 20% /boot tmpfs tmpfs 384M 0 384M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Tue Feb 21 08:39:20 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:B7:67:4E vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=PARTUUID=a372f35c-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Tue Feb 21 08:39:21 2023] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Tue Feb 21 08:39:21 2023] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Tue Feb 21 08:39:22 2023] EXT4-fs (mmcblk0p2): recovery complete [Tue Feb 21 08:39:22 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Tue Feb 21 08:39:22 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Tue Feb 21 08:39:24 2023] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 576M /var/ 213M /var/cache 200M /var/cache/apt 142M /var/log 141M /var/cache/apt/archives /opt/iobroker/backups: 103M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 449M /opt/iobroker/iobroker-data/ 311M /opt/iobroker/iobroker-data/files 85M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/files/telegram.admin 51M /opt/iobroker/iobroker-data/files/javascript.admin The five largest files in iobroker-data are: 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.904d455f.js.map 18M /opt/iobroker/iobroker-data/states.jsonl 15M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map 12M /opt/iobroker/iobroker-data/objects.jsonl 9.7M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.bbfeb1bf.js.map *** NodeJS-Installation *** /usr/bin/nodejs v16.19.1 /usr/bin/node v16.19.1 /usr/bin/npm 8.19.3 /usr/bin/npx 8.19.3 nodejs: Installed: 16.19.1-deb-1nodesource1 Candidate: 16.19.1-deb-1nodesource1 Version table: *** 16.19.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u3 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages find: '/opt/iobroker/node_modules/.osx-temperature-sensor-hwc16MPv': No such file or directory find: '/opt/iobroker/node_modules/.fsevents-yNYMVUiI': No such file or directory find: '/opt/iobroker/node_modules/.iobroker.history-EyYkjPpJ': No such file or directory Temp directories causing npm8 problem: 891 Some problems detected, please run iob fix *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 4.0.24 admin: "admin" not found javascript: 6.1.4 Adapters from github: 0 Adapter State system.adapter.admin.0 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.backitup.0 : backitup : raspberrypi - disabled system.adapter.broadlink2.0 : broadlink2 : raspberrypi - enabled system.adapter.chromecast.0 : chromecast : raspberrypi - enabled system.adapter.cloud.0 : cloud : raspberrypi - disabled system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.echarts.0 : echarts : raspberrypi - enabled system.adapter.fb-checkpresence.0 : fb-checkpresence : raspberrypi - disabled system.adapter.feiertage.0 : feiertage : raspberrypi - enabled system.adapter.fullybrowser.0 : fullybrowser : raspberrypi - enabled system.adapter.harmony.0 : harmony : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.hmip.0 : hmip : raspberrypi - enabled system.adapter.ical.0 : ical : raspberrypi - enabled + system.adapter.info.0 : info : raspberrypi - enabled + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.netatmo.0 : netatmo : raspberrypi - enabled + system.adapter.panasonic-comfort-cloud.0: panasonic-comfort-cloud: raspberrypi - enabled + system.adapter.ping.0 : ping : raspberrypi - enabled + system.adapter.sayit.0 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.1 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.2 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.3 : sayit : raspberrypi - enabled, port: 0 + system.adapter.scenes.0 : scenes : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.tado.0 : tado : raspberrypi - enabled + system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.1 : text2command : raspberrypi - enabled + system.adapter.trashschedule.0 : trashschedule : raspberrypi - enabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled + system.adapter.vis-inventwo.0 : vis-inventwo : raspberrypi - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled system.adapter.weatherunderground.0 : weatherunderground : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.worx.0 : worx : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014D8F906-if00 + instance is alive Enabled adapters with bindings + system.adapter.sayit.0 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.1 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.2 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.3 : sayit : raspberrypi - enabled, port: 0 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014D8F906-if00 ioBroker-Repositories Stable (default): http://download.iobroker.net/sources-dist.json Beta (latest) : http://download.iobroker.net/sources-dist-latest.json Active repo(s): Stable (default) Installed ioBroker-Instances Used repository: Stable (default) Adapter "history" : 2.2.4 , installed 2.2.4 Adapter "hmip" : 1.20.0 , installed 1.20.0 Adapter "ical" : 1.13.2 , installed 1.13.2 Adapter "info" : 1.9.19 , installed 1.9.19 Adapter "iot" : 1.14.2 , installed 1.14.2 Adapter "javascript" : 6.1.4 , installed 6.1.4 Controller "js-controller": 4.0.24 , installed 4.0.24 Adapter "netatmo" : 2.0.5 , installed 2.0.5 Adapter "panasonic-comfort-cloud": 2.1.0, installed 2.1.0 Adapter "ping" : 1.5.3 , installed 1.5.3 Adapter "sayit" : 1.12.3 , installed 1.12.3 Adapter "scenes" : 2.3.9 , installed 2.3.9 Adapter "shelly" : 6.3.1 , installed 6.3.1 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonoff" : 2.5.1 , installed 2.5.1 Adapter "tado" : 0.4.5 , installed 0.4.5 Adapter "tankerkoenig" : 3.3.7 , installed 3.3.7 Adapter "telegram" : 1.15.2 , installed 1.15.2 Adapter "text2command" : 2.3.0 , installed 2.3.0 Adapter "trashschedule": 2.2.0 , installed 2.2.0 Adapter "tuya" : 3.13.1 , installed 3.13.1 Adapter "vis" : 1.4.15 , installed 1.4.15 Adapter "vis-inventwo" : 3.3.1 , installed 3.3.1 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "weatherunderground": 3.4.2, installed 3.4.2 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "worx" : 2.0.3 , installed 2.0.3 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "zigbee" : 1.8.10 , installed 1.8.10 Objects and States Please stand by - This may take a while Objects: 8545 States: 8737 *** OS-Repositories and Updates *** Hit:1 http://archive.raspberrypi.org/debian buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 https://deb.nodesource.com/node_16.x buster InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 17659 556/sshd tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 364555978 8627/cupsd tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 366535826 32518/io.sonoff.0 tcp 0 0 0.0.0.0:8765 0.0.0.0:* LISTEN 0 13294 366/python tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 366534662 32324/iobroker.js-c tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 366531583 32324/iobroker.js-c tcp6 0 0 :::8082 :::* LISTEN 1001 366544012 1601/io.web.0 tcp6 0 0 :::22 :::* LISTEN 0 17661 556/sshd udp 0 0 0.0.0.0:36865 0.0.0.0:* 108 13851 344/avahi-daemon: r udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 366550232 3641/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 366550233 3641/io.tuya.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 366534930 32501/io.shelly.0 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 16570 545/dhcpcd udp 0 0 0.0.0.0:631 0.0.0.0:* 0 364552998 8628/cups-browsed udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 13849 344/avahi-daemon: r udp6 0 0 :::5353 :::* 108 13850 344/avahi-daemon: r udp6 0 0 :::54050 :::* 108 13852 344/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-04-03 18:56:10.723 - warn: shelly.0 (32501) [authEnabled] 192.168.178.61 (shellyswitch25 / shellyswitch25-40F520008D21 / SHSW-25#40F520008D21#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:10.731 - warn: shelly.0 (32501) [authEnabled] 192.168.178.66 (shellyswitch25 / shellyswitch25-40F520001056 / SHSW-25#40F520001056#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.031 - warn: shelly.0 (32501) [authEnabled] 192.168.178.88 (shelly1 / shelly1-483FDA8DAE88 / SHSW-1#483FDA8DAE88#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.158 - warn: shelly.0 (32501) [authEnabled] 192.168.178.64 (shelly1 / shelly1-E09806963CF8 / SHSW-1#E09806963CF8#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.165 - warn: shelly.0 (32501) [authEnabled] 192.168.178.91 (shellyplug-s / shellyplug-s-A4138B / SHPLG-S#A4138B#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.207 - warn: shelly.0 (32501) [authEnabled] 192.168.178.76 (shelly1 / shelly1-483FDA822EBC / SHSW-1#483FDA822EBC#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.340 - warn: shelly.0 (32501) [authEnabled] 192.168.178.72 (shellyswitch25 / shellyswitch25-40F52000DA81 / SHSW-25#40F52000DA81#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.430 - warn: shelly.0 (32501) [authEnabled] 192.168.178.63 (shelly1 / shelly1-40F52000CBB8 / SHSW-1#40F52000CBB8#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.592 - warn: shelly.0 (32501) [authEnabled] 192.168.178.94 (shelly1 / shelly1-F4CFA2ED662C / SHSW-1#F4CFA2ED662C#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.598 - warn: shelly.0 (32501) [authEnabled] 192.168.178.95 (shelly1 / shelly1-483FDAA23470 / SHSW-1#483FDAA23470#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.849 - warn: shelly.0 (32501) [authEnabled] 192.168.178.73 (shelly1 / shelly1-483FDA82B865 / SHSW-1#483FDA82B865#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:12.362 - warn: shelly.0 (32501) [authEnabled] 192.168.178.101 (shelly1 / shelly1-E8DB84D41EDF / SHSW-1#E8DB84D41EDF#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:12.490 - warn: shelly.0 (32501) [authEnabled] 192.168.178.33 (shelly1 / shelly1-C45BBE6B9506 / SHSW-1#C45BBE6B9506#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:12.701 - warn: shelly.0 (32501) [authEnabled] 192.168.178.65 (shelly1 / shelly1-E09806963C5D / SHSW-1#E09806963C5D#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:12.440 - info: netatmo.0 (32465) Websocket error: websocket error, Error: websocket error at WS.Transport.onError (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:64:13) at WebSocket.ws.onerror (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:149:10) at WebSocket.onError (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:452:14) at WebSocket.emit (node:events:513:28) at WebSocket.emit (node:domain:489:12) at ClientRequest.response (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:721:12) at Object.onceWrapper (node:events:628:26) at ClientRequest.emit (node:events:525:35) at ClientRequest.emit (node:domain:489:12) at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27)============ Mark until here for C&P =============
iob diag has finished.
Press any key for a summary
-
@glasfaser sagte in ioBroker Backup wieder einspielen:
Dann liegt ein Netzwerkproblem bei dir vor !Dann passt meine Vermutung ... in einem anderen Thread von dir :
@glasfaser said in ioBroker Backup wieder einspielen:
@glasfaser sagte in ioBroker Backup wieder einspielen:
Dann liegt ein Netzwerkproblem bei dir vor !Dann passt meine Vermutung ... in einem anderen Thread von dir :
es lag daran, dass iob und Motioneye gemeinsam auf einem pi genutzt wurden. Seit dem ich Motioneye deaktiviert habe, lief alles gut!
-
@glasfaser said in ioBroker Backup wieder einspielen:
@glasfaser sagte in ioBroker Backup wieder einspielen:
Dann liegt ein Netzwerkproblem bei dir vor !Dann passt meine Vermutung ... in einem anderen Thread von dir :
es lag daran, dass iob und Motioneye gemeinsam auf einem pi genutzt wurden. Seit dem ich Motioneye deaktiviert habe, lief alles gut!
Some problems detected, please run iob fixSolltest du tun. Und du solltest auch den Buster erlösen und durch das aktuelle Release Debian 11 'Bullseye' ersetzen, der Buster ist letztes Jahr im September abgekündigt worden.
Im Zuge dessen dann auch auf nodejs@18 springen. -
@homoran said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
wie kann ich sicherstellen, dass PuTTY nicht aussteigt?
was haben wir denn überhaupt als Basis?
was kommt bei
iob diag?======== Start marking the full check here =========
Skript v.2023-04-02 *** BASE SYSTEM *** Model : Raspberry Pi 4 Model B Rev 1.2 Architecture : armv7l Docker : false Virtualization : none Distributor ID: Raspbian Description: Raspbian GNU/Linux 10 (buster) Release: 10 Codename: buster PRETTY_NAME="Raspbian GNU/Linux 10 (buster)" NAME="Raspbian GNU/Linux" VERSION_ID="10" VERSION="10 (buster)" VERSION_CODENAME=buster ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" Systemuptime and Load: 18:54:45 up 41 days, 9:15, 2 users, load average: 2.40, 2.64, 2.80 CPU threads: 4 *** Time and Time Zones *** Local time: Mon 2023-04-03 18:54:45 CEST Universal time: Mon 2023-04-03 16:54:45 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm dialout cdrom sudo audio video plugdev games users input netdev lpadmin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 3.8G 1.6G 167M 190M 2.1G 2.3G Swap: 99M 37M 62M Total: 3.9G 1.6G 230M 3838 M total memory 1571 M used memory 853 M active memory 2584 M inactive memory 167 M free memory 264 M buffer memory 1836 M swap cache 99 M total swap 37 M used swap 62 M free swap *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 29G 7.8G 21G 28% / devtmpfs devtmpfs 1.8G 0 1.8G 0% /dev tmpfs tmpfs 1.9G 16K 1.9G 1% /dev/shm tmpfs tmpfs 1.9G 209M 1.7G 11% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup /dev/mmcblk0p1 vfat 253M 49M 204M 20% /boot tmpfs tmpfs 384M 0 384M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Tue Feb 21 08:39:20 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=DC:A6:32:B7:67:4E vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 dwc_otg.lpm_enable=0 console=ttyAMA0,115200 console=tty1 root=PARTUUID=a372f35c-02 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles [Tue Feb 21 08:39:21 2023] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Tue Feb 21 08:39:21 2023] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Tue Feb 21 08:39:22 2023] EXT4-fs (mmcblk0p2): recovery complete [Tue Feb 21 08:39:22 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Tue Feb 21 08:39:22 2023] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Tue Feb 21 08:39:24 2023] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 576M /var/ 213M /var/cache 200M /var/cache/apt 142M /var/log 141M /var/cache/apt/archives /opt/iobroker/backups: 103M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 449M /opt/iobroker/iobroker-data/ 311M /opt/iobroker/iobroker-data/files 85M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/files/telegram.admin 51M /opt/iobroker/iobroker-data/files/javascript.admin The five largest files in iobroker-data are: 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.904d455f.js.map 18M /opt/iobroker/iobroker-data/states.jsonl 15M /opt/iobroker/iobroker-data/files/telegram.admin/rules/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_d_ts-node_modules_io-1d9f06.44fe4a3f.chunk.js.map 12M /opt/iobroker/iobroker-data/objects.jsonl 9.7M /opt/iobroker/iobroker-data/files/text2command.admin/static/js/main.bbfeb1bf.js.map *** NodeJS-Installation *** /usr/bin/nodejs v16.19.1 /usr/bin/node v16.19.1 /usr/bin/npm 8.19.3 /usr/bin/npx 8.19.3 nodejs: Installed: 16.19.1-deb-1nodesource1 Candidate: 16.19.1-deb-1nodesource1 Version table: *** 16.19.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_16.x buster/main armhf Packages 100 /var/lib/dpkg/status 10.24.0~dfsg-1~deb10u3 500 500 http://raspbian.raspberrypi.org/raspbian buster/main armhf Packages find: '/opt/iobroker/node_modules/.osx-temperature-sensor-hwc16MPv': No such file or directory find: '/opt/iobroker/node_modules/.fsevents-yNYMVUiI': No such file or directory find: '/opt/iobroker/node_modules/.iobroker.history-EyYkjPpJ': No such file or directory Temp directories causing npm8 problem: 891 Some problems detected, please run iob fix *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 4.0.24 admin: "admin" not found javascript: 6.1.4 Adapters from github: 0 Adapter State system.adapter.admin.0 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.backitup.0 : backitup : raspberrypi - disabled system.adapter.broadlink2.0 : broadlink2 : raspberrypi - enabled system.adapter.chromecast.0 : chromecast : raspberrypi - enabled system.adapter.cloud.0 : cloud : raspberrypi - disabled system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.echarts.0 : echarts : raspberrypi - enabled system.adapter.fb-checkpresence.0 : fb-checkpresence : raspberrypi - disabled system.adapter.feiertage.0 : feiertage : raspberrypi - enabled system.adapter.fullybrowser.0 : fullybrowser : raspberrypi - enabled system.adapter.harmony.0 : harmony : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.hmip.0 : hmip : raspberrypi - enabled system.adapter.ical.0 : ical : raspberrypi - enabled + system.adapter.info.0 : info : raspberrypi - enabled + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.netatmo.0 : netatmo : raspberrypi - enabled + system.adapter.panasonic-comfort-cloud.0: panasonic-comfort-cloud: raspberrypi - enabled + system.adapter.ping.0 : ping : raspberrypi - enabled + system.adapter.sayit.0 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.1 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.2 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.3 : sayit : raspberrypi - enabled, port: 0 + system.adapter.scenes.0 : scenes : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.tado.0 : tado : raspberrypi - enabled + system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.1 : text2command : raspberrypi - enabled + system.adapter.trashschedule.0 : trashschedule : raspberrypi - enabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled + system.adapter.vis-inventwo.0 : vis-inventwo : raspberrypi - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled system.adapter.weatherunderground.0 : weatherunderground : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.worx.0 : worx : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014D8F906-if00 + instance is alive Enabled adapters with bindings + system.adapter.sayit.0 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.1 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.2 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.3 : sayit : raspberrypi - enabled, port: 0 + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014D8F906-if00 ioBroker-Repositories Stable (default): http://download.iobroker.net/sources-dist.json Beta (latest) : http://download.iobroker.net/sources-dist-latest.json Active repo(s): Stable (default) Installed ioBroker-Instances Used repository: Stable (default) Adapter "history" : 2.2.4 , installed 2.2.4 Adapter "hmip" : 1.20.0 , installed 1.20.0 Adapter "ical" : 1.13.2 , installed 1.13.2 Adapter "info" : 1.9.19 , installed 1.9.19 Adapter "iot" : 1.14.2 , installed 1.14.2 Adapter "javascript" : 6.1.4 , installed 6.1.4 Controller "js-controller": 4.0.24 , installed 4.0.24 Adapter "netatmo" : 2.0.5 , installed 2.0.5 Adapter "panasonic-comfort-cloud": 2.1.0, installed 2.1.0 Adapter "ping" : 1.5.3 , installed 1.5.3 Adapter "sayit" : 1.12.3 , installed 1.12.3 Adapter "scenes" : 2.3.9 , installed 2.3.9 Adapter "shelly" : 6.3.1 , installed 6.3.1 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonoff" : 2.5.1 , installed 2.5.1 Adapter "tado" : 0.4.5 , installed 0.4.5 Adapter "tankerkoenig" : 3.3.7 , installed 3.3.7 Adapter "telegram" : 1.15.2 , installed 1.15.2 Adapter "text2command" : 2.3.0 , installed 2.3.0 Adapter "trashschedule": 2.2.0 , installed 2.2.0 Adapter "tuya" : 3.13.1 , installed 3.13.1 Adapter "vis" : 1.4.15 , installed 1.4.15 Adapter "vis-inventwo" : 3.3.1 , installed 3.3.1 Adapter "vis-timeandweather": 1.2.2, installed 1.2.2 Adapter "weatherunderground": 3.4.2, installed 3.4.2 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "worx" : 2.0.3 , installed 2.0.3 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "zigbee" : 1.8.10 , installed 1.8.10 Objects and States Please stand by - This may take a while Objects: 8545 States: 8737 *** OS-Repositories and Updates *** Hit:1 http://archive.raspberrypi.org/debian buster InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian buster InRelease Hit:3 https://deb.nodesource.com/node_16.x buster InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 17659 556/sshd tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 364555978 8627/cupsd tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1001 366535826 32518/io.sonoff.0 tcp 0 0 0.0.0.0:8765 0.0.0.0:* LISTEN 0 13294 366/python tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 366534662 32324/iobroker.js-c tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 366531583 32324/iobroker.js-c tcp6 0 0 :::8082 :::* LISTEN 1001 366544012 1601/io.web.0 tcp6 0 0 :::22 :::* LISTEN 0 17661 556/sshd udp 0 0 0.0.0.0:36865 0.0.0.0:* 108 13851 344/avahi-daemon: r udp 0 0 0.0.0.0:6666 0.0.0.0:* 1001 366550232 3641/io.tuya.0 udp 0 0 0.0.0.0:6667 0.0.0.0:* 1001 366550233 3641/io.tuya.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 366534930 32501/io.shelly.0 udp 0 0 0.0.0.0:68 0.0.0.0:* 0 16570 545/dhcpcd udp 0 0 0.0.0.0:631 0.0.0.0:* 0 364552998 8628/cups-browsed udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 13849 344/avahi-daemon: r udp6 0 0 :::5353 :::* 108 13850 344/avahi-daemon: r udp6 0 0 :::54050 :::* 108 13852 344/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-04-03 18:56:10.723 - warn: shelly.0 (32501) [authEnabled] 192.168.178.61 (shellyswitch25 / shellyswitch25-40F520008D21 / SHSW-25#40F520008D21#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:10.731 - warn: shelly.0 (32501) [authEnabled] 192.168.178.66 (shellyswitch25 / shellyswitch25-40F520001056 / SHSW-25#40F520001056#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.031 - warn: shelly.0 (32501) [authEnabled] 192.168.178.88 (shelly1 / shelly1-483FDA8DAE88 / SHSW-1#483FDA8DAE88#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.158 - warn: shelly.0 (32501) [authEnabled] 192.168.178.64 (shelly1 / shelly1-E09806963CF8 / SHSW-1#E09806963CF8#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.165 - warn: shelly.0 (32501) [authEnabled] 192.168.178.91 (shellyplug-s / shellyplug-s-A4138B / SHPLG-S#A4138B#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.207 - warn: shelly.0 (32501) [authEnabled] 192.168.178.76 (shelly1 / shelly1-483FDA822EBC / SHSW-1#483FDA822EBC#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.340 - warn: shelly.0 (32501) [authEnabled] 192.168.178.72 (shellyswitch25 / shellyswitch25-40F52000DA81 / SHSW-25#40F52000DA81#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.430 - warn: shelly.0 (32501) [authEnabled] 192.168.178.63 (shelly1 / shelly1-40F52000CBB8 / SHSW-1#40F52000CBB8#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.592 - warn: shelly.0 (32501) [authEnabled] 192.168.178.94 (shelly1 / shelly1-F4CFA2ED662C / SHSW-1#F4CFA2ED662C#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.598 - warn: shelly.0 (32501) [authEnabled] 192.168.178.95 (shelly1 / shelly1-483FDAA23470 / SHSW-1#483FDAA23470#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:11.849 - warn: shelly.0 (32501) [authEnabled] 192.168.178.73 (shelly1 / shelly1-483FDA82B865 / SHSW-1#483FDA82B865#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:12.362 - warn: shelly.0 (32501) [authEnabled] 192.168.178.101 (shelly1 / shelly1-E8DB84D41EDF / SHSW-1#E8DB84D41EDF#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:12.490 - warn: shelly.0 (32501) [authEnabled] 192.168.178.33 (shelly1 / shelly1-C45BBE6B9506 / SHSW-1#C45BBE6B9506#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:12.701 - warn: shelly.0 (32501) [authEnabled] 192.168.178.65 (shelly1 / shelly1-E09806963C5D / SHSW-1#E09806963C5D#1): This device is not protected via restricted login (see adapter documentation for details) 2023-04-03 18:56:12.440 - info: netatmo.0 (32465) Websocket error: websocket error, Error: websocket error at WS.Transport.onError (/opt/iobroker/node_modules/engine.io-client/lib/transport.js:64:13) at WebSocket.ws.onerror (/opt/iobroker/node_modules/engine.io-client/lib/transports/websocket.js:149:10) at WebSocket.onError (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:452:14) at WebSocket.emit (node:events:513:28) at WebSocket.emit (node:domain:489:12) at ClientRequest.response (/opt/iobroker/node_modules/engine.io-client/node_modules/ws/lib/WebSocket.js:721:12) at Object.onceWrapper (node:events:628:26) at ClientRequest.emit (node:events:525:35) at ClientRequest.emit (node:domain:489:12) at HTTPParser.parserOnIncomingClient [as onIncoming] (node:_http_client:693:27)============ Mark until here for C&P =============
iob diag has finished.
Press any key for a summary
@federal was ist denn das?
@federal sagte in ioBroker Backup wieder einspielen:
18:54:45 up 41 days, 9:15,
ich denke der ist gerade neu gestartet?
@federal sagte in ioBroker Backup wieder einspielen:
load average: 2.40, 2.64, 2.80
hat auch gut zu rödeln!
Was läuft da sonst noch?und nur 5 Adapter sähen anders aus.
admin als https konfiguriert?
@federal sagte in ioBroker Backup wieder einspielen:
system.adapter.admin.0 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
und deaktiviert
kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@federal was ist denn das?
@federal sagte in ioBroker Backup wieder einspielen:
18:54:45 up 41 days, 9:15,
ich denke der ist gerade neu gestartet?
@federal sagte in ioBroker Backup wieder einspielen:
load average: 2.40, 2.64, 2.80
hat auch gut zu rödeln!
Was läuft da sonst noch?und nur 5 Adapter sähen anders aus.
admin als https konfiguriert?
@federal sagte in ioBroker Backup wieder einspielen:
system.adapter.admin.0 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin
und deaktiviert
Nee, die Kiste ist am
[Tue Feb 21 08:39:21 2023] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystemunsanft 'neugestartet' worden.
-
@federal sagte in ioBroker Backup wieder einspielen:
so wie ich es verstehe, wurden nur 5 Adapter gestartet.
Du hast doch ein Backup/Restore eingespielt ... und das dauert
Aber :
durch den krasch werden die anderen Adapter nicht mehr nachinstalliert .Wie soll ich weiter vorgehen?
Neues Backup/Restore einspielen .
@glasfaser said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
so wie ich es verstehe, wurden nur 5 Adapter gestartet.
Du hast doch ein Backup/Restore eingespielt ... und das dauert
Aber :
durch den krasch werden die anderen Adapter nicht mehr nachinstalliert .Wie soll ich weiter vorgehen?
Neues Backup/Restore einspielen .
habe ein Backup eigespielt
System successfully restored! pi@raspberrypi:/opt/iobroker/backups $ iobroker start all The adapter "history.0" was started. The adapter "javascript.0" was started. The adapter "scenes.0" was started. The adapter "telegram.0" was started. The adapter "chromecast.0" was started. The adapter "hmip.0" was started. The adapter "ical.0" was started. The adapter "netatmo.0" was started. The adapter "ping.0" was started. The adapter "shelly.0" was started. The adapter "sonoff.0" was started. The adapter "tuya.0" was started. The adapter "weatherunderground.0" was started. The adapter "zigbee.0" was started. The adapter "broadlink2.0" was started. The adapter "cloud.0" was started. The adapter "discovery.0" was started. The adapter "echarts.0" was started. The adapter "fb-checkpresence.0" was started. The adapter "feiertage.0" was started. The adapter "fullybrowser.0" was started. The adapter "harmony.0" was started. The adapter "info.0" was started. The adapter "iot.0" was started. The adapter "panasonic-comfort-cloud.0" was started. The adapter "sayit.0" was started. The adapter "sayit.1" was started. The adapter "sayit.2" was started. The adapter "sayit.3" was started. The adapter "tado.0" was started. The adapter "tankerkoenig.0" was started. The adapter "text2command.1" was started. The adapter "trashschedule.0" was started. The adapter "vis-inventwo.0" was started. The adapter "vis-timeandweather.0" was started. The adapter "vis.0" was started. The adapter "web.0" was started. The adapter "worx.0" was started. pi@raspberrypi:/opt/iobroker/backups $ iobroker startkann aber nach wie vor nicht auf iob zugreifen
-
@glasfaser said in ioBroker Backup wieder einspielen:
@federal sagte in ioBroker Backup wieder einspielen:
so wie ich es verstehe, wurden nur 5 Adapter gestartet.
Du hast doch ein Backup/Restore eingespielt ... und das dauert
Aber :
durch den krasch werden die anderen Adapter nicht mehr nachinstalliert .Wie soll ich weiter vorgehen?
Neues Backup/Restore einspielen .
habe ein Backup eigespielt
System successfully restored! pi@raspberrypi:/opt/iobroker/backups $ iobroker start all The adapter "history.0" was started. The adapter "javascript.0" was started. The adapter "scenes.0" was started. The adapter "telegram.0" was started. The adapter "chromecast.0" was started. The adapter "hmip.0" was started. The adapter "ical.0" was started. The adapter "netatmo.0" was started. The adapter "ping.0" was started. The adapter "shelly.0" was started. The adapter "sonoff.0" was started. The adapter "tuya.0" was started. The adapter "weatherunderground.0" was started. The adapter "zigbee.0" was started. The adapter "broadlink2.0" was started. The adapter "cloud.0" was started. The adapter "discovery.0" was started. The adapter "echarts.0" was started. The adapter "fb-checkpresence.0" was started. The adapter "feiertage.0" was started. The adapter "fullybrowser.0" was started. The adapter "harmony.0" was started. The adapter "info.0" was started. The adapter "iot.0" was started. The adapter "panasonic-comfort-cloud.0" was started. The adapter "sayit.0" was started. The adapter "sayit.1" was started. The adapter "sayit.2" was started. The adapter "sayit.3" was started. The adapter "tado.0" was started. The adapter "tankerkoenig.0" was started. The adapter "text2command.1" was started. The adapter "trashschedule.0" was started. The adapter "vis-inventwo.0" was started. The adapter "vis-timeandweather.0" was started. The adapter "vis.0" was started. The adapter "web.0" was started. The adapter "worx.0" was started. pi@raspberrypi:/opt/iobroker/backups $ iobroker startkann aber nach wie vor nicht auf iob zugreifen
-
@federal sagte in ioBroker Backup wieder einspielen:
kann aber nach wie vor nicht auf iob zugreifen
iob list instancessagt
@glasfaser said in ioBroker Backup wieder einspielen:
iob list instances
pi@raspberrypi:/opt/iobroker/backups $ iob list instances system.adapter.admin.0 : admin : raspberrypi - disabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.backitup.0 : backitup : raspberrypi - disabled system.adapter.broadlink2.0 : broadlink2 : raspberrypi - enabled system.adapter.chromecast.0 : chromecast : raspberrypi - enabled system.adapter.cloud.0 : cloud : raspberrypi - disabled system.adapter.discovery.0 : discovery : raspberrypi - enabled system.adapter.echarts.0 : echarts : raspberrypi - enabled system.adapter.fb-checkpresence.0 : fb-checkpresence : raspberrypi - disabled system.adapter.feiertage.0 : feiertage : raspberrypi - enabled system.adapter.fullybrowser.0 : fullybrowser : raspberrypi - enabled system.adapter.harmony.0 : harmony : raspberrypi - enabled + system.adapter.history.0 : history : raspberrypi - enabled + system.adapter.hmip.0 : hmip : raspberrypi - enabled system.adapter.ical.0 : ical : raspberrypi - enabled + system.adapter.info.0 : info : raspberrypi - enabled + system.adapter.iot.0 : iot : raspberrypi - enabled + system.adapter.javascript.0 : javascript : raspberrypi - enabled + system.adapter.netatmo.0 : netatmo : raspberrypi - enabled + system.adapter.panasonic-comfort-cloud.0: panasonic-comfort-cloud: raspberrypi - enabled + system.adapter.ping.0 : ping : raspberrypi - enabled + system.adapter.sayit.0 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.1 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.2 : sayit : raspberrypi - enabled, port: 0 + system.adapter.sayit.3 : sayit : raspberrypi - enabled, port: 0 + system.adapter.scenes.0 : scenes : raspberrypi - enabled + system.adapter.shelly.0 : shelly : raspberrypi - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : raspberrypi - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.tado.0 : tado : raspberrypi - enabled + system.adapter.tankerkoenig.0 : tankerkoenig : raspberrypi - enabled + system.adapter.telegram.0 : telegram : raspberrypi - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.text2command.1 : text2command : raspberrypi - enabled + system.adapter.trashschedule.0 : trashschedule : raspberrypi - enabled + system.adapter.tuya.0 : tuya : raspberrypi - enabled + system.adapter.vis-inventwo.0 : vis-inventwo : raspberrypi - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : raspberrypi - enabled system.adapter.vis.0 : vis : raspberrypi - enabled system.adapter.weatherunderground.0 : weatherunderground : raspberrypi - enabled + system.adapter.web.0 : web : raspberrypi - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.worx.0 : worx : raspberrypi - enabled + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/serial/by-id/usb-Texas_Instruments_TI_CC2531_USB_CDC___0X00124B0014D8F906-if00 + instance is alive pi@raspberrypi:/opt/iobroker/backups $
Support us
652
Online32.5k
Benutzer81.7k
Themen1.3m
Beiträge