SIGSEGV at startup
JanSund opened this issue · 2 comments
Problem/Motivation
After problem with node-red I first did a full restore than a partial restore of nodered, after that Influxdb wont start. To solve the Influxdb problem I first did a partial restore of Influxdb with no improvement. Then I did a reinstall of Influxdb, still no improvement.
I guess that I did something wrong at the first restore but how to I proceed from now?
Expected behavior
Start of Influxdb
Actual behavior
Startup starts normal but when it comes to KAPACITATOR it ends with fatal error.
Steps to reproduce
[15:46:27] INFO: InfluxDB init process in progress...
[15:46:32] INFO: InfluxDB init process in progress...
[tcp] 2023/11/18 15:46:37 tcp.Mux: Listener at 127.0.0.1:8088 failed failed to accept a connection, closing all listeners - accept tcp 127.0.0.1:8088: use of closed network connection
cont-init: info: /etc/cont-init.d/create-users.sh exited 0
cont-init: info: running /etc/cont-init.d/influxdb.sh
cont-init: info: /etc/cont-init.d/influxdb.sh exited 0
cont-init: info: running /etc/cont-init.d/kapacitor.sh
fatal error: unexpected signal during runtime execution
[signal SIGSEGV: segmentation violation code=0x1 addr=0x3ffffe9700 pc=0x5f1a4]
Proposed changes
(If you have a proposed change, workaround or fix,
describe the rationale behind it)
Restored back to Influxdb 4.7.0 and now I dont get the error. It looks very similar to case #308
here is an update available for this add-on!
Latest add-on version: 4.8.0
Please consider upgrading as soon as possible.
System: Home Assistant OS 11.1 (aarch64 / raspberrypi4-64)
Home Assistant Core: 2023.11.3
Home Assistant Supervisor: 2023.11.3
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
s6-rc: info: service base-addon-banner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service base-addon-timezone: starting
s6-rc: info: service base-addon-log-level: starting
s6-rc: info: service fix-attrs successfully started
[14:45:17] INFO: Configuring timezone (Europe/Stockholm)...
s6-rc: info: service base-addon-log-level successfully started
s6-rc: info: service base-addon-timezone successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/create-users.sh
cont-init: info: /etc/cont-init.d/create-users.sh exited 0
cont-init: info: running /etc/cont-init.d/influxdb.sh
cont-init: info: /etc/cont-init.d/influxdb.sh exited 0
cont-init: info: running /etc/cont-init.d/kapacitor.sh
cont-init: info: /etc/cont-init.d/kapacitor.sh exited 0
cont-init: info: running /etc/cont-init.d/nginx.sh
cont-init: info: /etc/cont-init.d/nginx.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun chronograf (no readiness notification)
services-up: info: copying legacy longrun influxdb (no readiness notification)
services-up: info: copying legacy longrun kapacitor (no readiness notification)
services-up: info: copying legacy longrun nginx (no readiness notification)
s6-rc: info: service legacy-services successfully started
[14:45:20] INFO: Kapacitor is waiting until InfluxDB is available...
[14:45:20] INFO: Chronograf is waiting until InfluxDB is available...
[14:45:20] INFO: Starting the InfluxDB...
[14:45:40] INFO: Starting the Kapacitor
[14:45:40] INFO: Starting Chronograf...
'##:::'##::::'###::::'########:::::'###:::::'######::'####:'########::'#######::'########::
##::'##::::'## ##::: ##.... ##:::'## ##:::'##... ##:. ##::... ##..::'##.... ##: ##.... ##:
##:'##::::'##:. ##:: ##:::: ##::'##:. ##:: ##:::..::: ##::::: ##:::: ##:::: ##: ##:::: ##:
2023/11/26 14:45:41 Using configuration at: /etc/kapacitor/kapacitor.conf
#####::::'##:::. ##: ########::'##:::. ##: ##:::::::: ##::::: ##:::: ##:::: ##: ########::
##. ##::: #########: ##.....::: #########: ##:::::::: ##::::: ##:::: ##:::: ##: ##.. ##:::
##:. ##:: ##.... ##: ##:::::::: ##.... ##: ##::: ##:: ##::::: ##:::: ##:::: ##: ##::. ##::
##::. ##: ##:::: ##: ##:::::::: ##:::: ##:. ######::'####:::: ##::::. #######:: ##:::. ##:
..::::..::..:::::..::..:::::::::..:::::..:::......:::....:::::..::::::.......:::..:::::..::
There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!