Backitup findet Dateien nicht auf NAS-Stick wird gesucht
-
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@olli63 hmmm!
was ich nicht verstehe
du hast NAS/COPY eingestellt und schreibst
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
der Server hat damit nichts zu tun . Der ist im Netz (MyCloud)
Das ist das NAS? oder ist das im WWW?
vielleicht falsch beschrieben. Das Backup erfolgt auf NAS (MyCloud) und meine vermutung war das Backitup die Sicherung auf dem USB Systemstick sucht. Wenn ich jetzt ein wiederherstellung anwähle stht im Protokoll: Backuplist cannot be found
@olli63 said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@olli63 hmmm!
was ich nicht verstehe
du hast NAS/COPY eingestellt und schreibst
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
der Server hat damit nichts zu tun . Der ist im Netz (MyCloud)
Das ist das NAS? oder ist das im WWW?
vielleicht falsch beschrieben. Das Backup erfolgt auf NAS (MyCloud) und meine vermutung war das Backitup die Sicherung auf dem USB Systemstick sucht. Wenn ich jetzt ein wiederherstellung anwähle stht im Protokoll: Backuplist cannot be found
pi@phoscon:~ $ mount | sort cgroup2 on /sys/fs/cgroup/unified type cgroup2 (rw,nosuid,nodev,noexec,relatime,nsdelegate) cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio) cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct) cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset) cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices) cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer) cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio) cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event) cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids) cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,name=systemd) configfs on /sys/kernel/config type configfs (rw,relatime) debugfs on /sys/kernel/debug type debugfs (rw,relatime) devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000) /dev/sda1 on /boot type vfat (rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro) /dev/sda2 on / type ext4 (rw,noatime) devtmpfs on /dev type devtmpfs (rw,relatime,size=793172k,nr_inodes=88619,mode=755) fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime) gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000) mqueue on /dev/mqueue type mqueue (rw,relatime) none on /sys/fs/bpf type bpf (rw,nosuid,nodev,noexec,relatime,mode=700) proc on /proc type proc (rw,relatime) securityfs on /sys/kernel/security type securityfs (rw,nosuid,nodev,noexec,relatime) sunrpc on /run/rpc_pipefs type rpc_pipefs (rw,relatime) sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime) systemd-1 on /proc/sys/fs/binfmt_misc type autofs (rw,relatime,fd=27,pgrp=1,timeout=0,minproto=5,maxproto=5,direct) tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev) tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k) tmpfs on /run type tmpfs (rw,nosuid,nodev,mode=755) tmpfs on /run/user/1000 type tmpfs (rw,nosuid,nodev,relatime,size=191604k,mode=700,uid=1000,gid=1000) tmpfs on /sys/fs/cgroup type tmpfs (ro,nosuid,nodev,noexec,mode=755)MOD-EDIT: Code in code-tags gesetzt!
-
@thomas-braun sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
Stell mal den SMB-Dialekt auf 3.1.1 um. Oder was auch immer dein NAS spricht, aber mit v1 sollte da eigentlich nichts mehr laufen.
hat es aber bisher.
zumindest in eine Richtungaber vielleicht mag backitup kein 1.0 mehr annehmen???
@Olli63
kannst du in deinem NAS die smb Version auch hochschrauben?@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@thomas-braun sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
Stell mal den SMB-Dialekt auf 3.1.1 um. Oder was auch immer dein NAS spricht, aber mit v1 sollte da eigentlich nichts mehr laufen.
hat es aber bisher.
zumindest in eine Richtungaber vielleicht mag backitup kein 1.0 mehr annehmen???
@Olli63
kannst du in deinem NAS die smb Version auch hochschrauben?steht jetzt schon auf 3.1.1
-
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@thomas-braun sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
Stell mal den SMB-Dialekt auf 3.1.1 um. Oder was auch immer dein NAS spricht, aber mit v1 sollte da eigentlich nichts mehr laufen.
hat es aber bisher.
zumindest in eine Richtungaber vielleicht mag backitup kein 1.0 mehr annehmen???
@Olli63
kannst du in deinem NAS die smb Version auch hochschrauben?steht jetzt schon auf 3.1.1
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
steht jetzt schon auf 3.1.1
wo?
in deinem NAS oder nur hier in Backitup?kein Support per PN! - Fragen im Forum stellen -
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton oben rechts. Danke!
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash - -
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
steht jetzt schon auf 3.1.1
wo?
in deinem NAS oder nur hier in Backitup?My Cloud OS 5 unterstützt SMB1, SMBv2, SMB3 und NTLMv1, NTLMv2.
-
My Cloud OS 5 unterstützt SMB1, SMBv2, SMB3 und NTLMv1, NTLMv2.
@thomas-braun sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
My Cloud OS 5 unterstützt SMB1, SMBv2, SMB3 und NTLMv1, NTLMv2.
jetzt müsste @Olli63 uns nur noch sagen auf was es bei ihm steht.
Wahrscheinlich smb v1 -
@thomas-braun sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
My Cloud OS 5 unterstützt SMB1, SMBv2, SMB3 und NTLMv1, NTLMv2.
jetzt müsste @Olli63 uns nur noch sagen auf was es bei ihm steht.
Wahrscheinlich smb v1@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@thomas-braun sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
My Cloud OS 5 unterstützt SMB1, SMBv2, SMB3 und NTLMv1, NTLMv2.
jetzt müsste @Olli63 uns nur noch sagen auf was es bei ihm steht.
Wahrscheinlich smb v1
steht jetzt auf 3.0
aber kann das überhaupt das Problem sein? die sicherung funktioniert ja auf dem NAS:
-
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@thomas-braun sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
My Cloud OS 5 unterstützt SMB1, SMBv2, SMB3 und NTLMv1, NTLMv2.
jetzt müsste @Olli63 uns nur noch sagen auf was es bei ihm steht.
Wahrscheinlich smb v1
steht jetzt auf 3.0
aber kann das überhaupt das Problem sein? die sicherung funktioniert ja auf dem NAS:
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
steht jetzt auf 3.0
Und warum nicht 3.1.1?
-
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@thomas-braun sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
My Cloud OS 5 unterstützt SMB1, SMBv2, SMB3 und NTLMv1, NTLMv2.
jetzt müsste @Olli63 uns nur noch sagen auf was es bei ihm steht.
Wahrscheinlich smb v1
steht jetzt auf 3.0
aber kann das überhaupt das Problem sein? die sicherung funktioniert ja auf dem NAS:
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
aber kann das überhaupt das Problem sein?
keine Ahnung, wäre zu testen.
-
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
aber kann das überhaupt das Problem sein?
keine Ahnung, wäre zu testen.
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
aber kann das überhaupt das Problem sein?
keine Ahnung, wäre zu testen.
mit allen SMB versionen das selbe Ergebnis
Ich dnke ihr wisst auch nicht woran es liegt und wir stochern hier mit einem Blinden( ich)
im Dunkeln -
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
aber kann das überhaupt das Problem sein?
keine Ahnung, wäre zu testen.
mit allen SMB versionen das selbe Ergebnis
Ich dnke ihr wisst auch nicht woran es liegt und wir stochern hier mit einem Blinden( ich)
im Dunkelncat /etc/fstab -
cat /etc/fstab@thomas-braun said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
cat /etc/fstabpi@phoscon:~ $ cat /etc/fstab proc /proc proc defaults 0 0 PARTUUID=ae48e9dc-01 /boot vfat defaults 0 2 PARTUUID=ae48e9dc-02 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, no line here # use dphys-swapfile swap[on|off] for thatMOD-EDIT: Code in code-tags gesetzt!
-
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
aber kann das überhaupt das Problem sein?
keine Ahnung, wäre zu testen.
mit allen SMB versionen das selbe Ergebnis
Ich dnke ihr wisst auch nicht woran es liegt und wir stochern hier mit einem Blinden( ich)
im Dunkeln@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
Ich dnke ihr wisst auch nicht woran es liegt
deswegen braucht es Daten, Daten, Daten.
das ist das erste mal, dass es nur als Einbahnstraße läuft.
sonst müssen wir mal den Entwickler @simatec fragen -
@thomas-braun said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
cat /etc/fstabpi@phoscon:~ $ cat /etc/fstab proc /proc proc defaults 0 0 PARTUUID=ae48e9dc-01 /boot vfat defaults 0 2 PARTUUID=ae48e9dc-02 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, no line here # use dphys-swapfile swap[on|off] for thatMOD-EDIT: Code in code-tags gesetzt!
ls -lAh /opt/iobroker/backupsvielleicht auch mal per
iob diagschauen was da so eingestellt ist.
-
@thomas-braun said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
cat /etc/fstabpi@phoscon:~ $ cat /etc/fstab proc /proc proc defaults 0 0 PARTUUID=ae48e9dc-01 /boot vfat defaults 0 2 PARTUUID=ae48e9dc-02 / ext4 defaults,noatime 0 1 # a swapfile is not a swap partition, no line here # use dphys-swapfile swap[on|off] for thatMOD-EDIT: Code in code-tags gesetzt!
Starte den Adapter mit aktiviertem Debug mal neu.
Schaut dann ungefähr so aus:2023-03-30 20:18:11.328 - info: host.chet stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-03-30 20:18:11.338 - info: backitup.0 (410075) Got terminate signal TERMINATE_YOURSELF 2023-03-30 20:18:11.342 - info: backitup.0 (410075) cleaned everything up... 2023-03-30 20:18:11.344 - info: backitup.0 (410075) terminating 2023-03-30 20:18:11.346 - info: backitup.0 (410075) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-03-30 20:18:11.402 - info: host.chet stopInstance system.adapter.backitup.0 send kill signal 2023-03-30 20:18:11.849 - info: backitup.0 (410075) terminating 2023-03-30 20:18:11.965 - info: host.chet instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-30 20:18:14.573 - info: host.chet instance system.adapter.backitup.0 started with pid 412036 2023-03-30 20:18:16.128 - debug: backitup.0 (412036) Redis Objects: Use Redis connection: 0.0.0.0:9001 2023-03-30 20:18:16.228 - debug: backitup.0 (412036) Objects client ready ... initialize now 2023-03-30 20:18:16.232 - debug: backitup.0 (412036) Objects create System PubSub Client 2023-03-30 20:18:16.233 - debug: backitup.0 (412036) Objects create User PubSub Client 2023-03-30 20:18:16.321 - debug: backitup.0 (412036) Objects client initialize lua scripts 2023-03-30 20:18:16.335 - debug: backitup.0 (412036) Objects connected to redis: 0.0.0.0:9001 2023-03-30 20:18:16.388 - debug: backitup.0 (412036) Redis States: Use Redis connection: 0.0.0.0:9000 2023-03-30 20:18:16.418 - debug: backitup.0 (412036) States create System PubSub Client 2023-03-30 20:18:16.420 - debug: backitup.0 (412036) States create User PubSub Client 2023-03-30 20:18:16.511 - debug: backitup.0 (412036) States connected to redis: 0.0.0.0:9000 2023-03-30 20:18:16.709 - debug: backitup.0 (412036) Plugin sentry Do not initialize Plugin (enabled=false) 2023-03-30 20:18:16.776 - debug: backitup.0 (412036) Plugin sentry destroyed because not initialized correctly 2023-03-30 20:18:17.202 - info: backitup.0 (412036) starting. Version 2.6.15 (non-npm: simatec/ioBroker.backitup) in /opt/iobroker/node_modules/iobroker.backitup, node: v19.8.1, js-controller: 5.0.1-alpha.0-20230330-e0b409fe 2023-03-30 20:18:17.318 - debug: backitup.0 (412036) Backitup has recognized a linux system 2023-03-30 20:18:17.358 - info: backitup.0 (412036) [iobroker] backup was activated at 03:42 every 1 day(s) 2023-03-30 20:18:17.467 - debug: backitup.0 (412036) noserverino option: true 2023-03-30 20:18:17.468 - debug: backitup.0 (412036) cifs-mount command: "sudo mount -t cifs -o username=iobroker,password=****,noserverino,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=3.1.1 //192.168.178.1/fritz.nas/Hitachi-HTS545012B9SA00-01/iobbackups/chet /opt/iobroker/backups" 2023-03-30 20:18:18.658 - debug: backitup.0 (412036) first mount attempt with smb option failed. try next mount attempt without smb option ... 2023-03-30 20:18:18.659 - debug: backitup.0 (412036) cifs-mount command: "sudo mount -t cifs -o username=iobroker,password=****,noserverino,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.178.1/fritz.nas/Hitachi-HTS545012B9SA00-01/iobbackups/chet /opt/iobroker/backups" 2023-03-30 20:18:18.743 - debug: backitup.0 (412036) device is busy... wait 2 Minutes!! 2023-03-30 20:18:18.770 - error: backitup.0 (412036) Error: Command failed: sudo mount -t cifs -o username=iobroker,password=****,noserverino,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.178.1/fritz.nas/Hitachi-HTS545012B9SA00-01/iobbackups/chet /opt/iobroker/backups mount error(16): Device or resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 2023-03-30 20:18:20.829 - debug: backitup.0 (412036) detect backup file 1 from NAS: iobroker_2023_03_21-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.833 - debug: backitup.0 (412036) detect backup file 2 from NAS: iobroker_2023_03_22-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.834 - debug: backitup.0 (412036) detect backup file 3 from NAS: iobroker_2023_03_23-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.834 - debug: backitup.0 (412036) detect backup file 4 from NAS: iobroker_2023_03_24-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.835 - debug: backitup.0 (412036) detect backup file 5 from NAS: iobroker_2023_03_25-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.835 - debug: backitup.0 (412036) detect backup file 6 from NAS: iobroker_2023_03_26-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.836 - debug: backitup.0 (412036) detect backup file 7 from NAS: iobroker_2023_03_27-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.837 - debug: backitup.0 (412036) detect backup file 8 from NAS: iobroker_2023_03_28-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.837 - debug: backitup.0 (412036) detect backup file 9 from NAS: iobroker_2023_03_29-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.838 - debug: backitup.0 (412036) detect backup file 10 from NAS: iobroker_2023_03_30-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.839 - debug: backitup.0 (412036) detect backup file 11 from NAS: iobroker_2023_03_30-19_37_47_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.839 - debug: backitup.0 (412036) detect backup file 12 from NAS: iobroker_2023_03_30-19_40_44_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.839 - debug: backitup.0 (412036) detect backup file 13 from NAS: iobroker_2023_03_30-19_49_33_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.265 - debug: backitup.0 (412036) detect backup file 1 from googledrive: iobroker_2023_03_30-19_49_33_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.266 - debug: backitup.0 (412036) detect backup file 2 from googledrive: iobroker_2023_03_30-19_40_44_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.267 - debug: backitup.0 (412036) detect backup file 3 from googledrive: iobroker_2023_03_30-19_37_47_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.267 - debug: backitup.0 (412036) detect backup file 4 from googledrive: iobroker_2023_03_30-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.267 - debug: backitup.0 (412036) detect backup file 5 from googledrive: iobroker_2023_03_29-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.267 - debug: backitup.0 (412036) detect backup file 6 from googledrive: iobroker_2023_03_28-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.268 - debug: backitup.0 (412036) detect backup file 7 from googledrive: iobroker_2023_03_27-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.268 - debug: backitup.0 (412036) detect backup file 8 from googledrive: iobroker_2023_03_26-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.268 - debug: backitup.0 (412036) detect backup file 9 from googledrive: iobroker_2023_03_25-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.268 - debug: backitup.0 (412036) detect backup file 10 from googledrive: iobroker_2023_03_24-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.269 - debug: backitup.0 (412036) detect backup file 11 from googledrive: iobroker_2023_03_23-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.269 - debug: backitup.0 (412036) detect backup file 12 from googledrive: iobroker_2023_03_22-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.269 - debug: backitup.0 (412036) detect backup file 13 from googledrive: iobroker_2023_03_21-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.271 - debug: backitup.0 (412036) detect last backup file: iobroker_2023_03_30-19_49_33_chet_backupiobroker.tar.gz 2023-03-30 20:18:27.363 - debug: backitup.0 (412036) mount activ... umount in 2 Seconds!! 2023-03-30 20:18:29.418 - debug: backitup.0 (412036) umount successfully completed 2023-03-30 20:20:18.783 - error: backitup.0 (412036) umount: /opt/iobroker/backups: not mounted. -
Starte den Adapter mit aktiviertem Debug mal neu.
Schaut dann ungefähr so aus:2023-03-30 20:18:11.328 - info: host.chet stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-03-30 20:18:11.338 - info: backitup.0 (410075) Got terminate signal TERMINATE_YOURSELF 2023-03-30 20:18:11.342 - info: backitup.0 (410075) cleaned everything up... 2023-03-30 20:18:11.344 - info: backitup.0 (410075) terminating 2023-03-30 20:18:11.346 - info: backitup.0 (410075) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-03-30 20:18:11.402 - info: host.chet stopInstance system.adapter.backitup.0 send kill signal 2023-03-30 20:18:11.849 - info: backitup.0 (410075) terminating 2023-03-30 20:18:11.965 - info: host.chet instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-30 20:18:14.573 - info: host.chet instance system.adapter.backitup.0 started with pid 412036 2023-03-30 20:18:16.128 - debug: backitup.0 (412036) Redis Objects: Use Redis connection: 0.0.0.0:9001 2023-03-30 20:18:16.228 - debug: backitup.0 (412036) Objects client ready ... initialize now 2023-03-30 20:18:16.232 - debug: backitup.0 (412036) Objects create System PubSub Client 2023-03-30 20:18:16.233 - debug: backitup.0 (412036) Objects create User PubSub Client 2023-03-30 20:18:16.321 - debug: backitup.0 (412036) Objects client initialize lua scripts 2023-03-30 20:18:16.335 - debug: backitup.0 (412036) Objects connected to redis: 0.0.0.0:9001 2023-03-30 20:18:16.388 - debug: backitup.0 (412036) Redis States: Use Redis connection: 0.0.0.0:9000 2023-03-30 20:18:16.418 - debug: backitup.0 (412036) States create System PubSub Client 2023-03-30 20:18:16.420 - debug: backitup.0 (412036) States create User PubSub Client 2023-03-30 20:18:16.511 - debug: backitup.0 (412036) States connected to redis: 0.0.0.0:9000 2023-03-30 20:18:16.709 - debug: backitup.0 (412036) Plugin sentry Do not initialize Plugin (enabled=false) 2023-03-30 20:18:16.776 - debug: backitup.0 (412036) Plugin sentry destroyed because not initialized correctly 2023-03-30 20:18:17.202 - info: backitup.0 (412036) starting. Version 2.6.15 (non-npm: simatec/ioBroker.backitup) in /opt/iobroker/node_modules/iobroker.backitup, node: v19.8.1, js-controller: 5.0.1-alpha.0-20230330-e0b409fe 2023-03-30 20:18:17.318 - debug: backitup.0 (412036) Backitup has recognized a linux system 2023-03-30 20:18:17.358 - info: backitup.0 (412036) [iobroker] backup was activated at 03:42 every 1 day(s) 2023-03-30 20:18:17.467 - debug: backitup.0 (412036) noserverino option: true 2023-03-30 20:18:17.468 - debug: backitup.0 (412036) cifs-mount command: "sudo mount -t cifs -o username=iobroker,password=****,noserverino,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=3.1.1 //192.168.178.1/fritz.nas/Hitachi-HTS545012B9SA00-01/iobbackups/chet /opt/iobroker/backups" 2023-03-30 20:18:18.658 - debug: backitup.0 (412036) first mount attempt with smb option failed. try next mount attempt without smb option ... 2023-03-30 20:18:18.659 - debug: backitup.0 (412036) cifs-mount command: "sudo mount -t cifs -o username=iobroker,password=****,noserverino,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.178.1/fritz.nas/Hitachi-HTS545012B9SA00-01/iobbackups/chet /opt/iobroker/backups" 2023-03-30 20:18:18.743 - debug: backitup.0 (412036) device is busy... wait 2 Minutes!! 2023-03-30 20:18:18.770 - error: backitup.0 (412036) Error: Command failed: sudo mount -t cifs -o username=iobroker,password=****,noserverino,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777 //192.168.178.1/fritz.nas/Hitachi-HTS545012B9SA00-01/iobbackups/chet /opt/iobroker/backups mount error(16): Device or resource busy Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg) 2023-03-30 20:18:20.829 - debug: backitup.0 (412036) detect backup file 1 from NAS: iobroker_2023_03_21-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.833 - debug: backitup.0 (412036) detect backup file 2 from NAS: iobroker_2023_03_22-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.834 - debug: backitup.0 (412036) detect backup file 3 from NAS: iobroker_2023_03_23-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.834 - debug: backitup.0 (412036) detect backup file 4 from NAS: iobroker_2023_03_24-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.835 - debug: backitup.0 (412036) detect backup file 5 from NAS: iobroker_2023_03_25-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.835 - debug: backitup.0 (412036) detect backup file 6 from NAS: iobroker_2023_03_26-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.836 - debug: backitup.0 (412036) detect backup file 7 from NAS: iobroker_2023_03_27-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.837 - debug: backitup.0 (412036) detect backup file 8 from NAS: iobroker_2023_03_28-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.837 - debug: backitup.0 (412036) detect backup file 9 from NAS: iobroker_2023_03_29-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.838 - debug: backitup.0 (412036) detect backup file 10 from NAS: iobroker_2023_03_30-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.839 - debug: backitup.0 (412036) detect backup file 11 from NAS: iobroker_2023_03_30-19_37_47_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.839 - debug: backitup.0 (412036) detect backup file 12 from NAS: iobroker_2023_03_30-19_40_44_chet_backupiobroker.tar.gz 2023-03-30 20:18:20.839 - debug: backitup.0 (412036) detect backup file 13 from NAS: iobroker_2023_03_30-19_49_33_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.265 - debug: backitup.0 (412036) detect backup file 1 from googledrive: iobroker_2023_03_30-19_49_33_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.266 - debug: backitup.0 (412036) detect backup file 2 from googledrive: iobroker_2023_03_30-19_40_44_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.267 - debug: backitup.0 (412036) detect backup file 3 from googledrive: iobroker_2023_03_30-19_37_47_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.267 - debug: backitup.0 (412036) detect backup file 4 from googledrive: iobroker_2023_03_30-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.267 - debug: backitup.0 (412036) detect backup file 5 from googledrive: iobroker_2023_03_29-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.267 - debug: backitup.0 (412036) detect backup file 6 from googledrive: iobroker_2023_03_28-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.268 - debug: backitup.0 (412036) detect backup file 7 from googledrive: iobroker_2023_03_27-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.268 - debug: backitup.0 (412036) detect backup file 8 from googledrive: iobroker_2023_03_26-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.268 - debug: backitup.0 (412036) detect backup file 9 from googledrive: iobroker_2023_03_25-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.268 - debug: backitup.0 (412036) detect backup file 10 from googledrive: iobroker_2023_03_24-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.269 - debug: backitup.0 (412036) detect backup file 11 from googledrive: iobroker_2023_03_23-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.269 - debug: backitup.0 (412036) detect backup file 12 from googledrive: iobroker_2023_03_22-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.269 - debug: backitup.0 (412036) detect backup file 13 from googledrive: iobroker_2023_03_21-03_42_20_chet_backupiobroker.tar.gz 2023-03-30 20:18:22.271 - debug: backitup.0 (412036) detect last backup file: iobroker_2023_03_30-19_49_33_chet_backupiobroker.tar.gz 2023-03-30 20:18:27.363 - debug: backitup.0 (412036) mount activ... umount in 2 Seconds!! 2023-03-30 20:18:29.418 - debug: backitup.0 (412036) umount successfully completed 2023-03-30 20:20:18.783 - error: backitup.0 (412036) umount: /opt/iobroker/backups: not mounted.@thomas-braun ne 120GB Travelstar an der Fritte?
kein Support per PN! - Fragen im Forum stellen -
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
Das Forum freut sich über eine Spende. Benutzt dazu den Spendenbutton oben rechts. Danke!
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash - -
@thomas-braun ne 120GB Travelstar an der Fritte?
Ja. Ist aber kein Geheimnis. :-)
-
@thomas-braun ne 120GB Travelstar an der Fritte?
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@thomas-braun ne 120GB Travelstar an der Fritte?
Ich weiß nicht was ich tun soll?
Adapeter ist neu gestartet -> ohne erfolg -
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@thomas-braun ne 120GB Travelstar an der Fritte?
Ich weiß nicht was ich tun soll?
Adapeter ist neu gestartet -> ohne erfolgIm LogFile den Neustart beobachten.
Geht wie oben schon mal erwähnt im Terminal periob logs --watch | uniq -
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@thomas-braun ne 120GB Travelstar an der Fritte?
Ich weiß nicht was ich tun soll?
Adapeter ist neu gestartet -> ohne erfolg@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
Ich weiß nicht was ich tun soll?
das war für Thomas!
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
ohne erfolg
Bitte Daten!
-
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
Ich weiß nicht was ich tun soll?
das war für Thomas!
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
ohne erfolg
Bitte Daten!
@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
Ich weiß nicht was ich tun soll?
das war für Thomas!
@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:
ohne erfolg
Bitte Daten!
pi@phoscon:~ $ iob logs --watch | uniq 2023-03-30 12:37:20.851 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 12:43:12.169 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 12:47:34.606 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 13:05:00.042 - info: wifilight.0 (23377) Scheduled restart. 2023-03-30 13:05:00.054 - info: wifilight.0 (23377) terminating 2023-03-30 13:05:00.057 - info: wifilight.0 (23377) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-03-30 13:05:00.684 - info: host.phoscon instance system.adapter.wifilight.0 scheduled normal terminated and will be restarted on schedule. 2023-03-30 13:05:00.692 - info: host.phoscon Restart adapter system.adapter.wifilight.0 because enabled 2023-03-30 13:05:01.813 - info: host.phoscon instance system.adapter.wifilight.0 started with pid 1085 2023-03-30 13:05:04.713 - info: wifilight.0 (1085) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.wifilight, node: v18.15.0, js-controller: 4.0.24 2023-03-30 13:05:05.054 - info: wifilight.0 (1085) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 13:05:05.123 - info: wifilight.0 (1085) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 13:36:50.014 - warn: shelly.0 (1521) [authEnabled] 192.168.178.75 (shelly1 / shelly1-E89F6D8616E8 / SHSW-1#E89F6D8616E8#1): This device is not protected via restricted login (see adapter documentation for details) 2023-03-30 13:36:50.614 - warn: shelly.0 (1521) [authEnabled] 192.168.178.60 (shelly1 / shelly1-C45BBE572A8D / SHSW-1#C45BBE572A8D#1): This device is not protected via restricted login (see adapter documentation for details) 2023-03-30 13:36:51.830 - warn: shelly.0 (1521) [authEnabled] 192.168.178.74 (shelly1 / shelly1-E89F6D865BEC / SHSW-1#E89F6D865BEC#1): This device is not protected via restricted login (see adapter documentation for details) 2023-03-30 14:05:00.034 - info: wifilight.0 (1085) Scheduled restart. 2023-03-30 14:05:00.046 - info: wifilight.0 (1085) terminating 2023-03-30 14:05:00.049 - info: wifilight.0 (1085) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-03-30 14:05:00.672 - info: host.phoscon instance system.adapter.wifilight.0 scheduled normal terminated and will be restarted on schedule. 2023-03-30 14:05:00.673 - info: host.phoscon Restart adapter system.adapter.wifilight.0 because enabled 2023-03-30 14:05:01.771 - info: host.phoscon instance system.adapter.wifilight.0 started with pid 11676 2023-03-30 14:05:04.585 - info: wifilight.0 (11676) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.wifilight, node: v18.15.0, js-controller: 4.0.24 2023-03-30 14:05:04.923 - info: wifilight.0 (11676) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 14:05:04.994 - info: wifilight.0 (11676) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 15:05:00.039 - info: wifilight.0 (11676) Scheduled restart. 2023-03-30 15:05:00.060 - info: wifilight.0 (11676) terminating 2023-03-30 15:05:00.063 - info: wifilight.0 (11676) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-03-30 15:05:00.720 - info: host.phoscon instance system.adapter.wifilight.0 scheduled normal terminated and will be restarted on schedule. 2023-03-30 15:05:00.723 - info: host.phoscon Restart adapter system.adapter.wifilight.0 because enabled 2023-03-30 15:05:01.800 - info: host.phoscon instance system.adapter.wifilight.0 started with pid 22047 2023-03-30 15:05:04.571 - info: wifilight.0 (22047) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.wifilight, node: v18.15.0, js-controller: 4.0.24 2023-03-30 15:05:04.944 - info: wifilight.0 (22047) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 15:05:05.024 - info: wifilight.0 (22047) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 15:21:25.221 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 15:21:25.226 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 admin 2023-03-30 16:05:00.032 - info: wifilight.0 (22047) Scheduled restart. 2023-03-30 16:05:00.044 - info: wifilight.0 (22047) terminating 2023-03-30 16:05:00.047 - info: wifilight.0 (22047) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-03-30 16:05:00.661 - info: host.phoscon instance system.adapter.wifilight.0 scheduled normal terminated and will be restarted on schedule. 2023-03-30 16:05:00.663 - info: host.phoscon Restart adapter system.adapter.wifilight.0 because enabled 2023-03-30 16:05:01.753 - info: host.phoscon instance system.adapter.wifilight.0 started with pid 32531 2023-03-30 16:05:04.316 - info: wifilight.0 (32531) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.wifilight, node: v18.15.0, js-controller: 4.0.24 2023-03-30 16:05:04.790 - info: wifilight.0 (32531) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 16:05:04.845 - info: wifilight.0 (32531) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 16:23:29.346 - warn: shelly.0 (1521) [authEnabled] 192.168.178.75 (shelly1 / shelly1-E89F6D8616E8 / SHSW-1#E89F6D8616E8#1): This device is not protected via restricted login (see adapter documentation for details) 2023-03-30 16:23:29.921 - warn: shelly.0 (1521) [authEnabled] 192.168.178.60 (shelly1 / shelly1-C45BBE572A8D / SHSW-1#C45BBE572A8D#1): This device is not protected via restricted login (see adapter documentation for details) 2023-03-30 16:23:31.381 - warn: shelly.0 (1521) [authEnabled] 192.168.178.74 (shelly1 / shelly1-E89F6D865BEC / SHSW-1#E89F6D865BEC#1): This device is not protected via restricted login (see adapter documentation for details) 2023-03-30 17:02:13.765 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 17:02:14.684 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 17:03:10.140 - info: host.phoscon stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-03-30 17:03:10.152 - info: host.phoscon stopInstance system.adapter.backitup.0 send kill signal 2023-03-30 17:03:10.150 - info: backitup.0 (29827) Got terminate signal TERMINATE_YOURSELF 2023-03-30 17:03:10.157 - info: backitup.0 (29827) cleaned everything up... 2023-03-30 17:03:10.158 - info: backitup.0 (29827) terminating 2023-03-30 17:03:10.160 - info: backitup.0 (29827) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-03-30 17:03:10.410 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 17:03:10.753 - info: host.phoscon instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-30 17:03:13.234 - info: host.phoscon instance system.adapter.backitup.0 started with pid 9257 2023-03-30 17:03:16.036 - info: backitup.0 (9257) starting. Version 2.5.12 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0.24 2023-03-30 17:03:16.231 - info: backitup.0 (9257) [iobroker] backup was activated at 02:40 every 3 day(s) 2023-03-30 17:03:16.348 - warn: backitup.0 (9257) No backup file was found 2023-03-30 17:03:21.742 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 17:03:33.259 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 17:05:00.029 - info: wifilight.0 (32531) Scheduled restart. 2023-03-30 17:05:00.036 - info: wifilight.0 (32531) terminating 2023-03-30 17:05:00.039 - info: wifilight.0 (32531) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-03-30 17:05:00.639 - info: host.phoscon instance system.adapter.wifilight.0 scheduled normal terminated and will be restarted on schedule. 2023-03-30 17:05:00.639 - info: host.phoscon Restart adapter system.adapter.wifilight.0 because enabled 2023-03-30 17:05:01.726 - info: host.phoscon instance system.adapter.wifilight.0 started with pid 10590 2023-03-30 17:05:04.299 - info: wifilight.0 (10590) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.wifilight, node: v18.15.0, js-controller: 4.0.24 2023-03-30 17:05:04.690 - info: wifilight.0 (10590) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 17:05:04.779 - info: wifilight.0 (10590) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 17:07:07.904 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 admin 2023-03-30 17:07:08.442 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:01:21.598 - info: host.phoscon stopInstance system.adapter.deconz.0 (force=false, process=true) 2023-03-30 18:01:21.672 - info: host.phoscon stopInstance system.adapter.deconz.0 send kill signal 2023-03-30 18:01:21.671 - info: deconz.0 (2323) Got terminate signal TERMINATE_YOURSELF 2023-03-30 18:01:21.674 - info: deconz.0 (2323) cleaned everything up... 2023-03-30 18:01:21.675 - info: deconz.0 (2323) terminating 2023-03-30 18:01:21.676 - info: deconz.0 (2323) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-03-30 18:01:22.271 - info: host.phoscon instance system.adapter.deconz.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-30 18:01:24.761 - info: host.phoscon instance system.adapter.deconz.0 started with pid 18063 2023-03-30 18:01:27.674 - info: deconz.0 (18063) starting. Version 1.3.21 in /opt/iobroker/node_modules/iobroker.deconz, node: v18.15.0, js-controller: 4.0.24 2023-03-30 18:01:28.023 - info: deconz.0 (18063) deConz Version: 2.13.4; API version: 1.16.0 2023-03-30 18:01:28.086 - info: deconz.0 (18063) Code 403: Forbidden get all lights: [{"error":{"address":"/lights","description":"unauthorized user","type":1}}] 2023-03-30 18:01:28.094 - info: deconz.0 (18063) Code 403: Forbidden get all sensors: [{"error":{"address":"/sensors","description":"unauthorized user","type":1}}] 2023-03-30 18:01:28.097 - info: deconz.0 (18063) Code 403: Forbidden get all groups: [{"error":{"address":"/groups","description":"unauthorized user","type":1}}] 2023-03-30 18:03:10.153 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:03:14.510 - warn: deconz.0 (18063) Unknown command: send 2023-03-30 18:03:15.577 - info: deconz.0 (18063) STATUS: {"statusCode":200,"body":"[{\"success\":{\"username\":\"850F98DFDE\"}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"39","etag":"\"1d4966a70bbd39cf8b1f9530d8661b14\""},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:03:15.580 - info: deconz.0 (18063) "850F98DFDE" 2023-03-30 18:03:15.596 - info: deconz.0 (18063) deConz Version: 2.13.4; API version: 1.16.0 2023-03-30 18:03:15.619 - info: deconz.0 (18063) Code 403: Forbidden get all lights: [{"error":{"address":"/lights","description":"unauthorized user","type":1}}] 2023-03-30 18:03:15.624 - info: deconz.0 (18063) Code 403: Forbidden get all sensors: [{"error":{"address":"/sensors","description":"unauthorized user","type":1}}] 2023-03-30 18:03:15.626 - info: deconz.0 (18063) Code 403: Forbidden get all groups: [{"error":{"address":"/groups","description":"unauthorized user","type":1}}] 2023-03-30 18:03:18.033 - info: host.phoscon stopInstance system.adapter.deconz.0 (force=false, process=true) 2023-03-30 18:03:18.042 - info: host.phoscon stopInstance system.adapter.deconz.0 send kill signal 2023-03-30 18:03:18.042 - info: deconz.0 (18063) Got terminate signal TERMINATE_YOURSELF 2023-03-30 18:03:18.045 - info: deconz.0 (18063) cleaned everything up... 2023-03-30 18:03:18.047 - info: deconz.0 (18063) terminating 2023-03-30 18:03:18.049 - info: deconz.0 (18063) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-03-30 18:03:18.638 - info: host.phoscon instance system.adapter.deconz.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-30 18:03:21.131 - info: host.phoscon instance system.adapter.deconz.0 started with pid 19314 2023-03-30 18:03:21.355 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:03:24.409 - info: deconz.0 (19314) starting. Version 1.3.21 in /opt/iobroker/node_modules/iobroker.deconz, node: v18.15.0, js-controller: 4.0.24 2023-03-30 18:03:24.740 - info: deconz.0 (19314) deConz Version: 2.13.4; API version: 1.16.0 2023-03-30 18:04:30.930 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:04:33.352 - warn: deconz.0 (19314) Unknown command: send 2023-03-30 18:04:35.417 - info: deconz.0 (19314) STATUS: {"statusCode":200,"body":"[{\"success\":{\"username\":\"99A716A195\"}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"39","etag":"\"4491fc0dbbbadc6036fdd47b0e461778\""},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:04:35.419 - info: deconz.0 (19314) "99A716A195" 2023-03-30 18:04:35.440 - info: deconz.0 (19314) deConz Version: 2.13.4; API version: 1.16.0 2023-03-30 18:04:38.723 - info: host.phoscon stopInstance system.adapter.deconz.0 (force=false, process=true) 2023-03-30 18:04:38.729 - info: deconz.0 (19314) Got terminate signal TERMINATE_YOURSELF 2023-03-30 18:04:38.731 - info: host.phoscon stopInstance system.adapter.deconz.0 send kill signal 2023-03-30 18:04:38.732 - info: deconz.0 (19314) cleaned everything up... 2023-03-30 18:04:38.733 - info: deconz.0 (19314) terminating 2023-03-30 18:04:38.735 - info: deconz.0 (19314) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-03-30 18:04:38.980 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:04:39.333 - info: host.phoscon instance system.adapter.deconz.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-30 18:04:41.813 - info: host.phoscon instance system.adapter.deconz.0 started with pid 21750 2023-03-30 18:04:44.739 - info: deconz.0 (21750) starting. Version 1.3.21 in /opt/iobroker/node_modules/iobroker.deconz, node: v18.15.0, js-controller: 4.0.24 2023-03-30 18:04:45.059 - info: deconz.0 (21750) deConz Version: 2.13.4; API version: 1.16.0 2023-03-30 18:05:00.032 - info: wifilight.0 (10590) Scheduled restart. 2023-03-30 18:05:00.039 - info: wifilight.0 (10590) terminating 2023-03-30 18:05:00.041 - info: wifilight.0 (10590) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-03-30 18:05:00.647 - info: host.phoscon instance system.adapter.wifilight.0 scheduled normal terminated and will be restarted on schedule. 2023-03-30 18:05:00.647 - info: host.phoscon Restart adapter system.adapter.wifilight.0 because enabled 2023-03-30 18:05:01.728 - info: host.phoscon instance system.adapter.wifilight.0 started with pid 21975 2023-03-30 18:05:04.535 - info: wifilight.0 (21975) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.wifilight, node: v18.15.0, js-controller: 4.0.24 2023-03-30 18:05:05.070 - info: wifilight.0 (21975) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 18:05:05.163 - info: wifilight.0 (21975) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 18:07:14.807 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:07:16.893 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 devices 2023-03-30 18:07:22.159 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:07:33.065 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:07:33.439 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:07:35.554 - info: host.phoscon Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-03-30 18:07:52.254 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:07:58.319 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:08:17.292 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:11:14.091 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:11:33.074 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:19:39.718 - info: host.phoscon stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-03-30 18:19:39.809 - info: host.phoscon stopInstance system.adapter.backitup.0 send kill signal 2023-03-30 18:19:39.812 - info: backitup.0 (9257) Got terminate signal TERMINATE_YOURSELF 2023-03-30 18:19:39.814 - info: backitup.0 (9257) cleaned everything up... 2023-03-30 18:19:39.816 - info: backitup.0 (9257) terminating 2023-03-30 18:19:39.818 - info: backitup.0 (9257) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-03-30 18:19:40.413 - info: host.phoscon instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-30 18:19:42.889 - info: host.phoscon instance system.adapter.backitup.0 started with pid 32554 2023-03-30 18:19:44.885 - debug: backitup.0 (32554) Redis Objects: Use Redis connection: 127.0.0.1:9001 2023-03-30 18:19:44.969 - debug: backitup.0 (32554) Objects client ready ... initialize now 2023-03-30 18:19:44.972 - debug: backitup.0 (32554) Objects create System PubSub Client 2023-03-30 18:19:44.974 - debug: backitup.0 (32554) Objects create User PubSub Client 2023-03-30 18:19:45.015 - debug: backitup.0 (32554) Objects client initialize lua scripts 2023-03-30 18:19:45.025 - debug: backitup.0 (32554) Objects connected to redis: 127.0.0.1:9001 2023-03-30 18:19:45.057 - debug: backitup.0 (32554) Redis States: Use Redis connection: 127.0.0.1:9000 2023-03-30 18:19:45.074 - debug: backitup.0 (32554) States create System PubSub Client 2023-03-30 18:19:45.076 - debug: backitup.0 (32554) States create User PubSub Client 2023-03-30 18:19:45.097 - debug: backitup.0 (32554) States connected to redis: 127.0.0.1:9000 2023-03-30 18:19:45.172 - debug: backitup.0 (32554) Plugin sentry Initialize Plugin (enabled=true) 2023-03-30 18:19:45.767 - info: backitup.0 (32554) starting. Version 2.5.12 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0.24 2023-03-30 18:19:45.838 - debug: backitup.0 (32554) Backitup has recognized a linux system 2023-03-30 18:19:45.931 - info: backitup.0 (32554) [iobroker] backup was activated at 02:40 every 3 day(s) 2023-03-30 18:19:46.049 - warn: backitup.0 (32554) No backup file was found 2023-03-30 18:26:20.365 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:26:20.654 - debug: backitup.0 (32554) telegram-instance: 2023-03-30 18:26:28.290 - debug: backitup.0 (32554) Backup list cannot be read ... 2023-03-30 18:26:28.292 - debug: backitup.0 (32554) Backup list cannot be read ... 2023-03-30 18:26:36.560 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:29:02.178 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:29:04.756 - warn: deconz.0 (21750) Unknown command: send 2023-03-30 18:29:06.416 - info: deconz.0 (21750) STATUS: {"statusCode":403,"body":"[{\"error\":{\"address\":\"/\",\"description\":\"link button not pressed\",\"type\":101}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"78"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:09.446 - info: deconz.0 (21750) STATUS: {"statusCode":403,"body":"[{\"error\":{\"address\":\"/\",\"description\":\"link button not pressed\",\"type\":101}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"78"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:13.161 - info: deconz.0 (21750) STATUS: {"statusCode":403,"body":"[{\"error\":{\"address\":\"/\",\"description\":\"link button not pressed\",\"type\":101}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"78"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:17.148 - info: deconz.0 (21750) STATUS: {"statusCode":403,"body":"[{\"error\":{\"address\":\"/\",\"description\":\"link button not pressed\",\"type\":101}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"78"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:21.164 - info: deconz.0 (21750) STATUS: {"statusCode":403,"body":"[{\"error\":{\"address\":\"/\",\"description\":\"link button not pressed\",\"type\":101}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"78"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:25.149 - info: deconz.0 (21750) STATUS: {"statusCode":403,"body":"[{\"error\":{\"address\":\"/\",\"description\":\"link button not pressed\",\"type\":101}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"78"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:29.150 - info: deconz.0 (21750) STATUS: {"statusCode":403,"body":"[{\"error\":{\"address\":\"/\",\"description\":\"link button not pressed\",\"type\":101}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"78"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:33.147 - info: deconz.0 (21750) STATUS: {"statusCode":403,"body":"[{\"error\":{\"address\":\"/\",\"description\":\"link button not pressed\",\"type\":101}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"78"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:37.200 - info: deconz.0 (21750) STATUS: {"statusCode":403,"body":"[{\"error\":{\"address\":\"/\",\"description\":\"link button not pressed\",\"type\":101}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"78"},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:40.752 - info: deconz.0 (21750) STATUS: {"statusCode":200,"body":"[{\"success\":{\"username\":\"9A67F9C407\"}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"39","etag":"\"d46d23379ad89f4dac01486137f80e6a\""},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:40.754 - info: deconz.0 (21750) "9A67F9C407" 2023-03-30 18:29:40.770 - info: deconz.0 (21750) deConz Version: 2.13.4; API version: 1.16.0 2023-03-30 18:29:44.774 - warn: deconz.0 (21750) Unknown command: send 2023-03-30 18:29:46.437 - info: deconz.0 (21750) STATUS: {"statusCode":200,"body":"[{\"success\":{\"username\":\"9A67F9C407\"}}]","headers":{"access-control-allow-origin":"*","content-type":"application/json; charset=utf-8","content-length":"39","etag":"\"988d5d5f4561ff6ac5c262208aa4a331\""},"request":{"uri":{"protocol":"http:","slashes":true,"auth":null,"host":"192.168.178.63:80","port":"80","hostname":"192.168.178.63","hash":null,"search":null,"query":null,"pathname":"/api","path":"/api","href":"http://192.168.178.63:80/api"},"method":"POST","headers":{"Content-Type":"text/plain;charset=UTF-8","Authorization":"Basic ZGVsaWdodDpkZWxpZ2h0","Content-Length":0}}} 2023-03-30 18:29:46.439 - info: deconz.0 (21750) "9A67F9C407" 2023-03-30 18:29:46.456 - info: deconz.0 (21750) deConz Version: 2.13.4; API version: 1.16.0 2023-03-30 18:29:49.919 - info: host.phoscon stopInstance system.adapter.deconz.0 (force=false, process=true) 2023-03-30 18:29:49.929 - info: deconz.0 (21750) Got terminate signal TERMINATE_YOURSELF 2023-03-30 18:29:49.932 - info: deconz.0 (21750) cleaned everything up... 2023-03-30 18:29:49.933 - info: deconz.0 (21750) terminating 2023-03-30 18:29:49.935 - info: deconz.0 (21750) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-03-30 18:29:49.954 - info: host.phoscon stopInstance system.adapter.deconz.0 send kill signal 2023-03-30 18:29:50.313 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:29:50.579 - info: host.phoscon instance system.adapter.deconz.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-30 18:29:53.055 - info: host.phoscon instance system.adapter.deconz.0 started with pid 7495 2023-03-30 18:29:56.076 - info: deconz.0 (7495) starting. Version 1.3.21 in /opt/iobroker/node_modules/iobroker.deconz, node: v18.15.0, js-controller: 4.0.24 2023-03-30 18:29:56.434 - info: deconz.0 (7495) deConz Version: 2.13.4; API version: 1.16.0 2023-03-30 18:48:41.501 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:48:41.751 - debug: backitup.0 (32554) telegram-instance: 2023-03-30 18:49:00.233 - info: host.phoscon stopInstance system.adapter.backitup.0 (force=false, process=true) 2023-03-30 18:49:00.238 - info: backitup.0 (32554) Got terminate signal TERMINATE_YOURSELF 2023-03-30 18:49:00.240 - info: backitup.0 (32554) cleaned everything up... 2023-03-30 18:49:00.241 - info: backitup.0 (32554) terminating 2023-03-30 18:49:00.242 - debug: backitup.0 (32554) Plugin sentry destroyed 2023-03-30 18:49:00.242 - info: backitup.0 (32554) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-03-30 18:49:00.255 - info: host.phoscon stopInstance system.adapter.backitup.0 send kill signal 2023-03-30 18:49:00.583 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:49:00.839 - info: host.phoscon instance system.adapter.backitup.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-03-30 18:49:03.389 - info: host.phoscon instance system.adapter.backitup.0 started with pid 21267 2023-03-30 18:49:05.584 - debug: backitup.0 (21267) Redis Objects: Use Redis connection: 127.0.0.1:9001 2023-03-30 18:49:05.637 - debug: backitup.0 (21267) Objects client ready ... initialize now 2023-03-30 18:49:05.640 - debug: backitup.0 (21267) Objects create System PubSub Client 2023-03-30 18:49:05.642 - debug: backitup.0 (21267) Objects create User PubSub Client 2023-03-30 18:49:05.681 - debug: backitup.0 (21267) Objects client initialize lua scripts 2023-03-30 18:49:05.690 - debug: backitup.0 (21267) Objects connected to redis: 127.0.0.1:9001 2023-03-30 18:49:05.726 - debug: backitup.0 (21267) Redis States: Use Redis connection: 127.0.0.1:9000 2023-03-30 18:49:05.739 - debug: backitup.0 (21267) States create System PubSub Client 2023-03-30 18:49:05.741 - debug: backitup.0 (21267) States create User PubSub Client 2023-03-30 18:49:05.763 - debug: backitup.0 (21267) States connected to redis: 127.0.0.1:9000 2023-03-30 18:49:05.832 - debug: backitup.0 (21267) Plugin sentry Initialize Plugin (enabled=true) 2023-03-30 18:49:06.364 - info: backitup.0 (21267) starting. Version 2.5.12 in /opt/iobroker/node_modules/iobroker.backitup, node: v18.15.0, js-controller: 4.0.24 2023-03-30 18:49:06.436 - debug: backitup.0 (21267) Backitup has recognized a linux system 2023-03-30 18:49:06.514 - info: backitup.0 (21267) [iobroker] backup was activated at 02:40 every 3 day(s) 2023-03-30 18:49:06.632 - warn: backitup.0 (21267) No backup file was found 2023-03-30 18:51:30.988 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:51:31.387 - debug: backitup.0 (21267) telegram-instance: 2023-03-30 18:51:36.557 - debug: backitup.0 (21267) Backup list cannot be read ... 2023-03-30 18:51:36.559 - debug: backitup.0 (21267) Backup list cannot be read ... 2023-03-30 18:51:44.162 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:52:43.552 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 18:52:43.920 - debug: backitup.0 (21267) telegram-instance: 2023-03-30 19:05:00.041 - info: wifilight.0 (21975) Scheduled restart. 2023-03-30 19:05:00.048 - info: wifilight.0 (21975) terminating 2023-03-30 19:05:00.051 - info: wifilight.0 (21975) Terminated (START_IMMEDIATELY_AFTER_STOP): Without reason 2023-03-30 19:05:00.667 - info: host.phoscon instance system.adapter.wifilight.0 scheduled normal terminated and will be restarted on schedule. 2023-03-30 19:05:00.669 - info: host.phoscon Restart adapter system.adapter.wifilight.0 because enabled 2023-03-30 19:05:01.799 - info: host.phoscon instance system.adapter.wifilight.0 started with pid 32348 2023-03-30 19:05:04.495 - info: wifilight.0 (32348) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.wifilight, node: v18.15.0, js-controller: 4.0.24 2023-03-30 19:05:04.893 - info: wifilight.0 (32348) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 19:05:04.944 - info: wifilight.0 (32348) State value to set for "wifilight.0.192_168_178_40.reachable" has to be type "number" but received type "boolean" 2023-03-30 19:10:08.628 - warn: shelly.0 (1521) [authEnabled] 192.168.178.75 (shelly1 / shelly1-E89F6D8616E8 / SHSW-1#E89F6D8616E8#1): This device is not protected via restricted login (see adapter documentation for details) 2023-03-30 19:10:09.195 - warn: shelly.0 (1521) [authEnabled] 192.168.178.60 (shelly1 / shelly1-C45BBE572A8D / SHSW-1#C45BBE572A8D#1): This device is not protected via restricted login (see adapter documentation for details) 2023-03-30 19:10:10.771 - warn: shelly.0 (1521) [authEnabled] 192.168.178.74 (shelly1 / shelly1-E89F6D865BEC / SHSW-1#E89F6D865BEC#1): This device is not protected via restricted login (see adapter documentation for details) 2023-03-30 19:14:11.133 - debug: backitup.0 (21267) Backup has started ... 2023-03-30 19:14:21.135 - debug: backitup.0 (21267) [iobroker/mount] noserverino option: false 2023-03-30 19:14:21.136 - debug: backitup.0 (21267) [iobroker/mount] cifs-mount command: "sudo mount -t cifs -o username=admin,password=****,rw,uid=iobroker,gid=iobroker,file_mode=0777,dir_mode=0777,vers=3.0 //192.168.178.23/TV_Aufnahmen /opt/iobroker/backups" 2023-03-30 19:14:21.254 - debug: backitup.0 (21267) [iobroker/mount] mount successfully completed 2023-03-30 19:14:21.257 - debug: backitup.0 (21267) [iobroker/mount] done 2023-03-30 19:14:25.163 - debug: backitup.0 (21267) [iobroker/iobroker] host.phoscon 1848 states saved 2023-03-30 19:14:25.252 - debug: backitup.0 (21267) [iobroker/iobroker] host.phoscon 2544 objects saved 2023-03-30 19:14:28.640 - debug: backitup.0 (21267) [iobroker/iobroker] Backup created: /opt/iobroker/backups/iobroker_2023_03_30-19_14_21_backupiobroker.tar.gz 2023-03-30 19:14:29.726 - debug: backitup.0 (21267) [iobroker/iobroker] done 2023-03-30 19:14:31.555 - debug: backitup.0 (21267) [iobroker/yahka] found yahka database: yahka.0 2023-03-30 19:14:31.556 - debug: backitup.0 (21267) [iobroker/yahka] done 2023-03-30 19:14:31.859 - debug: backitup.0 (21267) [iobroker/cifs] used copy path: /TV_Aufnahmen 2023-03-30 19:14:31.860 - debug: backitup.0 (21267) [iobroker/cifs] done 2023-03-30 19:14:32.474 - debug: backitup.0 (21267) [iobroker/clean] done 2023-03-30 19:14:33.406 - debug: backitup.0 (21267) [iobroker/historyHTML] new history html values created 2023-03-30 19:14:33.407 - debug: backitup.0 (21267) [iobroker/historyHTML] done 2023-03-30 19:14:33.571 - debug: backitup.0 (21267) [iobroker/historyJSON] new history json values created 2023-03-30 19:14:33.572 - debug: backitup.0 (21267) [iobroker/historyJSON] done 2023-03-30 19:14:33.775 - debug: backitup.0 (21267) [iobroker/umount] mount activ, umount is started ... 2023-03-30 19:14:38.830 - debug: backitup.0 (21267) [iobroker/umount] umount successfully completed 2023-03-30 19:14:38.832 - debug: backitup.0 (21267) [iobroker/umount] done 2023-03-30 19:14:38.983 - debug: backitup.0 (21267) [iobroker] exec: done 2023-03-30 19:14:53.081 - debug: backitup.0 (21267) Backup list cannot be read ... 2023-03-30 19:14:53.083 - debug: backitup.0 (21267) Backup list cannot be read ... 2023-03-30 19:15:11.048 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 19:31:03.569 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 admin 2023-03-30 19:31:29.675 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 19:31:32.504 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 19:31:34.326 - info: host.phoscon Updating repository "stable" under "http://download.iobroker.net/sources-dist.json" 2023-03-30 19:31:47.404 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87 2023-03-30 19:31:58.424 - info: admin.0 (1943) ==> Connected system.user.admin from ::ffff:192.168.178.87 2023-03-30 19:31:58.800 - debug: backitup.0 (21267) telegram-instance: 2023-03-30 19:32:02.902 - debug: backitup.0 (21267) Backup list cannot be read ... 2023-03-30 19:32:02.904 - debug: backitup.0 (21267) Backup list cannot be read ... 2023-03-30 19:32:12.440 - info: admin.0 (1943) <== Disconnect system.user.admin from ::ffff:192.168.178.87MOD-EDIT: Code in code-tags gesetzt!
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren Anmelden551
Online32.8k
Benutzer82.9k
Themen1.3m
Beiträge