Exec instance started: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1

Ashcora · November 5, 2022, 12:10pm

Referring to my reported issue on GitHub, I hope someone of you can support me
(Exec instance started: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1 · Issue #408 · openhab/openhab-docker · GitHub)

Portainer Event Log is showing frequent and repeated entries

2022-10-19 16:23:00 | container | Exec instance exited
2022-10-19 16:23:00 | container | Exec instance started: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 16:23:00 | container | Exec instance created: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 16:18:00 | container | Exec instance exited
2022-10-19 16:17:59 | container | Exec instance started: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 16:17:59 | container | Exec instance created: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 16:12:59 | container | Exec instance exited
2022-10-19 16:12:59 | container | Exec instance started: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 16:12:59 | container | Exec instance created: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 16:07:59 | container | Exec instance exited
2022-10-19 16:07:59 | container | Exec instance started: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 16:07:59 | container | Exec instance created: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 16:02:59 | container | Exec instance exited
2022-10-19 16:02:59 | container | Exec instance started: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 16:02:59 | container | Exec instance created: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 15:57:59 | container | Exec instance exited
2022-10-19 15:57:59 | container | Exec instance started: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
2022-10-19 15:57:59 | container | Exec instance created: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1

Summary
Log files within Portainer show events with regard to OPENHAB_HTTP_PORT

Expected Behavior
No error events are shown in the event log.

Current Behavior
container | Exec instance exited
container | Exec instance started: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
container | Exec instance created: /bin/sh -c curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1

Possible Solution
Adapt configuration and/or start command to fix these entries.

Steps to Reproduce
docker run
–name openhab
–net=host
-v /etc/localtime:/etc/localtime:ro
-v /etc/timezone:/etc/timezone:ro
-v /opt/openhab/conf:/openhab/conf
-v /opt/openhab/userdata:/openhab/userdata
-v /opt/openhab/addons:/openhab/addons
-d
-e OPENHAB_HTTP_PORT=8081
-e OPENHAB_HTTPS_PORT=8444
-e USER_ID=$USER_ID
-e GROUP_ID=$GROUP_ID
–restart=always
openhab/openhab:latest

Context
These entries are spamming the event log

Your Environment
Raspberry Pi 4 Model B Rev 1.5
Docker version 20.10.5+dfsg1, build 55c4c88

PRETTY_NAME=“Debian GNU/Linux 11 (bullseye)”
NAME=“Debian GNU/Linux”
VERSION_ID=“11”
VERSION=“11 (bullseye)”
VERSION_CODENAME=bullseye
ID=debian
HOME_URL=“https://www.debian.org/”
SUPPORT_URL=“https://www.debian.org/support”
BUG_REPORT_URL=“https://bugs.debian.org/”

Image
openhab/openhab:latest
Debian GNU/Linux 11 (bullseye)

Docker Host
pi@raspberrypi4:~ $ docker info
Client:
Context: default
Debug Mode: false
Plugins:
compose: Docker Compose (Docker Inc., v2.12.0)

Server:
Containers: 4
Running: 3
Paused: 0
Stopped: 1
Images: 4
Server Version: 20.10.5+dfsg1
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: systemd
Cgroup Version: 2
Plugins:
Volume: local
Network: bridge host ipvlan macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog
Swarm: inactive
Runtimes: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 1.4.13ds1-1deb11u2
runc version: 1.0.0~rc93+ds1-5+deb11u2
init version:
Security Options:
seccomp
Profile: default
cgroupns
Kernel Version: 5.15.65-v8+
Operating System: Debian GNU/Linux 11 (bullseye)
OSType: linux
Architecture: aarch64
CPUs: 4
Total Memory: 7.629GiB
Name: raspberrypi4
ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Docker Root Dir: /var/lib/docker
Debug Mode: false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false

Configuration
Start via Docker run command

Wolfgang_S · November 5, 2022, 12:32pm

I am wondering how it could be that it refers to curl and ‘exec instance’ ( is the later meaning the exec binding or is this something different like exec a process ? ). Is this something special for that docker build OH as I think the basic OH installation does not make use of curl nor of exec binding.
Seems to be executed every 5 minutes. Is this due to the fact that the previous one got a timeout ?

Ashcora · November 5, 2022, 1:18pm

Hello @Wolfgang_S, thank you for your reply.
I used the official docker build from openhab/openhab - Docker Image | Docker Hub
The docker run command you can find above. Do you mean there is a connection to the exec binding which is running?

wborn · November 5, 2022, 1:20pm

It does because the container has a healthcheck so if it fails the container is restarted:

github.com

openhab/openhab-docker/blob/661685c6d464d538481549a661977e9a327f4635/debian/Dockerfile#L101


      
          COPY update ${OPENHAB_HOME}/runtime/bin/update
          RUN chmod +x ${OPENHAB_HOME}/runtime/bin/update
          
          # Expose volume with configuration and userdata dir
          VOLUME ${OPENHAB_CONF} ${OPENHAB_USERDATA} ${OPENHAB_HOME}/addons
          
          # Expose HTTP, HTTPS, Console and LSP ports
          EXPOSE 8080 8443 8101 5007
          
          # Set healthcheck
          HEALTHCHECK --interval=5m --timeout=5s --retries=3 CMD curl -f http://localhost:${OPENHAB_HTTP_PORT}/ || exit 1
          
          # Set working directory and entrypoint
          WORKDIR ${OPENHAB_HOME}
          COPY entrypoint /entrypoint
          RUN chmod +x /entrypoint
          ENTRYPOINT ["/entrypoint"]
          
          # Execute command
          CMD ["gosu", "openhab", "tini", "-s", "./start.sh"]

wborn · November 5, 2022, 1:31pm

You could try to disable the healthcheck with by adding the --no-healthcheck when creating the container (see docs).

If that works better you can then run curl -f http://localhost:${OPENHAB_HTTP_PORT}/ in the container to investigate why that command fails.

Wolfgang_S · November 5, 2022, 1:38pm

thanks! I did check the OH source code but not the docker related, specific stuff.

Ashcora · November 5, 2022, 1:54pm

Thanks for taking care here as well (not only on GitHub ). Your help and engagement is really appreciated!

I turned off the HealthCheck within a new docker run. The 5 minute boarder is also crossed.
Result: NO message is logged in the Portainer Events.
To sum up: You seem to have found the issue

When then entering the cmd within the docker:
root@raspberrypi4:/openhab# curl -f http://localhost:${OPENHAB_HTTP_PORT}/

I get the following message displayed:

<!doctype html><html><head><meta charset="utf-8"><meta http-equiv="Content-Security-Policy" content="default-src * 'self' 'unsafe-inline' 'unsafe-eval' data: gap: content: blob:; style-src 'self' 'unsafe-inline';"><meta name="viewport" content="width=device-width,initial-scale=1,maximum-scale=1,minimum-scale=1,user-scalable=no,minimal-ui,viewport-fit=cover"><meta name="theme-color" content="#e64a19"><meta name="format-detection" content="telephone=no"><meta name="msapplication-tap-highlight" content="no"><title>openHAB</title><meta name="apple-mobile-web-app-capable" content="yes"><meta name="apple-mobile-web-app-status-bar-style" content="black-translucent"><link rel="apple-touch-icon" href="/res/icons/apple-touch-icon.png" type="image/png" sizes="180x180" crossorigin="use-credentials"><link rel="icon" href="/res/icons/favicon.svg" type="image/svg+xml" sizes="any" crossorigin="use-credentials"><link rel="icon" href="/res/icons/128x128.png" type="image/png" sizes="128x128" crossorigin="use-credentials"><link rel="manifest" href="/manifest.json" crossorigin="use-credentials"><link href="/css/app.css" rel="stylesheet"></head><body><div id="app"></div><script src="/js/app.js"></script></body></html>

wborn · November 5, 2022, 2:38pm

Maybe the issue is fixed in a more recent Docker version.

For instance in 20.10.18 there is a fix for healthchecks:

Fix an issue where exec processes and healthchecks were not terminated when they timed out moby/moby#44018.

Ashcora · November 6, 2022, 4:57pm

Thank you for the hint and your researches. I will give it a try

Ashcora · December 7, 2022, 12:32pm

a) I tried to use the latest snapshot version. The event log is still filled.

2022-12-07 13:25:37	container	Exec instance exited
2022-12-07 13:25:37	container	Exec instance started: /bin/sh -c curl --connect-timeout 5 --silent -f (…)localhost:8080/
2022-12-07 13:25:37	container	Exec instance created: /bin/sh -c curl --connect-timeout 5 --silent -f (…)localhost:8080/
2022-12-07 13:20:37	container	Exec instance exited
2022-12-07 13:20:36	container	Exec instance started: /bin/sh -c curl --connect-timeout 5 --silent -f (…)localhost:8080/
2022-12-07 13:20:36	container	Exec instance created: /bin/sh -c curl --connect-timeout 5 --silent -f (…)localhost:8080/
2022-12-07 13:15:36	container	Exec instance exited
2022-12-07 13:15:36	container	Exec instance started: /bin/sh -c curl --connect-timeout 5 --silent -f (…)localhost:8080/
2022-12-07 13:15:36	container	Exec instance created: /bin/sh -c curl --connect-timeout 5 --silent -f (…)localhost:8080/
2022-12-07 13:10:36	container	Exec instance exited
2022-12-07 13:10:36	container	Exec instance started: /bin/sh -c curl --connect-timeout 5 --silent -f (…)localhost:8080/
2022-12-07 13:10:36	container	Exec instance created: /bin/sh -c curl --connect-timeout 5 --silent -f (…)localhost:8080/
2022-12-07 13:05:36	container	Exec instance exited

(i needed to remove the “http” that I can post my reply )

b) Is there any possibility to use docker compose with “–no-healthcheck”? Via “command:” or in environment, …?

wborn · December 7, 2022, 12:42pm

According to the Compose file docs you can add the following YAML to the container config in the YAML file:

healthcheck:
  disable: true

Ashcora · December 7, 2022, 12:57pm

Thanks again for your quick help and the reference. Really appreciated