Navigation

    Logo
    • Register
    • Login
    • Search
    • Recent
    • Tags
    • Unread
    • Categories
    • Unreplied
    • Popular
    • GitHub
    • Docu
    • Hilfe
    1. Home
    2. Deutsch
    3. ioBroker Allgemein
    4. js-controller 5.0.x jetzt in der BETA

    NEWS

    • ioBroker@Smart Living Forum Solingen, 14.06. - Agenda added

    • ioBroker goes Matter ... Matter Adapter in Stable

    • Monatsrückblick - April 2025

    js-controller 5.0.x jetzt in der BETA

    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      ticaki Developer last edited by

      Bis auf ein nötiges iob fix lief alles glatt

      1 Reply Last reply Reply Quote 0
      • Feuersturm
        Feuersturm last edited by

        Ich hab gerade einmal todesmutig die js-controller Update Funktion über den Admin ausprobiert 🙂
        @apollon77 @foxriver76 Sollte das schon mit der 5.0.2 und Admin 5.6.7 funktionieren?
        Bei dieser Anzeige bleibt der Admin hängen:
        145bf730-ab27-43a6-bf15-31840a4b457c-grafik.png

        Wenn ich über die Konsole mir den Status anzeigen lasse sieht es wie folgt aus:

        proxmox@ioBrokerTestsystem:~$ iob status
iobroker is not running on this host.


Objects type: jsonl
States  type: jsonl
proxmox@ioBrokerTestsystem:~$ iob version
5.0.2

        Im Log steht folgendes:

        2023-06-12 19:30:35.219  - info: host.ioBrokerTestsystem Controller will upgrade itself to version 5.0.2
2023-06-12 19:30:40.279  - info: host.ioBrokerTestsystem received SIGTERM
2023-06-12 19:30:40.286  - info: admin.0 (345) terminating http server on port 8081
2023-06-12 19:30:40.285  - info: javascript.0 (379) Stop script script.js.Skripte.Kalender.ical_0_ToHtmlTable
2023-06-12 19:30:40.336  - info: trashschedule.0 (631) cleaned everything up...
2023-06-12 19:30:40.304  - info: hm-rpc.0 (500) xmlrpc -> 192.168.178.84:2010/ init ["http://192.168.178.77:2010",""]
2023-06-12 19:30:40.310  - info: backitup.0 (515) cleaned everything up...
2023-06-12 19:30:40.341  - info: unifi.0 (485) cleaned everything up...
2023-06-12 19:30:40.341  - info: simple-api.0 (605) terminating http server on port 8087
2023-06-12 19:30:40.337  - info: proxmox.0 (586) cleaned everything up...
2023-06-12 19:30:40.351  - info: device-watcher.0 (783) cleaned everything up...
2023-06-12 19:30:40.334  - info: valloxmv.0 (653) cleaned everything up...
2023-06-12 19:30:40.399  - info: hm-rpc.0 (500) Disconnected
2023-06-12 19:30:40.332  - info: javascript.0 (379) Stop script script.js.Skripte.Kalender.ical_2_ToHtmlTable
2023-06-12 19:30:40.334  - info: javascript.0 (379) Stop script script.js.Skripte.Kalender.ical_3_ToHtmlTable
2023-06-12 19:30:40.344  - info: javascript.0 (379) Stop script script.js.Skripte.Kalender.ical_4_ToHtmlTable
2023-06-12 19:30:40.345  - info: javascript.0 (379) Stop script script.js.Skripte.Kalender.muellkalender
2023-06-12 19:30:40.347  - info: javascript.0 (379) Stop script script.js.Skripte.Netzwerk.Unifi_Vouchers
2023-06-12 19:30:40.319  - info: info.0 (556) cleaned everything up...
2023-06-12 19:30:40.285  - info: host.ioBrokerTestsystem stopInstance system.adapter.admin.0 (force=false, process=true)
2023-06-12 19:30:40.287  - info: host.ioBrokerTestsystem stopInstance system.adapter.influxdb.0 (force=false, process=true)
2023-06-12 19:30:40.289  - info: host.ioBrokerTestsystem stopInstance system.adapter.javascript.0 (force=false, process=true)
2023-06-12 19:30:40.291  - info: host.ioBrokerTestsystem stopInstance system.adapter.scenes.0 (force=false, process=true)
2023-06-12 19:30:40.293  - info: host.ioBrokerTestsystem stopInstance system.adapter.telegram.0 (force=false, process=false)
2023-06-12 19:30:40.294  - info: host.ioBrokerTestsystem stopInstance system.adapter.scheduler.0 (force=false, process=true)
2023-06-12 19:30:40.295  - info: host.ioBrokerTestsystem stopInstance system.adapter.fritzbox.0 (force=false, process=true)
2023-06-12 19:30:40.297  - info: host.ioBrokerTestsystem stopInstance system.adapter.hue.0 (force=false, process=true)
2023-06-12 19:30:40.299  - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.0 (force=false, process=false)
2023-06-12 19:30:40.300  - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.1 (force=false, process=false)
2023-06-12 19:30:40.301  - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.2 (force=false, process=false)
2023-06-12 19:30:40.303  - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.3 (force=false, process=false)
2023-06-12 19:30:40.304  - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.4 (force=false, process=false)
2023-06-12 19:30:40.305  - info: host.ioBrokerTestsystem stopInstance system.adapter.ical.5 (force=false, process=false)
2023-06-12 19:30:40.307  - info: host.ioBrokerTestsystem stopInstance system.adapter.mqtt.0 (force=false, process=false)
2023-06-12 19:30:40.308  - info: host.ioBrokerTestsystem stopInstance system.adapter.samsung-community.0 (force=false, process=false)
2023-06-12 19:30:40.309  - info: host.ioBrokerTestsystem stopInstance system.adapter.spotify-premium.0 (force=false, process=false)
2023-06-12 19:30:40.310  - info: host.ioBrokerTestsystem stopInstance system.adapter.tr-064.0 (force=false, process=true)
2023-06-12 19:30:40.314  - info: host.ioBrokerTestsystem stopInstance system.adapter.unifi.0 (force=false, process=true)
2023-06-12 19:30:40.316  - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rpc.0 (force=false, process=true)
2023-06-12 19:30:40.317  - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rega.0 (force=false, process=false)
2023-06-12 19:30:40.319  - info: host.ioBrokerTestsystem stopInstance system.adapter.backitup.0 (force=false, process=true)
2023-06-12 19:30:40.320  - info: host.ioBrokerTestsystem stopInstance system.adapter.benchmark.0 (force=false, process=false)
2023-06-12 19:30:40.321  - info: host.ioBrokerTestsystem stopInstance system.adapter.daswetter.0 (force=false, process=false)
2023-06-12 19:30:40.324  - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.daswetter.0
2023-06-12 19:30:40.325  - info: host.ioBrokerTestsystem stopInstance system.adapter.dwd.0 (force=false, process=false)
2023-06-12 19:30:40.326  - info: host.ioBrokerTestsystem stopInstance canceled schedule system.adapter.dwd.0
2023-06-12 19:30:40.327  - info: host.ioBrokerTestsystem stopInstance system.adapter.fully-tablet-control.0 (force=false, process=false)
2023-06-12 19:30:40.328  - info: host.ioBrokerTestsystem stopInstance system.adapter.info.0 (force=false, process=true)
2023-06-12 19:30:40.330  - info: host.ioBrokerTestsystem stopInstance system.adapter.nina.0 (force=false, process=true)
2023-06-12 19:30:40.332  - info: host.ioBrokerTestsystem stopInstance system.adapter.proxmox.0 (force=false, process=true)
2023-06-12 19:30:40.333  - info: host.ioBrokerTestsystem stopInstance system.adapter.rainbird.0 (force=false, process=false)
2023-06-12 19:30:40.335  - info: host.ioBrokerTestsystem stopInstance system.adapter.sayit.0 (force=false, process=false)
2023-06-12 19:30:40.358  - info: host.ioBrokerTestsystem stopInstance system.adapter.simple-api.0 (force=false, process=true)
2023-06-12 19:30:40.359  - info: host.ioBrokerTestsystem stopInstance system.adapter.socketio.0 (force=false, process=false)
2023-06-12 19:30:40.361  - info: host.ioBrokerTestsystem stopInstance system.adapter.tankerkoenig.0 (force=false, process=true)
2023-06-12 19:30:40.380  - info: host.ioBrokerTestsystem stopInstance system.adapter.trashschedule.0 (force=false, process=true)
2023-06-12 19:30:40.382  - info: host.ioBrokerTestsystem stopInstance system.adapter.valloxmv.0 (force=false, process=true)
2023-06-12 19:30:40.383  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-fancyswitch.0 (force=false, process=false)
2023-06-12 19:30:40.385  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-google-fonts.0 (force=false, process=false)
2023-06-12 19:30:40.386  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-history.0 (force=false, process=false)
2023-06-12 19:30:40.387  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-jqui-mfd.0 (force=false, process=false)
2023-06-12 19:30:40.388  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-justgage.0 (force=false, process=false)
2023-06-12 19:30:40.389  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-map.0 (force=false, process=false)
2023-06-12 19:30:40.391  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-materialdesign.0 (force=false, process=false)
2023-06-12 19:30:40.392  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-timeandweather.0 (force=false, process=false)
2023-06-12 19:30:40.393  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis.0 (force=false, process=false)
2023-06-12 19:30:40.394  - info: host.ioBrokerTestsystem stopInstance system.adapter.web.0 (force=false, process=true)
2023-06-12 19:30:40.396  - info: host.ioBrokerTestsystem stopInstance system.adapter.worx.0 (force=false, process=false)
2023-06-12 19:30:40.397  - info: host.ioBrokerTestsystem stopInstance system.adapter.device-watcher.0 (force=false, process=true)
2023-06-12 19:30:40.399  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-beta.0 (force=false, process=true)
2023-06-12 19:30:40.400  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-metro.0 (force=false, process=false)
2023-06-12 19:30:40.402  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-jaeger-design.0 (force=false, process=false)
2023-06-12 19:30:40.403  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-energy.0 (force=false, process=false)
2023-06-12 19:30:40.404  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-gauges.0 (force=false, process=false)
2023-06-12 19:30:40.405  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-widgets-material.0 (force=false, process=false)
2023-06-12 19:30:40.532  - info: admin.0 (345) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.535  - info: scenes.0 (394) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.540  - info: hue.0 (455) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.541  - info: tr-064.0 (470) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.537  - info: javascript.0 (379) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.552  - info: unifi.0 (485) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.554  - info: hm-rpc.0 (500) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.557  - info: backitup.0 (515) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.560  - info: info.0 (556) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.541  - info: fritzbox.0 (436) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.568  - info: proxmox.0 (586) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.562  - info: nina.0 (563) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.573  - info: trashschedule.0 (631) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.574  - info: valloxmv.0 (653) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.543  - info: scheduler.0 (409) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.577  - info: simple-api.0 (605) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.572  - info: tankerkoenig.0 (616) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.581  - info: device-watcher.0 (783) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.588  - info: scenes.0 (394) terminating
2023-06-12 19:30:40.592  - info: scenes.0 (394) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.588  - info: tr-064.0 (470) terminating
2023-06-12 19:30:40.592  - info: tr-064.0 (470) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.597  - info: fritzbox.0 (436) terminating
2023-06-12 19:30:40.598  - info: unifi.0 (485) terminating
2023-06-12 19:30:40.597  - info: backitup.0 (515) terminating
2023-06-12 19:30:40.597  - info: admin.0 (345) terminating
2023-06-12 19:30:40.601  - info: backitup.0 (515) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.580  - info: web.0 (744) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.603  - info: tankerkoenig.0 (616) terminating
2023-06-12 19:30:40.599  - info: nina.0 (563) terminating
2023-06-12 19:30:40.606  - info: valloxmv.0 (653) terminating
2023-06-12 19:30:40.601  - info: fritzbox.0 (436) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.608  - info: nina.0 (563) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.608  - info: valloxmv.0 (653) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.594  - info: scheduler.0 (409) terminating
2023-06-12 19:30:40.603  - info: trashschedule.0 (631) terminating
2023-06-12 19:30:40.612  - info: info.0 (556) terminating
2023-06-12 19:30:40.612  - info: scheduler.0 (409) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.606  - info: proxmox.0 (586) terminating
2023-06-12 19:30:40.616  - info: info.0 (556) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.613  - info: trashschedule.0 (631) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.607  - info: tankerkoenig.0 (616) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.620  - info: device-watcher.0 (783) terminating
2023-06-12 19:30:40.623  - info: javascript.0 (379) terminating
2023-06-12 19:30:40.610  - info: unifi.0 (485) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.620  - info: simple-api.0 (605) terminating
2023-06-12 19:30:40.614  - info: admin.0 (345) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.627  - info: hm-rpc.0 (500) terminating
2023-06-12 19:30:40.623  - info: simple-api.0 (605) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.620  - info: influxdb.0 (356) terminating
2023-06-12 19:30:40.629  - info: influxdb.0 (356) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.626  - info: javascript.0 (379) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.618  - info: proxmox.0 (586) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.634  - info: hm-rpc.0 (500) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.630  - info: device-watcher.0 (783) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.583  - info: vis-2-beta.0 (799) Got terminate signal TERMINATE_YOURSELF
2023-06-12 19:30:40.645  - info: vis-2-beta.0 (799) terminating
2023-06-12 19:30:40.648  - info: vis-2-beta.0 (799) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.663  - info: host.ioBrokerTestsystem stopInstance system.adapter.admin.0 send kill signal
2023-06-12 19:30:40.670  - info: host.ioBrokerTestsystem stopInstance system.adapter.javascript.0 send kill signal
2023-06-12 19:30:40.671  - info: host.ioBrokerTestsystem stopInstance system.adapter.scenes.0 send kill signal
2023-06-12 19:30:40.672  - info: host.ioBrokerTestsystem stopInstance system.adapter.scheduler.0 send kill signal
2023-06-12 19:30:40.673  - info: host.ioBrokerTestsystem stopInstance system.adapter.fritzbox.0 send kill signal
2023-06-12 19:30:40.673  - info: host.ioBrokerTestsystem stopInstance system.adapter.hue.0 send kill signal
2023-06-12 19:30:40.674  - info: host.ioBrokerTestsystem stopInstance system.adapter.tr-064.0 send kill signal
2023-06-12 19:30:40.675  - info: host.ioBrokerTestsystem stopInstance system.adapter.unifi.0 send kill signal
2023-06-12 19:30:40.677  - info: host.ioBrokerTestsystem stopInstance system.adapter.hm-rpc.0 send kill signal
2023-06-12 19:30:40.677  - info: host.ioBrokerTestsystem stopInstance system.adapter.backitup.0 send kill signal
2023-06-12 19:30:40.679  - info: host.ioBrokerTestsystem stopInstance system.adapter.info.0 send kill signal
2023-06-12 19:30:40.680  - info: host.ioBrokerTestsystem stopInstance system.adapter.nina.0 send kill signal
2023-06-12 19:30:40.681  - info: host.ioBrokerTestsystem stopInstance system.adapter.proxmox.0 send kill signal
2023-06-12 19:30:40.682  - info: host.ioBrokerTestsystem stopInstance system.adapter.simple-api.0 send kill signal
2023-06-12 19:30:40.685  - info: host.ioBrokerTestsystem stopInstance system.adapter.tankerkoenig.0 send kill signal
2023-06-12 19:30:40.686  - info: host.ioBrokerTestsystem stopInstance system.adapter.trashschedule.0 send kill signal
2023-06-12 19:30:40.687  - info: host.ioBrokerTestsystem stopInstance system.adapter.valloxmv.0 send kill signal
2023-06-12 19:30:40.688  - info: host.ioBrokerTestsystem stopInstance system.adapter.web.0 send kill signal
2023-06-12 19:30:40.689  - info: host.ioBrokerTestsystem stopInstance system.adapter.device-watcher.0 send kill signal
2023-06-12 19:30:40.690  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-beta.0 send kill signal
2023-06-12 19:30:40.704  - info: hue.0 (455) cleaned everything up...
2023-06-12 19:30:40.727  - info: web.0 (744) terminated http server on port 8082
2023-06-12 19:30:40.771  - info: hue.0 (455) terminating
2023-06-12 19:30:40.777  - info: hue.0 (455) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.781  - info: web.0 (744) terminating
2023-06-12 19:30:40.790  - info: javascript.0 (379) terminating
2023-06-12 19:30:40.788  - info: web.0 (744) Terminated (NO_ERROR): Without reason
2023-06-12 19:30:40.800  - info: scenes.0 (394) terminating
2023-06-12 19:30:40.806  - info: scheduler.0 (409) terminating
2023-06-12 19:30:40.813  - info: tr-064.0 (470) terminating
2023-06-12 19:30:40.821  - info: fritzbox.0 (436) terminating
2023-06-12 19:30:40.823  - info: admin.0 (345) terminating
2023-06-12 19:30:40.832  - info: nina.0 (563) terminating
2023-06-12 19:30:40.850  - info: trashschedule.0 (631) terminating
2023-06-12 19:30:40.867  - info: web.0 (744) terminating
2023-06-12 19:30:40.872  - info: tankerkoenig.0 (616) terminating
2023-06-12 19:30:40.872  - info: hue.0 (455) terminating
2023-06-12 19:30:40.900  - info: unifi.0 (485) terminating
2023-06-12 19:30:40.907  - info: vis-2-beta.0 (799) terminating
2023-06-12 19:30:40.926  - info: backitup.0 (515) terminating
2023-06-12 19:30:40.935  - info: proxmox.0 (586) terminating
2023-06-12 19:30:40.940  - info: simple-api.0 (605) terminating
2023-06-12 19:30:40.944  - info: device-watcher.0 (783) terminating
2023-06-12 19:30:40.947  - info: info.0 (556) terminating
2023-06-12 19:30:40.949  - info: valloxmv.0 (653) terminating
2023-06-12 19:30:41.764  - info: host.ioBrokerTestsystem stopInstance system.adapter.hue.0 killing pid 455
2023-06-12 19:30:41.773  - info: host.ioBrokerTestsystem stopInstance system.adapter.web.0 killing pid 744
2023-06-12 19:30:41.776  - info: host.ioBrokerTestsystem stopInstance system.adapter.vis-2-beta.0 killing pid 799
2023-06-12 19:30:41.887  - info: host.ioBrokerTestsystem instance system.adapter.tr-064.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:41.930  - info: host.ioBrokerTestsystem instance system.adapter.scenes.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:43.735  - info: host.ioBrokerTestsystem instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:43.823  - info: host.ioBrokerTestsystem instance system.adapter.nina.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:43.825  - info: host.ioBrokerTestsystem instance system.adapter.simple-api.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:43.973  - info: host.ioBrokerTestsystem instance system.adapter.admin.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:43.975  - info: host.ioBrokerTestsystem instance system.adapter.influxdb.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.021  - info: host.ioBrokerTestsystem instance system.adapter.javascript.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.088  - info: host.ioBrokerTestsystem instance system.adapter.scheduler.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.089  - info: host.ioBrokerTestsystem instance system.adapter.fritzbox.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.209  - info: host.ioBrokerTestsystem instance system.adapter.unifi.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.210  - info: host.ioBrokerTestsystem instance system.adapter.hm-rpc.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.248  - info: host.ioBrokerTestsystem instance system.adapter.info.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.332  - info: host.ioBrokerTestsystem instance system.adapter.proxmox.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.333  - info: host.ioBrokerTestsystem instance system.adapter.tankerkoenig.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.450  - info: host.ioBrokerTestsystem instance system.adapter.trashschedule.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.451  - info: host.ioBrokerTestsystem instance system.adapter.valloxmv.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.542  - info: host.ioBrokerTestsystem instance system.adapter.device-watcher.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.543  - info: host.ioBrokerTestsystem All instances are stopped.
2023-06-12 19:30:44.545  - warn: host.ioBrokerTestsystem instance system.adapter.hue.0 terminated due to SIGTERM
2023-06-12 19:30:44.546  - info: host.ioBrokerTestsystem instance system.adapter.hue.0 terminated with code null ()
2023-06-12 19:30:44.547  - info: host.ioBrokerTestsystem All instances are stopped.
2023-06-12 19:30:44.656  - warn: host.ioBrokerTestsystem instance system.adapter.web.0 terminated due to SIGTERM
2023-06-12 19:30:44.658  - info: host.ioBrokerTestsystem instance system.adapter.web.0 terminated with code null ()
2023-06-12 19:30:44.659  - info: host.ioBrokerTestsystem All instances are stopped.
2023-06-12 19:30:44.760  - info: host.ioBrokerTestsystem instance system.adapter.vis-2-beta.0 terminated with code 0 (NO_ERROR)
2023-06-12 19:30:44.762  - info: host.ioBrokerTestsystem All instances are stopped.
2023-06-12 19:30:44.840  - info: host.ioBrokerTestsystem terminated

        foxriver76 crunchip 2 Replies Last reply Reply Quote 0
        • foxriver76
          foxriver76 Developer @Feuersturm last edited by

          @feuersturm Ja sollte gehen - sieht allerdings so aus als wäre Upgrade erfolgreich - allerdings Controller nicht wieder gestartet?

          Feuersturm 1 Reply Last reply Reply Quote 0
          • Feuersturm
            Feuersturm @foxriver76 last edited by

            @foxriver76 Ich hab gerade mal ein iob start ausgeführt und das System scheint normal zu funktionieren. Keine besonderen Fehler im Log und die Instanzen sind auch Grün.
            Issue beim js-controller anlegen?

            foxriver76 1 Reply Last reply Reply Quote 0
            • foxriver76
              foxriver76 Developer @Feuersturm last edited by foxriver76

              @feuersturm Ja bitte, und das im Screenshot war alles an Log was kam?

              Feuersturm 1 Reply Last reply Reply Quote 0
              • Feuersturm
                Feuersturm @foxriver76 last edited by Feuersturm

                @foxriver76 Ja, das war das Ende vom current Log.

                Edit: Github issue: https://github.com/ioBroker/ioBroker.js-controller/issues/2291

                Feuer-sturm created this issue in ioBroker/ioBroker.js-controller

                closed js-controller update over admin does not start iobroker after finishing #2291

                1 Reply Last reply Reply Quote 0
                • crunchip
                  crunchip Forum Testing Most Active @Feuersturm last edited by

                  @feuersturm sagte in js-controller 5.0.x jetzt in der BETA:

                  die js-controller Update Funktion über den Admin ausprobiert

                  @foxriver76
                  ich hab da gar keine Möglichkeit
                  88cb8e49-0150-426a-b28d-e81b890bee08-image.png

                  Feuersturm 1 Reply Last reply Reply Quote 0
                  • Feuersturm
                    Feuersturm @crunchip last edited by

                    @crunchip Welche Adminversion nutzt du?
                    Mit Admin 6.5.7 und dem letzten js-controller aus dem Alpha Stadium sieht das bei mir so aus:
                    e4bf2c07-0bab-4051-bde2-766a24122093-grafik.png

                    crunchip 1 Reply Last reply Reply Quote 0
                    • crunchip
                      crunchip Forum Testing Most Active @Feuersturm last edited by

                      @feuersturm sagte in js-controller 5.0.x jetzt in der BETA:

                      Admin 6.5.7

                      foxriver76 1 Reply Last reply Reply Quote 0
                      • heinhan
                        heinhan @foxriver76 last edited by

                        @foxriver76 upload durchgeführt, zusätzlich war ein Reboot notwendig. Jetzt läuft der Host ohne Fehlermeldung. Dies zur Info

                        heinhan 1 Reply Last reply Reply Quote 0
                        • ice987
                          ice987 last edited by ice987

                          bei mir erscheint

                          IMG_0254.jpeg

                          2023-06-12 21:02:59.879 - info: host.iobroker-testsystem8 Updating repository "beta" under "http://download.iobroker.net/sources-dist-latest.json"
2023-06-12 21:03:32.474 - info: host.iobroker-testsystem8 Controller will upgrade itself to version 5.0.2
2023-06-12 21:04:11.371 - info: host.iobroker-testsystem8 Controller will upgrade itself to version 5.0.2

                          Plattform: docker
                          Betriebssystem: linux
                          Architektur: x64
                          Node.js: v18.16.0
                          NPM: 9.5.1

                          ice987 1 Reply Last reply Reply Quote 0
                          • foxriver76
                            foxriver76 Developer @crunchip last edited by

                            @crunchip Welches Betriebssystem?

                            crunchip 1 Reply Last reply Reply Quote 0
                            • crunchip
                              crunchip Forum Testing Most Active @foxriver76 last edited by crunchip

                              @foxriver76 debian VM in Proxmox
                              aktuell js-controller: 5.0.1-alpha.0-20230406-4552d569
                              f9c214e7-78b9-422b-8ab1-bda8e9a9cdba-image.png

                              foxriver76 1 Reply Last reply Reply Quote 0
                              • foxriver76
                                foxriver76 Developer @crunchip last edited by

                                @crunchip Hmm.. ok dann sollte es eigentlich gehen. Müsste @Bluefox etwas zu sagen, wie der Admin Check genau ausschaut.

                                haselchen crunchip 2 Replies Last reply Reply Quote 0
                                • haselchen
                                  haselchen Most Active @foxriver76 last edited by

                                  @foxriver76

                                  @crunchip , ich und erstmal @heinhan hatten das „VIS“ Problem.
                                  Kommt da ein Fix zu ?!

                                  E 1 Reply Last reply Reply Quote 0
                                  • Chaot
                                    Chaot @apollon77 last edited by Chaot

                                    @apollon77
                                    Der LGTV Adapter fällt aus wie erwartet (ist aber bei mir eher unwichtig)
                                    Dazu kommt noch eine Fehlermeldung:

                                    host.ioBroker
2023-06-12 22:06:50.881	error	cannot call visUtils: Not exists

                                    Die Fehlermeldung blieb jetzt erstmal weg nachdem ich den VIS Adapter nochmal hochgeladen habe.
                                    Ansonsten scheint alles zu laufen.

                                    Edit:
                                    Scheinbar kommt doch noch was:

                                    host.ioBroker
2023-06-12 22:20:00.903	error	instance system.adapter.web.0 terminated with code 1 (JS_CONTROLLER_STOPPED)
host.ioBroker
2023-06-12 22:20:00.903	error	Caught by controller[1]: at processImmediate (node:internal/timers:478:21)
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[1]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46)
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[1]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[1]: Error: The pattern "Montag<br>12.06.2023" is not a valid ID pattern
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[0]: at processImmediate (node:internal/timers:478:21)
host.ioBroker
2023-06-12 22:20:00.902	error	Caught by controller[0]: at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46)
host.ioBroker
2023-06-12 22:20:00.901	error	Caught by controller[0]: at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15)
host.ioBroker
2023-06-12 22:20:00.899	error	Caught by controller[0]: Error: The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.678	error	The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.678	error	Error: The pattern "Montag<br>12.06.2023" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46) at processImmediate (node:internal/timers:478:21)

web.0
2023-06-12 22:20:00.677	error	uncaught exception: The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.638	error	The pattern "Montag<br>12.06.2023" is not a valid ID pattern

web.0
2023-06-12 22:20:00.637	error	Error: The pattern "Montag<br>12.06.2023" is not a valid ID pattern at Object.pattern2RegEx (/opt/iobroker/node_modules/@iobroker/js-controller-common/src/lib/common/tools.ts:2415:15) at Immediate.<anonymous> (/opt/iobroker/node_modules/@iobroker/js-controller-adapter/src/lib/adapter/adapter.ts:9313:46) at processImmediate (node:internal/timers:478:21)

web.0
2023-06-12 22:20:00.631	error	uncaught exception: The pattern "Montag<br>12.06.2023" is not a valid ID pattern
                                    apollon77 Neuschwansteini 2 Replies Last reply Reply Quote 0
                                    • Chaot
                                      Chaot last edited by

                                      Der VIS Editor hat auf zwei von 5 Projekten mit einem Absturz reagiert. Nach einem Neustart der ganzen VM scheint es jetzt allerdings zu laufen.
                                      Ich habe zwei Fehlermeldungen, die aber scheinbar bei mir aus dem System kommen und nichts mit dem Controler zu tun haben.
                                      Wie bekomme ich die weg?

                                      host.ioBroker
2023-06-12 22:30:52.020	error	iobroker npm-install: host.ioBroker Unknown packetName fontui. Please install packages from outside the repository using npm!
host.ioBroker
2023-06-12 22:30:43.727	error	iobroker npm-install: host.ioBroker Unknown packetName openuv. Please install packages from outside the repository using npm!

                                      Da scheint irgendwas falsch installiert zu sein.

                                      Thomas Braun 1 Reply Last reply Reply Quote 0
                                      • Thomas Braun
                                        Thomas Braun Most Active @Chaot last edited by

                                        @chaot sagte in js-controller 5.0.x jetzt in der BETA:

                                        Wie bekomme ich die weg?

                                        Das sind wohl verwaiste Adapter. Wenn die nicht benötigt werden würde ich die vor die Tür setzen.

                                        Chaot 1 Reply Last reply Reply Quote 0
                                        • Chaot
                                          Chaot @Thomas Braun last edited by

                                          @thomas-braun Dachte ich auch. Danke dir.
                                          Haben gerade den Tritt bekommen.

                                          1 Reply Last reply Reply Quote 0
                                          • E
                                            e-i-k-e @haselchen last edited by

                                            @haselchen sagte in js-controller 5.0.x jetzt in der BETA:

                                            @foxriver76

                                            @crunchip , ich und erstmal @heinhan hatten das „VIS“ Problem.
                                            Kommt da ein Fix zu ?!

                                            Ich habe den Fehler bei mir auch beobachten können. Bin allerdings noch auf der letzten Alpha von js.Controller.

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post

                                            Support us

                                            ioBroker
                                            Community Adapters
                                            Donate
                                            FAQ Cloud / IOT
                                            HowTo: Node.js-Update
                                            HowTo: Backup/Restore
                                            Downloads
                                            BLOG

                                            906
                                            Online

                                            31.7k
                                            Users

                                            79.8k
                                            Topics

                                            1.3m
                                            Posts

                                            71
                                            580
                                            120701
                                            Loading More Posts
                                            • Oldest to Newest
                                            • Newest to Oldest
                                            • Most Votes
                                            Reply
                                            • Reply as topic
                                            Log in to reply
                                            Community
                                            Impressum | Datenschutz-Bestimmungen | Nutzungsbedingungen
                                            The ioBroker Community 2014-2023
                                            logo