-
-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Segmentation fault (core dumped) - when ssh into docker container #1424
Comments
Also after the update to Version 24.1.0 Im still getting "Segmentation fault (core dumped)" when executing ebusctl within the docker container. |
Exactly same problem here after ebusd update from 23.2.6 to 24.1.0. and firmware upate of ebus adapter V5 (from 20240106 to 20241221). Home Assistant: Core: 2025.1.2, Supervisor: 2024.12.3 Edit: Seems unrelated to the firmware build of the V5 ebusd adapter. Swapping back to firmware 20240106 did not resolve the problem. Still have to try to roll back to ebusd 23.2.6... Edit2: Could be Docker/ProxMox-related? Similar reports here: Edit3: Seems to be related to the recently updated eBUSd-addon in HA |
both of the above issue was rooted in the latest ha-addon version - the fix is already released in 24.1.1: Please update your instance. There is nothing to do by @john30 in his repos, so please, close the ticket. |
I thought so, thanks for clarifiying. wondering why people still use the old (and no longer maintained) ebusctl instead of netcat or telnet and friends... |
Description
Executing ebusctl inside the docker container leads to error message "Segmentation fault (core dumped)".
Im following the steps described in the ebusd addon description in chapter "Running ebusd and ebusctl directly". It neither works via putty nor the terminal (ssh addon) in home assistant. My goal is to execute ebusctl write commands towards my vaillant heap pump.
➜ ~ docker exec -it
docker ps | grep ebusd | awk '{print $1}'
/bin/bash2ad9b828-ebusd:/# ebusctl
Segmentation fault (core dumped)
2ad9b828-ebusd:/#
Apart from that the addon works with the following config:
scanconfig: true
loglevel_all: notice
mqtttopic: ebusd
mqttint: /etc/ebusd/mqtt-hassio.cfg
mqttjson: true
mode: ens
network_device: 192.168.178.125:9999
latency: 10
configpath: /etc/ebusd/config/de
Im having almost all data inside MQTT. Now I would like to write values to the Vaillant Heap Pump (AroTherm 55).
I tried to reinstall the addon without success.
Patch Level:
Home Assistant: Core: 2024.12.5, Supervisor: 2024.12.0
Supervised HA installation
ebusd: 23.2.6
eBUS Adapter Shield C6
OS: Debian GNU/Linux 12 (bookworm)
Docker version: Docker version 27.4.1, build b9d17ea
Actual behavior
Segmentation fault (core dumped)
Expected behavior
Reading results from the vaillants heat pump ebus.
ebusd version
current source from git
ebusd arguments
ebusd --foreground --mqtthost=core-mosquitto --mqttport=1883 --mqttuser=addons --mqttpass=secret --scanconfig --mqttjson --configpath=/etc/ebusd/config/de --latency=10 --mqttint=/etc/ebusd/mqtt-hassio.cfg --mqtttopic=ebusd --device=ens:192.168.178.125:9999 --log=all:notice
Operating system
Debian 12 (Bookworm) / Ubuntu 22-23 / Raspberry Pi OS 12 (including lite)
CPU architecture
x64
Dockerized
None
Hardware interface
Adapter Shield v5 via USB
Related integration
No response
Logs
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
The text was updated successfully, but these errors were encountered: