ioBroker lässt RAM überlaufen und andere Phänomene

AnneTheke

RAM "läuft über": Ja buchstäblich, es werden derart viele Prozesse gestartet, dass irgendwann kein Platz mehr ist und es wird fleißig ausgelagert und komprimiert.

Meldungen in ??: In der Webansicht unter "Protokolle"

Prozese doppelt: Meinst du die angeblich laufenden Adapter? Die sehe ich nur 1 mal im Task Manager bzw Process-Explorer. Wenn es um die ständig startenden WMIC und conhost geht, ist "doppelt" arg untertrieben.

@homoran said in ioBroker lässt RAM überlaufen und andere Phänomene:

Aver verstehe ich das richtig dass du einen Server X hast auf dem eine VM läuft in der Windows läuft und darin ioBroker?

Exakt!

@djmarc75 said in ioBroker lässt RAM überlaufen und andere Phänomene:

Meine Vermutung ist dass Dein "Problem" eher vom Windooze herrührt. Warum in einer VM kein Debian als Basis ?

Und warum verschwindet das Problem nicht, wenn man zu einem Stand zurück geht, an dem man sicher weiß, dass alles ok war? Auf der Maschine wird kein Update gefahren ohne es vorher zu testen und nach 3 Jahren problemlosen Betrieb glaube ich nicht, dass Windows da wirklich das Problem ist...

Homoran

@annetheke sagte in ioBroker lässt RAM überlaufen und andere Phänomene:

dass Windows da wirklich das Problem ist...

ich aber auch!

error 7 entsteht, wenn durch einen unsauberen Neustart ein Prozwss nicht beendet und trotzdem neu gestartet wird.

Diese Neustarts könnten tatsächlich durch mangelnden ram entstehen.

leider kann ich bei WIN kein bischen helfen

OliverIO

@annetheke

Dann hast du auch nicht den exakt gleichen Stand wieder erreicht

AnneTheke

@homoran

Der Error entsteht sofort beim Systemstart, da lief noch nicht ein Prozess von ioBroker

Homoran

@annetheke sagte in ioBroker lässt RAM überlaufen und andere Phänomene:

WMIC und conhos

sagt mir gar nichts.

das log bitte als Text in code-tags posten und nicht nur auf warn gefiltert. ggf. dann in Spoiler.
in dem Ausschnitt startet anscheinend gerade alles neu, die Ursache oder was auch immer weiterhelfen könnte ist da nicht zu sehen

AnneTheke

@homoran

Bitteschön.

 2024-02-14 10:20:49.815 - info: host.HK01-MA iobroker.js-controller version 5.0.17 js-controller starting
2024-02-14 10:20:49.816 - info: host.HK01-MA Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
2024-02-14 10:20:49.817 - info: host.HK01-MA hostname: HK01-MA, node: v18.19.0
2024-02-14 10:20:49.817 - info: host.HK01-MA ip addresses: fe80::e813:36d1:6136:d1a4 169.254.81.252 fe80::cee8:cf33:5c20:fb92 169.254.19.167 fe80::e556:8e21:6fc1:a33e 169.254.94.115 192.168.2.37 192.168.2.38 192.168.0.80 fe80::3ec8:d5d9:6bcf:acf3 169.254.94.3
2024-02-14 10:20:49.917 - info: host.HK01-MA connected to Objects and States
2024-02-14 10:20:49.924 - info: host.HK01-MA Node.js version has changed from unknown to 18.19.0
2024-02-14 10:20:49.936 - info: host.HK01-MA added notifications configuration of host
2024-02-14 10:20:50.450 - info: host.HK01-MA 3 instances found
2024-02-14 10:20:50.454 - info: host.HK01-MA starting 3 instances
2024-02-14 10:20:50.489 - info: host.HK01-MA instance system.adapter.admin.0 started with pid 2852
2024-02-14 10:20:52.782 - info: admin.0 (2852) starting. Version 6.13.16 in C:/ioBroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:20:52.800 - info: admin.0 (2852) requesting all objects
2024-02-14 10:20:52.857 - info: admin.0 (2852) received all objects
2024-02-14 10:20:52.901 - info: admin.0 (2852) socket.io server listening on port 8081
2024-02-14 10:20:52.903 - info: admin.0 (2852) http server listening on port 8081
2024-02-14 10:20:52.903 - info: admin.0 (2852) Use link "http://127.0.0.1:8081" to configure.
2024-02-14 10:20:52.915 - warn: admin.0 (2852) Repository cannot be read: Active repo - stable
2024-02-14 10:20:52.915 - warn: admin.0 (2852) Active repository "stable" cannot be read
2024-02-14 10:20:54.511 - info: host.HK01-MA instance system.adapter.discovery.0 started with pid 3856
2024-02-14 10:20:54.886 - info: admin.0 (2852) register notification info
2024-02-14 10:20:55.961 - info: discovery.0 (3856) starting. Version 4.2.0 in C:/ioBroker/node_modules/iobroker.discovery, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:20:58.484 - info: host.HK01-MA instance system.adapter.backitup.0 started with pid 3244
2024-02-14 10:20:59.693 - info: backitup.0 (3244) starting. Version 2.9.8 in C:/ioBroker/node_modules/iobroker.backitup, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:20:59.723 - info: backitup.0 (3244) [iobroker] backup will be activated at 02:48 every 1 day(s)
2024-02-14 10:21:07.156 - info: admin.0 (2852) ==> Connected system.user.admin from ::ffff:127.0.0.1
2024-02-14 10:21:07.199 - info: host.HK01-MA Updating repository "stable" under "http://download.iobroker.net/sources-dist.json"
2024-02-14 10:23:00.334 - info: host.HK01-MA iobroker add s7 --host HK01-MA
2024-02-14 10:23:03.145 - info: host.HK01-MA iobroker NPM version: 10.2.3
2024-02-14 10:23:03.147 - info: host.HK01-MA iobroker Installing iobroker.s7@1.4.2... (System call)
2024-02-14 10:23:15.482 - info: host.HK01-MA iobroker
added 23 packages, and audited 597 packages in 11s
2024-02-14 10:23:15.483 - info: host.HK01-MA iobroker
63 packages are looking for funding
run `npm fund` for details
2024-02-14 10:23:15.542 - info: host.HK01-MA iobroker
28 vulnerabilities (1 low, 20 moderate, 7 high)
To address issues that do not require attention, run:
2024-02-14 10:23:15.543 - info: host.HK01-MA iobroker npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
2024-02-14 10:23:15.573 - info: host.HK01-MA iobroker host.HK01-MA install adapter s7
2024-02-14 10:23:15.611 - info: host.HK01-MA iobroker upload [129] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/asset-manifest.json asset-manifest.json application/json
2024-02-14 10:23:18.840 - info: host.HK01-MA iobroker upload [100] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Cold Water.937aad5fa21b0c20a856.svg static/media/Cold Water.937aad5fa21b0c20a856.svg image/svg+xml
2024-02-14 10:23:18.886 - info: host.HK01-MA iobroker upload [90] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Doorstep.10630b759b4867a10776.svg static/media/Doorstep.10630b759b4867a10776.svg image/svg+xml
2024-02-14 10:23:18.947 - info: host.HK01-MA iobroker upload [80] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Garage Doors.0c2a1cfca7ad1ea59625.svg static/media/Garage Doors.0c2a1cfca7ad1ea59625.svg image/svg+xml
2024-02-14 10:23:18.996 - info: host.HK01-MA iobroker upload [70] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Handle.3de1d1320fc3ce2f9712.svg static/media/Handle.3de1d1320fc3ce2f9712.svg image/svg+xml
2024-02-14 10:23:19.043 - info: host.HK01-MA iobroker upload [60] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Laundry Room.58da550dff0173676e02.svg static/media/Laundry Room.58da550dff0173676e02.svg image/svg+xml
2024-02-14 10:23:19.096 - info: host.HK01-MA iobroker upload [50] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Music.67bc6063cb601642fd74.svg static/media/Music.67bc6063cb601642fd74.svg image/svg+xml
2024-02-14 10:23:19.147 - info: host.HK01-MA iobroker upload [40] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Power Consumption.4faab614c3c788f2d338.svg static/media/Power Consumption.4faab614c3c788f2d338.svg image/svg+xml
2024-02-14 10:23:19.184 - info: host.HK01-MA iobroker upload [30] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Shutters.db7d7b0d498f40779210.svg static/media/Shutters.db7d7b0d498f40779210.svg image/svg+xml
2024-02-14 10:23:19.231 - info: host.HK01-MA iobroker upload [20] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Swimming Pool.190b378cb0707edb9461.svg static/media/Swimming Pool.190b378cb0707edb9461.svg image/svg+xml
2024-02-14 10:23:19.235 - info: host.HK01-MA iobroker upload [19] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Table Lamps.bd92de33bf86b6cbaec9.svg static/media/Table Lamps.bd92de33bf86b6cbaec9.svg image/svg+xml
2024-02-14 10:23:19.242 - info: host.HK01-MA iobroker upload [18] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Temperature Sensors.75d805988a6b77b231d8.svg static/media/Temperature Sensors.75d805988a6b77b231d8.svg image/svg+xml
2024-02-14 10:23:19.249 - info: host.HK01-MA iobroker upload [17] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Terrace.d71d07d9290674f2ca20.svg static/media/Terrace.d71d07d9290674f2ca20.svg image/svg+xml
2024-02-14 10:23:19.255 - info: host.HK01-MA iobroker upload [16] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Toilet.83604dd2daafb67067dd.svg static/media/Toilet.83604dd2daafb67067dd.svg image/svg+xml
2024-02-14 10:23:19.260 - info: host.HK01-MA iobroker upload [15] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Tv.4e9745a548e57bfac0c7.svg static/media/Tv.4e9745a548e57bfac0c7.svg image/svg+xml
2024-02-14 10:23:19.265 - info: host.HK01-MA iobroker upload [14] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Upstairs.441813e54e0daca0882d.svg static/media/Upstairs.441813e54e0daca0882d.svg image/svg+xml
2024-02-14 10:23:19.270 - info: host.HK01-MA iobroker upload [13] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Vacuum Cleaner.9c8d50e436e6cea06dfa.svg static/media/Vacuum Cleaner.9c8d50e436e6cea06dfa.svg image/svg+xml
2024-02-14 10:23:19.278 - info: host.HK01-MA iobroker upload [12] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Ventilation.c31761d86d67e245ac92.svg static/media/Ventilation.c31761d86d67e245ac92.svg image/svg+xml
2024-02-14 10:23:19.284 - info: host.HK01-MA iobroker upload [11] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Wardrobe.e8019970a2b51412cfdc.svg static/media/Wardrobe.e8019970a2b51412cfdc.svg image/svg+xml
2024-02-14 10:23:19.289 - info: host.HK01-MA iobroker upload [10] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Washing Machines.577f3acdb3cef002b523.svg static/media/Washing Machines.577f3acdb3cef002b523.svg image/svg+xml
2024-02-14 10:23:19.293 - info: host.HK01-MA iobroker upload [9] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Washroom.bfb54196f381f36de9d6.svg static/media/Washroom.bfb54196f381f36de9d6.svg image/svg+xml
2024-02-14 10:23:19.297 - info: host.HK01-MA iobroker upload [8] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Water Consumption.68891649591cc2434c5b.svg static/media/Water Consumption.68891649591cc2434c5b.svg image/svg+xml
2024-02-14 10:23:19.303 - info: host.HK01-MA iobroker upload [7] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Water Heater.7e4bb4d99a5213f24d08.svg static/media/Water Heater.7e4bb4d99a5213f24d08.svg image/svg+xml
2024-02-14 10:23:19.311 - info: host.HK01-MA iobroker upload [6] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Water.f50411984c5c24fa574d.svg static/media/Water.f50411984c5c24fa574d.svg image/svg+xml
2024-02-14 10:23:19.317 - info: host.HK01-MA iobroker upload [5] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Wc.83604dd2daafb67067dd.svg static/media/Wc.83604dd2daafb67067dd.svg image/svg+xml
2024-02-14 10:23:19.322 - info: host.HK01-MA iobroker upload [4] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Weather.e91dae647698d48365e3.svg static/media/Weather.e91dae647698d48365e3.svg image/svg+xml
2024-02-14 10:23:19.327 - info: host.HK01-MA iobroker upload [3] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Window.421664f57c35e5109aa2.svg static/media/Window.421664f57c35e5109aa2.svg image/svg+xml
2024-02-14 10:23:19.331 - info: host.HK01-MA iobroker upload [2] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Windscreen.6058448bf63f72dd5036.svg static/media/Windscreen.6058448bf63f72dd5036.svg image/svg+xml
2024-02-14 10:23:19.340 - info: host.HK01-MA iobroker upload [1] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Workshop.7856e59fe4f164c90609.svg static/media/Workshop.7856e59fe4f164c90609.svg image/svg+xml
2024-02-14 10:23:19.346 - info: host.HK01-MA iobroker upload [0] s7.admin C:/ioBroker/node_modules/iobroker.s7/admin/static/media/Workspace.97d73e419d966bfb6428.svg static/media/Workspace.97d73e419d966bfb6428.svg image/svg+xml
2024-02-14 10:23:19.370 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7 created/updated
2024-02-14 10:23:19.405 - info: host.HK01-MA iobroker host.HK01-MA create instance s7
2024-02-14 10:23:19.410 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.alive created
2024-02-14 10:23:19.413 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.connected created
2024-02-14 10:23:19.415 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.compactMode created
2024-02-14 10:23:19.418 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.cpu created
2024-02-14 10:23:19.421 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.cputime created
2024-02-14 10:23:19.424 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.memHeapUsed created
2024-02-14 10:23:19.428 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.memHeapTotal created
2024-02-14 10:23:19.432 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.memRss created
2024-02-14 10:23:19.436 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.uptime created
2024-02-14 10:23:19.440 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.inputCount created
2024-02-14 10:23:19.443 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.outputCount created
2024-02-14 10:23:19.445 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.eventLoopLag created
2024-02-14 10:23:19.447 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.sigKill created
2024-02-14 10:23:19.449 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0.logLevel created
2024-02-14 10:23:19.459 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.0 created
2024-02-14 10:23:20.498 - info: host.HK01-MA iobroker exit 0
2024-02-14 10:23:22.289 - info: admin.0 (2852) ==> Connected system.user.admin from ::ffff:127.0.0.1
2024-02-14 10:25:04.055 - info: admin.0 (2852) <== Disconnect system.user.admin from ::ffff:127.0.0.1 s7
2024-02-14 10:25:06.591 - info: host.HK01-MA "system.adapter.s7.0" enabled
2024-02-14 10:25:06.611 - info: host.HK01-MA instance system.adapter.s7.0 started with pid 7592
2024-02-14 10:25:07.819 - info: s7.0 (7592) starting. Version 1.4.2 in C:/ioBroker/node_modules/iobroker.s7, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:25:07.848 - info: s7.0 (7592) Connect in S7 mode to 0 / 2
2024-02-14 10:25:07.858 - info: s7.0 (7592) Successfully connected in S7 mode
2024-02-14 10:29:27.439 - info: admin.0 (2852) <== Disconnect system.user.admin from ::ffff:127.0.0.1 admin
2024-02-14 10:29:41.317 - error: discovery.0 (3856) uncaught exception: spawn EROFS
2024-02-14 10:29:41.317 - error: discovery.0 (3856) Error: spawn EROFS
at ChildProcess.spawn (node:internal/child_process:414:11)
at spawn (node:child_process:761:9)
at run (C:\ioBroker\node_modules\pidusage\lib\bin.js:18:14)
at wmic (C:\ioBroker\node_modules\pidusage\lib\wmic.js:48:3)
at get (C:\ioBroker\node_modules\pidusage\lib\stats.js:82:3)
at pidusage (C:\ioBroker\node_modules\pidusage\index.js:30:5)
at AdapterClass._reportStatus (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:10587:21)
at Timeout._onTimeout (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:11834:40)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
2024-02-14 10:29:41.318 - error: discovery.0 (3856) Exception-Code: EROFS: spawn EROFS
2024-02-14 10:29:41.327 - info: discovery.0 (3856) terminating
2024-02-14 10:29:41.327 - warn: discovery.0 (3856) Terminated (UNCAUGHT_EXCEPTION): Without reason
2024-02-14 10:29:41.397 - error: host.HK01-MA Caught by controller[0]: Error: spawn EROFS
2024-02-14 10:29:41.397 - error: host.HK01-MA Caught by controller[0]: at ChildProcess.spawn (node:internal/child_process:414:11)
2024-02-14 10:29:41.397 - error: host.HK01-MA Caught by controller[0]: at spawn (node:child_process:761:9)
2024-02-14 10:29:41.397 - error: host.HK01-MA Caught by controller[0]: at run (C:\ioBroker\node_modules\pidusage\lib\bin.js:18:14)
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: at wmic (C:\ioBroker\node_modules\pidusage\lib\wmic.js:48:3)
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: at get (C:\ioBroker\node_modules\pidusage\lib\stats.js:82:3)
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: at pidusage (C:\ioBroker\node_modules\pidusage\index.js:30:5)
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: at AdapterClass._reportStatus (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:10587:21)
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: at Timeout._onTimeout (C:\ioBroker\node_modules\@iobroker\js-controller-adapter\src\lib\adapter\adapter.ts:11834:40)
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: at listOnTimeout (node:internal/timers:569:17)
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: at processTimers (node:internal/timers:512:7) {
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: errno: -4043,
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: code: 'EROFS',
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: syscall: 'spawn'
2024-02-14 10:29:41.398 - error: host.HK01-MA Caught by controller[0]: }
2024-02-14 10:29:41.398 - error: host.HK01-MA instance system.adapter.discovery.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
2024-02-14 10:29:41.398 - info: host.HK01-MA Restart adapter system.adapter.discovery.0 because enabled
2024-02-14 10:30:12.886 - info: host.HK01-MA iobroker.js-controller version 5.0.17 js-controller starting
2024-02-14 10:30:12.888 - info: host.HK01-MA Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
2024-02-14 10:30:12.889 - info: host.HK01-MA hostname: HK01-MA, node: v18.19.0
2024-02-14 10:30:12.889 - info: host.HK01-MA ip addresses: fe80::e813:36d1:6136:d1a4 169.254.81.252 fe80::cee8:cf33:5c20:fb92 169.254.19.167 fe80::e556:8e21:6fc1:a33e 169.254.94.115 192.168.2.37 169.254.245.206 192.168.2.38 169.254.60.37 169.254.78.228 fe80::3ec8:d5d9:6bcf:acf3 169.254.94.3
2024-02-14 10:30:13.083 - info: host.HK01-MA connected to Objects and States
2024-02-14 10:30:13.093 - info: host.HK01-MA added notifications configuration of host
2024-02-14 10:30:13.420 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeCurrent"
2024-02-14 10:30:13.421 - info: host.HK01-MA 4 instances found
2024-02-14 10:30:13.424 - info: host.HK01-MA starting 4 instances
2024-02-14 10:30:13.443 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeNewest"
2024-02-14 10:30:13.447 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeNewestNext"
2024-02-14 10:30:13.452 - info: host.HK01-MA instance system.adapter.admin.0 started with pid 3652
2024-02-14 10:30:13.454 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmCurrent"
2024-02-14 10:30:13.456 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmNewest"
2024-02-14 10:30:13.458 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmNewestNext"
2024-02-14 10:30:13.460 - info: host.HK01-MA Some obsolete host states deleted.
2024-02-14 10:30:15.640 - error: admin.0 (3652) admin.0 already running
2024-02-14 10:30:15.641 - warn: admin.0 (3652) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 10:30:17.849 - info: host.HK01-MA instance system.adapter.s7.0 started with pid 7284
2024-02-14 10:30:17.861 - error: host.HK01-MA instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 10:30:17.862 - info: host.HK01-MA Restart adapter system.adapter.admin.0 because enabled
2024-02-14 10:30:19.065 - error: s7.0 (7284) s7.0 already running
2024-02-14 10:30:19.067 - warn: s7.0 (7284) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 10:30:19.582 - error: host.HK01-MA instance system.adapter.s7.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 10:30:19.582 - info: host.HK01-MA Restart adapter system.adapter.s7.0 because enabled
2024-02-14 10:30:21.444 - info: host.HK01-MA instance system.adapter.discovery.0 started with pid 7972
2024-02-14 10:30:22.054 - error: discovery.0 (7972) discovery.0 already running
2024-02-14 10:30:22.055 - warn: discovery.0 (7972) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 10:30:22.578 - error: host.HK01-MA instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 10:30:22.578 - info: host.HK01-MA Restart adapter system.adapter.discovery.0 because enabled
2024-02-14 10:30:25.457 - info: host.HK01-MA instance system.adapter.backitup.0 started with pid 8280
2024-02-14 10:30:26.224 - error: backitup.0 (8280) backitup.0 already running
2024-02-14 10:30:26.225 - warn: backitup.0 (8280) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 10:30:26.749 - error: host.HK01-MA instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 10:30:26.749 - info: host.HK01-MA Restart adapter system.adapter.backitup.0 because enabled
2024-02-14 10:30:47.884 - info: host.HK01-MA instance system.adapter.admin.0 started with pid 8196
2024-02-14 10:30:49.250 - info: admin.0 (8196) starting. Version 6.13.16 in C:/ioBroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:30:49.274 - info: admin.0 (8196) requesting all objects
2024-02-14 10:30:49.519 - info: admin.0 (8196) received all objects
2024-02-14 10:30:49.580 - info: admin.0 (8196) socket.io server listening on port 8081
2024-02-14 10:30:49.582 - info: admin.0 (8196) http server listening on port 8081
2024-02-14 10:30:49.582 - info: admin.0 (8196) Use link "http://127.0.0.1:8081" to configure.
2024-02-14 10:30:49.604 - info: host.HK01-MA instance system.adapter.s7.0 started with pid 8684
2024-02-14 10:30:50.709 - info: s7.0 (8684) starting. Version 1.4.2 in C:/ioBroker/node_modules/iobroker.s7, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:30:50.749 - info: s7.0 (8684) Connect in S7 mode to 0 / 2
2024-02-14 10:30:50.763 - info: s7.0 (8684) Successfully connected in S7 mode
2024-02-14 10:30:52.602 - info: host.HK01-MA instance system.adapter.discovery.0 started with pid 4596
2024-02-14 10:30:53.531 - info: discovery.0 (4596) starting. Version 4.2.0 in C:/ioBroker/node_modules/iobroker.discovery, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:30:56.771 - info: host.HK01-MA instance system.adapter.backitup.0 started with pid 8324
2024-02-14 10:30:57.610 - info: backitup.0 (8324) starting. Version 2.9.8 in C:/ioBroker/node_modules/iobroker.backitup, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:30:57.639 - info: backitup.0 (8324) [iobroker] backup will be activated at 02:48 every 1 day(s)
2024-02-14 10:40:42.868 - info: admin.0 (8196) ==> Connected system.user.admin from ::ffff:127.0.0.1
2024-02-14 10:43:01.308 - info: host.HK01-MA iobroker add yahka --host HK01-MA
2024-02-14 10:43:03.626 - info: host.HK01-MA iobroker NPM version: 10.2.3
2024-02-14 10:43:03.626 - info: host.HK01-MA iobroker Installing iobroker.yahka@1.0.3... (System call)
2024-02-14 10:43:21.919 - info: host.HK01-MA iobroker
2024-02-14 10:43:21.920 - info: host.HK01-MA iobroker added 74 packages, and audited 671 packages in 17s
94 packages are looking for funding
run `npm fund` for details
2024-02-14 10:43:21.975 - info: host.HK01-MA iobroker
31 vulnerabilities (1 low, 20 moderate, 10 high)
To address issues that do not require attention, run:
2024-02-14 10:43:21.976 - info: host.HK01-MA iobroker npm audit fix
To address all issues (including breaking changes), run:
npm audit fix --force
Run `npm audit` for details.
2024-02-14 10:43:22.004 - info: host.HK01-MA iobroker host.HK01-MA install adapter yahka
2024-02-14 10:43:22.030 - info: host.HK01-MA iobroker upload [19] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/css/yahka.admin.css css/yahka.admin.css text/css
2024-02-14 10:43:22.040 - info: host.HK01-MA iobroker upload [18] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro-colors.min.css ext/metroui/css/metro-colors.min.css text/css
2024-02-14 10:43:22.048 - info: host.HK01-MA iobroker upload [17] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro-icons.min.css ext/metroui/css/metro-icons.min.css text/css
2024-02-14 10:43:22.056 - info: host.HK01-MA iobroker upload [16] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro-responsive.min.css ext/metroui/css/metro-responsive.min.css text/css
2024-02-14 10:43:22.067 - info: host.HK01-MA iobroker upload [15] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro-rtl.min.css ext/metroui/css/metro-rtl.min.css text/css
2024-02-14 10:43:22.074 - info: host.HK01-MA iobroker upload [14] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro-schemes.min.css ext/metroui/css/metro-schemes.min.css text/css
2024-02-14 10:43:22.082 - info: host.HK01-MA iobroker upload [13] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/css/metro.min.css ext/metroui/css/metro.min.css text/css
2024-02-14 10:43:22.092 - info: host.HK01-MA iobroker upload [12] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/fonts/metro.eot ext/metroui/fonts/metro.eot application/vnd.ms-fontobject
2024-02-14 10:43:22.097 - info: host.HK01-MA iobroker upload [11] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/fonts/metro.svg ext/metroui/fonts/metro.svg image/svg+xml
2024-02-14 10:43:22.104 - info: host.HK01-MA iobroker upload [10] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/fonts/metro.ttf ext/metroui/fonts/metro.ttf font/ttf
2024-02-14 10:43:22.110 - info: host.HK01-MA iobroker upload [9] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/fonts/metro.woff ext/metroui/fonts/metro.woff font/woff
2024-02-14 10:43:22.116 - info: host.HK01-MA iobroker upload [8] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/fonts/selection.json ext/metroui/fonts/selection.json application/json
2024-02-14 10:43:22.129 - info: host.HK01-MA iobroker upload [7] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/ext/metroui/js/metro.min.js ext/metroui/js/metro.min.js application/javascript
2024-02-14 10:43:22.148 - info: host.HK01-MA iobroker upload [6] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/home_icon_large.png home_icon_large.png image/png
2024-02-14 10:43:22.155 - info: host.HK01-MA iobroker upload [5] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/index.html index.html text/html
2024-02-14 10:43:22.173 - info: host.HK01-MA iobroker upload [4] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/index_m.html index_m.html text/html
2024-02-14 10:43:22.184 - info: host.HK01-MA iobroker upload [3] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/words.js words.js application/javascript
2024-02-14 10:43:22.191 - info: host.HK01-MA iobroker upload [2] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/yahka.admin.js yahka.admin.js application/javascript
2024-02-14 10:43:22.472 - info: host.HK01-MA iobroker upload [1] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/yahka.admin.js.map yahka.admin.js.map application/json
2024-02-14 10:43:22.612 - info: host.HK01-MA iobroker upload [0] yahka.admin C:/ioBroker/node_modules/iobroker.yahka/admin/yahka.png yahka.png image/png
2024-02-14 10:43:22.626 - info: host.HK01-MA iobroker host.HK01-MA object yahka.meta._accessoryCategories created/updated
2024-02-14 10:43:22.629 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka created/updated
2024-02-14 10:43:22.645 - info: host.HK01-MA iobroker host.HK01-MA create instance yahka
2024-02-14 10:43:22.650 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.alive created
2024-02-14 10:43:22.653 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.connected created
2024-02-14 10:43:22.655 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.compactMode created
2024-02-14 10:43:22.658 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.cpu created
2024-02-14 10:43:22.662 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.cputime created
2024-02-14 10:43:22.664 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.memHeapUsed created
2024-02-14 10:43:22.667 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.memHeapTotal created
2024-02-14 10:43:22.669 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.memRss created
2024-02-14 10:43:22.672 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.uptime created
2024-02-14 10:43:22.675 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.inputCount created
2024-02-14 10:43:22.678 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.outputCount created
2024-02-14 10:43:22.681 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.eventLoopLag created
2024-02-14 10:43:22.683 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.sigKill created
2024-02-14 10:43:22.686 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0.logLevel created
2024-02-14 10:43:22.699 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.yahka.0 created
2024-02-14 10:43:23.726 - info: host.HK01-MA iobroker exit 0
2024-02-14 10:43:25.046 - info: admin.0 (8196) ==> Connected system.user.admin from ::ffff:127.0.0.1
2024-02-14 10:43:25.714 - info: host.HK01-MA instance system.adapter.yahka.0 started with pid 15256
2024-02-14 10:43:27.364 - info: yahka.0 (15256) starting. Version 1.0.3 in C:/ioBroker/node_modules/iobroker.yahka, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:43:27.378 - info: yahka.0 (15256) adapter ready, checking config
2024-02-14 10:43:27.378 - info: yahka.0 (15256) first time initialization
2024-02-14 10:43:27.383 - info: yahka.0 (15256) publishing bridge Yahka-0 on 0.0.0.0 using avahi
2024-02-14 10:43:27.442 - info: host.HK01-MA stopInstance system.adapter.yahka.0 (force=false, process=true)
2024-02-14 10:43:27.444 - info: yahka.0 (15256) Got terminate signal TERMINATE_YOURSELF
2024-02-14 10:43:27.444 - info: host.HK01-MA stopInstance system.adapter.yahka.0 send kill signal
2024-02-14 10:43:27.444 - info: yahka.0 (15256) cleaning up ...
2024-02-14 10:43:27.444 - info: yahka.0 (15256) cleaned up ...
2024-02-14 10:43:27.444 - info: yahka.0 (15256) terminating
2024-02-14 10:43:27.445 - info: yahka.0 (15256) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
2024-02-14 10:43:27.951 - info: yahka.0 (15256) terminating
2024-02-14 10:43:27.971 - info: host.HK01-MA instance system.adapter.yahka.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
2024-02-14 10:43:30.467 - info: host.HK01-MA instance system.adapter.yahka.0 started with pid 3968
2024-02-14 10:43:31.517 - info: yahka.0 (3968) starting. Version 1.0.3 in C:/ioBroker/node_modules/iobroker.yahka, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:43:31.531 - info: yahka.0 (3968) adapter ready, checking config
2024-02-14 10:43:31.535 - info: yahka.0 (3968) publishing bridge Yahka-0 on 0.0.0.0 using avahi
2024-02-14 10:47:24.896 - info: admin.0 (8196) <== Disconnect system.user.admin from ::ffff:127.0.0.1
2024-02-14 10:47:42.057 - info: host.HK01-MA iobroker add s7 --host HK01-MA
2024-02-14 10:47:43.213 - info: host.HK01-MA iobroker host.HK01-MA create instance s7
2024-02-14 10:47:43.223 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.alive created
2024-02-14 10:47:43.225 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.connected created
2024-02-14 10:47:43.229 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.compactMode created
2024-02-14 10:47:43.232 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.cpu created
2024-02-14 10:47:43.235 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.cputime created
2024-02-14 10:47:43.238 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.memHeapUsed created
2024-02-14 10:47:43.241 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.memHeapTotal created
2024-02-14 10:47:43.244 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.memRss created
2024-02-14 10:47:43.247 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.uptime created
2024-02-14 10:47:43.251 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.inputCount created
2024-02-14 10:47:43.254 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.outputCount created
2024-02-14 10:47:43.257 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.eventLoopLag created
2024-02-14 10:47:43.259 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.sigKill created
2024-02-14 10:47:43.263 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1.logLevel created
2024-02-14 10:47:43.273 - info: host.HK01-MA iobroker host.HK01-MA object system.adapter.s7.1 created
2024-02-14 10:47:44.292 - info: host.HK01-MA iobroker exit 0
2024-02-14 10:47:46.629 - info: admin.0 (8196) ==> Connected system.user.admin from ::ffff:127.0.0.1
2024-02-14 10:48:11.569 - info: admin.0 (8196) <== Disconnect system.user.admin from ::ffff:127.0.0.1 s7
2024-02-14 10:48:13.821 - info: host.HK01-MA "system.adapter.s7.1" enabled
2024-02-14 10:48:13.842 - info: host.HK01-MA instance system.adapter.s7.1 started with pid 16204
2024-02-14 10:48:14.803 - info: s7.1 (16204) starting. Version 1.4.2 in C:/ioBroker/node_modules/iobroker.s7, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:48:14.834 - info: s7.1 (16204) Connect in S7 mode to 0 / 2
2024-02-14 10:48:14.843 - info: s7.1 (16204) Successfully connected in S7 mode
2024-02-14 10:50:31.391 - error: host.HK01-MA instance system.adapter.admin.0 terminated with code 4294967295 ()
2024-02-14 10:50:31.392 - info: host.HK01-MA Restart adapter system.adapter.admin.0 because enabled
2024-02-14 10:50:31.470 - error: host.HK01-MA instance system.adapter.s7.0 terminated with code 4294967295 ()
2024-02-14 10:50:31.470 - info: host.HK01-MA Restart adapter system.adapter.s7.0 because enabled
2024-02-14 10:50:31.554 - error: host.HK01-MA instance system.adapter.discovery.0 terminated with code 4294967295 ()
2024-02-14 10:50:31.554 - info: host.HK01-MA Restart adapter system.adapter.discovery.0 because enabled
2024-02-14 10:50:31.633 - error: host.HK01-MA instance system.adapter.backitup.0 terminated with code 4294967295 ()
2024-02-14 10:50:31.634 - info: host.HK01-MA Restart adapter system.adapter.backitup.0 because enabled
2024-02-14 10:50:31.723 - error: host.HK01-MA instance system.adapter.yahka.0 terminated with code 4294967295 ()
2024-02-14 10:50:31.724 - info: host.HK01-MA Restart adapter system.adapter.yahka.0 because enabled
2024-02-14 10:50:53.308 - info: host.HK01-MA iobroker.js-controller version 5.0.17 js-controller starting
2024-02-14 10:50:53.310 - info: host.HK01-MA Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
2024-02-14 10:50:53.310 - info: host.HK01-MA hostname: HK01-MA, node: v18.19.0
2024-02-14 10:50:53.310 - info: host.HK01-MA ip addresses: fe80::e813:36d1:6136:d1a4 169.254.81.252 fe80::cee8:cf33:5c20:fb92 169.254.19.167 fe80::e556:8e21:6fc1:a33e 169.254.94.115 192.168.2.37 192.168.2.38 192.168.0.80 fe80::3ec8:d5d9:6bcf:acf3 169.254.94.3
2024-02-14 10:50:53.484 - info: host.HK01-MA connected to Objects and States
2024-02-14 10:50:53.491 - info: host.HK01-MA added notifications configuration of host
2024-02-14 10:50:53.761 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeCurrent"
2024-02-14 10:50:53.761 - info: host.HK01-MA 6 instances found
2024-02-14 10:50:53.763 - info: host.HK01-MA starting 6 instances
2024-02-14 10:50:53.784 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeNewest"
2024-02-14 10:50:53.788 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeNewestNext"
2024-02-14 10:50:53.801 - info: host.HK01-MA instance system.adapter.admin.0 started with pid 17820
2024-02-14 10:50:53.804 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmCurrent"
2024-02-14 10:50:53.806 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmNewest"
2024-02-14 10:50:53.808 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmNewestNext"
2024-02-14 10:50:53.810 - info: host.HK01-MA Some obsolete host states deleted.
2024-02-14 10:50:54.778 - error: admin.0 (17820) admin.0 already running
2024-02-14 10:50:54.779 - warn: admin.0 (17820) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 10:50:55.327 - error: host.HK01-MA instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 10:50:55.327 - info: host.HK01-MA Restart adapter system.adapter.admin.0 because enabled
2024-02-14 10:50:57.794 - info: host.HK01-MA instance system.adapter.s7.0 started with pid 17772
2024-02-14 10:50:58.875 - error: s7.0 (17772) s7.0 already running
2024-02-14 10:50:58.876 - warn: s7.0 (17772) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 10:50:59.438 - error: host.HK01-MA instance system.adapter.s7.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 10:50:59.438 - info: host.HK01-MA Restart adapter system.adapter.s7.0 because enabled
2024-02-14 10:51:01.795 - info: host.HK01-MA instance system.adapter.s7.1 started with pid 3400
2024-02-14 10:51:02.499 - error: s7.1 (3400) s7.1 already running
2024-02-14 10:51:02.500 - warn: s7.1 (3400) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 10:51:03.027 - error: host.HK01-MA instance system.adapter.s7.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 10:51:03.027 - info: host.HK01-MA Restart adapter system.adapter.s7.1 because enabled
2024-02-14 10:51:05.783 - info: host.HK01-MA instance system.adapter.discovery.0 started with pid 7024
2024-02-14 10:51:06.449 - error: discovery.0 (7024) discovery.0 already running
2024-02-14 10:51:06.450 - warn: discovery.0 (7024) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 10:51:06.987 - error: host.HK01-MA instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 10:51:06.987 - info: host.HK01-MA Restart adapter system.adapter.discovery.0 because enabled
2024-02-14 10:51:09.787 - info: host.HK01-MA instance system.adapter.backitup.0 started with pid 17816
2024-02-14 10:51:10.464 - error: backitup.0 (17816) backitup.0 already running
2024-02-14 10:51:10.465 - warn: backitup.0 (17816) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 10:51:10.995 - error: host.HK01-MA instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 10:51:10.995 - info: host.HK01-MA Restart adapter system.adapter.backitup.0 because enabled
2024-02-14 10:51:13.780 - info: host.HK01-MA instance system.adapter.yahka.0 started with pid 6828
2024-02-14 10:51:14.688 - error: yahka.0 (6828) yahka.0 already running
2024-02-14 10:51:14.689 - warn: yahka.0 (6828) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 10:51:15.230 - error: host.HK01-MA instance system.adapter.yahka.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 10:51:15.230 - info: host.HK01-MA Restart adapter system.adapter.yahka.0 because enabled
2024-02-14 10:51:25.356 - info: host.HK01-MA instance system.adapter.admin.0 started with pid 19056
2024-02-14 10:51:26.580 - info: admin.0 (19056) starting. Version 6.13.16 in C:/ioBroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:51:26.598 - info: admin.0 (19056) requesting all objects
2024-02-14 10:51:26.825 - info: admin.0 (19056) received all objects
2024-02-14 10:51:26.890 - info: admin.0 (19056) socket.io server listening on port 8081
2024-02-14 10:51:26.891 - info: admin.0 (19056) http server listening on port 8081
2024-02-14 10:51:26.891 - info: admin.0 (19056) Use link "http://127.0.0.1:8081" to configure.
2024-02-14 10:51:27.643 - info: admin.0 (19056) ==> Connected system.user.admin from ::1
2024-02-14 10:51:29.467 - info: host.HK01-MA instance system.adapter.s7.0 started with pid 14232
2024-02-14 10:51:30.370 - info: s7.0 (14232) starting. Version 1.4.2 in C:/ioBroker/node_modules/iobroker.s7, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:51:30.404 - info: s7.0 (14232) Connect in S7 mode to 0 / 2
2024-02-14 10:51:30.427 - info: s7.0 (14232) Successfully connected in S7 mode
2024-02-14 10:51:33.053 - info: host.HK01-MA instance system.adapter.s7.1 started with pid 19072
2024-02-14 10:51:33.950 - info: s7.1 (19072) starting. Version 1.4.2 in C:/ioBroker/node_modules/iobroker.s7, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:51:33.984 - info: s7.1 (19072) Connect in S7 mode to 0 / 2
2024-02-14 10:51:33.993 - info: s7.1 (19072) Successfully connected in S7 mode
2024-02-14 10:51:34.783 - info: admin.0 (19056) ==> Connected system.user.admin from ::1
2024-02-14 10:51:37.005 - info: host.HK01-MA instance system.adapter.discovery.0 started with pid 18008
2024-02-14 10:51:37.865 - info: discovery.0 (18008) starting. Version 4.2.0 in C:/ioBroker/node_modules/iobroker.discovery, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:51:41.009 - info: host.HK01-MA instance system.adapter.backitup.0 started with pid 19036
2024-02-14 10:51:41.960 - info: backitup.0 (19036) starting. Version 2.9.8 in C:/ioBroker/node_modules/iobroker.backitup, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:51:41.987 - info: backitup.0 (19036) [iobroker] backup will be activated at 02:48 every 1 day(s)
2024-02-14 10:51:42.859 - info: admin.0 (19056) <== Disconnect system.user.admin from ::1
2024-02-14 10:51:45.241 - info: host.HK01-MA instance system.adapter.yahka.0 started with pid 19344
2024-02-14 10:51:46.370 - info: yahka.0 (19344) starting. Version 1.0.3 in C:/ioBroker/node_modules/iobroker.yahka, node: v18.19.0, js-controller: 5.0.17
2024-02-14 10:51:46.389 - info: yahka.0 (19344) adapter ready, checking config
2024-02-14 10:51:46.394 - info: yahka.0 (19344) publishing bridge Yahka-0 on 0.0.0.0 using avahi
2024-02-14 11:05:38.844 - info: admin.0 (19056) <== Disconnect system.user.admin from ::1 admin
2024-02-14 11:05:44.061 - error: host.HK01-MA instance system.adapter.admin.0 terminated with code 4294967295 ()
2024-02-14 11:05:44.061 - info: host.HK01-MA Restart adapter system.adapter.admin.0 because enabled
2024-02-14 11:05:44.140 - error: host.HK01-MA instance system.adapter.s7.0 terminated with code 4294967295 ()
2024-02-14 11:05:44.140 - info: host.HK01-MA Restart adapter system.adapter.s7.0 because enabled
2024-02-14 11:05:44.210 - error: host.HK01-MA instance system.adapter.s7.1 terminated with code 4294967295 ()
2024-02-14 11:05:44.210 - info: host.HK01-MA Restart adapter system.adapter.s7.1 because enabled
2024-02-14 11:05:44.279 - error: host.HK01-MA instance system.adapter.discovery.0 terminated with code 4294967295 ()
2024-02-14 11:05:44.279 - info: host.HK01-MA Restart adapter system.adapter.discovery.0 because enabled
2024-02-14 11:05:44.349 - error: host.HK01-MA instance system.adapter.backitup.0 terminated with code 4294967295 ()
2024-02-14 11:05:44.349 - info: host.HK01-MA Restart adapter system.adapter.backitup.0 because enabled
2024-02-14 11:21:35.512 - info: host.HK01-MA iobroker.js-controller version 5.0.17 js-controller starting
2024-02-14 11:21:35.513 - info: host.HK01-MA Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
2024-02-14 11:21:35.514 - info: host.HK01-MA hostname: HK01-MA, node: v18.19.0
2024-02-14 11:21:35.514 - info: host.HK01-MA ip addresses: fe80::e813:36d1:6136:d1a4 169.254.81.252 fe80::cee8:cf33:5c20:fb92 169.254.19.167 fe80::e556:8e21:6fc1:a33e 169.254.94.115 192.168.2.37 192.168.2.38 192.168.0.80 fe80::3ec8:d5d9:6bcf:acf3 169.254.94.3
2024-02-14 11:21:35.674 - info: host.HK01-MA connected to Objects and States
2024-02-14 11:21:35.680 - info: host.HK01-MA added notifications configuration of host
2024-02-14 11:21:35.919 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeCurrent"
2024-02-14 11:21:35.920 - info: host.HK01-MA 6 instances found
2024-02-14 11:21:35.923 - info: host.HK01-MA starting 6 instances
2024-02-14 11:21:35.946 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeNewest"
2024-02-14 11:21:35.950 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeNewestNext"
2024-02-14 11:21:35.963 - info: host.HK01-MA instance system.adapter.admin.0 started with pid 3820
2024-02-14 11:21:35.965 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmCurrent"
2024-02-14 11:21:35.968 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmNewest"
2024-02-14 11:21:35.970 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmNewestNext"
2024-02-14 11:21:35.973 - info: host.HK01-MA Some obsolete host states deleted.
2024-02-14 11:21:36.962 - error: admin.0 (3820) admin.0 already running
2024-02-14 11:21:36.963 - warn: admin.0 (3820) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 11:21:37.496 - error: host.HK01-MA instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 11:21:37.496 - info: host.HK01-MA Restart adapter system.adapter.admin.0 because enabled
2024-02-14 11:21:39.942 - info: host.HK01-MA instance system.adapter.s7.0 started with pid 8344
2024-02-14 11:21:40.629 - error: s7.0 (8344) s7.0 already running
2024-02-14 11:21:40.630 - warn: s7.0 (8344) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 11:21:41.148 - error: host.HK01-MA instance system.adapter.s7.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 11:21:41.148 - info: host.HK01-MA Restart adapter system.adapter.s7.0 because enabled
2024-02-14 11:21:43.941 - info: host.HK01-MA instance system.adapter.s7.1 started with pid 19448
2024-02-14 11:21:44.635 - error: s7.1 (19448) s7.1 already running
2024-02-14 11:21:44.636 - warn: s7.1 (19448) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 11:21:45.154 - error: host.HK01-MA instance system.adapter.s7.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 11:21:45.154 - info: host.HK01-MA Restart adapter system.adapter.s7.1 because enabled
2024-02-14 11:21:47.943 - info: host.HK01-MA instance system.adapter.discovery.0 started with pid 10784
2024-02-14 11:21:48.599 - error: discovery.0 (10784) discovery.0 already running
2024-02-14 11:21:48.600 - warn: discovery.0 (10784) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 11:21:49.135 - error: host.HK01-MA instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 11:21:49.135 - info: host.HK01-MA Restart adapter system.adapter.discovery.0 because enabled
2024-02-14 11:21:51.941 - info: host.HK01-MA instance system.adapter.backitup.0 started with pid 11040
2024-02-14 11:21:52.634 - error: backitup.0 (11040) backitup.0 already running
2024-02-14 11:21:52.635 - warn: backitup.0 (11040) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 11:21:53.168 - error: host.HK01-MA instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 11:21:53.168 - info: host.HK01-MA Restart adapter system.adapter.backitup.0 because enabled
2024-02-14 11:21:55.947 - info: host.HK01-MA instance system.adapter.yahka.0 started with pid 15708
2024-02-14 11:21:56.869 - error: yahka.0 (15708) yahka.0 already running
2024-02-14 11:21:56.870 - warn: yahka.0 (15708) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 11:21:57.401 - error: host.HK01-MA instance system.adapter.yahka.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 11:21:57.402 - info: host.HK01-MA Restart adapter system.adapter.yahka.0 because enabled
2024-02-14 11:22:07.521 - info: host.HK01-MA instance system.adapter.admin.0 started with pid 8376
2024-02-14 11:22:09.439 - info: admin.0 (8376) starting. Version 6.13.16 in C:/ioBroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17
2024-02-14 11:22:09.459 - info: admin.0 (8376) requesting all objects
2024-02-14 11:22:09.657 - info: admin.0 (8376) received all objects
2024-02-14 11:22:09.768 - info: admin.0 (8376) socket.io server listening on port 8081
2024-02-14 11:22:09.769 - info: admin.0 (8376) http server listening on port 8081
2024-02-14 11:22:09.769 - info: admin.0 (8376) Use link "http://127.0.0.1:8081" to configure.
2024-02-14 11:22:11.172 - info: host.HK01-MA instance system.adapter.s7.0 started with pid 20476
2024-02-14 11:22:12.274 - info: s7.0 (20476) starting. Version 1.4.2 in C:/ioBroker/node_modules/iobroker.s7, node: v18.19.0, js-controller: 5.0.17
2024-02-14 11:22:12.309 - info: s7.0 (20476) Connect in S7 mode to 0 / 2
2024-02-14 11:22:12.320 - info: s7.0 (20476) Successfully connected in S7 mode
2024-02-14 11:22:15.172 - info: host.HK01-MA instance system.adapter.s7.1 started with pid 20724
2024-02-14 11:22:15.917 - info: admin.0 (8376) ==> Connected system.user.admin from ::ffff:127.0.0.1
2024-02-14 11:22:16.934 - info: s7.1 (20724) starting. Version 1.4.2 in C:/ioBroker/node_modules/iobroker.s7, node: v18.19.0, js-controller: 5.0.17
2024-02-14 11:22:16.973 - info: s7.1 (20724) Connect in S7 mode to 0 / 2
2024-02-14 11:22:16.986 - info: s7.1 (20724) Successfully connected in S7 mode
2024-02-14 11:22:19.151 - info: host.HK01-MA instance system.adapter.discovery.0 started with pid 21240
2024-02-14 11:22:20.070 - info: discovery.0 (21240) starting. Version 4.2.0 in C:/ioBroker/node_modules/iobroker.discovery, node: v18.19.0, js-controller: 5.0.17
2024-02-14 11:22:23.184 - info: host.HK01-MA instance system.adapter.backitup.0 started with pid 20316
2024-02-14 11:22:24.076 - info: backitup.0 (20316) starting. Version 2.9.8 in C:/ioBroker/node_modules/iobroker.backitup, node: v18.19.0, js-controller: 5.0.17
2024-02-14 11:22:24.109 - info: backitup.0 (20316) [iobroker] backup will be activated at 02:48 every 1 day(s)
2024-02-14 11:22:27.421 - info: host.HK01-MA instance system.adapter.yahka.0 started with pid 21116
2024-02-14 11:22:28.506 - info: yahka.0 (21116) starting. Version 1.0.3 in C:/ioBroker/node_modules/iobroker.yahka, node: v18.19.0, js-controller: 5.0.17
2024-02-14 11:22:28.521 - info: yahka.0 (21116) adapter ready, checking config
2024-02-14 11:22:28.526 - info: yahka.0 (21116) publishing bridge Yahka-0 on 0.0.0.0 using avahi

MOD-EDIT: Code in code-tags gesetzt!

DJMarc75

@annetheke sagte in ioBroker lässt RAM überlaufen und andere Phänomene:

Der Error entsteht sofort beim Systemstart, da lief noch nicht ein Prozess von ioBroker

Dann sollte das eigentlich auch kein Problem von ioBroker sein.

AnneTheke

@oliverio Wenn ich einen neuen Datenträger nehme und da ein Fullbackup von einem ausgewählten Zeitpunkt drauf spiele, habe ich exakt den Softwarestand erreicht, den ich ausgewählt habe, zumal ich das auch an anderen Punkten der alten VM festmachen kann, wie ob ein bestimmtes Update des OS installiert ist oder nicht.

Homoran

@annetheke sagte in ioBroker lässt RAM überlaufen und andere Phänomene:

                        2024-02-14 10:23:00.334 - info: host.HK01-MA iobroker add s7 --host HK01-MA

warum wird der beim Start neu installiert?
ist da etwas früher schiefgelaufen?

@annetheke sagte in ioBroker lässt RAM überlaufen und andere Phänomene:

spawn EROFS

Read Only File System

Warum?

.... und Neustart

AnneTheke

@homoran said in ioBroker lässt RAM überlaufen und andere Phänomene:

warum wird der beim Start neu installiert?
ist da etwas früher schiefgelaufen?

Eigentlich nicht. Ich habe 2 s7 Adapter installiert und einen yahka. Schief gelaufen ist da nichts.

@homoran said in ioBroker lässt RAM überlaufen und andere Phänomene:

Read Only File System
Warum?

Das Filesystem ist kein Read Only System...

Homoran

@annetheke sagte in ioBroker lässt RAM überlaufen und andere Phänomene:

Das Filesystem ist kein Read Only System...

das log lügt eigentlich nicht

AnneTheke

@homoran

Es wäre ziemlich schlecht, wenn meine Systemplatte Read Only wäre, zumal ich ja fleißig Daten hin und her schicken kann... Ich habe allerdings mal grade dem ioBroker Dienst ein Benutzerkonto zugewiesen, für den Fall, dass das Systemkonto sich aus irgendwelchen Gründen weigern sollte, mitzuspielen.

OliverIO

@annetheke
Du gehst hier durch verschiedene Schichten mit Berechtigungen und Verfügbarkeiten.
Iobroker - vm Betriebssystem - VM - hypervisor - windows - Festplatten

An jeder Stelle könnte ein Problem auftreten.
Ist das festplattenimage für die vm noch groß genug?

Hast du eine Begrenzung auf Kerne/Threads eingestellt?
Der Fehler entsteht ja beim starten eines neuen Prozesses, der Brauch eine Zuordnung zu einen thread/Kern. Das könnte auch so ein Engpass sein. Der eigentlich nicht auftreten sollte.

Nutzt du in der vm wieder Windows? Besser wäre ein linux Betriebssystem zu verwenden. Ich denke so eine Konstellation haben nicht wirklich viele.

AnneTheke

@oliverio

Ist nur die Frage, was sich von jetzt auf gleich geändert hat, ohne dass jemand die Maschine berührt hat... Etwas über 80GB sind frei.

OliverIO

@annetheke
Ja damit versuchen wir dir zu helfen.
Allerdings mit deiner Konstellation stehst du ziemlich alleine da
Xcp, Windows auf Windows virtualisiert
Etwas muss sich verändert haben und wenn sich durch ein systemupdste von Windows sich irgendein Treiber geändert hat.
Deswegen auch der Tipp bei xcp auch mal in den Foren zu forschen.

AnneTheke

@oliverio

Dafür bin ich euch auch sehr dankbar, das Projekt ist etwas Umfangreich und leider nicht mal eben neu erstellt...

Windows ist nicht auf Windows virtualisiert.

XCP - Windows mit ioBroker, mehr gibt es nicht. Treiber haben sich keine geändert, auch nicht in einem Update, da das Windows keine Treiber aktualisiert, schon gar nicht selbst, und die Treiber sich bei XCP auch nicht wirklich oft ändern, es sei denn es käme eine neue Version von XCP raus und die wären auch wieder weg, wenn man auf einen älteren Stand restauriert. Eine Beschränkung an Threads gibt es nicht und Kerne logischer Weise nicht mehr, als die Hardware selbst hat.

AnneTheke

Hier das log vom letzten Start...

2024-02-14 14:21:36.990 - info: host.HK01-MA iobroker.js-controller version 5.0.17 js-controller starting
2024-02-14 14:21:36.992 - info: host.HK01-MA Copyright (c) 2014-2023 bluefox, 2014 hobbyquaker
2024-02-14 14:21:36.993 - info: host.HK01-MA hostname: HK01-MA, node: v18.19.0
2024-02-14 14:21:36.993 - info: host.HK01-MA ip addresses: fe80::e813:36d1:6136:d1a4 169.254.81.252 fe80::cee8:cf33:5c20:fb92 169.254.19.167 fe80::e556:8e21:6fc1:a33e 169.254.94.115 192.168.2.37 192.168.2.38 192.168.0.80 fe80::3ec8:d5d9:6bcf:acf3 169.254.94.3
2024-02-14 14:21:37.203 - info: host.HK01-MA connected to Objects and States
2024-02-14 14:21:37.210 - info: host.HK01-MA added notifications configuration of host
2024-02-14 14:21:37.528 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeCurrent"
2024-02-14 14:21:37.528 - info: host.HK01-MA 6 instances found
2024-02-14 14:21:37.532 - info: host.HK01-MA starting 6 instances
2024-02-14 14:21:37.556 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeNewest"
2024-02-14 14:21:37.560 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.nodeNewestNext"
2024-02-14 14:21:37.571 - info: host.HK01-MA instance system.adapter.admin.0 started with pid 7672
2024-02-14 14:21:37.571 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmCurrent"
2024-02-14 14:21:37.574 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmNewest"
2024-02-14 14:21:37.576 - info: host.HK01-MA Delete state "system.host.HK01-MA.versions.npmNewestNext"
2024-02-14 14:21:37.578 - info: host.HK01-MA Some obsolete host states deleted.
2024-02-14 14:21:38.769 - error: admin.0 (7672) admin.0 already running
2024-02-14 14:21:38.770 - warn: admin.0 (7672) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 14:21:39.330 - error: host.HK01-MA instance system.adapter.admin.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 14:21:39.330 - info: host.HK01-MA Restart adapter system.adapter.admin.0 because enabled
2024-02-14 14:21:41.551 - info: host.HK01-MA instance system.adapter.s7.0 started with pid 7200
2024-02-14 14:21:42.198 - error: s7.0 (7200) s7.0 already running
2024-02-14 14:21:42.199 - warn: s7.0 (7200) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 14:21:42.717 - error: host.HK01-MA instance system.adapter.s7.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 14:21:42.717 - info: host.HK01-MA Restart adapter system.adapter.s7.0 because enabled
2024-02-14 14:21:45.550 - info: host.HK01-MA instance system.adapter.s7.1 started with pid 8324
2024-02-14 14:21:46.265 - error: s7.1 (8324) s7.1 already running
2024-02-14 14:21:46.267 - warn: s7.1 (8324) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 14:21:46.798 - error: host.HK01-MA instance system.adapter.s7.1 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 14:21:46.799 - info: host.HK01-MA Restart adapter system.adapter.s7.1 because enabled
2024-02-14 14:21:49.571 - info: host.HK01-MA instance system.adapter.discovery.0 started with pid 8888
2024-02-14 14:21:50.323 - error: discovery.0 (8888) discovery.0 already running
2024-02-14 14:21:50.324 - warn: discovery.0 (8888) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 14:21:50.853 - error: host.HK01-MA instance system.adapter.discovery.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 14:21:50.853 - info: host.HK01-MA Restart adapter system.adapter.discovery.0 because enabled
2024-02-14 14:21:53.556 - info: host.HK01-MA instance system.adapter.backitup.0 started with pid 9124
2024-02-14 14:21:54.217 - error: backitup.0 (9124) backitup.0 already running
2024-02-14 14:21:54.218 - warn: backitup.0 (9124) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 14:21:54.744 - error: host.HK01-MA instance system.adapter.backitup.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 14:21:54.744 - info: host.HK01-MA Restart adapter system.adapter.backitup.0 because enabled
2024-02-14 14:21:57.550 - info: host.HK01-MA instance system.adapter.yahka.0 started with pid 8424
2024-02-14 14:21:58.665 - error: yahka.0 (8424) yahka.0 already running
2024-02-14 14:21:58.666 - warn: yahka.0 (8424) Terminated (ADAPTER_ALREADY_RUNNING): Without reason
2024-02-14 14:21:59.196 - error: host.HK01-MA instance system.adapter.yahka.0 terminated with code 7 (ADAPTER_ALREADY_RUNNING)
2024-02-14 14:21:59.196 - info: host.HK01-MA Restart adapter system.adapter.yahka.0 because enabled
2024-02-14 14:22:09.348 - info: host.HK01-MA instance system.adapter.admin.0 started with pid 6272
2024-02-14 14:22:10.413 - info: admin.0 (6272) starting. Version 6.13.16 in C:/ioBroker/node_modules/iobroker.admin, node: v18.19.0, js-controller: 5.0.17
2024-02-14 14:22:10.430 - info: admin.0 (6272) requesting all objects
2024-02-14 14:22:10.657 - info: admin.0 (6272) received all objects
2024-02-14 14:22:10.724 - info: admin.0 (6272) socket.io server listening on port 8081
2024-02-14 14:22:10.725 - info: admin.0 (6272) http server listening on port 8081
2024-02-14 14:22:10.725 - info: admin.0 (6272) Use link "http://127.0.0.1:8081" to configure.
2024-02-14 14:22:12.738 - info: host.HK01-MA instance system.adapter.s7.0 started with pid 3108
2024-02-14 14:22:13.573 - info: s7.0 (3108) starting. Version 1.4.2 in C:/ioBroker/node_modules/iobroker.s7, node: v18.19.0, js-controller: 5.0.17
2024-02-14 14:22:13.607 - info: s7.0 (3108) Connect in S7 mode to 0 / 2
2024-02-14 14:22:13.619 - info: s7.0 (3108) Successfully connected in S7 mode
2024-02-14 14:22:16.817 - info: host.HK01-MA instance system.adapter.s7.1 started with pid 6132
2024-02-14 14:22:17.677 - info: s7.1 (6132) starting. Version 1.4.2 in C:/ioBroker/node_modules/iobroker.s7, node: v18.19.0, js-controller: 5.0.17
2024-02-14 14:22:17.707 - info: s7.1 (6132) Connect in S7 mode to 0 / 2
2024-02-14 14:22:17.720 - info: s7.1 (6132) Successfully connected in S7 mode
2024-02-14 14:22:20.876 - info: host.HK01-MA instance system.adapter.discovery.0 started with pid 8124
2024-02-14 14:22:21.620 - info: discovery.0 (8124) starting. Version 4.2.0 in C:/ioBroker/node_modules/iobroker.discovery, node: v18.19.0, js-controller: 5.0.17
2024-02-14 14:22:24.768 - info: host.HK01-MA instance system.adapter.backitup.0 started with pid 6556
2024-02-14 14:22:25.567 - info: backitup.0 (6556) starting. Version 2.9.8 in C:/ioBroker/node_modules/iobroker.backitup, node: v18.19.0, js-controller: 5.0.17
2024-02-14 14:22:25.596 - info: backitup.0 (6556) [iobroker] backup will be activated at 02:48 every 1 day(s)
2024-02-14 14:22:29.222 - info: host.HK01-MA instance system.adapter.yahka.0 started with pid 1848
2024-02-14 14:22:30.045 - info: yahka.0 (1848) starting. Version 1.0.3 in C:/ioBroker/node_modules/iobroker.yahka, node: v18.19.0, js-controller: 5.0.17
2024-02-14 14:22:30.060 - info: yahka.0 (1848) adapter ready, checking config
2024-02-14 14:22:30.064 - info: yahka.0 (1848) publishing bridge Yahka-0 on 0.0.0.0 using avahi
2024-02-14 14:57:25.412 - info: admin.0 (6272) ==> Connected system.user.admin from ::ffff:127.0.0.1

AnneTheke

@oliverio

So, es funktioniert wieder. Falls jemand das Problem mal haben sollte, Antiviren-Software kann komische Sachen machen. Was auch immer beim Automatischen Update dieser passiert, es war nicht gut für ioBroker.

@Homoran

Thema kann dann geschlossen werden, die Kiste läuft seit mehreren Stunden auf der alten Instanz und fehlerfrei.

Danke für die Hilfe an alle!

Wildbill

@annetheke Was sagt uns das? Antivirensoftware gehört heutzutage auch nicht mehr separat installiert. Die in den Systemen integrierten (bei Dir der Windows Defender“ sind ausreichend. Jede zusätzlich installierte Antivirensoftware muss, um zu funktionieren, Löcher in diese Schutzschicht reißen. Die einzigen, die heutzutage noch von Antivirensoftware profitieren sind deren Hersteller.
Die integrierten Systeme und etwas überlegtes Handeln (nicht alles anklicken, nicht überall alles was kostenlos ist udn woanders Geld kostet herunterladen, …) sind mehr als ausreichend.
BTW, welche Antivirensoftware war es denn bei Dir?

Gruss, Jürgen

OliverIO

@annetheke

Also war doch etwas anders und nicht exakt der gleiche Zustand wieder hergestellt.

NEWS

ioBroker lässt RAM überlaufen und andere Phänomene

Support us

890
Online

32.0k
Users

80.4k
Topics

1.3m
Posts

NEWS

ioBroker lässt RAM überlaufen und andere Phänomene

Support us

890Online

32.0kUsers

80.4kTopics

1.3mPosts

890
Online

32.0k
Users

80.4k
Topics

1.3m
Posts