In my portainer environment i observed, that my iobroker installatin was suddenly unhealthy.
I tried to setup a fresh container with iobroker only and also this container changes from healthy to unhealthy immediately after installation.
in the logs (container and iobroker) i can not detect any problems. the iobroker is running as expected. but has the state unhealthy.
the only thing i can see is the following output in portainer.
is this a problem in the container, or do i have a problem on my system?
edit:
i checked within the container console... seems for me to be an issue in the container...
br peter
Image version
latest-v9
Docker logs / Docker Protokoll
--------------------------------------------------------------------------------
------------------------- 2023-12-28 11:39:18 -------------------------
--------------------------------------------------------------------------------
----- -----
----- ██╗ ██████╗ ██████╗ ██████╗ ██████╗ ██╗ ██╗ ███████╗ ██████╗ -----
----- ██║ ██╔═══██╗ ██╔══██╗ ██╔══██╗ ██╔═══██╗ ██║ ██╔╝ ██╔════╝ ██╔══██╗ -----
----- ██║ ██║ ██║ ██████╔╝ ██████╔╝ ██║ ██║ █████╔╝ █████╗ ██████╔╝ -----
----- ██║ ██║ ██║ ██╔══██╗ ██╔══██╗ ██║ ██║ ██╔═██╗ ██╔══╝ ██╔══██╗ -----
----- ██║ ╚██████╔╝ ██████╔╝ ██║ ██║ ╚██████╔╝ ██║ ██╗ ███████╗ ██║ ██║ -----
----- ╚═╝ ╚═════╝ ╚═════╝ ╚═╝ ╚═╝ ╚═════╝ ╚═╝ ╚═╝ ╚══════╝ ╚═╝ ╚═╝ -----
----- -----
----- Welcome to your ioBroker Docker container! -----
----- Startupscript is now running! -----
----- Please be patient! -----
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
----- System Information -----
----- arch: x86_64 -----
----- hostname: IOBroker -----
----- -----
----- Version Information -----
----- image: v9.0.1 -----
----- build: 2023-10-26T23:44:46+00:00 -----
----- node: v18.18.2 -----
----- npm: 9.8.1 -----
----- -----
----- Environment Variables -----
----- SETGID: 1000 -----
----- SETUID: 1000 -----
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
----- Step 1 of 5: Preparing container -----
--------------------------------------------------------------------------------
Updating Linux packages on first run... Done.
Registering maintenance script as command... Done.
--------------------------------------------------------------------------------
----- Step 2 of 5: Detecting ioBroker installation -----
--------------------------------------------------------------------------------
Existing installation of ioBroker detected in "/opt/iobroker".
--------------------------------------------------------------------------------
----- Step 3 of 5: Checking ioBroker installation -----
--------------------------------------------------------------------------------
(Re)setting permissions (This might take a while! Please be patient!)... Done.
Checking Database connection... Done.
Hostname in ioBroker matches the hostname of this container.
No action required.
--------------------------------------------------------------------------------
----- Step 4 of 5: Applying special settings -----
--------------------------------------------------------------------------------
Some adapters have special requirements/ settings which can be activated by the use of environment variables.
For more information see ioBroker Docker Image Docs (https://docs.buanet.de/iobroker-docker-image/docs/).
--------------------------------------------------------------------------------
----- Step 5 of 5: ioBroker startup -----
--------------------------------------------------------------------------------
Starting ioBroker...
##### #### ### ## # iobroker.js-controller log output # ## ### #### #####
host.IOBroker check instance "system.adapter.admin.0" for host "IOBroker"
host.IOBroker check instance "system.adapter.discovery.0" for host "IOBroker"
host.IOBroker check instance "system.adapter.backitup.0" for host "IOBroker"
Send diag info: {"uuid":"80ba583f-babc-4bb9-843d-750c66a4e62d","language":"de","country":"","hosts":[{"version":"5.0.17","platform":"Javascript/Node.js","type":"linux"}],"node":"v18.18.2","arch":"x64","docker":true,"adapters":{"admin":{"version":"6.12.0","platform":"Javascript/Node.js"},"discovery":{"version":"4.2.0","platform":"Javascript/Node.js"},"backitup":{"version":"2.9.8","platform":"Javascript/Node.js"}},"statesType":"jsonl","objectsType":"jsonl","noInstances":3,"compactMode":false,"noCompactInstances":0,"model":"Intel(R) Celeron(R) CPU J1900 @ 1.99GHz","cpus":4,"mem":8023482368,"ostype":"Linux","city":""}
i deleted the image in portainer and explicitely loaded 9.0.1. with this image the container stayed healthy...
don't know exactly whats the matter here...
Description / Beschreibung
In my portainer environment i observed, that my iobroker installatin was suddenly unhealthy. I tried to setup a fresh container with iobroker only and also this container changes from healthy to unhealthy immediately after installation.
in the logs (container and iobroker) i can not detect any problems. the iobroker is running as expected. but has the state unhealthy.
the only thing i can see is the following output in portainer.
is this a problem in the container, or do i have a problem on my system?
edit: i checked within the container console... seems for me to be an issue in the container...
br peter
Image version
latest-v9
Docker logs / Docker Protokoll