NEWS
iobroker zeschossen
-
:disappointed_relieved:
Hallo allerseits, ich habe gestern versucht Nodje auf die neueste Version zu aktualisieren und hab bestimmt was falsch gemacht. Jetzt startet iob überhaupt nicht mehr.
Bei " iobroker start" über Konsole kommt:root@Marek2:~# iobroker start /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted stringWenn ich " iob diag " mache kommt das:
Skript v.2023-06-20 *** BASE SYSTEM *** Failed to connect to bus: Host is down model name : Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz Docker : false Virtualization : wsl Kernel : x86_64 Userland : amd64 Systemuptime and Load: 18:46:07 up 27 min, 0 users, load average: 0.52, 0.58, 0.59 CPU threads: 8 *** Time and Time Zones *** System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 16G 5.9G 10G 17M 223M 10G Swap: 30G 0B 30G Total: 46G 5.9G 40G Error: /proc must be mounted To mount /proc at boot you need an /etc/fstab line like: proc /proc proc defaults In the meantime, run "mount proc /proc -t proc" *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on rootfs lxfs 238G 195G 43G 83% / none tmpfs 238G 195G 43G 83% /dev none tmpfs 238G 195G 43G 83% /run none tmpfs 238G 195G 43G 83% /run/lock none tmpfs 238G 195G 43G 83% /run/shm none tmpfs 238G 195G 43G 83% /run/user tmpfs tmpfs 238G 195G 43G 83% /sys/fs/cgroup C:\ drvfs 238G 195G 43G 83% /mnt/c D:\ drvfs 932G 541G 391G 59% /mnt/d Messages concerning ext4 filesystem in dmesg: Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / rootfs lxfs rw,noatime |-/mnt/c C:\ drvfs rw,noatime,uid=0,gid=0,case=off `-/mnt/d D:\ drvfs rw,noatime,uid=0,gid=0,case=off Files in neuralgic directories: /var: 428M /var/ 330M /var/lib 157M /var/lib/snapd/seed/snaps 157M /var/lib/snapd/seed 157M /var/lib/snapd No journal files were found. Archived and active journals take up 0B in the file system. /opt/iobroker/backups: 103M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 431M /opt/iobroker/iobroker-data/ 285M /opt/iobroker/iobroker-data/files 107M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/files/telegram.admin 52M /opt/iobroker/iobroker-data/files/javascript.admin The five largest files in iobroker-data are: 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js.map 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js.map 15M /opt/iobroker/iobroker-data/objects.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 8.9M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/2.7de3299d.chunk.js.map *** NodeJS-Installation *** /home/iobroker/.diag.sh: line 177: /usr/bin/nodejs: cannot execute binary file: Exec format error /usr/bin/nodejs /home/iobroker/.diag.sh: line 178: /usr/bin/node: cannot execute binary file: Exec format error /usr/bin/node /mnt/c/Windows/system32/npm : not foundram Files/nodejs/npx: 2: : not foundram Files/nodejs/npx: 5: : not foundram Files/nodejs/npx: 7: : not foundram Files/nodejs/npx: 9: /mnt/c/Program Files/nodejs/npx: 10: Syntax error: word unexpected (expecting "in") /mnt/c/Program Files/nodejs/npx /home/iobroker/.diag.sh: line 186: /usr/bin/nodejs: cannot execute binary file: Exec format error /home/iobroker/.diag.sh: line 187: /usr/bin/node: cannot execute binary file: Exec format error : not foundram Files/nodejs/npx: 2: : not foundram Files/nodejs/npx: 5: : not foundram Files/nodejs/npx: 7: : not foundram Files/nodejs/npx: 9: /mnt/c/Program Files/nodejs/npx: 10: Syntax error: word unexpected (expecting "in") *** nodejs is NOT correctly installed *** nodejs: Installed: 12.22.9~dfsg-1ubuntu3 Candidate: 12.22.9~dfsg-1ubuntu3 Version table: *** 12.22.9~dfsg-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: 0 *** ioBroker-Installation *** ioBroker Status /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string Core adapters versions /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string js-controller: /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string admin: /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string javascript: Adapters from github: 0 Adapter State /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string Enabled adapters with bindings /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string ioBroker-Repositories /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string Installed ioBroker-Instances /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string Objects and States Please stand by - This may take a while Objects: 0 States: 0 *** OS-Repositories and Updates *** W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Some index files failed to download. They have been ignored, or old ones used instead. Get:1 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB] Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Err:1 https://dl.yarnpkg.com/debian stable InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> Fetched 17.1 kB in 3s (5230 B/s) Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Some index files failed to download. They have been ignored, or old ones used instead. 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 *** Log File - Last 25 Lines *** 2023-10-07 21:49:27.501 - info: host.Marek2 instance system.adapter.kodi.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.502 - info: host.Marek2 instance system.adapter.tr-064.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.502 - info: host.Marek2 instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.502 - info: host.Marek2 stopInstance system.adapter.pushover.0 killing pid 9396 2023-10-07 21:49:27.537 - info: host.Marek2 instance system.adapter.discovery.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.538 - info: host.Marek2 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.539 - info: host.Marek2 instance system.adapter.javascript.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.634 - info: host.Marek2 stopInstance system.adapter.web.0 killing pid 10344 2023-10-07 21:49:27.635 - info: host.Marek2 stopInstance system.adapter.philips-tv.0 killing pid 10481 2023-10-07 21:49:27.647 - info: host.Marek2 instance system.adapter.sonoff.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.668 - info: host.Marek2 instance system.adapter.iot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.668 - info: host.Marek2 instance system.adapter.broadlink2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.730 - info: host.Marek2 instance system.adapter.info.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.730 - info: host.Marek2 instance system.adapter.yahka.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.730 - info: host.Marek2 instance system.adapter.tankerkoenig.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.765 - info: host.Marek2 instance system.adapter.firetv.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.765 - info: host.Marek2 instance system.adapter.parcel.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.839 - info: host.Marek2 instance system.adapter.web.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.840 - info: host.Marek2 instance system.adapter.philips-tv.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.901 - info: host.Marek2 instance system.adapter.pushover.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:29.473 - info: tuya.0 (9456) terminating 2023-10-07 21:49:29.475 - info: tuya.0 (9456) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-10-07 21:49:30.080 - info: host.Marek2 instance system.adapter.tuya.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:30.081 - info: host.Marek2 All instances are stopped. 2023-10-07 21:49:30.150 - info: host.Marek2 terminatedKann mir da jemand helfen oder ist das schon ein hofnungsose Fahl?
@krisiun sagte in iobroker zeschossen:
root@Marek2:
Das Thema dazu hatte wir schonmal und auch dich mehrmals dazu gewarnt !!
-
@krisiun sagte in iobroker zeschossen:
OK Sorry das kommt davon wenn man nicht auf Euch hört
Wird ja nicht ohne Grund immer wieder darauf hingewiesen.
Wer nicht hören will, muss ein Backup haben.
Oder seinen Umgang mit dem System ändern. -
Ich habe schon verstanden. Macht mich nicht noch mehr fertig als ich schon bin.
Die istallation auf Windows rechner war für mich für Testzwecke. Ich wollte nicht riskieren aufm rassby zu experimentieren.
Eins möchte ich von Euch wissen? Kann man die installation noch retten oder nicht? -
:disappointed_relieved:
Hallo allerseits, ich habe gestern versucht Nodje auf die neueste Version zu aktualisieren und hab bestimmt was falsch gemacht. Jetzt startet iob überhaupt nicht mehr.
Bei " iobroker start" über Konsole kommt:root@Marek2:~# iobroker start /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted stringWenn ich " iob diag " mache kommt das:
Skript v.2023-06-20 *** BASE SYSTEM *** Failed to connect to bus: Host is down model name : Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz Docker : false Virtualization : wsl Kernel : x86_64 Userland : amd64 Systemuptime and Load: 18:46:07 up 27 min, 0 users, load average: 0.52, 0.58, 0.59 CPU threads: 8 *** Time and Time Zones *** System has not been booted with systemd as init system (PID 1). Can't operate. Failed to connect to bus: Host is down *** User and Groups *** root /root root *** X-Server-Setup *** X-Server: false Desktop: Terminal: Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 16G 5.9G 10G 17M 223M 10G Swap: 30G 0B 30G Total: 46G 5.9G 40G Error: /proc must be mounted To mount /proc at boot you need an /etc/fstab line like: proc /proc proc defaults In the meantime, run "mount proc /proc -t proc" *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on rootfs lxfs 238G 195G 43G 83% / none tmpfs 238G 195G 43G 83% /dev none tmpfs 238G 195G 43G 83% /run none tmpfs 238G 195G 43G 83% /run/lock none tmpfs 238G 195G 43G 83% /run/shm none tmpfs 238G 195G 43G 83% /run/user tmpfs tmpfs 238G 195G 43G 83% /sys/fs/cgroup C:\ drvfs 238G 195G 43G 83% /mnt/c D:\ drvfs 932G 541G 391G 59% /mnt/d Messages concerning ext4 filesystem in dmesg: Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / rootfs lxfs rw,noatime |-/mnt/c C:\ drvfs rw,noatime,uid=0,gid=0,case=off `-/mnt/d D:\ drvfs rw,noatime,uid=0,gid=0,case=off Files in neuralgic directories: /var: 428M /var/ 330M /var/lib 157M /var/lib/snapd/seed/snaps 157M /var/lib/snapd/seed 157M /var/lib/snapd No journal files were found. Archived and active journals take up 0B in the file system. /opt/iobroker/backups: 103M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 431M /opt/iobroker/iobroker-data/ 285M /opt/iobroker/iobroker-data/files 107M /opt/iobroker/iobroker-data/backup-objects 72M /opt/iobroker/iobroker-data/files/telegram.admin 52M /opt/iobroker/iobroker-data/files/javascript.admin The five largest files in iobroker-data are: 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.edf7552a.js.map 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js.map 15M /opt/iobroker/iobroker-data/objects.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 8.9M /opt/iobroker/iobroker-data/files/scenes.admin/static/js/2.7de3299d.chunk.js.map *** NodeJS-Installation *** /home/iobroker/.diag.sh: line 177: /usr/bin/nodejs: cannot execute binary file: Exec format error /usr/bin/nodejs /home/iobroker/.diag.sh: line 178: /usr/bin/node: cannot execute binary file: Exec format error /usr/bin/node /mnt/c/Windows/system32/npm : not foundram Files/nodejs/npx: 2: : not foundram Files/nodejs/npx: 5: : not foundram Files/nodejs/npx: 7: : not foundram Files/nodejs/npx: 9: /mnt/c/Program Files/nodejs/npx: 10: Syntax error: word unexpected (expecting "in") /mnt/c/Program Files/nodejs/npx /home/iobroker/.diag.sh: line 186: /usr/bin/nodejs: cannot execute binary file: Exec format error /home/iobroker/.diag.sh: line 187: /usr/bin/node: cannot execute binary file: Exec format error : not foundram Files/nodejs/npx: 2: : not foundram Files/nodejs/npx: 5: : not foundram Files/nodejs/npx: 7: : not foundram Files/nodejs/npx: 9: /mnt/c/Program Files/nodejs/npx: 10: Syntax error: word unexpected (expecting "in") *** nodejs is NOT correctly installed *** nodejs: Installed: 12.22.9~dfsg-1ubuntu3 Candidate: 12.22.9~dfsg-1ubuntu3 Version table: *** 12.22.9~dfsg-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages 100 /var/lib/dpkg/status Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: 0 *** ioBroker-Installation *** ioBroker Status /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string Core adapters versions /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string js-controller: /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string admin: /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string javascript: Adapters from github: 0 Adapter State /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string Enabled adapters with bindings /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string ioBroker-Repositories /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string Installed ioBroker-Instances /usr/bin/node: 1: cannot create : Permission denied /usr/bin/node: 2: : not found /usr/bin/node: 4: Syntax error: Unterminated quoted string Objects and States Please stand by - This may take a while Objects: 0 States: 0 *** OS-Repositories and Updates *** W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Some index files failed to download. They have been ignored, or old ones used instead. Get:1 https://dl.yarnpkg.com/debian stable InRelease [17.1 kB] Hit:2 http://security.ubuntu.com/ubuntu jammy-security InRelease Hit:3 http://archive.ubuntu.com/ubuntu jammy InRelease Hit:4 http://archive.ubuntu.com/ubuntu jammy-updates InRelease Hit:5 http://archive.ubuntu.com/ubuntu jammy-backports InRelease Err:1 https://dl.yarnpkg.com/debian stable InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> Fetched 17.1 kB in 3s (5230 B/s) Reading package lists... W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://dl.yarnpkg.com/debian stable InRelease: The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Failed to fetch https://dl.yarnpkg.com/debian/dists/stable/InRelease The following signatures were invalid: EXPKEYSIG 23E7166788B63E1E Yarn Packaging <yarn@dan.cx> W: Some index files failed to download. They have been ignored, or old ones used instead. 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 *** Log File - Last 25 Lines *** 2023-10-07 21:49:27.501 - info: host.Marek2 instance system.adapter.kodi.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.502 - info: host.Marek2 instance system.adapter.tr-064.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.502 - info: host.Marek2 instance system.adapter.shelly.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.502 - info: host.Marek2 stopInstance system.adapter.pushover.0 killing pid 9396 2023-10-07 21:49:27.537 - info: host.Marek2 instance system.adapter.discovery.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.538 - info: host.Marek2 instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.539 - info: host.Marek2 instance system.adapter.javascript.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.634 - info: host.Marek2 stopInstance system.adapter.web.0 killing pid 10344 2023-10-07 21:49:27.635 - info: host.Marek2 stopInstance system.adapter.philips-tv.0 killing pid 10481 2023-10-07 21:49:27.647 - info: host.Marek2 instance system.adapter.sonoff.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.668 - info: host.Marek2 instance system.adapter.iot.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.668 - info: host.Marek2 instance system.adapter.broadlink2.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.730 - info: host.Marek2 instance system.adapter.info.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.730 - info: host.Marek2 instance system.adapter.yahka.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.730 - info: host.Marek2 instance system.adapter.tankerkoenig.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.765 - info: host.Marek2 instance system.adapter.firetv.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.765 - info: host.Marek2 instance system.adapter.parcel.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.839 - info: host.Marek2 instance system.adapter.web.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.840 - info: host.Marek2 instance system.adapter.philips-tv.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:27.901 - info: host.Marek2 instance system.adapter.pushover.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:29.473 - info: tuya.0 (9456) terminating 2023-10-07 21:49:29.475 - info: tuya.0 (9456) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-10-07 21:49:30.080 - info: host.Marek2 instance system.adapter.tuya.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-10-07 21:49:30.081 - info: host.Marek2 All instances are stopped. 2023-10-07 21:49:30.150 - info: host.Marek2 terminatedKann mir da jemand helfen oder ist das schon ein hofnungsose Fahl?
@krisiun sagte in iobroker zeschossen:
System has not been booted with systemd as init system (PID 1). Can't operate.
eine Normal Abfrage funktioniert ja noch nicht mal.
Ich denke mal da ist Linux zerschossen -
Ich habe schon verstanden. Macht mich nicht noch mehr fertig als ich schon bin.
Die istallation auf Windows rechner war für mich für Testzwecke. Ich wollte nicht riskieren aufm rassby zu experimentieren.
Eins möchte ich von Euch wissen? Kann man die installation noch retten oder nicht?@krisiun sagte in iobroker zeschossen:
Kann man die installation noch retten oder nicht?
Keine Ahnung. Du kannst ja nicht sagen, was du da wo mit root-Rechten herumgefummelt hast.
Ich würde zuerstmal ordentliche user anlegen, den root dann in Ruh' lassen und ordentlich das nodesource-Repo anlegen.
-
Ich habe schon verstanden. Macht mich nicht noch mehr fertig als ich schon bin.
Die istallation auf Windows rechner war für mich für Testzwecke. Ich wollte nicht riskieren aufm rassby zu experimentieren.
Eins möchte ich von Euch wissen? Kann man die installation noch retten oder nicht?@krisiun sagte in iobroker zeschossen:
Die istallation auf Windows rechner war für mich für Testzwecke. Ich wollte nicht riskieren aufm rassby zu experimentieren.
Hab ich alles hinter mir.
Kauf dir ein ordentliches System (z.B. nuc) und mach proxmox drauf. Dann kannst du ganz schnell ein backup machen; und dies evtl. wieder zurück spielen.
Fazit:
nuc kaufen
proxmox drauf
backup von deinem backitup einspielen.
Fertig.P.S.
was ist ein rassby ? -
@krisiun sagte in iobroker zeschossen:
System has not been booted with systemd as init system (PID 1). Can't operate.
eine Normal Abfrage funktioniert ja noch nicht mal.
Ich denke mal da ist Linux zerschossen@glasfaser sagte in iobroker zeschossen:
System has not been booted with systemd as init system (PID 1). Can't operate.
Ich vermute, das wsl bootet nicht per systemd.
Edit:
Näheres hier
https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/ -
@glasfaser sagte in iobroker zeschossen:
System has not been booted with systemd as init system (PID 1). Can't operate.
Ich vermute, das wsl bootet nicht per systemd.
Edit:
Näheres hier
https://devblogs.microsoft.com/commandline/systemd-support-is-now-available-in-wsl/@thomas-braun sagte in iobroker zeschossen:
@glasfaser sagte in iobroker zeschossen:
System has not been booted with systemd as init system (PID 1). Can't operate.
Ich vermute, das wsl bootet nicht per systemd.
Nein leider nicht
-
@krisiun sagte in iobroker zeschossen:
Die istallation auf Windows rechner war für mich für Testzwecke. Ich wollte nicht riskieren aufm rassby zu experimentieren.
Hab ich alles hinter mir.
Kauf dir ein ordentliches System (z.B. nuc) und mach proxmox drauf. Dann kannst du ganz schnell ein backup machen; und dies evtl. wieder zurück spielen.
Fazit:
nuc kaufen
proxmox drauf
backup von deinem backitup einspielen.
Fertig.P.S.
was ist ein rassby ?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 sagte in iobroker zeschossen:
@bahnuhr sagte in iobroker zeschossen:
was ist ein rassby ?
Raspberry Pi
-
Das ist cool.
Bild bitte per Link ;-) -
@krisiun sagte in iobroker zeschossen:
Dann muss ich wohl wieder von vorne anfangen
Was hast du denn jetzt von den bisherigen Ansätzen umgesetzt?
User angelegt?
Diesem die Gruppenzugehörigkeit zuadm,sudo,iobrokergegeben?
nodesource-Repo hinzugefügt?
nodejs aus diesem dann installiert? -
@krisiun sagte in iobroker zeschossen:
Dann muss ich wohl wieder von vorne anfangen
Was hast du denn jetzt von den bisherigen Ansätzen umgesetzt?
User angelegt?
Diesem die Gruppenzugehörigkeit zuadm,sudo,iobrokergegeben?
nodesource-Repo hinzugefügt?
nodejs aus diesem dann installiert?@thomas-braun sagte in iobroker zeschossen:
@krisiun sagte in iobroker zeschossen:
Dann muss ich wohl wieder von vorne anfangen
Was hast du denn jetzt von den bisherigen Ansätzen umgesetzt?
https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian
Die Anleitung probiert
-
@krisiun sagte in iobroker zeschossen:
Dann muss ich wohl wieder von vorne anfangen
Bei 0 .. nicht , du hast doch Backups !
/opt/iobroker/backups:
103M /opt/iobroker/backups/ -
@thomas-braun sagte in iobroker zeschossen:
@krisiun sagte in iobroker zeschossen:
Dann muss ich wohl wieder von vorne anfangen
Was hast du denn jetzt von den bisherigen Ansätzen umgesetzt?
https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian
Die Anleitung probiert
-
@krisiun sagte in iobroker zeschossen:
Dann muss ich wohl wieder von vorne anfangen
Bei 0 .. nicht , du hast doch Backups !
/opt/iobroker/backups:
103M /opt/iobroker/backups/ -
@thomas-braun sagte in iobroker zeschossen:
@krisiun sagte in iobroker zeschossen:
Die Anleitung probiert
Mit welchem Resultat?
Kein Erfolg
520
Online32.6k
Users82.3k
Topics1.3m
Posts