Backitup findet Dateien nicht auf NAS-Stick wird gesucht

Thomas Braun

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.

Homoran

@thomas-braun ne 120GB Travelstar an der Fritte?

Thomas Braun

@homoran

Ja. Ist aber kein Geheimnis. :-)

Olli63

@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

Thomas Braun

@olli63

Im LogFile den Neustart beobachten.
Geht wie oben schon mal erwähnt im Terminal per

iob logs --watch | uniq

Homoran

@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

@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.87

MOD-EDIT: Code in code-tags gesetzt!

Homoran

@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

2023-03-30 19:14:11.133

bitt die Ausgabe von iob diag da stimmt was nicht!

Olli63 · 2023-03-30 19:14:11.133

@homoran said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

> iob diag

======================= SUMMARY =======================
                     v.2023-01-02


Operatingsystem:        Raspbian GNU/Linux 10 (buster)
Installation:           Native
Timezone:               Europe/London
User-ID:                1000
X-Server:               true
Boot Target:            graphical.target

Pending OS-Updates:     232

Nodejs-Installation:    /usr/bin/nodejs         v18.15.0
                        /usr/bin/node           v18.15.0
                        /usr/bin/npm            9.5.0
                        /usr/bin/npx            9.5.0

ioBroker Core:          js-controller           4.0.24
                        admin                   6.3.5

ioBroker Status:        iobroker is running on this host.


Objects type: jsonl
States  type: jsonl

Status admin:
+ system.adapter.admin.0                  : admin                 : phoscon                                  -  enabled, port: 8081, bind: 0.0.0.0, run as: admin

Pending iob updates:    0

Active repo(s): stable

Objects:                2541
States:                 1848

Size of iob-Database:

11M     /opt/iobroker/iobroker-data/objects.jsonl
4.6M    /opt/iobroker/iobroker-data/objects.json.migrated
4.6M    /opt/iobroker/iobroker-data/objects.json.bak.migrated
0       /opt/iobroker/iobroker-data/objects.json.broken
7.1M    /opt/iobroker/iobroker-data/states.jsonl
608K    /opt/iobroker/iobroker-data/states.json.migrated
608K    /opt/iobroker/iobroker-data/states.json.bak.migrated
0       /opt/iobroker/iobroker-data/states.json.broken


=================== END OF SUMMARY ====================

MOD-EDIT: Code in code-tags gesetzt!

Thomas Braun

@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

Timezone: Europe/London
X-Server: true
Boot Target: graphical.target

Dreimal falsch eingestellt.
Die Zeitzone wird vermutlich aus der DACH-Region sein. Berlin?
Stell es um.

Und Server werden ohne Desktop und damit ohne X-Server betrieben. Gleiches gilt für das Boot Target.
Davon abgesehen ist (buster) tot und mit 232 ausstehenden Updates chronisch ungepflegt.
Viele Baustellen bei dem System.

Homoran

@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

Timezone: Europe/London

wo wohnst du?

@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

Raspbian GNU/Linux 10 (buster)

ist auch tot

@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

Pending OS-Updates: 232

ehrlich?
nie ein Update gemacht?

@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

/usr/bin/npm 9.5.0

@Thomas-Braun ist das ok?
bei so altem Datenbestand?

Thomas Braun

@homoran

Die nodejs-Installation ist fast das einzige was da aktuell und so auch erstmal korrekt ist.

Olli63

@thomas-braun said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

@homoran

Die nodejs-Installation ist fast das einzige was da aktuell und so auch erstmal korrekt ist.

was soll ich jetzt tun?
ich hab doch die Updates der Adapter ständig gemacht. Und IO Broker sagt alles ist aktuell

Thomas Braun

@olli63

Ja, der iobroker schon. Aber das Betriebssystem ist komplett sumpfig.

Homoran

@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

ich hab doch die Updates der Adapter ständig gemacht. Und IO Broker sagt alles ist aktuell

aber das Betriebssystem nie aktualisiert

Olli63

@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 hab doch die Updates der Adapter ständig gemacht. Und IO Broker sagt alles ist aktuell

aber das Betriebssystem nie aktualisiert

also was soll ich tun?

Homoran

@thomas-braun um es nicht zu viel werden zu lassen würde ich bullseye hinten anstellen und erst mal mit sudo apt update und sudo apt upgrade den Stau wegarbeitenDann die Zeitzone richten, vielleicht mag die mycloud den time warp nicht.

Thomas Braun

@homoran sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

Dann die Zeitzone richten

Das würde ich als allererstes richten. Denn auch apt mag eine richtige Zeit. Sonst kann es da updates verweigern, weil unlogische Zeitstempel vorhanden sind.

Olli63

@thomas-braun said in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

@homoran sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

Dann die Zeitzone richten

Das würde ich als allererstes richten. Denn auch apt mag eine richtige Zeit. Sonst kann es da updates verweigern, weil unlogische Zeitstempel vorhanden sind.

wi richte ich die zeitzone ein

Thomas Braun

@olli63 sagte in Backitup findet Dateien nicht auf NAS-Stick wird gesucht:

also was soll ich tun?

In

sudo raspi-config

die Zeitzone setzen und den Desktop ausknipsen. Wenn da nicht ein Bildschirm direkt am Raspi hängt jedenfalls.

Community Forum

NEWS

Backitup findet Dateien nicht auf NAS-Stick wird gesucht

Support us

556

32.8k

82.9k

1.3m