Diskussion zum HowTo nodejs-Installation und upgrade
-
@knatterman und beim sonoff Adapter einmal das Passwort erneut eintragen und Instanz neu starten.
-
Woran siehst Du das?
Und wäre das etwas, was ich in der VM, auf dem Host oder an noch anderer Stelle korrigieren/einstellen müsste?Danke für die Hilfe soweit.
-
Danke fürs schauen und das sind die Kleinigkeiten, um die ich mich noch kümmern muss.
Gruß
Frank -
Das sieht man z. B. hier:
W: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease Undetermined Error [IP: 2a0a:a547:5d63:0:464e:6dff:fefe:9d8 80] W: Failed to fetch http://security.debian.org/debian-security/dists/bookworm-security/InRelease Undetermined Error [IP: 2a0a:a547:5d63:0:464e:6dff:fefe:9d8 80] W: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease Undetermined Error [IP: 2a0a:a547:5d63:0:464e:6dff:fefe:9d8 80] W: Some index files failed to download. They have been ignored, or old ones used instead.Da wird der host nicht unter seiner IPv6
2a0a:a547:5d63:0:464e:6dff:fefe:9d8erreicht.Und setz das Ding auf boot.target multi-user.
sudo systemctl set-default multi-user.targetDeinen user würde ich noch in die Gruppe
admaufnehmen.sudo usermod -a -G adm iobrokerWobei die Wahl von 'iobroker' als username jetzt auch nicht die geschickteste war...
-
Moin,
ich habe soeben auf meinen Master und Slave Nodejs hochgezogen.
Mir ist jetzt aufgefallen, dass npm die Version 10.2.3 hat.
/usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3Ist das so korrekt?
Vielen Dank!
-
@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
Ist das so korrekt?
ja
@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
Mir ist jetzt aufgefallen, dass npm die Version 10.2.3 hat.
soll es auch
-
@homoran vielen Dank!
-
Guten Morgen,
ich habe jetzt doch nochmal ein Frage. Seit dem ich gestern Nodejs geupdatet habe, kann ich keine Adapter mehr installieren. Die Installation bleibt bei Installing iobroker.zigbee@1.9.5... (System call) stehen.
Kann das an dem Update liegen?
Vielen Dank!
-
@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
Kann das an dem Update liegen?
Nein.
iob diagsagt? LogFile sagt?
-
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: raspberrypi Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Model : Raspberry Pi 3 Model B Rev 1.2 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 09:27:08 up 14:00, 1 user, load average: 2.07, 2.00, 1.17 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Thu 2024-01-04 09:27:08 CET Universal time: Thu 2024-01-04 08:27:08 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) 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 render netdev gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 909M 589M 64M 0.0K 255M 260M Swap: 99M 99M 0.0K Total: 1.0G 689M 64M 909 M total memory 590 M used memory 416 M active memory 344 M inactive memory 63 M free memory 9 M buffer memory 246 M swap cache 99 M total swap 99 M used swap 0 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 59G 32G 25G 57% / devtmpfs devtmpfs 325M 0 325M 0% /dev tmpfs tmpfs 455M 0 455M 0% /dev/shm tmpfs tmpfs 182M 1020K 181M 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 31M 225M 13% /boot tmpfs tmpfs 91M 0 91M 0% /run/user/1000 tmpfs tmpfs 91M 0 91M 0% /run/user/0 Messages concerning ext4 filesystem in dmesg: [Wed Jan 3 19:27:05 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 video=Composite-1:720x480@60i vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=d3cf0315-02 rootfstype=ext4 fsck.repair=yes rootwait [Wed Jan 3 19:27:08 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Wed Jan 3 19:27:08 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Wed Jan 3 19:27:08 2024] EXT4-fs (mmcblk0p2): orphan cleanup on readonly fs [Wed Jan 3 19:27:08 2024] EXT4-fs (mmcblk0p2): 4 orphan inodes deleted [Wed Jan 3 19:27:08 2024] EXT4-fs (mmcblk0p2): recovery complete [Wed Jan 3 19:27:08 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Wed Jan 3 19:27:08 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Wed Jan 3 19:27:12 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 27G /var/ 22G /var/lib/mysql/iobroker 22G /var/lib/mysql 22G /var/lib 4.5G /var/log Archived and active journals take up 4.0G in the file system. /opt/iobroker/backups: 4.0K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 18M /opt/iobroker/iobroker-data/ 14M /opt/iobroker/iobroker-data/files 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js 13M /opt/iobroker/iobroker-data/files/admin.admin/custom/static 13M /opt/iobroker/iobroker-data/files/admin.admin/custom The five largest files in iobroker-data are: 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map 3.0M /opt/iobroker/iobroker-data/objects.jsonl 2.8M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js 1.6M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_Accordion_index_js-node_modules_mui_material_AccordionDetai-57e02d.0886b730.chunk.js.map 652K /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_mui_material_index_js.40e01f69.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-1a86_USB_Serial-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /usr/bin/npm 10.2.3 /usr/bin/npx 10.2.3 /usr/bin/corepack 0.22.0 nodejs: Installed: 18.19.0-1nodesource1 Candidate: 18.19.0-1nodesource1 Version table: *** 18.19.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main arm64 Packages 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. At least one iobroker host is running. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 4.0.24 admin: 6.12.0 javascript: "javascript" not found Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : debian - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.alexa2.0 : alexa2 : debian - enabled + system.adapter.backitup.0 : backitup : debian - enabled system.adapter.daswetter.0 : daswetter : debian - enabled system.adapter.devices.0 : devices : debian - enabled + system.adapter.discovery.0 : discovery : debian - enabled system.adapter.dwd.0 : dwd : debian - enabled + system.adapter.enigma2.0 : enigma2 : raspberrypi - enabled system.adapter.feiertage.0 : feiertage : debian - enabled system.adapter.flot.0 : flot : debian - enabled + system.adapter.history.0 : history : debian - enabled + system.adapter.hm-rega.0 : hm-rega : debian - enabled + system.adapter.hm-rpc.0 : hm-rpc : debian - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : debian - enabled, port: 0 system.adapter.ical.0 : ical : debian - enabled system.adapter.ical.1 : ical : debian - enabled system.adapter.ical.2 : ical : debian - enabled system.adapter.icons-mfd-png.0 : icons-mfd-png : debian - enabled system.adapter.icons-mfd-svg.0 : icons-mfd-svg : debian - enabled + system.adapter.info.0 : info : debian - enabled + system.adapter.iot.0 : iot : debian - enabled + system.adapter.javascript.0 : javascript : debian - enabled + system.adapter.lg-thinq.0 : lg-thinq : debian - enabled + system.adapter.linux-control.0 : linux-control : debian - enabled + system.adapter.logparser.0 : logparser : debian - enabled + system.adapter.meross.0 : meross : debian - enabled + system.adapter.mihome-vacuum.0 : mihome-vacuum : debian - enabled, port: 54321 system.adapter.mobile.0 : mobile : debian - enabled + system.adapter.modbus.0 : modbus : debian - enabled + system.adapter.openligadb.0 : openligadb : debian - enabled + system.adapter.ping.0 : ping : debian - enabled + system.adapter.pollenflug.0 : pollenflug : debian - enabled + system.adapter.rpi2.1 : rpi2 : raspberrypi - enabled + system.adapter.scenes.0 : scenes : debian - enabled + system.adapter.shelly.0 : shelly : debian - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : debian - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : debian - enabled, port: 8084, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.sql.0 : sql : debian - enabled, port: 3306 + system.adapter.systeminfo.0 : systeminfo : debian - enabled + system.adapter.tankerkoenig.0 : tankerkoenig : debian - enabled + system.adapter.telegram.0 : telegram : debian - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.terminal.0 : terminal : debian - enabled, port: 8088, bind: 0.0.0.0, run as: admin + system.adapter.text2command.0 : text2command : debian - enabled + system.adapter.tibberlink.0 : tibberlink : debian - enabled + system.adapter.tr-064.0 : tr-064 : debian - enabled + system.adapter.trashschedule.0 : trashschedule : debian - enabled + system.adapter.upnp.0 : upnp : debian - enabled + system.adapter.viessmannapi.0 : viessmannapi : debian - enabled system.adapter.vis-bars.0 : vis-bars : debian - enabled system.adapter.vis-canvas-gauges.0 : vis-canvas-gauges : debian - enabled system.adapter.vis-colorpicker.0 : vis-colorpicker : debian - enabled system.adapter.vis-fancyswitch.0 : vis-fancyswitch : debian - enabled system.adapter.vis-history.0 : vis-history : debian - enabled system.adapter.vis-hqwidgets.0 : vis-hqwidgets : debian - enabled system.adapter.vis-jqui-mfd.0 : vis-jqui-mfd : debian - enabled system.adapter.vis-justgage.0 : vis-justgage : debian - enabled system.adapter.vis-materialdesign.0 : vis-materialdesign : debian - enabled system.adapter.vis-metro.0 : vis-metro : debian - enabled system.adapter.vis-plumb.0 : vis-plumb : debian - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : debian - enabled system.adapter.vis-weather.0 : vis-weather : debian - enabled system.adapter.vis.0 : vis : debian - enabled + system.adapter.web.0 : web : debian - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/ttyUSB0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : debian - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.hm-rpc.0 : hm-rpc : debian - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : debian - enabled, port: 0 + system.adapter.mihome-vacuum.0 : mihome-vacuum : debian - enabled, port: 54321 + system.adapter.shelly.0 : shelly : debian - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : debian - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : debian - enabled, port: 8084, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.sql.0 : sql : debian - enabled, port: 3306 + system.adapter.telegram.0 : telegram : debian - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.terminal.0 : terminal : debian - enabled, port: 8088, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : debian - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : raspberrypi - enabled, port: /dev/ttyUSB0 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.12.0 , installed 6.12.0 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "enigma2" : 2.0.5 , installed 2.0.5 Controller "js-controller": 5.0.17 , installed 4.0.24 [Updatable] Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "unifi" : 0.6.7 , installed 0.6.7 Adapter "zigbee" : 1.9.5 , installed 1.8.23 [Updatable] Objects and States Please stand by - This may take a while Objects: 27972 States: 22604 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye-updates InRelease Hit:3 http://security.debian.org/debian-security bullseye-security InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://deb.nodesource.com/node_18.x nodistro 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 11952 526/sshd: /usr/sbin tcp6 0 0 :::22 :::* LISTEN 0 11954 526/sshd: /usr/sbin tcp6 0 0 :::3306 :::* LISTEN 110 14596 568/mariadbd udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 12753 394/avahi-daemon: r udp 0 0 0.0.0.0:58923 0.0.0.0:* 108 12755 394/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 12822 697/dhcpcd udp6 0 0 :::5353 :::* 108 12754 394/avahi-daemon: r udp6 0 0 :::59929 :::* 108 12756 394/avahi-daemon: r udp6 0 0 :::546 :::* 0 12083 697/dhcpcd *** Log File - Last 25 Lines *** 2024-01-04 08:46:50.276 - info: zigbee.0 (129073) --> transmitPower : normal 2024-01-04 08:46:50.308 - info: zigbee.0 (129073) Currently 18 devices are joined: 2024-01-04 08:46:50.630 - info: zigbee.0 (129073) 0x00158d00069b00d3 (addr 12111): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2024-01-04 08:46:50.642 - info: zigbee.0 (129073) 0x00158d00053f42d6 (addr 25476): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-01-04 08:46:50.652 - info: zigbee.0 (129073) 0x00124b001f7a8b1c (addr 48495): GL-C-007-2ID - Gledopto Zigbee LED Controller RGBW (2 ID) (Router) 2024-01-04 08:46:50.658 - info: zigbee.0 (129073) 0x00158d00045ced13 (addr 57845): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-01-04 08:46:50.663 - info: zigbee.0 (129073) 0x7cb03eaa0a07df5f (addr 3784): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router) 2024-01-04 08:46:50.667 - info: zigbee.0 (129073) 0x00158d00053f72a6 (addr 38940): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-01-04 08:46:50.671 - info: zigbee.0 (129073) 0x00158d0006a034d9 (addr 9912): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2024-01-04 08:46:50.675 - info: zigbee.0 (129073) 0x7cb03eaa0a07df70 (addr 52141): AC03641 - OSRAM LIGHTIFY LED Classic A60 clear (Router) 2024-01-04 08:46:50.681 - info: zigbee.0 (129073) 0xb4e3f9fffe8119c5 (addr 52016): E1603/E1702/E1708 - IKEA TRADFRI control outlet (Router) 2024-01-04 08:46:50.685 - info: zigbee.0 (129073) 0xb4e3f9fffe810ccf (addr 7537): E1603/E1702/E1708 - IKEA TRADFRI control outlet (Router) 2024-01-04 08:46:50.690 - info: zigbee.0 (129073) 0x00158d00068b6d42 (addr 4761): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2024-01-04 08:46:50.693 - info: zigbee.0 (129073) 0x00158d00069c5148 (addr 61445): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-01-04 08:46:50.697 - info: zigbee.0 (129073) 0x00158d00069d3207 (addr 54025): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-01-04 08:46:50.701 - info: zigbee.0 (129073) 0x00158d00047dd980 (addr 56066): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-01-04 08:46:50.706 - info: zigbee.0 (129073) 0x00158d00069ae75b (addr 18976): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-01-04 08:46:50.712 - info: zigbee.0 (129073) 0x00158d00069c52b6 (addr 10299): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-01-04 08:46:50.716 - info: zigbee.0 (129073) 0x00158d00053fad60 (addr 54656): MCCGQ11LM - Xiaomi Aqara door & window contact sensor (EndDevice) 2024-01-04 08:46:50.720 - info: zigbee.0 (129073) 0x00158d000659e158 (addr 22041): WSDCGQ11LM - Xiaomi Aqara temperature, humidity and pressure sensor (EndDevice) 2024-01-04 08:46:50.723 - info: zigbee.0 (129073) Zigbee started 2024-01-04 08:46:50.937 - info: zigbee.0 (129073) debug devices set to [] 2024-01-04 08:47:10.049 - warn: zigbee.0 (129073) DeviceAvailability:Failed to ping 0x7cb03eaa0a07df70 Classic A60 W clear - LIGHTIFY 2024-01-04 09:18:02.612 - warn: zigbee.0 (129073) DeviceAvailability:Stopping to ping 0x7cb03eaa0a07df70 Classic A60 W clear - LIGHTIFY after 4 ping attempts 2024-01-04 09:28:52.925 - warn: zigbee.0 (129073) Device '0x7cb03eaa0a07df70' announced itself ============ Mark until here for C&P ============= iob diag has finished.Log sagt nichts, da ich das Update irgendwann abbreche, weil es nicht weiter geht.
host.raspberrypi 2024-01-04 09:34:57.508 info iobroker Installing iobroker.zigbee@1.9.5... (System call) host.raspberrypi 2024-01-04 09:34:57.504 info iobroker NPM version: 10.2.3 host.raspberrypi 2024-01-04 09:34:56.787 info instance system.adapter.zigbee.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) host.raspberrypi 2024-01-04 09:34:56.225 info stopInstance system.adapter.zigbee.0 killing pid 129073 host.raspberrypi 2024-01-04 09:34:55.220 info stopInstance system.adapter.zigbee.0 send kill signal host.raspberrypi 2024-01-04 09:34:55.108 info stopInstance system.adapter.zigbee.0 (force=false, process=true) host.raspberrypi 2024-01-04 09:34:55.103 info "system.adapter.zigbee.0" disabled host.raspberrypi 2024-01-04 09:34:55.087 info iobroker host.raspberrypi Adapter "system.adapter.zigbee.0" is stopped. host.raspberrypi 2024-01-04 09:34:55.025 info iobroker Update zigbee from @1.8.23 to @1.9.5 host.raspberrypi 2024-01-04 09:34:50.295 info iobroker upgrade zigbee@1.9.5 --debug -
@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
da ich das Update irgendwann abbreche, weil es nicht weiter geht.
Dann lass es einfach mal laufen...
-
So am Rande: auf einem RPI3 mit 1 GB RAM sind 30+ aktive Instanzen mehr als sportlich.
Dir geht definitiv der Speicher aus. -
@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
4 orphan inodes deleted
Dein Dateisystem hat 'nen Treffer.
Controller "js-controller": 5.0.17 , installed 4.0.24 [Updatable]
Update den js-controller.
-
@djmarc75 auf dem System laufen nur 3 Instanzen, es handelt sich hierbei um ein Slave.
-
@thomas-braun Ich habe das Update um 09:34 gestartet und es hängt noch immer.
-
@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
und es hängt noch immer.
Nein, das läuft noch immer. Finger weg, laufen lassen.
-
Es hat sich nichts mehr getan. Hab jetzt versucht auf meinem Master den js-controller zu updaten.
Leider bleibt er auch hängen.
/opt/iobroker$ iob upgrade self Update js-controller from @4.0.24 to @5.0.17 Stopped Objects DB Stopped States DB NPM version: 10.2.3 Installing iobroker.js-controller@5.0.17... (System call) -
@djsirius dann mach es mal mit --debug
-
@homoran keine Veränderung
iobroker@debian:~$ cd /opt/iobroker iobroker@debian:/opt/iobroker$ iobroker stop iobroker@debian:/opt/iobroker$ iob upgrade self --debug Update js-controller from @4.0.24 to @5.0.17 Stopped Objects DB Stopped States DB NPM version: 10.2.3 Installing iobroker.js-controller@5.0.17... (System call) -
@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
keine Veränderung
was bedeutet
@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
bleibt er auch hängen.
denn in Zahlen?
wie sieht es denn
@djsirius sagte in Diskussion zum HowTo nodejs-Installation und upgrade:
auf meinem Master
mit
iob diagaus?
was ist das für ein Rechner?hast du mal eine zweite Terminalsession aufgemacht und z.B. mit
topnachgesehen was da gerade rödelt?
