VIS Views aus Backup herstellen
-
@stefan0875 sagte in VIS Views aus Backup herstellen:
Leider funktionierte VIS anschließend nicht, so dass ich den Adapter gelöscht und neu installiert habe.
Leider fehlen mir nun meine Views.ist aber "eigentlich" nicht normal!
Was heisst "funktionierte nicht"?@stefan0875 sagte in VIS Views aus Backup herstellen:
wie ich die in die nun frische Installation des VIS Adapters bekomme?
die was?
das sieht aus, als hättest du 3 Projekte gehabt.
In jedem der Projektordner befindet sich dann eine vis-views.json
und die muss wieder genau da hin. -
@homoran Ja, es waren wohl drei, wobei mich nur eines wirklich interessiert.
Was meinst du mit " die muss wieder genau da hin."? Wo ist denn "da"?Ich hole die manuell aus dem tar.gz und kopiere die Dateien dann wo genau hin?
Nach dem zurückspielen des Backups wollte VIS nicht starten, bzw sich nicht mal installieren:
2024-09-06 14:27:59.209 - [33mwarn[39m: host.ioBrokerMasterPi4 startInstance cannot find adapter "vis@1.4.16". Try to install it... 1 attempt 2024-09-06 14:27:59.209 - [32minfo[39m: host.ioBrokerMasterPi4 iobroker install vis@1.4.16 using installedFrom 2024-09-06 14:28:00.978 - [32minfo[39m: host.ioBrokerMasterPi4 iobroker npm-install: NPM version: 10.8.2 2024-09-06 14:28:00.979 - [32minfo[39m: host.ioBrokerMasterPi4 iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2024-09-06 14:28:05.357 - [32minfo[39m: vis.0 (2051) Sets unsupported 2024-09-06 14:28:05.548 - [32minfo[39m: vis.0 (2051) starting. Version 1.4.16 in /opt/iobroker/node_modules/iobroker.vis, node: v20.17.0, js-controller: 6.0.11 2024-09-06 14:28:05.714 - [32minfo[39m: vis.0 (2051) vis license is OK. 2024-09-06 14:28:05.765 - [31merror[39m: vis.0 (2051) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2024-09-06 14:28:05.766 - [31merror[39m: vis.0 (2051) unhandled promise rejection: Not exists 2024-09-06 14:28:05.767 - [31merror[39m: vis.0 (2051) Error: Not exists at ObjectsInRedisClient._readFile (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/objectsInRedisClient.js:850:19) at Immediate.<anonymous> (file:///opt/iobroker/node_modules/@iobroker/db-objects-redis/build/esm/lib/objects/objectsInRedisClient.js:887:59) at process.processImmediate (node:internal/timers:485:21) 2024-09-06 14:28:05.768 - [31merror[39m: vis.0 (2051) Not exists 2024-09-06 14:28:06.271 - [32minfo[39m: vis.0 (2051) terminating 2024-09-06 14:28:06.272 - [33mwarn[39m: vis.0 (2051) Terminated (UNCAUGHT_EXCEPTION): Without reason 2024-09-06 14:28:06.864 - [31merror[39m: host.ioBrokerMasterPi4 iobroker npm-install: npm error code 6npm error path /opt/iobroker/node_modules/iobroker.visnpm error command failednpm error command sh -c node main.js --installnpm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-09-06T12_28_01_102Z-debug-0.log 2024-09-06 14:28:06.864 - [31merror[39m: host.ioBrokerMasterPi4 iobroker npm-install: host.ioBrokerMasterPi4 Cannot install iobroker.vis@1.4.16: 6 2024-09-06 14:28:07.891 - [32minfo[39m: host.ioBrokerMasterPi4 iobroker npm-install: exit 25 -
@stefan0875 sagte in VIS Views aus Backup herstellen:
Wo ist denn "da"?
da, wo die Projektdaten liegen!
müsste in etwa
/opt/iobroker/iobroker-data/vis.0/main/sein. -
@stefan0875 sagte in VIS Views aus Backup herstellen:
2024-09-06 14:28:05.357 - [32minfo[39m: vis.0 (2051) Sets unsupportedwas sind das für sets?
(rhetorisch! )nicht dass da widget sets sind, die du jetzt wieder in den vis-views.json hast
-
@homoran said in VIS Views aus Backup herstellen:
Sets unsupported
"Sets unsupported" meldet fast jeder Adapter, das hat nichts mit vis selbst zu tun.
Was es bedeutet weiß nur der, der die Logausgabe geschrieben hat.Ich installiere iobroker noch einmal neu und versuche es dann noch einmal.
VIS ist leider nicht der einzige Adapter der nicht funktioniert
Sitze schon den ganzen Tag dran und stehe noch immer am Anfang -
@stefan0875 sagte in VIS Views aus Backup herstellen:
VIS ist leider nicht der einzige Adapter der nicht funktioniert
na dann zeig mal die LANGFASSUNG von
iob diagbitte
-
@stefan0875 sagte in VIS Views aus Backup herstellen:
Sitze schon den ganzen Tag dran und stehe noch immer am Anfang
dann würde ich auch empfehlen von Grund auf neu anzufangen.
Aber falls du einen systematischen Fehler gemacht hattest wäre due Info von
iob diagjetzt sehr hilfreuch, um das bei der neuen Installation zu vermeiden -
Ich habe von vorne angefangen und nun läuft vis incl. meiner Views, immerhin. Warum jetzt und eben nicht bleibt ein Rätsel.
Mein zweites Problem ist yahka, aber dazu mache ich besser ein anderes Thema auf
-
@stefan0875 sagte in VIS Views aus Backup herstellen:
Warum jetzt und eben nicht bleibt ein Rätsel.
leider hattest du das
iob diagaus der alten Installation nicht gezeigt, somit wird das ein Geheimnis bleiben. -
Hier vor meiner neuinstallation das diag
Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: ioBrokerMasterPi4 Icon name: computer-container Chassis: container ☐ Virtualization: lxc Operating System: Ubuntu 23.04 Kernel: Linux 5.15.74-1-pve Architecture: x86-64 Firmware Version: GB7 0.08 model name : Intel(R) Celeron(R) J4125 CPU @ 2.00GHz Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 16:45:53 up 20 min, 4 users, load average: 1.59, 2.22, 1.96 CPU threads: 4 *** Time and Time Zones *** Local time: Fri 2024-09-06 16:45:53 UTC Universal time: Fri 2024-09-06 16:45:53 UTC RTC time: n/a Time zone: Etc/UTC (UTC, +0000) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: tty Boot Target: graphical.target *** MEMORY *** total used free shared buff/cache available Mem: 2.1G 531M 702M 114K 912M 1.6G Swap: 2.1G 512K 2.1G Total: 4.3G 532M 2.8G Active iob-Instances: 2 2048 M total memory 507 M used memory 423 M active memory 808 M inactive memory 669 M free memory 0 M buffer memory 870 M swap cache 2048 M total swap 0 M used swap 2047 M free swap *** top - Table Of Processes *** top - 16:45:53 up 20 min, 4 users, load average: 1.59, 2.22, 1.96 Tasks: 36 total, 1 running, 35 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 33.3 sy, 0.0 ni, 0.0 id, 33.3 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 2048.0 total, 668.2 free, 509.1 used, 870.7 buff/cache MiB Swap: 2048.0 total, 2047.5 free, 0.5 used. 1538.9 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System 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. 1 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--106--disk--0 ext4 32G 3.3G 27G 11% / none tmpfs 492K 4.0K 488K 1% /dev tmpfs tmpfs 3.8G 0 3.8G 0% /dev/shm tmpfs tmpfs 1.6G 152K 1.6G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 778M 0 778M 0% /run/user/0 Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--106--disk--0 ext4 rw,relatime,stripe=16 |-/run tmpfs tmpfs rw,nosuid,nodev,size=1591332k,nr_inodes=819200,mode=755,uid=100000,gid=100000,inode64 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k,uid=100000,gid=100000,inode64 | `-/run/user/0 tmpfs tmpfs rw,nosuid,nodev,relatime,size=795664k,nr_inodes=198916,mode=700,uid=100000,gid=100000,inode64 |-/dev none tmpfs rw,relatime,size=492k,mode=755,uid=100000,gid=100000,inode64 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev,uid=100000,gid=100000,inode64 | |-/dev/mqueue mqueue mqueue rw,relatime | |-/dev/.lxc/proc proc proc rw,relatime | |-/dev/.lxc/sys sys sysfs rw,relatime | |-/dev/full udev[/full] devtmpfs rw,nosuid,relatime,size=3944644k,nr_inodes=986161,mode=755,inode64 | |-/dev/null udev[/null] devtmpfs rw,nosuid,relatime,size=3944644k,nr_inodes=986161,mode=755,inode64 | |-/dev/random udev[/random] devtmpfs rw,nosuid,relatime,size=3944644k,nr_inodes=986161,mode=755,inode64 | |-/dev/tty udev[/tty] devtmpfs rw,nosuid,relatime,size=3944644k,nr_inodes=986161,mode=755,inode64 | |-/dev/urandom udev[/urandom] devtmpfs rw,nosuid,relatime,size=3944644k,nr_inodes=986161,mode=755,inode64 | |-/dev/zero udev[/zero] devtmpfs rw,nosuid,relatime,size=3944644k,nr_inodes=986161,mode=755,inode64 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026 | |-/dev/ptmx devpts[/ptmx] devpts rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026 | |-/dev/console devpts[/0] devpts rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026 | |-/dev/tty1 devpts[/1] devpts rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026 | `-/dev/tty2 devpts[/2] devpts rw,nosuid,noexec,relatime,gid=100005,mode=620,ptmxmode=666,max=1026 |-/proc proc proc rw,nosuid,nodev,noexec,relatime | |-/proc/sys proc[/sys] proc ro,relatime | | |-/proc/sys/net proc[/sys/net] proc rw,nosuid,nodev,noexec,relatime | | |-/proc/sys/fs/binfmt_misc binfmt_misc binfmt_misc rw,nosuid,nodev,noexec,relatime | | `-/proc/sys/kernel/random/boot_id none[/.lxc-boot-id] tmpfs ro,nosuid,nodev,noexec,relatime,size=492k,mode=755,uid=100000,gid=100000,inode64 | |-/proc/sysrq-trigger proc[/sysrq-trigger] proc ro,relatime | |-/proc/cpuinfo lxcfs[/proc/cpuinfo] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other | |-/proc/diskstats lxcfs[/proc/diskstats] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other | |-/proc/loadavg lxcfs[/proc/loadavg] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other | |-/proc/meminfo lxcfs[/proc/meminfo] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other | |-/proc/stat lxcfs[/proc/stat] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other | |-/proc/swaps lxcfs[/proc/swaps] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other | `-/proc/uptime lxcfs[/proc/uptime] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other `-/sys sysfs sysfs ro,nosuid,nodev,noexec,relatime |-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime |-/sys/devices/virtual/net sysfs[/devices/virtual/net] sysfs rw,nosuid,nodev,noexec,relatime |-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime |-/sys/firmware/efi/efivars efivarfs efivarfs rw,nosuid,nodev,noexec,relatime |-/sys/fs/cgroup none cgroup2 rw,nosuid,nodev,noexec,relatime `-/sys/devices/system/cpu/online lxcfs[/sys/devices/system/cpu/online] fuse.lxcfs rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other Files in neuralgic directories: /var: 538M /var/ 288M /var/cache 283M /var/cache/apt 233M /var/lib 195M /var/cache/apt/archives Archived and active journals take up 16.0M in the file system. /opt/iobroker/backups: 6.1M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 229M /opt/iobroker/iobroker-data/ 201M /opt/iobroker/iobroker-data/files 52M /opt/iobroker/iobroker-data/files/javascript.admin 34M /opt/iobroker/iobroker-data/files/javascript.admin/static 33M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 25M /opt/iobroker/iobroker-data/objects.jsonl 19M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.a5972028.js.map 19M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js.map 8.4M /opt/iobroker/iobroker-data/files/backitup.admin/static/js/main.70cad8ba.js 8.2M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.2975a411.js USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' *** NodeJS-Installation *** /usr/bin/nodejs v20.17.0 /usr/bin/node v20.17.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 nodejs: Installed: 20.17.0-1nodesource1 Candidate: 20.17.0-1nodesource1 Version table: *** 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 18.13.0+dfsg1-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu lunar/universe amd64 Packages Temp directories causing npm8 problem: 1 Some problems detected, please run iob fix Errors in npm tree: *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 6.0.11 admin: 6.3.7 javascript: 7.0.3 nodejs modules from github: 1 +-- iobroker.gree_aircon@0.0.1 (git+ssh://git@github.com/weltmeyer/ioBroker.gree_aircon.git#f951ced87269e260475c8a1bc92c48489e0cd421) Adapter State system.adapter.admin.0 : admin : ioBrokerMasterPi4 - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.alexa2.0 : alexa2 : ioBrokerMasterPi4 - disabled + system.adapter.backitup.0 : backitup : ioBrokerMasterPi4 - enabled system.adapter.backitup.1 : backitup : ioBrokerSlave - enabled system.adapter.cloud.0 : cloud : ioBrokerMasterPi4 - disabled system.adapter.discovery.0 : discovery : ioBrokerMasterPi4 - disabled system.adapter.fakeroku.0 : fakeroku : ioBrokerMasterPi4 - disabled system.adapter.flot.0 : flot : ioBrokerMasterPi4 - disabled system.adapter.geofency.0 : geofency : ioBrokerMasterPi4 - disabled, port: 7789, bind: 0.0.0.0 system.adapter.geofency.1 : geofency : ioBrokerMasterPi4 - disabled, port: 7789, bind: 0.0.0.0 system.adapter.gree_aircon.0 : gree_aircon : ioBrokerMasterPi4 - disabled system.adapter.harmony.0 : harmony : ioBrokerMasterPi4 - disabled system.adapter.history.0 : history : ioBrokerMasterPi4 - disabled system.adapter.hm-rega.0 : hm-rega : ioBrokerMasterPi4 - disabled system.adapter.hm-rpc.0 : hm-rpc : ioBrokerMasterPi4 - disabled, port: 0 system.adapter.hm-rpc.1 : hm-rpc : ioBrokerMasterPi4 - disabled, port: 0 system.adapter.hue.0 : hue : ioBrokerMasterPi4 - disabled, port: 443 system.adapter.influxdb.0 : influxdb : ioBrokerMasterPi4 - disabled, port: 8086 system.adapter.iot.0 : iot : ioBrokerMasterPi4 - disabled system.adapter.javascript.0 : javascript : ioBrokerMasterPi4 - disabled system.adapter.milight.0 : milight : ioBrokerMasterPi4 - disabled, port: 8899 system.adapter.modbus.0 : modbus : ioBrokerMasterPi4 - disabled system.adapter.mqtt.0 : mqtt : ioBrokerMasterPi4 - disabled, port: 1883, bind: 0.0.0.0 system.adapter.pvforecast.0 : pvforecast : ioBrokerMasterPi4 - disabled system.adapter.rpi2.0 : rpi2 : ioBrokerSlave - disabled system.adapter.sayit.0 : sayit : ioBrokerMasterPi4 - disabled, port: 0 system.adapter.smartmeter.0 : smartmeter : ioBrokerSlave - disabled system.adapter.sonos.0 : sonos : ioBrokerMasterPi4 - disabled system.adapter.sql.0 : sql : ioBrokerSlave - disabled, port: 3307 system.adapter.telegram.0 : telegram : ioBrokerMasterPi4 - disabled, port: 8443, bind: 0.0.0.0 system.adapter.telegram.1 : telegram : ioBrokerMasterPi4 - disabled, port: 8443, bind: 0.0.0.0 system.adapter.terminal.0 : terminal : ioBrokerMasterPi4 - disabled, port: 8088, bind: 0.0.0.0, run as: admin system.adapter.tesla-motors.0 : tesla-motors : ioBrokerMasterPi4 - disabled system.adapter.tradfri.0 : tradfri : ioBrokerMasterPi4 - disabled system.adapter.vis.0 : vis : ioBrokerMasterPi4 - disabled system.adapter.web.0 : web : ioBrokerMasterPi4 - disabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.web.1 : web : ioBrokerMasterPi4 - disabled, port: 8083, bind: 0.0.0.0, run as: admin system.adapter.yahka.0 : yahka : ioBrokerMasterPi4 - disabled + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : ioBrokerMasterPi4 - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): beta Upgrade policy: none Installed ioBroker-Instances Used repository: beta Adapter "admin" : 7.1.0 , installed 6.3.7 [Updatable] Adapter "alexa2" : 3.26.5 , installed 3.23.2 [Updatable] Adapter "backitup" : 3.0.22 , installed 2.4.12 [Updatable] Adapter "cloud" : 5.0.1 , installed 4.3.1 [Updatable] Adapter "discovery" : 5.0.0 , installed 3.1.0 [Updatable] Adapter "fakeroku" : 0.3.0 , installed 0.2.1 [Updatable] Adapter "flot" : 1.12.0 , installed 1.12.0 Adapter "geofency" : 1.2.4 , installed 1.2.4 Adapter "harmony" : 1.5.0 , installed 1.3.0 [Updatable] Adapter "history" : 3.0.1 , installed 2.2.4 [Updatable] Adapter "hm-rega" : 5.1.0 , installed 3.0.44 [Updatable] Adapter "hm-rpc" : 2.0.2 , installed 1.15.16 [Updatable] Adapter "hue" : 3.12.0 , installed 3.10.0 [Updatable] Adapter "influxdb" : 4.0.2 , installed 3.2.0 [Updatable] Adapter "iot" : 3.4.0 , installed 1.14.5 [Updatable] Adapter "javascript" : 8.8.3 , installed 7.0.3 [Updatable] Controller "js-controller": 6.0.11 , installed 6.0.11 Adapter "milight" : 0.4.0 , installed 0.4.0 Adapter "modbus" : 6.3.2 , installed 5.0.11 [Updatable] Adapter "mqtt" : 6.1.2 , installed 4.0.7 [Updatable] Adapter "pvforecast" : 3.0.0 , installed 2.6.0 [Updatable] Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.3.4 [Updatable] Adapter "sonos" : 3.0.0 , installed 2.3.0 [Updatable] Adapter "telegram" : 3.9.0 , installed 1.15.6 [Updatable] Adapter "terminal" : 1.0.0 , installed 1.0.0 Adapter "tesla-motors" : 1.4.5 , installed 1.4.5 Adapter "tradfri" : 3.1.3 , installed 3.1.3 Adapter "web" : 6.3.0 , installed 5.5.2 [Updatable] Adapter "ws" : 2.6.2 , installed 2.3.6 [Updatable] Adapter "yahka" : 1.0.8 , installed 1.0.3 [Updatable] Objects and States Please stand by - This may take a while Objects: 12119 States: 9725 *** OS-Repositories and Updates *** Hit:1 http://archive.ubuntu.com/ubuntu lunar InRelease Hit:2 http://archive.ubuntu.com/ubuntu lunar-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu lunar-security InRelease Hit:4 https://deb.nodesource.com/node_20.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:6010 0.0.0.0:* LISTEN 0 544736689 3540/sshd: root@pts tcp 0 0 127.0.0.1:6011 0.0.0.0:* LISTEN 0 544785255 12193/sshd: root@pt tcp 0 0 127.0.0.54:53 0.0.0.0:* LISTEN 996 544733193 3123/systemd-resolv tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 544722487 293/master tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 544768790 1/systemd tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 1000 544782936 11847/iobroker.js-c tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 1000 544782219 11847/iobroker.js-c tcp 0 0 127.0.0.53:53 0.0.0.0:* LISTEN 996 544733191 3123/systemd-resolv tcp6 0 0 ::1:25 :::* LISTEN 0 544722488 293/master tcp6 0 0 ::1:6010 :::* LISTEN 0 544736688 3540/sshd: root@pts tcp6 0 0 ::1:6011 :::* LISTEN 0 544785254 12193/sshd: root@pt tcp6 0 0 :::22 :::* LISTEN 0 544732802 1/systemd tcp6 0 0 :::111 :::* LISTEN 0 544768792 1/systemd udp 0 0 127.0.0.54:53 0.0.0.0:* 996 544733192 3123/systemd-resolv udp 0 0 127.0.0.53:53 0.0.0.0:* 996 544733190 3123/systemd-resolv udp 0 0 0.0.0.0:111 0.0.0.0:* 0 544768791 1/systemd udp6 0 0 :::111 :::* 0 544768793 1/systemd *** Log File - Last 25 Lines *** 2024-09-06 16:43:16.177 - warn: host.ioBrokerMasterPi4 startInstance cannot find adapter "vis@1.4.16". Try to install it... 3 attempt 2024-09-06 16:43:16.178 - info: host.ioBrokerMasterPi4 iobroker install vis@1.4.16 using installedVersion 2024-09-06 16:43:17.942 - info: host.ioBrokerMasterPi4 iobroker npm-install: NPM version: 10.8.2 2024-09-06 16:43:17.943 - info: host.ioBrokerMasterPi4 iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2024-09-06 16:43:20.771 - info: host.ioBrokerMasterPi4 iobroker npm-install: Try to solve ENOTEMPTY error automatically 2024-09-06 16:43:20.771 - error: host.ioBrokerMasterPi4 iobroker npm-install: Could not handle ENOTEMPTY, because no deletable files were found 2024-09-06 16:43:20.771 - error: host.ioBrokerMasterPi4 iobroker npm-install: npm error code ENOTEMPTYnpm error syscall renamenpm error path /opt/iobroker/node_modules/mdnsnpm error dest /opt/iobroker/node_modules/.mdns-FIdgAav9npm error errno -39npm error ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/mdns' -> '/opt/iobroker/node_modules/.mdns-FIdgAav9'npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-09-06T16_43_18_067Z-debug-0.loghost.ioBrokerMasterPi4 Cannot install iobroker.vis@1.4.16: 217 2024-09-06 16:43:21.801 - info: host.ioBrokerMasterPi4 iobroker npm-install: exit 25 2024-09-06 16:43:22.803 - warn: host.ioBrokerMasterPi4 startInstance cannot find adapter "sayit@1.12.6". Try to install it... 4 attempt 2024-09-06 16:43:22.804 - info: host.ioBrokerMasterPi4 iobroker install sayit@1.12.6 using installedVersion 2024-09-06 16:43:24.551 - info: host.ioBrokerMasterPi4 iobroker npm-install: NPM version: 10.8.2 2024-09-06 16:43:24.552 - info: host.ioBrokerMasterPi4 iobroker npm-install: Installing iobroker.sayit@1.12.6... (System call) 2024-09-06 16:43:28.101 - info: host.ioBrokerMasterPi4 iobroker npm-install: Try to solve ENOTEMPTY error automatically 2024-09-06 16:43:28.102 - error: host.ioBrokerMasterPi4 iobroker npm-install: Could not handle ENOTEMPTY, because no deletable files were foundnpm error code ENOTEMPTYnpm error syscall renamenpm error path /opt/iobroker/node_modules/mdnsnpm error dest /opt/iobroker/node_modules/.mdns-FIdgAav9npm error errno -39npm error ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/mdns' -> '/opt/iobroker/node_modules/.mdns-FIdgAav9'npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-09-06T16_43_24_674Z-debug-0.log 2024-09-06 16:43:28.103 - error: host.ioBrokerMasterPi4 iobroker npm-install: host.ioBrokerMasterPi4 Cannot install iobroker.sayit@1.12.6: 217 2024-09-06 16:43:29.130 - info: host.ioBrokerMasterPi4 iobroker npm-install: exit 25 2024-09-06 16:43:30.132 - warn: host.ioBrokerMasterPi4 startInstance cannot find adapter "vis@1.4.16". Try to install it... 4 attempt 2024-09-06 16:43:30.133 - info: host.ioBrokerMasterPi4 iobroker install vis@1.4.16 using installedVersion 2024-09-06 16:43:31.848 - info: host.ioBrokerMasterPi4 iobroker npm-install: NPM version: 10.8.2 2024-09-06 16:43:31.849 - info: host.ioBrokerMasterPi4 iobroker npm-install: Installing iobroker.vis@1.4.16... (System call) 2024-09-06 16:43:34.873 - info: host.ioBrokerMasterPi4 iobroker npm-install: Try to solve ENOTEMPTY error automatically 2024-09-06 16:43:34.874 - error: host.ioBrokerMasterPi4 iobroker npm-install: Could not handle ENOTEMPTY, because no deletable files were foundnpm error code ENOTEMPTYnpm error syscall renamenpm error path /opt/iobroker/node_modules/mdnsnpm error dest /opt/iobroker/node_modules/.mdns-FIdgAav9npm error errno -39npm error ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/mdns' -> '/opt/iobroker/node_modules/.mdns-FIdgAav9'npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-09-06T16_43_31_978Z-debug-0.loghost.ioBrokerMasterPi4 Cannot install iobroker.vis@1.4.16: 217 2024-09-06 16:43:35.896 - info: host.ioBrokerMasterPi4 iobroker npm-install: exit 25 2024-09-06 16:43:36.897 - error: host.ioBrokerMasterPi4 Cannot download and install adapter "sayit@1.12.6". To retry it disable/enable the adapter or restart host. Also check the error messages in the log! 2024-09-06 16:43:37.399 - error: host.ioBrokerMasterPi4 Cannot download and install adapter "vis@1.4.16". To retry it disable/enable the adapter or restart host. Also check the error messages in the log!======================= SUMMARY ======================= v.2024-05-22 Static hostname: ioBrokerMasterPi4 Icon name: computer-container Chassis: container ☐ Virtualization: lxc Operating System: Ubuntu 23.04 Kernel: Linux 5.15.74-1-pve Architecture: x86-64 Firmware Version: GB7 0.08 Installation: lxc Kernel: x86_64 Userland: 64 bit Timezone: Etc/UTC (UTC, +0000) User-ID: 0 Display-Server: false Boot Target: graphical.target Pending OS-Updates: 0 Pending iob updates: 23 Nodejs-Installation: /usr/bin/nodejs v20.17.0 /usr/bin/node v20.17.0 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.29.3 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 2.1G 542M 688M 118K 916M 1.6G Swap: 2.1G 507K 2.1G Total: 4.3G 542M 2.8G Active iob-Instances: 2 Upgrade policy: none ioBroker Core: js-controller 6.0.11 admin 6.3.7 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: system.adapter.admin.0 : admin : ioBrokerMasterPi4 - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.web.0 : web : ioBrokerMasterPi4 - disabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.web.1 : web : ioBrokerMasterPi4 - disabled, port: 8083, bind: 0.0.0.0, run as: admin Objects: 12119 States: 9725 Size of iob-Database: 25M /opt/iobroker/iobroker-data/objects.jsonl 2.7M /opt/iobroker/iobroker-data/states.jsonl ********************************************************************* Some problems detected, please run iob fix and try to have them fixed ********************************************************************* =================== END OF SUMMARY ==================== -
@stefan0875 sagte in VIS Views aus Backup herstellen:
Hier vor meiner neuinstallation das diag
danke, aber das zeigt den Fehler der alten Installation natürlich nicht.
@stefan0875 sagte in VIS Views aus Backup herstellen:
Virtualization: lxc
ach ein container!
@stefan0875 sagte in VIS Views aus Backup herstellen:
Mem: 2.1G
warum nur 2GB??
Das ist zu wenig!und keucht schon
@stefan0875 sagte in VIS Views aus Backup herstellen:
load average: 1.59, 2.22, 1.96
@stefan0875 sagte in VIS Views aus Backup herstellen:
Time zone: Etc/UTC (UTC, +0000)
Da sollte schon deine Zeitzone eingestellt sein.
@stefan0875 sagte in VIS Views aus Backup herstellen:
NTP service: inactive
warum?
Du solltest auch die Uhr immer richtig stellen lassen.@stefan0875 sagte in VIS Views aus Backup herstellen:
User that called 'iob diag':
rootniemals als root arbeiten. Das verbiegt die Rechte
leg dir einen user an, log dich damit ein, und fixe die Rechte mitiob diag@stefan0875 sagte in VIS Views aus Backup herstellen:
Active iob-Instances: 2
und damit schon ein load von 2??
@stefan0875 sagte in VIS Views aus Backup herstellen:
run-rpc_pipefs.mount loaded failed failed RPC Pipe File System
was immer das ist, es läuft nicht.
@stefan0875 sagte in VIS Views aus Backup herstellen:
Adapter State
system.adapter.admin.0 : admin : ioBrokerMasterPi4warum läuft der admin nicht?
@stefan0875 sagte in VIS Views aus Backup herstellen:
ioBrokerSlave
auch noch ein Multihost?
@stefan0875 sagte in VIS Views aus Backup herstellen:
Used repository: beta
aha! Eine Installation für Betatests!
da sollten dann aber auch alle Instanzen auf dem neuesten Stand sein.BetaTests von älteren Versionen bringen nichts.@stefan0875 sagte in VIS Views aus Backup herstellen:
Operating System: Ubuntu 23.04
wird das noch gepflegt?
warum keine LTS Version? -
Hallo Stefan,
ich habe auch ein Problem und muss entweder ein altes Backup einspielen und danach eventuell das neueste von vor 3 Tagen.
Wenn das nicht funktioniert würde ich auch den IOBroker löschen.
kannst du kurz schreiben, wie du das gemacht hast. Ich muss auf alle Fälle meine Skripte (8 Stück) behalten.
Die sichere ich erst mal auf alle Fälle woanders hin.
Gruss karl-Heinz
