NEWS
[beantwortet] ioBroker.benchmark, und nun?
ioBroker Allgemein
48
Beiträge
8
Kommentatoren
5.1k
Aufrufe
9
Watching
-
@thomas4170 im aktuellen logfile von ioBroker siehst du was gerade passiert und wie weit der Benchmark ist.
@feuersturm kannst Du mir bitte Aufzeigen wie ich da ran komme?
-
Ich habe mit
cd /opt/iobroker/logund
lsdas Log
iobroker.2022-02-26.logmit nano geöffnet und das steht im Log.
2022-02-26 15:45:45.457 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker add admin --host PI-IOBROKER 2022-02-26 15:45:47.620 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER create instance admin 2022-02-26 15:45:47.632 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.updatesList created 2022-02-26 15:45:47.664 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.newsLastId created 2022-02-26 15:45:47.696 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.newsETag created 2022-02-26 15:45:47.728 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.newsFeed created 2022-02-26 15:45:47.760 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.connection created 2022-02-26 15:45:47.792 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1 created 2022-02-26 15:45:47.823 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info created 2022-02-26 15:45:47.860 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.upload created 2022-02-26 15:45:47.896 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.logLevel created 2022-02-26 15:45:47.930 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.sigKill created 2022-02-26 15:45:47.964 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.eventLoopLag created 2022-02-26 15:45:47.999 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.outputCount created 2022-02-26 15:45:48.036 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.inputCount created 2022-02-26 15:45:48.076 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.uptime created 2022-02-26 15:45:48.115 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.memRss created 2022-02-26 15:45:48.154 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.memHeapTotal created 2022-02-26 15:45:48.189 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.memHeapUsed created 2022-02-26 15:45:48.227 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.cputime created 2022-02-26 15:45:48.264 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.cpu created 2022-02-26 15:45:48.301 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.compactMode created 2022-02-26 15:45:48.337 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.connected created 2022-02-26 15:45:48.375 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.alive created 2022-02-26 15:45:48.410 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Set default value of admin.1.info.updatesList: 2022-02-26 15:45:48.438 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Set default value of admin.1.info.connection: 2022-02-26 15:45:48.507 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1 created 2022-02-26 15:45:49.546 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker exit 0 2022-02-26 15:45:51.565 - ^[[32minfo^[[39m: host.PI-IOBROKER instance system.adapter.admin.1 started with pid 20365 2022-02-26 15:45:53.967 - ^[[32minfo^[[39m: admin.1 (20365) starting. Version 5.2.3 in /opt/iobroker/node_modules/iobroker.admin, node: v16.14.0, js-controller: 3.3.22 2022-02-26 15:45:54.021 - ^[[32minfo^[[39m: admin.1 (20365) requesting all states 2022-02-26 15:45:54.023 - ^[[32minfo^[[39m: admin.1 (20365) requesting all objects 2022-02-26 15:45:54.843 - ^[[32minfo^[[39m: admin.1 (20365) received all objects 2022-02-26 15:45:55.152 - ^[[31merror^[[39m: admin.1 (20365) port 8081 already in use 2022-02-26 15:45:55.154 - ^[[32minfo^[[39m: admin.1 (20365) Terminated (ADAPTER_REQUESTED_TERMINATION): port 8081 already in use 2022-02-26 15:45:55.670 - ^[[32minfo^[[39m: admin.1 (20365) terminating http server on port 8081 2022-02-26 15:45:55.722 - ^[[31merror^[[39m: host.PI-IOBROKER instance system.adapter.admin.1 terminated by request of the instance itself and will not be restarted, before user restarts it. 2022-02-26 15:45:55.724 - ^[[32minfo^[[39m: host.PI-IOBROKER Do not restart adapter system.adapter.admin.1 because desired by instance 2022-02-26 15:46:21.842 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker del admin.1 2022-02-26 15:46:23.947 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker Delete adapter "admin.1" 2022-02-26 15:46:23.959 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 1 instances of admin.1 2022-02-26 15:46:23.971 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 1 channels of admin.1 2022-02-26 15:46:23.977 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 9 states of admin.1 2022-02-26 15:46:23.984 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 15 states of system.adapter.admin.1 2022-02-26 15:46:23.990 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 8 states (admin.1.*) from states 2022-02-26 15:46:23.992 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 15 states (system.adapter.admin.1.*) from states 2022-02-26 15:46:24.672 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 1 objects of admin.1 2022-02-26 15:46:24.674 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Deleting 27 object(s). 2022-02-26 15:46:25.210 - ^[[32minfo^[[39m: host.PI-IOBROKER object deleted system.adapter.admin.1 2022-02-26 15:46:25.239 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Deleting 23 state(s). 2022-02-26 15:46:26.307 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker exit 0 2022-02-26 15:52:13.099 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker upgrade admin@5.3.1 2022-02-26 15:52:15.458 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker Update admin from @5.2.3 to @5.3.1 2022-02-26 15:52:15.486 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Adapter "system.adapter.admin.0" is stopped. 2022-02-26 15:52:15.520 - ^[[32minfo^[[39m: admin.0 (9706) Adapter is disabled => stop 2022-02-26 15:52:15.532 - ^[[32minfo^[[39m: host.PI-IOBROKER "system.adapter.admin.0" disabled 2022-02-26 15:52:15.526 - ^[[32minfo^[[39m: admin.0 (9706) terminating http server on port 8081 2022-02-26 15:52:15.534 - ^[[32minfo^[[39m: host.PI-IOBROKER stopInstance system.adapter.admin.0 (force=false, process=true)Irgendwie sieht das so aus als passiert da nichts, oder?
-
Ich habe mit
cd /opt/iobroker/logund
lsdas Log
iobroker.2022-02-26.logmit nano geöffnet und das steht im Log.
2022-02-26 15:45:45.457 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker add admin --host PI-IOBROKER 2022-02-26 15:45:47.620 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER create instance admin 2022-02-26 15:45:47.632 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.updatesList created 2022-02-26 15:45:47.664 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.newsLastId created 2022-02-26 15:45:47.696 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.newsETag created 2022-02-26 15:45:47.728 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.newsFeed created 2022-02-26 15:45:47.760 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.connection created 2022-02-26 15:45:47.792 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1 created 2022-02-26 15:45:47.823 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info created 2022-02-26 15:45:47.860 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.upload created 2022-02-26 15:45:47.896 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.logLevel created 2022-02-26 15:45:47.930 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.sigKill created 2022-02-26 15:45:47.964 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.eventLoopLag created 2022-02-26 15:45:47.999 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.outputCount created 2022-02-26 15:45:48.036 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.inputCount created 2022-02-26 15:45:48.076 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.uptime created 2022-02-26 15:45:48.115 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.memRss created 2022-02-26 15:45:48.154 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.memHeapTotal created 2022-02-26 15:45:48.189 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.memHeapUsed created 2022-02-26 15:45:48.227 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.cputime created 2022-02-26 15:45:48.264 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.cpu created 2022-02-26 15:45:48.301 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.compactMode created 2022-02-26 15:45:48.337 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.connected created 2022-02-26 15:45:48.375 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.alive created 2022-02-26 15:45:48.410 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Set default value of admin.1.info.updatesList: 2022-02-26 15:45:48.438 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Set default value of admin.1.info.connection: 2022-02-26 15:45:48.507 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1 created 2022-02-26 15:45:49.546 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker exit 0 2022-02-26 15:45:51.565 - ^[[32minfo^[[39m: host.PI-IOBROKER instance system.adapter.admin.1 started with pid 20365 2022-02-26 15:45:53.967 - ^[[32minfo^[[39m: admin.1 (20365) starting. Version 5.2.3 in /opt/iobroker/node_modules/iobroker.admin, node: v16.14.0, js-controller: 3.3.22 2022-02-26 15:45:54.021 - ^[[32minfo^[[39m: admin.1 (20365) requesting all states 2022-02-26 15:45:54.023 - ^[[32minfo^[[39m: admin.1 (20365) requesting all objects 2022-02-26 15:45:54.843 - ^[[32minfo^[[39m: admin.1 (20365) received all objects 2022-02-26 15:45:55.152 - ^[[31merror^[[39m: admin.1 (20365) port 8081 already in use 2022-02-26 15:45:55.154 - ^[[32minfo^[[39m: admin.1 (20365) Terminated (ADAPTER_REQUESTED_TERMINATION): port 8081 already in use 2022-02-26 15:45:55.670 - ^[[32minfo^[[39m: admin.1 (20365) terminating http server on port 8081 2022-02-26 15:45:55.722 - ^[[31merror^[[39m: host.PI-IOBROKER instance system.adapter.admin.1 terminated by request of the instance itself and will not be restarted, before user restarts it. 2022-02-26 15:45:55.724 - ^[[32minfo^[[39m: host.PI-IOBROKER Do not restart adapter system.adapter.admin.1 because desired by instance 2022-02-26 15:46:21.842 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker del admin.1 2022-02-26 15:46:23.947 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker Delete adapter "admin.1" 2022-02-26 15:46:23.959 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 1 instances of admin.1 2022-02-26 15:46:23.971 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 1 channels of admin.1 2022-02-26 15:46:23.977 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 9 states of admin.1 2022-02-26 15:46:23.984 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 15 states of system.adapter.admin.1 2022-02-26 15:46:23.990 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 8 states (admin.1.*) from states 2022-02-26 15:46:23.992 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 15 states (system.adapter.admin.1.*) from states 2022-02-26 15:46:24.672 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 1 objects of admin.1 2022-02-26 15:46:24.674 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Deleting 27 object(s). 2022-02-26 15:46:25.210 - ^[[32minfo^[[39m: host.PI-IOBROKER object deleted system.adapter.admin.1 2022-02-26 15:46:25.239 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Deleting 23 state(s). 2022-02-26 15:46:26.307 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker exit 0 2022-02-26 15:52:13.099 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker upgrade admin@5.3.1 2022-02-26 15:52:15.458 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker Update admin from @5.2.3 to @5.3.1 2022-02-26 15:52:15.486 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Adapter "system.adapter.admin.0" is stopped. 2022-02-26 15:52:15.520 - ^[[32minfo^[[39m: admin.0 (9706) Adapter is disabled => stop 2022-02-26 15:52:15.532 - ^[[32minfo^[[39m: host.PI-IOBROKER "system.adapter.admin.0" disabled 2022-02-26 15:52:15.526 - ^[[32minfo^[[39m: admin.0 (9706) terminating http server on port 8081 2022-02-26 15:52:15.534 - ^[[32minfo^[[39m: host.PI-IOBROKER stopInstance system.adapter.admin.0 (force=false, process=true)Irgendwie sieht das so aus als passiert da nichts, oder?
@thomas4170 sagte in [beantwortet] ioBroker.benchmark, und nun?:
mit nano geöffnet und das steht im Log.
das ist ja auch nur eine Momentaufnahme!
"live" kannst du es mit
iobroker logs --watchsehenkein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@thomas4170 sagte in [beantwortet] ioBroker.benchmark, und nun?:
mit nano geöffnet und das steht im Log.
das ist ja auch nur eine Momentaufnahme!
"live" kannst du es mit
iobroker logs --watchsehen@homoran Danke für die Info
-
Ich habe mit
cd /opt/iobroker/logund
lsdas Log
iobroker.2022-02-26.logmit nano geöffnet und das steht im Log.
2022-02-26 15:45:45.457 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker add admin --host PI-IOBROKER 2022-02-26 15:45:47.620 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER create instance admin 2022-02-26 15:45:47.632 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.updatesList created 2022-02-26 15:45:47.664 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.newsLastId created 2022-02-26 15:45:47.696 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.newsETag created 2022-02-26 15:45:47.728 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.newsFeed created 2022-02-26 15:45:47.760 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info.connection created 2022-02-26 15:45:47.792 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1 created 2022-02-26 15:45:47.823 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object admin.1.info created 2022-02-26 15:45:47.860 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.upload created 2022-02-26 15:45:47.896 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.logLevel created 2022-02-26 15:45:47.930 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.sigKill created 2022-02-26 15:45:47.964 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.eventLoopLag created 2022-02-26 15:45:47.999 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.outputCount created 2022-02-26 15:45:48.036 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.inputCount created 2022-02-26 15:45:48.076 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.uptime created 2022-02-26 15:45:48.115 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.memRss created 2022-02-26 15:45:48.154 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.memHeapTotal created 2022-02-26 15:45:48.189 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.memHeapUsed created 2022-02-26 15:45:48.227 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.cputime created 2022-02-26 15:45:48.264 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.cpu created 2022-02-26 15:45:48.301 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.compactMode created 2022-02-26 15:45:48.337 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.connected created 2022-02-26 15:45:48.375 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1.alive created 2022-02-26 15:45:48.410 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Set default value of admin.1.info.updatesList: 2022-02-26 15:45:48.438 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Set default value of admin.1.info.connection: 2022-02-26 15:45:48.507 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER object system.adapter.admin.1 created 2022-02-26 15:45:49.546 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker exit 0 2022-02-26 15:45:51.565 - ^[[32minfo^[[39m: host.PI-IOBROKER instance system.adapter.admin.1 started with pid 20365 2022-02-26 15:45:53.967 - ^[[32minfo^[[39m: admin.1 (20365) starting. Version 5.2.3 in /opt/iobroker/node_modules/iobroker.admin, node: v16.14.0, js-controller: 3.3.22 2022-02-26 15:45:54.021 - ^[[32minfo^[[39m: admin.1 (20365) requesting all states 2022-02-26 15:45:54.023 - ^[[32minfo^[[39m: admin.1 (20365) requesting all objects 2022-02-26 15:45:54.843 - ^[[32minfo^[[39m: admin.1 (20365) received all objects 2022-02-26 15:45:55.152 - ^[[31merror^[[39m: admin.1 (20365) port 8081 already in use 2022-02-26 15:45:55.154 - ^[[32minfo^[[39m: admin.1 (20365) Terminated (ADAPTER_REQUESTED_TERMINATION): port 8081 already in use 2022-02-26 15:45:55.670 - ^[[32minfo^[[39m: admin.1 (20365) terminating http server on port 8081 2022-02-26 15:45:55.722 - ^[[31merror^[[39m: host.PI-IOBROKER instance system.adapter.admin.1 terminated by request of the instance itself and will not be restarted, before user restarts it. 2022-02-26 15:45:55.724 - ^[[32minfo^[[39m: host.PI-IOBROKER Do not restart adapter system.adapter.admin.1 because desired by instance 2022-02-26 15:46:21.842 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker del admin.1 2022-02-26 15:46:23.947 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker Delete adapter "admin.1" 2022-02-26 15:46:23.959 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 1 instances of admin.1 2022-02-26 15:46:23.971 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 1 channels of admin.1 2022-02-26 15:46:23.977 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 9 states of admin.1 2022-02-26 15:46:23.984 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 15 states of system.adapter.admin.1 2022-02-26 15:46:23.990 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 8 states (admin.1.*) from states 2022-02-26 15:46:23.992 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 15 states (system.adapter.admin.1.*) from states 2022-02-26 15:46:24.672 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Counted 1 objects of admin.1 2022-02-26 15:46:24.674 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Deleting 27 object(s). 2022-02-26 15:46:25.210 - ^[[32minfo^[[39m: host.PI-IOBROKER object deleted system.adapter.admin.1 2022-02-26 15:46:25.239 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Deleting 23 state(s). 2022-02-26 15:46:26.307 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker exit 0 2022-02-26 15:52:13.099 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker upgrade admin@5.3.1 2022-02-26 15:52:15.458 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker Update admin from @5.2.3 to @5.3.1 2022-02-26 15:52:15.486 - ^[[32minfo^[[39m: host.PI-IOBROKER iobroker host.PI-IOBROKER Adapter "system.adapter.admin.0" is stopped. 2022-02-26 15:52:15.520 - ^[[32minfo^[[39m: admin.0 (9706) Adapter is disabled => stop 2022-02-26 15:52:15.532 - ^[[32minfo^[[39m: host.PI-IOBROKER "system.adapter.admin.0" disabled 2022-02-26 15:52:15.526 - ^[[32minfo^[[39m: admin.0 (9706) terminating http server on port 8081 2022-02-26 15:52:15.534 - ^[[32minfo^[[39m: host.PI-IOBROKER stopInstance system.adapter.admin.0 (force=false, process=true)Irgendwie sieht das so aus als passiert da nichts, oder?
@thomas4170 In dem Log sehe ich nicht mal das benchmark überhaupt gestartet wurde, man sieht das jemand eine zweie Admin instanz angelegt hat und die admin0 gestoppt hat
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
-
@thomas4170 In dem Log sehe ich nicht mal das benchmark überhaupt gestartet wurde, man sieht das jemand eine zweie Admin instanz angelegt hat und die admin0 gestoppt hat
@apollon77 Ja das ist versehentlich bei Update des Adapter passiert, hatte ich aber wieder deinstalliert. Mehr gibt dasLog nicht her
-
@apollon77 Ja das ist versehentlich bei Update des Adapter passiert, hatte ich aber wieder deinstalliert. Mehr gibt dasLog nicht her
@thomas4170 also dann würde ich sagen starte mal Admin.0 wieder und schau nochmal. Ich sehe da nix von Benchmark at all
Beitrag hat geholfen? Votet rechts unten im Beitrag :-) https://paypal.me/Apollon77 / https://github.com/sponsors/Apollon77
- Debug-Log für Instanz einschalten? Admin -> Instanzen -> Expertenmodus -> Instanz aufklappen - Loglevel ändern
- Logfiles auf Platte /opt/iobroker/log/… nutzen, Admin schneidet Zeilen ab
-
@thomas4170 also dann würde ich sagen starte mal Admin.0 wieder und schau nochmal. Ich sehe da nix von Benchmark at all
-
@apollon77 Ok versuche ich mal
Ich hole diesen Topic mal nach oben.
Bei mir scheint der Bechmark (gestartet gestern gegen 10:00) zu "hängen" - das sind die letzten Loggings - Log für heute ist leer ...
martin@iobroker-test-sicher:~$ tail /opt/iobroker/log/iobroker.2023-06-21.log 2023-06-21 13:57:36.137 - error: benchmark.0 (8223) Exception-Code: 22: Command failed: "/usr/bin/node" "/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js" del benchmark.1 2023-06-21 13:57:36.141 - info: benchmark.0 (8223) terminating 2023-06-21 13:57:36.143 - warn: benchmark.0 (8223) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-06-21 13:57:38.586 - error: host.iobroker-test-sicher instance system.adapter.benchmark.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-06-21 13:57:38.588 - info: host.iobroker-test-sicher Restart adapter system.adapter.benchmark.0 because enabled 2023-06-21 13:58:10.589 - info: host.iobroker-test-sicher instance system.adapter.benchmark.0 started with pid 9628 2023-06-21 13:58:28.269 - warn: benchmark.0 (9628) slow connection to states DB. Still waiting ... 2023-06-21 13:58:35.054 - info: benchmark.0 (9628) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.benchmark, node: v16.20.0, js-controller: 4.0.24 2023-06-21 13:58:35.166 - info: benchmark.0 (9628) Adapter started... controller determined (pid: 354)martin@iobroker-test-sicher:~$ tail /opt/iobroker/log/iobroker.2023-06-22.log martin@iobroker-test-sicher:~$ ls /opt/iobroker/log/ iobroker-audit.json iobroker.2023-06-17.log.gz iobroker.2023-06-20.log.gz iobroker.current.log iobroker.2023-06-15.log.gz iobroker.2023-06-18.log.gz iobroker.2023-06-21.log iobroker.2023-06-16.log.gz iobroker.2023-06-19.log.gz iobroker.2023-06-22.log martin@iobroker-test-sicher:~$ tail /opt/iobroker/log/iobroker.current.log martin@iobroker-test-sicher:~$Kann man den Benchmark irgendwie "abschießen", und den ioBroker in den "normalbetrieb" zurückversetzen?
Letzter gestarteter Test scheint zu sein
2023-06-21 11:41:10.858 - info: benchmark.0 (8223) Starting test "setStatesParallel"Intel(R) Celeron(R) CPU N3000 @ 1.04GHz 8G RAM 480G SSD
Virtualization : unprivileged lxc container (debian 12 on Proxmox 8.4.14)
Linux pve 6.8.12-16-pve
6 GByte RAM für den Container
Fritzbox 6591 FW 8.03 (Vodafone Leih-Box)
Remote-Access über Wireguard der Fritzbox -
Ich hole diesen Topic mal nach oben.
Bei mir scheint der Bechmark (gestartet gestern gegen 10:00) zu "hängen" - das sind die letzten Loggings - Log für heute ist leer ...
martin@iobroker-test-sicher:~$ tail /opt/iobroker/log/iobroker.2023-06-21.log 2023-06-21 13:57:36.137 - error: benchmark.0 (8223) Exception-Code: 22: Command failed: "/usr/bin/node" "/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js" del benchmark.1 2023-06-21 13:57:36.141 - info: benchmark.0 (8223) terminating 2023-06-21 13:57:36.143 - warn: benchmark.0 (8223) Terminated (UNCAUGHT_EXCEPTION): Without reason 2023-06-21 13:57:38.586 - error: host.iobroker-test-sicher instance system.adapter.benchmark.0 terminated with code 6 (UNCAUGHT_EXCEPTION) 2023-06-21 13:57:38.588 - info: host.iobroker-test-sicher Restart adapter system.adapter.benchmark.0 because enabled 2023-06-21 13:58:10.589 - info: host.iobroker-test-sicher instance system.adapter.benchmark.0 started with pid 9628 2023-06-21 13:58:28.269 - warn: benchmark.0 (9628) slow connection to states DB. Still waiting ... 2023-06-21 13:58:35.054 - info: benchmark.0 (9628) starting. Version 1.1.4 in /opt/iobroker/node_modules/iobroker.benchmark, node: v16.20.0, js-controller: 4.0.24 2023-06-21 13:58:35.166 - info: benchmark.0 (9628) Adapter started... controller determined (pid: 354)martin@iobroker-test-sicher:~$ tail /opt/iobroker/log/iobroker.2023-06-22.log martin@iobroker-test-sicher:~$ ls /opt/iobroker/log/ iobroker-audit.json iobroker.2023-06-17.log.gz iobroker.2023-06-20.log.gz iobroker.current.log iobroker.2023-06-15.log.gz iobroker.2023-06-18.log.gz iobroker.2023-06-21.log iobroker.2023-06-16.log.gz iobroker.2023-06-19.log.gz iobroker.2023-06-22.log martin@iobroker-test-sicher:~$ tail /opt/iobroker/log/iobroker.current.log martin@iobroker-test-sicher:~$Kann man den Benchmark irgendwie "abschießen", und den ioBroker in den "normalbetrieb" zurückversetzen?
Letzter gestarteter Test scheint zu sein
2023-06-21 11:41:10.858 - info: benchmark.0 (8223) Starting test "setStatesParallel"@martinp sagte in [beantwortet] ioBroker.benchmark, und nun?:
2023-06-21 13:57:38.586 - error: host.iobroker-test-sicher instance system.adapter.benchmark.0 terminated with code 6 (UNCAUGHT_EXCEPTION)das hab ich im anderen Thread wohl übersehen
@martinp sagte in [beantwortet] ioBroker.benchmark, und nun?:
Kann man den Benchmark irgendwie "abschießen",
ich würde es mit
iob stop benchmarkversuchen und zur Sicherheit mittopmal nachsehen was da noch läuft.
dann ggf. mit Instanz ID wiederholen z.B.iob stop benchmark.24 -
@martinp
iob start allbzwiob start adminholt alle Adapter wieder hoch. Bzw Admin.Und ja da hab’s ne uncaught exception leider sieht man keine Details aber er konnte Benchmark 1 nicht löschen.
In den Einstellungen von Benchmark gibt es nen Button cleanup der sollte alle Test States etc aufräumen nach einem fehlgeschlagenen run.
Hier könnt ihr mich unterstützen.
-
@martinp
iob start allbzwiob start adminholt alle Adapter wieder hoch. Bzw Admin.Und ja da hab’s ne uncaught exception leider sieht man keine Details aber er konnte Benchmark 1 nicht löschen.
In den Einstellungen von Benchmark gibt es nen Button cleanup der sollte alle Test States etc aufräumen nach einem fehlgeschlagenen run.
okay, mit "iob start all" holt man sich die Oberfläche im Browser zurück, und kann dann auch wieder auf die Einstellung von Benchmark zugreifen ...
Korrekt?
Hier die Ausgabe für den ersten Versuch angeregt aus dem vorletzten Post
martin@iobroker-test-sicher:~$ iob stop benchmark Cannot determine Lua scripts strategy: Connection is closed. ["cfg.o.system.host.iobroker-test-sicher"] Unable to subscribe to meta namespace "meta." changes: Connection is closed. No connection to databases possible ... martin@iobroker-test-sicher:~$EDIT:
habe als Erstes mit "iob stop benchmark.x" mit x=0 ... 30 sukzessive alle Instanzen abgeschossen
Danach "iob start all"
Die Oberfläche ist aber noch nicht ganz operationell. Kann mir die Objekte anschauen, aber die Sidebar links ist noch leer
EDIT2:
Die Benchmarks wurden nach "iob start all" auch wieder mit gestartet ... kann man das irgendwie verhindern?
Wahrscheinlich bin ich jetzt in einen komischen Zustand gelangt - Habe die Benchmark-Objekte gelöscht ...2023-06-22 11:03:01.805 - error: host.iobroker-test-sicher iobroker /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:301:12)Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at processTicksAndRejections (node:internal/process/task_queues:96:5) 2023-06-22 11:03:01.843 - info: host.iobroker-test-sicher iobroker exit 1EDIT3:
Die Benchmark-Instanzen (Benchmark 0 ..... Benchmark 30) für die parallelisierte Ausführung sind im Objektbaum geblieben. Laufen zwar nicht, als Karteileichen sehen sie aber nicht nett aus ...Die Ausgabe, wenn ich sie per Kommandozeile lösche, sieht beendruckend aus ...
martin@iobroker-test-sicher:~$ iobroker del benchmark.4 Delete instance "benchmark.4" host.iobroker-test-sicher Counted 1 instances of benchmark.4 host.iobroker-test-sicher Counted 10001 states of benchmark.4 host.iobroker-test-sicher Counted 14 states of system.adapter.benchmark.4 host.iobroker-test-sicher Counted 10000 states (io.benchmark.4.*) from states host.iobroker-test-sicher Counted 14 states (system.adapter.benchmark.4.*) from states host.iobroker-test-sicher Deleting 10016 object(s). Be patient... host.iobroker-test-sicher: Only 10000 objects left to be deleted. host.iobroker-test-sicher: Only 9800 objects left to be deleted. host.iobroker-test-sicher: Only 9600 objects left to be deleted. host.iobroker-test-sicher: Only 9400 objects left to be deleted. host.iobroker-test-sicher: Only 9200 objects left to be deleted. host.iobroker-test-sicher: Only 9000 objects left to be deleted. host.iobroker-test-sicher: Only 8800 objects left to be deleted. host.iobroker-test-sicher: Only 8600 objects left to be deleted. host.iobroker-test-sicher: Only 8400 objects left to be deleted. host.iobroker-test-sicher: Only 8200 objects left to be deleted. host.iobroker-test-sicher: Only 8000 objects left to be deleted. host.iobroker-test-sicher: Only 7800 objects left to be deleted. host.iobroker-test-sicher: Only 7600 objects left to be deleted. host.iobroker-test-sicher: Only 7400 objects left to be deleted. host.iobroker-test-sicher: Only 7200 objects left to be deleted. host.iobroker-test-sicher: Only 7000 objects left to be deleted. host.iobroker-test-sicher: Only 6800 objects left to be deleted. host.iobroker-test-sicher: Only 6600 objects left to be deleted. host.iobroker-test-sicher: Only 6400 objects left to be deleted. host.iobroker-test-sicher: Only 6200 objects left to be deleted. host.iobroker-test-sicher: Only 6000 objects left to be deleted. host.iobroker-test-sicher: Only 5800 objects left to be deleted. host.iobroker-test-sicher: Only 5600 objects left to be deleted. host.iobroker-test-sicher: Only 5400 objects left to be deleted. host.iobroker-test-sicher: Only 5200 objects left to be deleted. host.iobroker-test-sicher: Only 5000 objects left to be deleted. host.iobroker-test-sicher: Only 4800 objects left to be deleted. host.iobroker-test-sicher: Only 4600 objects left to be deleted. host.iobroker-test-sicher: Only 4400 objects left to be deleted. host.iobroker-test-sicher: Only 4200 objects left to be deleted. host.iobroker-test-sicher: Only 4000 objects left to be deleted. host.iobroker-test-sicher: Only 3800 objects left to be deleted. host.iobroker-test-sicher: Only 3600 objects left to be deleted. host.iobroker-test-sicher: Only 3400 objects left to be deleted. host.iobroker-test-sicher: Only 3200 objects left to be deleted. host.iobroker-test-sicher: Only 3000 objects left to be deleted. host.iobroker-test-sicher: Only 2800 objects left to be deleted. host.iobroker-test-sicher: Only 2600 objects left to be deleted. host.iobroker-test-sicher: Only 2400 objects left to be deleted. host.iobroker-test-sicher: Only 2200 objects left to be deleted. host.iobroker-test-sicher: Only 2000 objects left to be deleted. host.iobroker-test-sicher: Only 1800 objects left to be deleted. host.iobroker-test-sicher: Only 1600 objects left to be deleted. host.iobroker-test-sicher: Only 1400 objects left to be deleted. host.iobroker-test-sicher: Only 1200 objects left to be deleted. host.iobroker-test-sicher: Only 1000 objects left to be deleted. host.iobroker-test-sicher: Only 800 objects left to be deleted. host.iobroker-test-sicher: Only 600 objects left to be deleted. host.iobroker-test-sicher: Only 400 objects left to be deleted. host.iobroker-test-sicher: Only 200 objects left to be deleted. host.iobroker-test-sicher Deleting 10014 state(s). Be patient... host.iobroker-test-sicher: Only 10000 states left to be deleted. host.iobroker-test-sicher: Only 9800 states left to be deleted. host.iobroker-test-sicher: Only 9600 states left to be deleted. host.iobroker-test-sicher: Only 9400 states left to be deleted. host.iobroker-test-sicher: Only 9200 states left to be deleted. host.iobroker-test-sicher: Only 9000 states left to be deleted. host.iobroker-test-sicher: Only 8800 states left to be deleted. host.iobroker-test-sicher: Only 8600 states left to be deleted. host.iobroker-test-sicher: Only 8400 states left to be deleted. host.iobroker-test-sicher: Only 8200 states left to be deleted. host.iobroker-test-sicher: Only 8000 states left to be deleted. host.iobroker-test-sicher: Only 7800 states left to be deleted. host.iobroker-test-sicher: Only 7600 states left to be deleted. host.iobroker-test-sicher: Only 7400 states left to be deleted. host.iobroker-test-sicher: Only 7200 states left to be deleted. host.iobroker-test-sicher: Only 7000 states left to be deleted. host.iobroker-test-sicher: Only 6800 states left to be deleted. host.iobroker-test-sicher: Only 6600 states left to be deleted. host.iobroker-test-sicher: Only 6400 states left to be deleted. host.iobroker-test-sicher: Only 6200 states left to be deleted. host.iobroker-test-sicher: Only 6000 states left to be deleted. host.iobroker-test-sicher: Only 5800 states left to be deleted. host.iobroker-test-sicher: Only 5600 states left to be deleted. host.iobroker-test-sicher: Only 5400 states left to be deleted. host.iobroker-test-sicher: Only 5200 states left to be deleted. host.iobroker-test-sicher: Only 5000 states left to be deleted. host.iobroker-test-sicher: Only 4800 states left to be deleted. host.iobroker-test-sicher: Only 4600 states left to be deleted. host.iobroker-test-sicher: Only 4400 states left to be deleted. host.iobroker-test-sicher: Only 4200 states left to be deleted. host.iobroker-test-sicher: Only 4000 states left to be deleted. host.iobroker-test-sicher: Only 3800 states left to be deleted. host.iobroker-test-sicher: Only 3600 states left to be deleted. host.iobroker-test-sicher: Only 3400 states left to be deleted. host.iobroker-test-sicher: Only 3200 states left to be deleted. host.iobroker-test-sicher: Only 3000 states left to be deleted. host.iobroker-test-sicher: Only 2800 states left to be deleted. host.iobroker-test-sicher: Only 2600 states left to be deleted. host.iobroker-test-sicher: Only 2400 states left to be deleted. host.iobroker-test-sicher: Only 2200 states left to be deleted. host.iobroker-test-sicher: Only 2000 states left to be deleted. host.iobroker-test-sicher: Only 1800 states left to be deleted. host.iobroker-test-sicher: Only 1600 states left to be deleted. host.iobroker-test-sicher: Only 1400 states left to be deleted. host.iobroker-test-sicher: Only 1200 states left to be deleted. host.iobroker-test-sicher: Only 1000 states left to be deleted. host.iobroker-test-sicher: Only 800 states left to be deleted. host.iobroker-test-sicher: Only 600 states left to be deleted. host.iobroker-test-sicher: Only 400 states left to be deleted. host.iobroker-test-sicher: Only 200 states left to be deleted. martin@iobroker-test-sicher:~$Intel(R) Celeron(R) CPU N3000 @ 1.04GHz 8G RAM 480G SSD
Virtualization : unprivileged lxc container (debian 12 on Proxmox 8.4.14)
Linux pve 6.8.12-16-pve
6 GByte RAM für den Container
Fritzbox 6591 FW 8.03 (Vodafone Leih-Box)
Remote-Access über Wireguard der Fritzbox -
okay, mit "iob start all" holt man sich die Oberfläche im Browser zurück, und kann dann auch wieder auf die Einstellung von Benchmark zugreifen ...
Korrekt?
Hier die Ausgabe für den ersten Versuch angeregt aus dem vorletzten Post
martin@iobroker-test-sicher:~$ iob stop benchmark Cannot determine Lua scripts strategy: Connection is closed. ["cfg.o.system.host.iobroker-test-sicher"] Unable to subscribe to meta namespace "meta." changes: Connection is closed. No connection to databases possible ... martin@iobroker-test-sicher:~$EDIT:
habe als Erstes mit "iob stop benchmark.x" mit x=0 ... 30 sukzessive alle Instanzen abgeschossen
Danach "iob start all"
Die Oberfläche ist aber noch nicht ganz operationell. Kann mir die Objekte anschauen, aber die Sidebar links ist noch leer
EDIT2:
Die Benchmarks wurden nach "iob start all" auch wieder mit gestartet ... kann man das irgendwie verhindern?
Wahrscheinlich bin ich jetzt in einen komischen Zustand gelangt - Habe die Benchmark-Objekte gelöscht ...2023-06-22 11:03:01.805 - error: host.iobroker-test-sicher iobroker /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:301:12)Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at processTicksAndRejections (node:internal/process/task_queues:96:5) 2023-06-22 11:03:01.843 - info: host.iobroker-test-sicher iobroker exit 1EDIT3:
Die Benchmark-Instanzen (Benchmark 0 ..... Benchmark 30) für die parallelisierte Ausführung sind im Objektbaum geblieben. Laufen zwar nicht, als Karteileichen sehen sie aber nicht nett aus ...Die Ausgabe, wenn ich sie per Kommandozeile lösche, sieht beendruckend aus ...
martin@iobroker-test-sicher:~$ iobroker del benchmark.4 Delete instance "benchmark.4" host.iobroker-test-sicher Counted 1 instances of benchmark.4 host.iobroker-test-sicher Counted 10001 states of benchmark.4 host.iobroker-test-sicher Counted 14 states of system.adapter.benchmark.4 host.iobroker-test-sicher Counted 10000 states (io.benchmark.4.*) from states host.iobroker-test-sicher Counted 14 states (system.adapter.benchmark.4.*) from states host.iobroker-test-sicher Deleting 10016 object(s). Be patient... host.iobroker-test-sicher: Only 10000 objects left to be deleted. host.iobroker-test-sicher: Only 9800 objects left to be deleted. host.iobroker-test-sicher: Only 9600 objects left to be deleted. host.iobroker-test-sicher: Only 9400 objects left to be deleted. host.iobroker-test-sicher: Only 9200 objects left to be deleted. host.iobroker-test-sicher: Only 9000 objects left to be deleted. host.iobroker-test-sicher: Only 8800 objects left to be deleted. host.iobroker-test-sicher: Only 8600 objects left to be deleted. host.iobroker-test-sicher: Only 8400 objects left to be deleted. host.iobroker-test-sicher: Only 8200 objects left to be deleted. host.iobroker-test-sicher: Only 8000 objects left to be deleted. host.iobroker-test-sicher: Only 7800 objects left to be deleted. host.iobroker-test-sicher: Only 7600 objects left to be deleted. host.iobroker-test-sicher: Only 7400 objects left to be deleted. host.iobroker-test-sicher: Only 7200 objects left to be deleted. host.iobroker-test-sicher: Only 7000 objects left to be deleted. host.iobroker-test-sicher: Only 6800 objects left to be deleted. host.iobroker-test-sicher: Only 6600 objects left to be deleted. host.iobroker-test-sicher: Only 6400 objects left to be deleted. host.iobroker-test-sicher: Only 6200 objects left to be deleted. host.iobroker-test-sicher: Only 6000 objects left to be deleted. host.iobroker-test-sicher: Only 5800 objects left to be deleted. host.iobroker-test-sicher: Only 5600 objects left to be deleted. host.iobroker-test-sicher: Only 5400 objects left to be deleted. host.iobroker-test-sicher: Only 5200 objects left to be deleted. host.iobroker-test-sicher: Only 5000 objects left to be deleted. host.iobroker-test-sicher: Only 4800 objects left to be deleted. host.iobroker-test-sicher: Only 4600 objects left to be deleted. host.iobroker-test-sicher: Only 4400 objects left to be deleted. host.iobroker-test-sicher: Only 4200 objects left to be deleted. host.iobroker-test-sicher: Only 4000 objects left to be deleted. host.iobroker-test-sicher: Only 3800 objects left to be deleted. host.iobroker-test-sicher: Only 3600 objects left to be deleted. host.iobroker-test-sicher: Only 3400 objects left to be deleted. host.iobroker-test-sicher: Only 3200 objects left to be deleted. host.iobroker-test-sicher: Only 3000 objects left to be deleted. host.iobroker-test-sicher: Only 2800 objects left to be deleted. host.iobroker-test-sicher: Only 2600 objects left to be deleted. host.iobroker-test-sicher: Only 2400 objects left to be deleted. host.iobroker-test-sicher: Only 2200 objects left to be deleted. host.iobroker-test-sicher: Only 2000 objects left to be deleted. host.iobroker-test-sicher: Only 1800 objects left to be deleted. host.iobroker-test-sicher: Only 1600 objects left to be deleted. host.iobroker-test-sicher: Only 1400 objects left to be deleted. host.iobroker-test-sicher: Only 1200 objects left to be deleted. host.iobroker-test-sicher: Only 1000 objects left to be deleted. host.iobroker-test-sicher: Only 800 objects left to be deleted. host.iobroker-test-sicher: Only 600 objects left to be deleted. host.iobroker-test-sicher: Only 400 objects left to be deleted. host.iobroker-test-sicher: Only 200 objects left to be deleted. host.iobroker-test-sicher Deleting 10014 state(s). Be patient... host.iobroker-test-sicher: Only 10000 states left to be deleted. host.iobroker-test-sicher: Only 9800 states left to be deleted. host.iobroker-test-sicher: Only 9600 states left to be deleted. host.iobroker-test-sicher: Only 9400 states left to be deleted. host.iobroker-test-sicher: Only 9200 states left to be deleted. host.iobroker-test-sicher: Only 9000 states left to be deleted. host.iobroker-test-sicher: Only 8800 states left to be deleted. host.iobroker-test-sicher: Only 8600 states left to be deleted. host.iobroker-test-sicher: Only 8400 states left to be deleted. host.iobroker-test-sicher: Only 8200 states left to be deleted. host.iobroker-test-sicher: Only 8000 states left to be deleted. host.iobroker-test-sicher: Only 7800 states left to be deleted. host.iobroker-test-sicher: Only 7600 states left to be deleted. host.iobroker-test-sicher: Only 7400 states left to be deleted. host.iobroker-test-sicher: Only 7200 states left to be deleted. host.iobroker-test-sicher: Only 7000 states left to be deleted. host.iobroker-test-sicher: Only 6800 states left to be deleted. host.iobroker-test-sicher: Only 6600 states left to be deleted. host.iobroker-test-sicher: Only 6400 states left to be deleted. host.iobroker-test-sicher: Only 6200 states left to be deleted. host.iobroker-test-sicher: Only 6000 states left to be deleted. host.iobroker-test-sicher: Only 5800 states left to be deleted. host.iobroker-test-sicher: Only 5600 states left to be deleted. host.iobroker-test-sicher: Only 5400 states left to be deleted. host.iobroker-test-sicher: Only 5200 states left to be deleted. host.iobroker-test-sicher: Only 5000 states left to be deleted. host.iobroker-test-sicher: Only 4800 states left to be deleted. host.iobroker-test-sicher: Only 4600 states left to be deleted. host.iobroker-test-sicher: Only 4400 states left to be deleted. host.iobroker-test-sicher: Only 4200 states left to be deleted. host.iobroker-test-sicher: Only 4000 states left to be deleted. host.iobroker-test-sicher: Only 3800 states left to be deleted. host.iobroker-test-sicher: Only 3600 states left to be deleted. host.iobroker-test-sicher: Only 3400 states left to be deleted. host.iobroker-test-sicher: Only 3200 states left to be deleted. host.iobroker-test-sicher: Only 3000 states left to be deleted. host.iobroker-test-sicher: Only 2800 states left to be deleted. host.iobroker-test-sicher: Only 2600 states left to be deleted. host.iobroker-test-sicher: Only 2400 states left to be deleted. host.iobroker-test-sicher: Only 2200 states left to be deleted. host.iobroker-test-sicher: Only 2000 states left to be deleted. host.iobroker-test-sicher: Only 1800 states left to be deleted. host.iobroker-test-sicher: Only 1600 states left to be deleted. host.iobroker-test-sicher: Only 1400 states left to be deleted. host.iobroker-test-sicher: Only 1200 states left to be deleted. host.iobroker-test-sicher: Only 1000 states left to be deleted. host.iobroker-test-sicher: Only 800 states left to be deleted. host.iobroker-test-sicher: Only 600 states left to be deleted. host.iobroker-test-sicher: Only 400 states left to be deleted. host.iobroker-test-sicher: Only 200 states left to be deleted. martin@iobroker-test-sicher:~$ -
okay, mit "iob start all" holt man sich die Oberfläche im Browser zurück, und kann dann auch wieder auf die Einstellung von Benchmark zugreifen ...
Korrekt?
Hier die Ausgabe für den ersten Versuch angeregt aus dem vorletzten Post
martin@iobroker-test-sicher:~$ iob stop benchmark Cannot determine Lua scripts strategy: Connection is closed. ["cfg.o.system.host.iobroker-test-sicher"] Unable to subscribe to meta namespace "meta." changes: Connection is closed. No connection to databases possible ... martin@iobroker-test-sicher:~$EDIT:
habe als Erstes mit "iob stop benchmark.x" mit x=0 ... 30 sukzessive alle Instanzen abgeschossen
Danach "iob start all"
Die Oberfläche ist aber noch nicht ganz operationell. Kann mir die Objekte anschauen, aber die Sidebar links ist noch leer
EDIT2:
Die Benchmarks wurden nach "iob start all" auch wieder mit gestartet ... kann man das irgendwie verhindern?
Wahrscheinlich bin ich jetzt in einen komischen Zustand gelangt - Habe die Benchmark-Objekte gelöscht ...2023-06-22 11:03:01.805 - error: host.iobroker-test-sicher iobroker /opt/iobroker/node_modules/standard-as-callback/built/index.js:6 throw e; ^Error: Connection is closed. at close (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:184:25) at Socket.<anonymous> (/opt/iobroker/node_modules/ioredis/built/redis/event_handler.js:151:20) at Object.onceWrapper (node:events:628:26) at Socket.emit (node:events:513:28) at TCP.<anonymous> (node:net:301:12)Emitted 'error' event on ScanStream instance at: at /opt/iobroker/node_modules/ioredis/built/ScanStream.js:38:22 at tryCatcher (/opt/iobroker/node_modules/standard-as-callback/built/utils.js:12:23) at /opt/iobroker/node_modules/standard-as-callback/built/index.js:33:51 at processTicksAndRejections (node:internal/process/task_queues:96:5) 2023-06-22 11:03:01.843 - info: host.iobroker-test-sicher iobroker exit 1EDIT3:
Die Benchmark-Instanzen (Benchmark 0 ..... Benchmark 30) für die parallelisierte Ausführung sind im Objektbaum geblieben. Laufen zwar nicht, als Karteileichen sehen sie aber nicht nett aus ...Die Ausgabe, wenn ich sie per Kommandozeile lösche, sieht beendruckend aus ...
martin@iobroker-test-sicher:~$ iobroker del benchmark.4 Delete instance "benchmark.4" host.iobroker-test-sicher Counted 1 instances of benchmark.4 host.iobroker-test-sicher Counted 10001 states of benchmark.4 host.iobroker-test-sicher Counted 14 states of system.adapter.benchmark.4 host.iobroker-test-sicher Counted 10000 states (io.benchmark.4.*) from states host.iobroker-test-sicher Counted 14 states (system.adapter.benchmark.4.*) from states host.iobroker-test-sicher Deleting 10016 object(s). Be patient... host.iobroker-test-sicher: Only 10000 objects left to be deleted. host.iobroker-test-sicher: Only 9800 objects left to be deleted. host.iobroker-test-sicher: Only 9600 objects left to be deleted. host.iobroker-test-sicher: Only 9400 objects left to be deleted. host.iobroker-test-sicher: Only 9200 objects left to be deleted. host.iobroker-test-sicher: Only 9000 objects left to be deleted. host.iobroker-test-sicher: Only 8800 objects left to be deleted. host.iobroker-test-sicher: Only 8600 objects left to be deleted. host.iobroker-test-sicher: Only 8400 objects left to be deleted. host.iobroker-test-sicher: Only 8200 objects left to be deleted. host.iobroker-test-sicher: Only 8000 objects left to be deleted. host.iobroker-test-sicher: Only 7800 objects left to be deleted. host.iobroker-test-sicher: Only 7600 objects left to be deleted. host.iobroker-test-sicher: Only 7400 objects left to be deleted. host.iobroker-test-sicher: Only 7200 objects left to be deleted. host.iobroker-test-sicher: Only 7000 objects left to be deleted. host.iobroker-test-sicher: Only 6800 objects left to be deleted. host.iobroker-test-sicher: Only 6600 objects left to be deleted. host.iobroker-test-sicher: Only 6400 objects left to be deleted. host.iobroker-test-sicher: Only 6200 objects left to be deleted. host.iobroker-test-sicher: Only 6000 objects left to be deleted. host.iobroker-test-sicher: Only 5800 objects left to be deleted. host.iobroker-test-sicher: Only 5600 objects left to be deleted. host.iobroker-test-sicher: Only 5400 objects left to be deleted. host.iobroker-test-sicher: Only 5200 objects left to be deleted. host.iobroker-test-sicher: Only 5000 objects left to be deleted. host.iobroker-test-sicher: Only 4800 objects left to be deleted. host.iobroker-test-sicher: Only 4600 objects left to be deleted. host.iobroker-test-sicher: Only 4400 objects left to be deleted. host.iobroker-test-sicher: Only 4200 objects left to be deleted. host.iobroker-test-sicher: Only 4000 objects left to be deleted. host.iobroker-test-sicher: Only 3800 objects left to be deleted. host.iobroker-test-sicher: Only 3600 objects left to be deleted. host.iobroker-test-sicher: Only 3400 objects left to be deleted. host.iobroker-test-sicher: Only 3200 objects left to be deleted. host.iobroker-test-sicher: Only 3000 objects left to be deleted. host.iobroker-test-sicher: Only 2800 objects left to be deleted. host.iobroker-test-sicher: Only 2600 objects left to be deleted. host.iobroker-test-sicher: Only 2400 objects left to be deleted. host.iobroker-test-sicher: Only 2200 objects left to be deleted. host.iobroker-test-sicher: Only 2000 objects left to be deleted. host.iobroker-test-sicher: Only 1800 objects left to be deleted. host.iobroker-test-sicher: Only 1600 objects left to be deleted. host.iobroker-test-sicher: Only 1400 objects left to be deleted. host.iobroker-test-sicher: Only 1200 objects left to be deleted. host.iobroker-test-sicher: Only 1000 objects left to be deleted. host.iobroker-test-sicher: Only 800 objects left to be deleted. host.iobroker-test-sicher: Only 600 objects left to be deleted. host.iobroker-test-sicher: Only 400 objects left to be deleted. host.iobroker-test-sicher: Only 200 objects left to be deleted. host.iobroker-test-sicher Deleting 10014 state(s). Be patient... host.iobroker-test-sicher: Only 10000 states left to be deleted. host.iobroker-test-sicher: Only 9800 states left to be deleted. host.iobroker-test-sicher: Only 9600 states left to be deleted. host.iobroker-test-sicher: Only 9400 states left to be deleted. host.iobroker-test-sicher: Only 9200 states left to be deleted. host.iobroker-test-sicher: Only 9000 states left to be deleted. host.iobroker-test-sicher: Only 8800 states left to be deleted. host.iobroker-test-sicher: Only 8600 states left to be deleted. host.iobroker-test-sicher: Only 8400 states left to be deleted. host.iobroker-test-sicher: Only 8200 states left to be deleted. host.iobroker-test-sicher: Only 8000 states left to be deleted. host.iobroker-test-sicher: Only 7800 states left to be deleted. host.iobroker-test-sicher: Only 7600 states left to be deleted. host.iobroker-test-sicher: Only 7400 states left to be deleted. host.iobroker-test-sicher: Only 7200 states left to be deleted. host.iobroker-test-sicher: Only 7000 states left to be deleted. host.iobroker-test-sicher: Only 6800 states left to be deleted. host.iobroker-test-sicher: Only 6600 states left to be deleted. host.iobroker-test-sicher: Only 6400 states left to be deleted. host.iobroker-test-sicher: Only 6200 states left to be deleted. host.iobroker-test-sicher: Only 6000 states left to be deleted. host.iobroker-test-sicher: Only 5800 states left to be deleted. host.iobroker-test-sicher: Only 5600 states left to be deleted. host.iobroker-test-sicher: Only 5400 states left to be deleted. host.iobroker-test-sicher: Only 5200 states left to be deleted. host.iobroker-test-sicher: Only 5000 states left to be deleted. host.iobroker-test-sicher: Only 4800 states left to be deleted. host.iobroker-test-sicher: Only 4600 states left to be deleted. host.iobroker-test-sicher: Only 4400 states left to be deleted. host.iobroker-test-sicher: Only 4200 states left to be deleted. host.iobroker-test-sicher: Only 4000 states left to be deleted. host.iobroker-test-sicher: Only 3800 states left to be deleted. host.iobroker-test-sicher: Only 3600 states left to be deleted. host.iobroker-test-sicher: Only 3400 states left to be deleted. host.iobroker-test-sicher: Only 3200 states left to be deleted. host.iobroker-test-sicher: Only 3000 states left to be deleted. host.iobroker-test-sicher: Only 2800 states left to be deleted. host.iobroker-test-sicher: Only 2600 states left to be deleted. host.iobroker-test-sicher: Only 2400 states left to be deleted. host.iobroker-test-sicher: Only 2200 states left to be deleted. host.iobroker-test-sicher: Only 2000 states left to be deleted. host.iobroker-test-sicher: Only 1800 states left to be deleted. host.iobroker-test-sicher: Only 1600 states left to be deleted. host.iobroker-test-sicher: Only 1400 states left to be deleted. host.iobroker-test-sicher: Only 1200 states left to be deleted. host.iobroker-test-sicher: Only 1000 states left to be deleted. host.iobroker-test-sicher: Only 800 states left to be deleted. host.iobroker-test-sicher: Only 600 states left to be deleted. host.iobroker-test-sicher: Only 400 states left to be deleted. host.iobroker-test-sicher: Only 200 states left to be deleted. martin@iobroker-test-sicher:~$@martinp sagte in [beantwortet] ioBroker.benchmark, und nun?:
Die Benchmarks wurden nach "iob start all" auch wieder mit gestartet ... kann man das irgendwie verhindern?
nöö, all ist eben all :-)
iob start adminund dann dort manuell alles gewünschte anklicken.@martinp sagte in [beantwortet] ioBroker.benchmark, und nun?:
als Karteileichen sehen sie aber nicht nett aus ...
kannst du auch im admin als Baum löschen.
@martinp sagte in [beantwortet] ioBroker.benchmark, und nun?:
habe als Erstes mit "iob stop benchmark.x" mit x=0 ... 30 sukzessive alle Instanzen abgeschossen
jepp. so hatte ich das gemeint
nur schade, dass die Informationen jetztvmal wieder auf mehrere Threads verteilt sind
kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@martinp sagte in [beantwortet] ioBroker.benchmark, und nun?:
Die Benchmarks wurden nach "iob start all" auch wieder mit gestartet ... kann man das irgendwie verhindern?
nöö, all ist eben all :-)
iob start adminund dann dort manuell alles gewünschte anklicken.@martinp sagte in [beantwortet] ioBroker.benchmark, und nun?:
als Karteileichen sehen sie aber nicht nett aus ...
kannst du auch im admin als Baum löschen.
@martinp sagte in [beantwortet] ioBroker.benchmark, und nun?:
habe als Erstes mit "iob stop benchmark.x" mit x=0 ... 30 sukzessive alle Instanzen abgeschossen
jepp. so hatte ich das gemeint
nur schade, dass die Informationen jetztvmal wieder auf mehrere Threads verteilt sind
@homoran Ich dachte der hier hätte ältere Rechte ;-) in Medias Res gibt es ja erst in den letzten Beiträgen ...
Bei einem LXC Container ist es wahrscheinlich die naheliegenste Lösung, wenn der Benchmark so lange blockieren kann, und dann auch ggfs. bei einer geworfenen Exception nicht vernünftig aufräumt, den Benchmark auf einem Duplikat des operativen Containers zu starten, und währenddessen den operativen Container zu pausieren/stoppen.
Nach dem Benchmark oder wenn der Benchmark in die Hose gegangen ist, löscht man das Duplikat, und hat einen unveränderten operativen Container ...
Bin noch nicht so in der Denkweise von Containern und VMs ....
Intel(R) Celeron(R) CPU N3000 @ 1.04GHz 8G RAM 480G SSD
Virtualization : unprivileged lxc container (debian 12 on Proxmox 8.4.14)
Linux pve 6.8.12-16-pve
6 GByte RAM für den Container
Fritzbox 6591 FW 8.03 (Vodafone Leih-Box)
Remote-Access über Wireguard der Fritzbox -
@homoran Ich dachte der hier hätte ältere Rechte ;-) in Medias Res gibt es ja erst in den letzten Beiträgen ...
Bei einem LXC Container ist es wahrscheinlich die naheliegenste Lösung, wenn der Benchmark so lange blockieren kann, und dann auch ggfs. bei einer geworfenen Exception nicht vernünftig aufräumt, den Benchmark auf einem Duplikat des operativen Containers zu starten, und währenddessen den operativen Container zu pausieren/stoppen.
Nach dem Benchmark oder wenn der Benchmark in die Hose gegangen ist, löscht man das Duplikat, und hat einen unveränderten operativen Container ...
Bin noch nicht so in der Denkweise von Containern und VMs ....
@martinp sagte in [beantwortet] ioBroker.benchmark, und nun?:
der hier hätte ältere Rechte
so alt, das er schon Grünspan angesetzt hatte.
Deswegen war der eigene Thread die korrekte LösungEDIT:
und nicht nachträglich noch eine halbe Seite hinzufügen ohne es als Edit kennzuzeichnen :rage: -
@homoran Ich dachte der hier hätte ältere Rechte ;-) in Medias Res gibt es ja erst in den letzten Beiträgen ...
Bei einem LXC Container ist es wahrscheinlich die naheliegenste Lösung, wenn der Benchmark so lange blockieren kann, und dann auch ggfs. bei einer geworfenen Exception nicht vernünftig aufräumt, den Benchmark auf einem Duplikat des operativen Containers zu starten, und währenddessen den operativen Container zu pausieren/stoppen.
Nach dem Benchmark oder wenn der Benchmark in die Hose gegangen ist, löscht man das Duplikat, und hat einen unveränderten operativen Container ...
Bin noch nicht so in der Denkweise von Containern und VMs ....
735
Online32.5k
Benutzer81.6k
Themen1.3m
Beiträge