Web Interface nach Update nicht erreichbar
-
@thomas-braun said in Web Interface nach Update nicht erreichbar:
iob start admin
Habe ich alles gemacht, funktioniert leider nicht :-(.
-
@viper2033 sagte in Web Interface nach Update nicht erreichbar:
Habe ich alles gemacht, funktioniert leider nicht :-(.
Dann nochmal
iob diagDiesmal bitte besser lesbar inkl. der CodeTags.
-
Sehe ich gerade erst:
/usr/bin/npm 10.3.0 /usr/bin/npx 10.3.0Das ist nicht die Version, die mit nodejs 18.19.0 gebündelt kommt. Von Hand irgendwas gefummelt? Muss ja...
sudo apt install --reinstall nodejs -
@thomas-braun
Habe nodejs geupdatet leider kein Erfolg:code_text` Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: CT210 Icon name: computer-container Chassis: container Virtualization: lxc Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.5.11-4-pve Architecture: x86-64 model name : Intel(R) Celeron(R) J4105 CPU @ 1.50GHz Docker : false Virtualization : lxc Kernel : x86_64 Userland : amd64 Systemuptime and Load: 16:00:19 up 1 min, 1 user, load average: 0.52, 0.49, 0.41 CPU threads: 2 *** Time and Time Zones *** Local time: Thu 2024-01-18 16:00:19 CET Universal time: Thu 2024-01-18 15:00:19 UTC RTC time: n/a Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** User and Groups *** test /home/test test adm sudo iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 2.0G 575M 1.3G 0.0K 185M 1.5G Swap: 512M 0B 512M Total: 2.6G 575M 1.8G 2048 M total memory 576 M used memory 641 M active memory 74 M inactive memory 1285 M free memory 0 M buffer memory 185 M swap cache 512 M total swap 0 M used swap 512 M free swap *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System * sys-kernel-config.mount loaded failed failed Kernel Configuration File System * systemd-journald-audit.socket loaded failed failed Journal Audit Socket LOAD = Reflects whether the unit definition was properly loaded. ACTIVE = The high-level unit activation state, i.e. generalization of SUB. SUB = The low-level unit activation state, values depend on unit type. 3 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--210--disk--0 ext4 7.8G 4.4G 3.1G 60% / none tmpfs 492K 4.0K 488K 1% /dev udev devtmpfs 3.8G 0 3.8G 0% /dev/tty tmpfs tmpfs 3.8G 0 3.8G 0% /dev/shm tmpfs tmpfs 1.6G 112K 1.6G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--210--disk--0 ext4 rw,relatime,stripe=16 Files in neuralgic directories: /var: 909M /var/ 429M /var/log 388M /var/log/journal/e982dcf1ad9c45638928dfce9f1ddc3d 388M /var/log/journal 344M /var/cache Archived and active journals take up 387.6M in the file system. /opt/iobroker/backups: 34M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 369M /opt/iobroker/iobroker-data/ 319M /opt/iobroker/iobroker-data/files 89M /opt/iobroker/iobroker-data/files/echarts.admin 67M /opt/iobroker/iobroker-data/files/javascript.admin 57M /opt/iobroker/iobroker-data/files/echarts The five largest files in iobroker-data are: 33M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.map 24M /opt/iobroker/iobroker-data/files/echarts/static/js/main.2b7495c2.js.map 24M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.2b7495c2.js.map 23M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.245b61c0.js.map 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** 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 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://ftp.debian.org/debian bullseye/main amd64 Packages 500 http://security.debian.org bullseye-security/main amd64 Packages Temp directories causing npm8 problem: 1 Some problems detected, please run iob fix Errors in npm tree: npm ERR! code ELSPROBLEMS npm ERR! extraneous: es6-promise@4.2.8 /opt/iobroker/node_modules/es6-promise npm ERR! invalid: diskusage@ /opt/iobroker/node_modules/diskusage npm ERR! A complete log of this run can be found in: /home/test/.npm/_logs/2024-01-18T15_00_24_400Z-debug-0.log *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 4.0.23 admin: 6.12.0 javascript: 7.1.6 Adapters from github: 0 Adapter State system.adapter.admin.0 : admin : CT210 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : CT210 - enabled + system.adapter.deyeidc.0 : deyeidc : CT210 - enabled, port: 8899 + system.adapter.discovery.0 : discovery : CT210 - enabled system.adapter.ebus.0 : ebus : CT210 - disabled + system.adapter.echarts.0 : echarts : CT210 - enabled + system.adapter.heatingcontrol.0 : heatingcontrol : CT210 - enabled + system.adapter.history.0 : history : CT210 - enabled system.adapter.hm-rega.0 : hm-rega : CT210 - enabled + system.adapter.hm-rpc.0 : hm-rpc : CT210 - enabled, port: 0 + system.adapter.influxdb.0 : influxdb : CT210 - enabled, port: 8086 system.adapter.iot.0 : iot : CT210 - enabled + system.adapter.javascript.0 : javascript : CT210 - enabled system.adapter.openknx.0 : openknx : CT210 - enabled system.adapter.pvforecast.0 : pvforecast : CT210 - enabled system.adapter.solarmanpv.0 : solarmanpv : CT210 - disabled + system.adapter.sonos.0 : sonos : CT210 - enabled system.adapter.weatherunderground.0 : weatherunderground : CT210 - enabled + system.adapter.web.0 : web : CT210 - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.yeelight-2.0 : yeelight-2 : CT210 - enabled system.adapter.zigbee.0 : zigbee : CT210 - enabled, port: /dev/ttyACM0 + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : CT210 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.deyeidc.0 : deyeidc : CT210 - enabled, port: 8899 + system.adapter.hm-rpc.0 : hm-rpc : CT210 - enabled, port: 0 + system.adapter.influxdb.0 : influxdb : CT210 - enabled, port: 8086 + system.adapter.web.0 : web : CT210 - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.zigbee.0 : zigbee : CT210 - enabled, port: /dev/ttyACM0 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 "backitup" : 2.9.8 , installed 2.9.8 Adapter "deyeidc" : 0.0.14 , installed 0.0.14 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "ebus" : 3.2.4 , installed 3.2.4 Adapter "echarts" : 1.7.2 , installed 1.7.2 Adapter "heatingcontrol": 2.12.2 , installed 2.12.2 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 4.0.0 , installed 4.0.0 Adapter "hm-rpc" : 1.15.19 , installed 1.15.19 Adapter "influxdb" : 3.2.0 , installed 3.2.0 Adapter "iot" : 2.0.11 , installed 2.0.11 Adapter "javascript" : 7.1.6 , installed 7.1.6 Controller "js-controller": 5.0.17 , installed 4.0.23 [Updatable] Adapter "openknx" : 0.6.3 , installed 0.6.3 Adapter "pvforecast" : 2.9.1 , installed 2.9.1 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "solarmanpv" : 0.5.1 , installed 0.5.1 Adapter "sonos" : 3.0.0 , installed 3.0.0 Adapter "weatherunderground": 3.6.0, installed 3.6.0 Adapter "web" : 6.1.10 , installed 6.1.10 Adapter "ws" : 2.5.8 , installed 2.5.8 Adapter "yeelight-2" : 1.2.1 , installed 1.2.1 Adapter "zigbee" : 1.9.7 , installed 1.9.7 Objects and States Please stand by - This may take a while Objects: 2394 States: 1949 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org bullseye-security InRelease Hit:2 http://ftp.debian.org/debian bullseye InRelease Hit:3 http://ftp.debian.org/debian bullseye-updates InRelease Hit:4 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 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 91450790 141/iobroker.js-con tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 91451539 141/iobroker.js-con tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 91450633 314/master tcp 0 0 192.168.2.52:2001 0.0.0.0:* LISTEN 1000 91451867 406/io.hm-rpc.0 tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 104 91451396 101/systemd-resolve tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 91447175 1/init tcp 0 0 0.0.0.0:5355 0.0.0.0:* LISTEN 104 91448317 101/systemd-resolve tcp6 0 0 ::1:25 :::* LISTEN 0 91450634 314/master tcp6 0 0 :::8082 :::* LISTEN 1000 91451245 472/io.web.0 tcp6 0 0 :::3500 :::* LISTEN 1000 91451732 377/io.sonos.0 tcp6 0 0 :::111 :::* LISTEN 0 91447177 1/init tcp6 0 0 :::22 :::* LISTEN 0 91448192 1/init tcp6 0 0 :::5355 :::* LISTEN 104 91448320 101/systemd-resolve udp 0 0 127.0.0.53:53 0.0.0.0:* 104 91451395 101/systemd-resolve udp 0 0 0.0.0.0:68 0.0.0.0:* 0 91448251 86/dhclient udp 0 0 0.0.0.0:111 0.0.0.0:* 0 91447176 1/init udp 0 0 0.0.0.0:5355 0.0.0.0:* 104 91448316 101/systemd-resolve udp6 0 0 :::111 :::* 0 91447178 1/init udp6 0 0 :::5355 :::* 104 91448319 101/systemd-resolve *** Log File - Last 25 Lines *** 2024-01-18 16:00:40.892 - error: host.CT210 Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.hm-rega/lib/rega.js:16:15) 2024-01-18 16:00:40.893 - error: host.CT210 Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1356:14) 2024-01-18 16:00:40.893 - error: host.CT210 Caught by controller[1]: Node.js v18.19.0 2024-01-18 16:00:40.893 - error: host.CT210 instance system.adapter.hm-rega.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2024-01-18 16:00:40.893 - info: host.CT210 Restart adapter system.adapter.hm-rega.0 because enabled 2024-01-18 16:00:41.567 - info: host.CT210 instance system.adapter.pvforecast.0 started with pid 940 2024-01-18 16:00:42.104 - error: host.CT210 Caught by controller[0]: /opt/iobroker/node_modules/axios/dist/node/axios.cjs:1444 2024-01-18 16:00:42.104 - error: host.CT210 Caught by controller[0]: const hasJSONContentType = contentType.indexon$'K0qhicaTx+ljson?i*%-1;�( #Onst"i7ObjekvPaiekad�=$etils9*ysE"Kect8dit! ;J 2024-01-18 16:00:42.104 - error: host.CT210 Caught by controller[0]: ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 2024-01-18 16:00:42.104 - error: host.CT210 Caught by controller[0]: SyntaxError: Invalid or unexpected token 2024-01-18 16:00:42.104 - error: host.CT210 Caught by controller[0]: at internalCompileFunction (node:internal/vm:73:18) 2024-01-18 16:00:42.104 - error: host.CT210 Caught by controller[0]: at wrapSafe (node:internal/modules/cjs/loader:1274:20) 2024-01-18 16:00:42.104 - error: host.CT210 Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1320:27) 2024-01-18 16:00:42.105 - error: host.CT210 Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1414:10) 2024-01-18 16:00:42.105 - error: host.CT210 Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1197:32) 2024-01-18 16:00:42.105 - error: host.CT210 Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1013:12) 2024-01-18 16:00:42.105 - error: host.CT210 Caught by controller[0]: at Module.require (node:internal/modules/cjs/loader:1225:19) 2024-01-18 16:00:42.105 - error: host.CT210 Caught by controller[0]: at require (node:internal/modules/helpers:177:18) 2024-01-18 16:00:42.105 - error: host.CT210 Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.pvforecast/main.js:5:15) 2024-01-18 16:00:42.105 - error: host.CT210 Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1356:14) 2024-01-18 16:00:42.105 - error: host.CT210 Caught by controller[1]: Node.js v18.19.0 2024-01-18 16:00:42.105 - error: host.CT210 instance system.adapter.pvforecast.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2024-01-18 16:00:42.105 - info: host.CT210 Restart adapter system.adapter.pvforecast.0 because enabled 2024-01-18 16:00:54.358 - info: host.CT210 instance system.adapter.yeelight-2.0 started with pid 1270 2024-01-18 16:00:55.733 - info: yeelight-2.0 (1270) starting. Version 1.2.1 in /opt/iobroker/node_modules/iobroker.yeelight-2, node: v18.19.0, js-controller: 4.0.23code_text ======================= SUMMARY ======================= v.2023-10-10 Static hostname: CT210 Icon name: computer-container Chassis: container Virtualization: lxc Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.5.11-4-pve Architecture: x86-64 Installation: lxc Kernel: x86_64 Userland: amd64 Timezone: Europe/Berlin (CET, +0100) User-ID: 1001 X-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 1 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 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 2.0G 587M 1.1G 0.0K 362M 1.5G Swap: 512M 0B 512M Total: 2.6G 587M 1.6G Active iob-Instances: 12 Active repo(s): stable ioBroker Core: js-controller 4.0.23 admin 6.12.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : CT210 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.web.0 : web : CT210 - enabled, port: 8082, bind: 0.0.0.0, run as: admin Objects: 2394 States: 1949 Size of iob-Database: 5.8M /opt/iobroker/iobroker-data/objects.jsonl 484K /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ======================= Mark text until here for copying ===```
-
@viper2033 sagte in Web Interface nach Update nicht erreichbar:
js-controller: 4.0.23
Das ist dein Problem.
cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller -
@thomas-braun said in Web Interface nach Update nicht erreichbar:
sudo -H -u iobroker npm install iobroker.js-controller
Es kommt folgende Meldung:
code_textnpm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/diskusage npm ERR! dest /opt/iobroker/node_modules/.diskusage-SbL2R1mm npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/diskusage' -> '/opt/iobroker/node_modules/.diskusage-SbL2R1mm'``` -
Dann
iob stop iob fix cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller -
@thomas-braun said in Web Interface nach Update nicht erreichbar:
sudo -H -u iobroker npm install iobroker.js-controller
Folgende Fehlermeldung:
code_text pm WARN cleanup Failed to remove some directories [ npm WARN cleanup [ npm WARN cleanup '/opt/iobroker/node_modules/diskusage', npm WARN cleanup [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/diskusage'] { npm WARN cleanup errno: -39, npm WARN cleanup code: 'ENOTEMPTY', npm WARN cleanup syscall: 'rmdir', npm WARN cleanup path: '/opt/iobroker/node_modules/diskusage' npm WARN cleanup } npm WARN cleanup ], npm WARN cleanup [ npm WARN cleanup '/opt/iobroker/node_modules/diskusage', npm WARN cleanup [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/diskusage'] { npm WARN cleanup errno: -39, npm WARN cleanup code: 'ENOTEMPTY', npm WARN cleanup syscall: 'rmdir', npm WARN cleanup path: '/opt/iobroker/node_modules/diskusage' npm WARN cleanup } npm WARN cleanup ] npm WARN cleanup ] npm ERR! code 1 npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller npm ERR! command failed npm ERR! command sh -c node iobroker.js setup first npm ERR! /opt/iobroker/node_modules/axios/dist/node/axios.cjs:1444 npm ERR! const hasJSONContentType = contentType.indexon$'K0qhicaTx+ljson?i*%-1;�( #Onst"i7ObjekvPaiekad�=$etils9*ysE"Kect8dit! ;J npm ERR! ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ npm ERR! npm ERR! SyntaxError: Invalid or unexpected token npm ERR! at internalCompileFunction (node:internal/vm:73:18) npm ERR! at wrapSafe (node:internal/modules/cjs/loader:1274:20) npm ERR! at Module._compile (node:internal/modules/cjs/loader:1320:27) npm ERR! at Module._extensions..js (node:internal/modules/cjs/loader:1414:10) npm ERR! at Module.load (node:internal/modules/cjs/loader:1197:32) npm ERR! at Module._load (node:internal/modules/cjs/loader:1013:12) npm ERR! at Module.require (node:internal/modules/cjs/loader:1225:19) npm ERR! at require (node:internal/modules/helpers:177:18) npm ERR! at Object.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-common/build/lib/common/tools.js:36:33) npm ERR! at Module._compile (node:internal/modules/cjs/loader:1356:14) npm ERR! npm ERR! Node.js v18.19.0``` -
@viper2033 sagte in Web Interface nach Update nicht erreichbar:
npm ERR! /opt/iobroker/node_modules/axios/dist/node/axios.cjs:1444 npm ERR! const hasJSONContentType = contentType.indexon$'K0qhicaTx+ljson?i*%-1;�( #Onst"i7ObjekvPaiekad�=$etils9*ysE"Kect8dit! ;J npm ERR!Hab ich so auch noch nicht gesehen. Keine Ahnung was da kaputt ist.
-
@viper2033 sagte in Web Interface nach Update nicht erreichbar:
Folgende Fehlermeldung:
wo bist du da?
bitte immer alles komplett zeigen.Ein- und Ausgaben
-
Jetzt zeigt er mir folgendes an nach eingabe von
sudo -H -u iobroker npm install iobroker.js-controllercode_text npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/diskusage npm ERR! dest /opt/iobroker/node_modules/.diskusage-SbL2R1mm npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/diskusage' -> '/opt/iobroker/node_modules/.diskusage-SbL2R1mm'``` -
Nochmal:
iob stop iob fix cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller -
@viper2033 sagte in Web Interface nach Update nicht erreichbar:
nach eingabe von
das sehe ich nicht!
bitte Prompt und Eingabebefehl zeigen!!
-
code_text root@CT210:/opt/iobroker# sudo -H -u iobroker npm install iobroker.js-controller npm ERR! code ENOTEMPTY npm ERR! syscall rename npm ERR! path /opt/iobroker/node_modules/diskusage npm ERR! dest /opt/iobroker/node_modules/.diskusage-SbL2R1mm npm ERR! errno -39 npm ERR! ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/diskusage' -> '/opt/iobroker/node_modules/.diskusage-SbL2R1mm' npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-01-18T15_53_31_534Z-debug-0.log -
@viper2033 sagte in Web Interface nach Update nicht erreichbar:
root@CT210
War mir klar...
Auch im LXC wird NICHT als root herumgehampelt. -
@homoran da nutzt dann der ganze fix der Rechte nichts, wenn anschließend der root die Rechte wieder verbiegt.
Noch schlimmer ist nur noch als root den fixer auszuführen. und dazu noch mit sudo für Hyperrechte
-
@homoran
Und wie mache ich jetzt weiter? -
@viper2033 sagte in Web Interface nach Update nicht erreichbar:
Und wie mache ich jetzt weiter?
Fragt der super root...
Da niemand hier nachvollziehen kann was du da wann und wie kaputtgemacht hast:Installier es neu.
-
Gibt es keine andere Lösung außer neu installieren?
-
Wenn du nicht weißt was du wann, warum mit welchen Rechten wo angepackt hast?
Nö.Und die Neuinstallation dann direkt richtig machen...
