iobroker läuft nach einspielen des Backups nicht mehr.

Thomas Braun · Backup vom 30.05.2020 zurück geladen.

@kmuenke
Eine Idee nicht. Aber einen Hinweis.

Objects type: redis

ist in den meisten Konstellationen ungünstiger als 'file'

Und zu den Repos noch: Bist du sicher, dass du

https://dl.yarnpkg.com/debian stable InRelease

benötigst? Wenn ja, wofür?

Thomas Braun · Backup vom 30.05.2020 zurück geladen.

@kmuenke

iobroker list adapters
iobroker list instances

simatec · Backup vom 30.05.2020 zurück geladen.

@kmuenke
Dein altes System hat redis als Datenbank für file und objects genutzt.
Das muss beim Restore beachtet werden.

Also installiere zuerst redis auf deinem neuen System

sudo apt-get update
sudo apt-get install redis-server
sudo usermod -a -G redis iobroker
sudo reboot now

Im Anschluss nimm ein redis backup deines alten Systems und stelle dies auf deinem neuen System mit backitup wieder her.
Erst dann kannst du dein iobroker backup wiederherstellen.

Hier mal eine detaillierte Anleitung ...
https://forum.iobroker.net/topic/27271/howto-iobroker-restore-unter-linux-durchführen

kmuenke

@simatec
danke für die antwort. die Redisdatenbank hatte ich schon auf dem System installiert.

kmuenke@iobroker-neu:~$ systemctl status redis
● redis-server.service - Advanced key-value store
     Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2020-05-30 18:33:46 CEST; 17h ago
       Docs: http://redis.io/documentation,
             man:redis-server(1)
   Main PID: 679 (redis-server)
      Tasks: 4 (limit: 2208)
     Memory: 20.6M
     CGroup: /system.slice/redis-server.service
             └─679 /usr/bin/redis-server 127.0.0.1:6379

Mai 30 18:33:46 iobroker-neu systemd[1]: Starting Advanced key-value store...
Mai 30 18:33:46 iobroker-neu systemd[1]: redis-server.service: Can't open PID file /run/redis/redis-server.pid (yet?) after start: Operation not permitted
Mai 30 18:33:46 iobroker-neu systemd[1]: Started Advanced key-value store.

Ich bekomme bein versuch die redis Daten vom Backup wieder herzustellen leider diese Meldung.

======================
Log Backitup Restore:
======================

[DEBUG] [redis] Start Redis Restore ...
[DEBUG] [redis] Created Redis tmp
[ERROR] [redis] Redis Restore not completed
[ERROR] [redis] Error: EPERM: operation not permitted, utime '/opt/iobroker/backups/tmp/'
[EXIT] undefined **** Restore completed successfully!! ****

The log can be closed ...

kmuenke

So jetzt habe ich die Backupdaten local auf dem Host liegen.

Redis Daten wieder eingepsielt.

======================
Log Backitup Restore:
======================

[DEBUG] [redis] Start Redis Restore ...
[DEBUG] [redis] Created Redis tmp
[DEBUG] [redis] Restore Redis Backup
[DEBUG] [redis] Copy Redis File for Restore ...
[DEBUG] [redis] Delete tmp Files:/opt/iobroker/backups/tmp/dump.rdb
[DEBUG] [redis] Redis Restore completed successfully
[EXIT] redis restore done **** Restore completed successfully!! ****

The log can be closed ...

Aber auch das hatte leider keinen Erfolg. Keine Webseite :-(

root@iobroker-neu:~# tail -f /opt/iobroker/log/iobroker.current.log
2020-05-31 12:41:14.147  - info: host.iobroker instance system.adapter.admin.0 terminated with code 156 (START_IMMEDIATELY_AFTER_STOP)
2020-05-31 12:41:14.147  - info: host.iobroker All instances are stopped.
2020-05-31 12:41:14.199  - info: host.iobroker terminated
2020-05-31 12:41:20.901  - info: host.iobroker-neu iobroker.js-controller version 3.1.4 js-controller starting
2020-05-31 12:41:20.902  - info: host.iobroker-neu Copyright (c) 2014-2020 bluefox, 2014 hobbyquaker
2020-05-31 12:41:20.903  - info: host.iobroker-neu hostname: iobroker-neu, node: v12.17.0
2020-05-31 12:41:20.903  - info: host.iobroker-neu ip addresses: 192.168.2.56 2a00:6020:24f8:a400:798a:8a92:ddf6:e38a 2a00:6020:24f8:a400:a96f:7bc9:5a06:39ff fe80::fd97:fc00:580a:2910
2020-05-31 12:41:20.942  - info: host.iobroker-neu connected to Objects and States
2020-05-31 12:41:21.038  - info: host.iobroker-neu 4 instances found
2020-05-31 12:41:21.040  - warn: host.iobroker-neu does not start any instances on this host

kmuenke

@Thomas-Braun said in iobroker läuft nach einspielen des Backups nicht mehr.:

iobroker list adapters

hier die Daten:

kmuenke@iobroker-neu:~$ iobroker list adapters
system.adapter.admin                   : admin          - v4.0.10
system.adapter.backitup                : backitup       - v1.4.5
system.adapter.discovery               : discovery      - v2.3.5
system.adapter.info                    : info           - v1.7.2

kmuenke@iobroker-neu:~$ iobroker list instances
  system.adapter.admin.0                 : admin                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin
  system.adapter.backitup.0              : backitup              -  enabled
  system.adapter.discovery.0             : discovery             -  enabled
  system.adapter.info.0                  : info                  -  enabled

+ instance is alive

simatec

@kmuenke
führe bitte folgendes auf deinem System aus

iobroker stop
iobroker host this
iobroker start

kmuenke

@simatec

hi ich habe es hin bekommen das jetzt der iobroker kurzfistig lief nach dem ändern auf seinen alten hostname ging leider nichts mehr. Ich komme dann nicht mehr auf die Webseite.

nach einem iobroker debug admin --ip:0.0.0.0 komme ich wieder auf die Console.

kmuenke@iobroker:~$ iobroker debug admin --ip:0.0.0.0
Debugger listening on ws://127.0.0.1:9229/20ddff7d-9907-4886-9235-ebc69304f09d
For help, see: https://nodejs.org/en/docs/inspector
2020-05-31 17:08:16.346  - debug: admin.0 (1744) Redis Objects: Use Redis connection: 127.0.0.1:6379
2020-05-31 17:08:16.360  - debug: admin.0 (1744) Objects client ready ... initialize now
2020-05-31 17:08:16.362  - debug: admin.0 (1744) Objects create System PubSub Client
2020-05-31 17:08:16.363  - debug: admin.0 (1744) Objects create User PubSub Client
2020-05-31 17:08:16.363  - debug: admin.0 (1744) Objects client initialize lua scripts
2020-05-31 17:08:16.371  - debug: admin.0 (1744) Objects connected to redis: 127.0.0.1:6379
2020-05-31 17:08:16.374  - debug: admin.0 (1744) objectDB connected
2020-05-31 17:08:16.374  - debug: admin.0 (1744) Redis States: Use Redis connection: 127.0.0.1:6379
2020-05-31 17:08:16.376  - debug: admin.0 (1744) States create User PubSub Client
2020-05-31 17:08:16.377  - debug: admin.0 (1744) States create System PubSub Client
2020-05-31 17:08:16.380  - debug: admin.0 (1744) States connected to redis: 127.0.0.1:6379
2020-05-31 17:08:16.381  - debug: admin.0 (1744) statesDB connected
2020-05-31 17:08:16.407  - debug: admin.0 (1744) Plugin sentry Initialize Plugin (enabled=true)
2020-05-31 17:08:16.452  - info: admin.0 (1744) starting. Version 4.0.10 in /opt/iobroker/node_modules/iobroker.admin, node: v12.17.0, js-controller: 3.1.4
2020-05-31 17:08:16.463  - info: admin.0 (1744) requesting all states
2020-05-31 17:08:16.464  - info: admin.0 (1744) requesting all objects
2020-05-31 17:08:16.768  - info: admin.0 (1744) received all objects
2020-05-31 17:08:16.928  - info: admin.0 (1744) http server listening on port 8081
2020-05-31 17:08:16.928  - info: admin.0 (1744) Use link "http://localhost:8081" to configure.
2020-05-31 17:08:16.950  - debug: admin.0 (1744) Subscribe OBJECTS: *
2020-05-31 17:08:16.984  - debug: admin.0 (1744) Next repo update on 2020-6-1 0:59:29
2020-05-31 17:08:23.497  - debug: admin.0 (1744) Subscribe OBJECTS: system.adapter.*
2020-05-31 17:08:23.500  - debug: admin.0 (1744) Subscribe OBJECTS: system.host.*

Nach dem strg x geht dann wieder nichts mehr.

simatec

@kmuenke
ja mit strg + x killst du den debug
Starte mal dein System neu

kmuenke

@simatec

habe ich schon mehrfach gemacht leider ohne Erfolg.

wenn dort keine IP Adresse eingetragen ist wie bekomme ich diese bei dem Admin adpater dort rein ?

admin.0

simatec

@kmuenke

iobroker set admin.0 --ip 0.0.0.0

Homoran

@kmuenke sagte in iobroker läuft nach einspielen des Backups nicht mehr.:

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

ist er doch

simatec

@kmuenke
Konntest du deinen Restore nun hinbekommen und läuft dein iobroker?
Wenn ja, beschreibe hier mL bitte deinen Weg dorthin und wo die Probleme lagen.
Interessant wäre auch, ob du redis mit Backitup sauber wiederherstellen konntest.

kmuenke

@simatec

leider hat das setzen der ip nicht funktioniert.

kmuenke@iobroker:~$ iobroker set admin.0 --ip=0.0.0.0
No parameters set.

kmuenke@iobroker:~$ iobroker set admin.0 --ip 0.0.0.0
Adapter "admin.0" has no setting "ip".
No parameters set.

im Browser wird nichts angezeigt. Selbst auf dem Rechner unter localhost:8081 kommt nichts.

kmuenke

@Homoran

Hallo ja denke ich auch aber leider kommt da nichts

kmuenke@iobroker:~$ iobroker list instances
  system.adapter.admin.0                 : admin                 -  enabled, port: 8081, bind: 0.0.0.0, run as: admin

kmuenke

So kleines zwischen Fazit.

nach dem ich jetzt das Backup noch mal eingespielt habe läuft der Admin. Jedoch ein Start der VIS schlägt fehl. Reinstall ist leider nicht möglich, Multihost ist mit diese App nicht möglich.

2020-06-01 16:50:09.490  - ^[[32minfo^[[39m: host.iobroker iobroker npm-install: npm ERR! A complete log of this run can be found in:npm ERR!     /home/iobroker/.npm/_logs/2020-06-01T14_50_09_480Z-debug.log
2020-06-01 16:50:09.498  - ^[[31merror^[[39m: host.iobroker iobroker npm-install: host.iobroker Cannot install iobroker.vis-material@1.2.6: 1
2020-06-01 16:50:10.502  - ^[[32minfo^[[39m: host.iobroker iobroker npm-install: exit 25
2020-06-01 16:50:11.503  - ^[[33mwarn^[[39m: host.iobroker startInstance cannot find adapter "vis-justgage@1.2.6". Try to install it... 1 attempt
2020-06-01 16:50:11.504  - ^[[32minfo^[[39m: host.iobroker iobroker install vis-justgage@1.2.6 using installedVersion
2020-06-01 16:50:12.554  - ^[[32minfo^[[39m: host.iobroker iobroker npm-install: NPM version: 6.14.4
2020-06-01 16:50:12.555  - ^[[32minfo^[[39m: host.iobroker iobroker npm-install: npm install iobroker.vis-justgage@1.2.6 --loglevel error --prefix "/opt/iobroker" (System call)
2020-06-01 16:50:14.944  - ^[[32minfo^[[39m: host.iobroker iobroker npm-install: npm
2020-06-01 16:50:14.944  - ^[[32minfo^[[39m: host.iobroker iobroker npm-install:  ERR! code ETARGET
2020-06-01 16:50:14.944  - ^[[32minfo^[[39m: host.iobroker iobroker npm-install: npm ERR! notarget No matching version found for iobroker.vis-justgage@1.2.6.npm ERR! notarget
2020-06-01 16:50:14.945  - ^[[32minfo^[[39m: host.iobroker iobroker npm-install:  In most cases you or one of your dependencies are requestingnpm ERR! notarget a package version that doesn't exist.

usw.

Ich denke ich werde noch mal von vorne beginnen.

iobroker mit gleich richtigen Namen aufsetzen so wie auch im Backup. Vielleicht wird es ja dann was.

Bei dem Node.js benötige ich nochmanl einen Tip welche Version sollte man einspielen ??? 12.17 bringt bei div Adaptern Fehler. Die alte Version (v10.20.1) war dagegen fehlerfrei.

Wünsche allen noch einen schönen Abend.

Thomas Braun

@kmuenke Bei welchen Adaptern hakt es denn mit 12.17.0?

kmuenke

@Thomas-Braun

2020-06-01 17:53:54.616  - ^[[32minfo^[[39m: sayit.0 (8134) Terminated (NO_ERROR): Without reason
2020-06-01 17:53:54.617  - ^[[32minfo^[[39m: sayit.0 (8134) terminating
2020-06-01 17:53:55.118  - ^[[32minfo^[[39m: sayit.0 (8134) stopping...
2020-06-01 17:55:24.694  - ^[[32minfo^[[39m: host.iobroker iobroker add vis-bars  --host iobroker
2020-06-01 17:55:25.766  - ^[[32minfo^[[39m: host.iobroker iobroker NPM version: 6.14.4
2020-06-01 17:55:25.767  - ^[[32minfo^[[39m: host.iobroker iobroker npm install iobroker.vis-bars@0.1.4 --loglevel error --prefix "/opt/iobroker" (System call)
2020-06-01 17:55:34.590  - ^[[32minfo^[[39m: host.iobroker iobroker In file included from ../authenticate_pam.cc:23:../../nan/nan.h: In function ‘void Nan::AsyncQueueWorker(Nan::AsyncWorker*)’:../../nan/nan.h:2294:62: warning: cast between incompatible function types from ‘void (*)(uv_work_t*)’ {aka ‘void (*)(uv_work_s*)’} to ‘uv_after_work_cb’ {aka ‘void (*)(uv_work_s*, int)’} [-Wcast-function-type] 2294 |     , reinterpret_cast<uv_after_work_cb>(AsyncExecuteComplete)      |                                                              ^
2020-06-01 17:55:34.616  - ^[[32minfo^[[39m: host.iobroker iobroker ../authenticate_pam.cc: In function ‘void after_doing_auth(uv_work_t*, int)’:../authenticate_pam.cc:107:87: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]  107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);      |                                                                                       ^In file included from ../authenticate_pam.cc:23:../../nan/nan.h:1026:46: note: declared here 1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(      |                                              ^~~~~~~~~~~~../authenticate_pam.cc:107:87: warning: ‘v8::Local<v8::Value> Nan::MakeCallback(v8::Local<v8::Object>, v8::Local<v8::Function>, int, v8::Local<v8::Value>*)’ is deprecated [-Wdeprecated-declarations]  107 |   Nan::MakeCallback(Nan::GetCurrentContext()->Global(), Nan::New(m->callback), 1, args);      |                                                                                       ^In file included from ../authenticate_pam.cc:23:../../nan/nan.h:1026:46: note: declared here 1026 |   NAN_DEPRECATED inline v8::Local<v8::Value> MakeCallback(      |                                              ^~~~~~~~~~~~
2020-06-01 17:55:34.618  - ^[[32minfo^[[39m: host.iobroker iobroker ../authenticate_pam.cc: In function ‘Nan::NAN_METHOD_RETURN_TYPE Authenticate(Nan::NAN_METHOD_ARGS_TYPE)’:../authenticate_pam.cc:147:83: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]  147 |   Local<Value> res = options->Get(Nan::New<String>("serviceName").ToLocalChecked());      |                                                                                   ^
2020-06-01 17:55:34.618  - ^[[32minfo^[[39m: host.iobroker iobroker In file included from /home/iobroker/.cache/node-gyp/12.17.0/include/node/v8-internal.h:14,                 from /home/iobroker/.cache/node-gyp/12.17.0/include/node/v8.h:27,                 from /home/iobroker/.cache/node-gyp/12.17.0/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.17.0/include/node/v8.h:3553:51: note: declared here 3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));      |                                                   ^~~/home/iobroker/.cache/node-gyp/12.17.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’  328 |   declarator __attribute__((deprecated(message)))      |   ^~~~~~~~~~../authenticate_pam.cc:150:30: error: cannot convert ‘char [128]’ to ‘v8::Isolate*’  150 |    serviceName->WriteUtf8(m->serviceName, sizeof(m->serviceName) - 1);      |                           ~~~^~~~~~~~~~~      |                              |      |                              char [128]In file included from /home/iobroker/.cache/node-gyp/12.17.0/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.17.0/include/node/v8.h:2878:26: note:   initializing argument 1 of ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’ 2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,      |                 ~~~~~~~~~^~~~~~~
2020-06-01 17:55:34.619  - ^[[32minfo^[[39m: host.iobroker iobroker ../authenticate_pam.cc:152:69: warning: ‘v8::Local<v8::Value> v8::Object::Get(v8::Local<v8::Value>)’ is deprecated: Use maybe version [-Wdeprecated-declarations]  152 |   res = options->Get(Nan::New<String>("remoteHost").ToLocalChecked());      |                                                                     ^In file included from /home/iobroker/.cache/node-gyp/12.17.0/include/node/v8-internal.h:14,                 from /home/iobroker/.cache/node-gyp/12.17.0/include/node/v8.h:27,                 from /home/iobroker/.cache/node-gyp/12.17.0/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.17.0/include/node/v8.h:3553:51: note: declared here 3553 |   V8_DEPRECATED("Use maybe version", Local<Value> Get(Local<Value> key));      |                                                   ^~~/home/iobroker/.cache/node-gyp/12.17.0/include/node/v8config.h:328:3: note: in definition of macro ‘V8_DEPRECATED’  328 |   declarator __attribute__((deprecated(message)))      |   ^~~~~~~~~~../authenticate_pam.cc:155:29: error: cannot convert ‘char [128]’ to ‘v8::Isolate*’  155 |    remoteHost->WriteUtf8(m->remoteHost, sizeof(m->remoteHost) - 1);      |                          ~~~^~~~~~~~~~      |                             |      |                             char [128]
2020-06-01 17:55:34.619  - ^[[32minfo^[[39m: host.iobroker iobroker In file included from /home/iobroker/.cache/node-gyp/12.17.0/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.17.0/include/node/v8.h:2878:26: note:   initializing argument 1 of ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’ 2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,      |                 ~~~~~~~~~^~~~~~~../authenticate_pam.cc:160:25: error: cannot convert ‘char [128]’ to ‘v8::Isolate*’  160 |  username->WriteUtf8(m->username, sizeof(m->username) - 1);      |                      ~~~^~~~~~~~      |                         |      |                         char [128]In file included from /home/iobroker/.cache/node-gyp/12.17.0/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.17.0/include/node/v8.h:2878:26: note:   initializing argument 1 of ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’ 2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,      |                 ~~~~~~~~~^~~~~~~../authenticate_pam.cc:161:25: error: cannot convert ‘char [128]’ to ‘v8::Isolate*’  161 |  password->WriteUtf8(m->password, sizeof(m->password) - 1);      |                      ~~~^~~~~~~~      |                         |      |                         char [128]In file included from /home/iobroker/.cache/node-gyp/12.17.0/include/node/node.h:67,                 from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:/home/iobroker/.cache/node-gyp/12.17.0/include/node/v8.h:2878:26: note:   initializing argument 1 of ‘int v8::String::WriteUtf8(v8::Isolate*, char*, int, int*, int) const’ 2878 |   int WriteUtf8(Isolate* isolate, char* buffer, int length = -1,      |                 ~~~~~~~~~^~~~~~~
2020-06-01 17:55:34.620  - ^[[32minfo^[[39m: host.iobroker iobroker ../authenticate_pam.cc: At global scope:../authenticate_pam.cc:170:11: error: variable or field ‘init’ declared void  170 | void init(Handle<Object> exports) {      |           ^~~~~~
2020-06-01 17:55:34.622  - ^[[32minfo^[[39m: host.iobroker iobroker ../authenticate_pam.cc:170:11: error: ‘Handle’ was not declared in this scope../authenticate_pam.cc:170:24: error: expected primary-expression before ‘>’ token  170 | void init(Handle<Object> exports) {      |                        ^
2020-06-01 17:55:34.623  - ^[[32minfo^[[39m: host.iobroker iobroker ../authenticate_pam.cc:170:26: error: ‘exports’ was not declared in this scope  170 | void init(Handle<Object> exports) {      |                          ^~~~~~~
2020-06-01 17:55:34.624  - ^[[32minfo^[[39m: host.iobroker iobroker In file included from ../../nan/nan.h:56,                 from ../authenticate_pam.cc:23:../authenticate_pam.cc:175:31: error: ‘init’ was not declared in this scope; did you mean ‘int’?  175 | NODE_MODULE(authenticate_pam, init);      |                               ^~~~/home/iobroker/.cache/node-gyp/12.17.0/include/node/node.h:608:36: note: in definition of macro ‘NODE_MODULE_X’  608 |       (node::addon_register_func) (regfunc),                          \      |                                    ^~~~~~~../authenticate_pam.cc:175:1: note: in expansion of macro ‘NODE_MODULE’  175 | NODE_MODULE(authenticate_pam, init);      | ^~~~~~~~~~~
2020-06-01 17:55:34.707  - ^[[32minfo^[[39m: host.iobroker iobroker make: *** [authenticate_pam.target.mk:111: Release/obj.target/authenticate_pam/authenticate_pam.o] Fehler 1
2020-06-01 17:55:34.708  - ^[[32minfo^[[39m: host.iobroker iobroker gyp
2020-06-01 17:55:34.708  - ^[[32minfo^[[39m: host.iobroker iobroker  ERR! build error
2020-06-01 17:55:34.709  - ^[[32minfo^[[39m: host.iobroker iobroker gyp
2020-06-01 17:55:34.709  - ^[[32minfo^[[39m: host.iobroker iobroker  ERR! stack Error: `make` failed with exit code: 2gyp ERR! stack     at ChildProcess.onExit (/usr/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
2020-06-01 17:55:34.710  - ^[[32minfo^[[39m: host.iobroker iobroker gyp ERR! stack     at ChildProcess.emit (events.js:315:20)gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)gyp
2020-06-01 17:55:34.710  - ^[[32minfo^[[39m: host.iobroker iobroker ERR! System Linux 5.4.0-33-genericgyp ERR! command "/usr/bin/node" "/usr/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"gyp ERR! cwd /opt/iobroker/node_modules/authenticate-pamgyp
2020-06-01 17:55:34.710  - ^[[32minfo^[[39m: host.iobroker iobroker ERR! node -v v12.17.0gyp ERR! node-gyp -v v5.1.0gyp ERR!
2020-06-01 17:55:34.711  - ^[[32minfo^[[39m: host.iobroker iobroker  not ok
2020-06-01 17:55:36.447  - ^[[32minfo^[[39m: host.iobroker iobroker host.iobroker install adapter vis-bars
2020-06-01 17:55:36.511  - ^[[32minfo^[[39m: host.iobroker iobroker upload [1] vis-bars.admin /opt/iobroker/node_modules/iobroker.vis-bars/admin/index.html index.html text/html
2020-06-01 17:55:36.588  - ^[[32minfo^[[39m: host.iobroker iobroker upload [0] vis-bars.admin /opt/iobroker/node_modules/iobroker.vis-bars/admin/bars.png bars.png image/png
2020-06-01 17:55:36.640  - ^[[32minfo^[[39m: host.iobroker iobroker INFO: Directory "/opt/iobroker/node_modules/iobroker.vis-bars/www" was not found! Nothing was uploaded or deleted.
2020-06-01 17:55:36.949  - ^[[32minfo^[[39m: host.iobroker iobroker host.iobroker object system.adapter.vis-bars created/updated
2020-06-01 17:55:37.020  - ^[[32minfo^[[39m: host.iobroker iobroker Update "system.adapter.vis-bars.0"
2020-06-01 17:55:37.023  - ^[[32minfo^[[39m: host.iobroker iobroker INFO: Directory "/opt/iobroker/node_modules/iobroker.vis-bars/www" was not found! Nothing was uploaded or deleted.
2020-06-01 17:55:37.104  - ^[[31merror^[[39m: host.iobroker iobroker host.iobroker error: this adapter does not allow multiple instances
2020-06-01 17:55:38.108  - ^[[32minfo^[[39m: host.iobroker iobroker exit 19

JB_Sullivan

Kurze Frage am Rande - ist eigentlich bekannt, das BackItUp (1.5.8) nach einem ioB & einem History Restore auf einer Windows Maschine (bitte keine Kommentare zu dem ach so bösen Windoof als BS) den ioB Dienst nicht selbstständig startet?

Ich habe heute mein Testsystem mal ein wenig aktualisiert und dann die Sicherung des Produktiv System eingespielt. Nach Abschluss des Backup wird der ioB Windows Dienst nicht automatisch gestartet.

Das ist kein Beinbruch, kann man leicht selber machen - ich wollte auch nur fragen ob das ggf. bekannt ist?

simatec

@JB_Sullivan
Schaue ich mir an

Community Forum

NEWS

iobroker läuft nach einspielen des Backups nicht mehr.

Support us

238

32.8k

82.9k

1.3m