Jahresrückblick 2025 – unser neuer Blogbeitrag ist online! ✨

[ChrisNett]

kann ich mit putty versuchen ein bestimmtes einzuspielen?

[ChrisNett]

nach dem Neustart vom iobroker kommt dieser Fehler

backitup.0
2021-08-16 17:45:56.923	warn	Cannot read log file: ReferenceError: config is not defined

der Adapter ist aber grün.

[Thomas Braun]

@christian-sandkaulen
Installier den Adapter nochmal.

[ChrisNett]

@thomas-braun

als zweite Instanz ?

[Thomas Braun]

@christian-sandkaulen
Nein, über den Adapter drüber.

iobroker upgrade backitup@2.1.13

[ChrisNett]

@thomas-braun said in Kein restore mit backitup:

iobroker upgrade backitup@2.1.13

pi@PI4:~ $ iobroker upgrade backitup@2.1.13
Would you like to reinstall version 2.1.13 of backitup now? [(y)es, (n)o]: y
Update backitup from @2.1.13 to @2.1.13
host.PI4 Adapter "system.adapter.backitup.0" is stopped.
NPM version: 6.14.14
npm install iobroker.backitup@2.1.13 --loglevel error --prefix "/opt/iobroker" (                                                                                                                                                             System call)

müsste da nicht mehr passsieren?

[ChrisNett]

@christian-sandkaulen

upload [9] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/words.js words.js application/javascript
upload [8] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.js tab_m.js application/javascript
upload [7] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/tab_m.html tab_m.html text/html
upload [6] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/style.css style.css text/css
upload [5] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.js index_m.js application/javascript
upload [4] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index_m.html index_m.html text/html
upload [3] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/index.html index.html text/html
upload [2] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.svg backitup.svg image/svg+xml
upload [1] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/backitup.png backitup.png image/png
upload [0] backitup.admin /opt/iobroker/node_modules/iobroker.backitup/admin/adapter-settings.js adapter-settings.js application/javascript
Adapter "backitup" updated

hat ewig gedauert.

[Thomas Braun]

@christian-sandkaulen

Du bist zu ungeduldig.

[Homoran]

@christian-sandkaulen sagte in Kein restore mit backitup:

hat ewig gedauert.

5 Minuten?

was ist dein Server?

[ChrisNett]

@homoran

backupt ist 6,3Mb
pi4 mit 4gb

[ChrisNett]

@thomas-braun

ja da hast du recht, ich versuche noch mal einen restore nach dem update

[Homoran]

@christian-sandkaulen sagte in Kein restore mit backitup:

pi4 mit 4gb

der sollte einen Install etwas schneller hinbekommen

@Thomas-Braun
Was kann denn da so bremsen, dann wird ein 6MB Backup möglicherweise in ein timeout laufen?

[ChrisNett]

@homoran

auf dem pi läuft noch motioneye das habe ich gerade mal gestoppt mal sehen ob das jetzt geht.

[Thomas Braun]

@christian-sandkaulen @Homoran

Motioneye ist ja auch für die Leichtigkeit bekannt.

[ChrisNett]

pi@PI4:~ $ free
              total        used        free      shared  buff/cache   available
Mem:        3930860       52152     3282432       16836      596276     3719800
Swap:        102396 

pi@PI4:~ $ top
top - 18:24:24 up  1:09,  1 user,  load average: 0,03, 0,55, 1,79
Tasks: 118 total,   1 running, 117 sleeping,   0 stopped,   0 zombie
%Cpu(s):   0,1/2,5     3[||                                                                                                  ]
MiB Mem :   3838,7 total,   3205,0 free,     51,2 used,    582,5 buff/cache
MiB Swap:    100,0 total,    100,0 free,      0,0 used.   3632,3 avail Mem

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU  %MEM     TIME+ COMMAND
  505 root      20   0       0      0      0 I   0,0   0,0   0:48.38 kworker/u8:3-events_unbound
14545 root      20   0       0      0      0 I   4,3   0,0   0:27.40 kworker/u8:0-brcmf_wq/mmc1:0001:1
  134 root      20   0   37620  22608  21744 S   0,0   0,6   0:09.33 systemd-journal
22629 root      20   0       0      0      0 I   0,0   0,0   0:09.32 kworker/0:2-events
 9386 root      20   0       0      0      0 I   0,3   0,0   0:09.27 kworker/u8:4-events_unbound
    1 root      20   0   32724   8132   6520 S   0,0   0,2   0:04.49 systemd
   12 root      20   0       0      0      0 I   0,0   0,0   0:04.20 rcu_sched
   62 root       0 -20       0      0      0 I   0,0   0,0   0:02.93 kworker/0:1H-kblockd
  363 root      20   0   25512   2728   2420 S   0,0   0,1   0:02.27 rsyslogd
  271 root      20   0       0      0      0 S   0,0   0,0   0:02.02 brcmf_wdog/mmc1
22638 root      20   0       0      0      0 I   0,0   0,0   0:01.47 kworker/0:3-events
  380 avahi     20   0    5900   2612   2360 S   0,0   0,1   0:01.36 avahi-daemon

[Homoran]

@christian-sandkaulen sagte in Kein restore mit backitup:

top - 18:24:24 up 1:09, 1 user, load average: 0,03, 0,55, 1,79

da sieht man aber, dass es eben noch nicht so ruhig war.
jetzt ist motioneye natürlich aus

[Thomas Braun]

@christian-sandkaulen

free -ht 

kann man besser lesen.

[ChrisNett]

@thomas-braun said in Kein restore mit backitup:

free -ht

pi@PI4:~ $ free -ht
              total        used        free      shared  buff/cache   available
Mem:          3,7Gi       1,1Gi       2,1Gi        16Mi       585Mi       2,7Gi
Swap:          99Mi          0B        99Mi
Total:        3,8Gi       1,1Gi       2,2Gi

motion io ist aus und der ioBroker läuft.

[ChrisNett]

@christian-sandkaulen

er macht ein restore yes... lag es wirklich an MotionEye? soll das mal auf einen eigenen PI4?

kann gerade keine code kopieren...

[ChrisNett]

@christian-sandkaulen

[DEBUG] [iobroker] Start ioBroker Restore ...
[DEBUG] [iobroker] iobroker controller daemon is not running
[DEBUG] [iobroker] host.PI4 OK.
[DEBUG] [iobroker] host.PI4 Clear all objects and states...
[DEBUG] [iobroker] clean 8767 objects...
[DEBUG] [iobroker] Server Objects 127.0.0.1:52796 Error from InMemDB: Error: Object is marked as non deletable
[ERROR] [iobroker] [Not critical] Cannot delete object 0_userdata.0: {"command":{"name":"del","args":["cfg.o.0_userdata.0"]}}
[DEBUG] [iobroker] Server Objects 127.0.0.1:52796 Error from InMemDB: Error: Object is marked as non deletable
[ERROR] [iobroker] [Not critical] Cannot delete object alias.0: {"command":{"name":"del","args":["cfg.o.alias.0"]}}
[DEBUG] [iobroker] Server Objects 127.0.0.1:52796 Error from InMemDB: Error: Object is marked as non deletable
[ERROR] [iobroker] [Not critical] Cannot delete object enum.functions: {"command":{"name":"del","args":["cfg.o.enum.functions"]}}
[ERROR] [iobroker] [Not critical] Cannot delete object enum.rooms: {"command":{"name":"del","args":["cfg.o.enum.rooms"]}}
[DEBUG] [iobroker] Server Objects 127.0.0.1:52796 Error from InMemDB: Error: Object is marked as non deletable
[DEBUG] [iobroker] Server Objects 127.0.0.1:52796 Error from InMemDB: Error: Object is marked as non deletable
[ERROR] [iobroker] [Not critical] Cannot delete object system.config: {"command":{"name":"del","args":["cfg.o.system.config"]}}
[DEBUG] [iobroker] Server Objects 127.0.0.1:52796 Error from InMemDB: Error: Object is marked as non deletable
[DEBUG] [iobroker] Server Objects 127.0.0.1:52796 Error from InMemDB: Error: Object is marked as non deletable
[DEBUG] [iobroker] Server Objects 127.0.0.1:52796 Error from InMemDB: Error: Object is marked as non deletable
[ERROR] [iobroker] [Not critical] Cannot delete object system.repositories: {"command":{"name":"del","args":["cfg.o.system.repositories"]}}
[DEBUG] [iobroker] Server Objects 127.0.0.1:52796 Error from InMemDB: Error: Object is marked as non deletable
[DEBUG] [iobroker] clean 7218 states...
[DEBUG] [iobroker] host.PI4 done.

[DEBUG] [iobroker] System successfully restored!
[DEBUG] [iobroker] ioBroker Restore completed successfully
[EXIT] 0 **** Restore completed successfully!! ****

The log can be closed ...

also doch einen pi für motion eye? wisst ihr warum nach einem neustart (Stromausfall die vis weg sein kann?)