Closed wernerhp closed 1 year ago
I suspect it may be memory related. I recently switched from Mosquitto Broker
to EMQX
.
After reverting to Mosquitto
and stopping UniFi Network Application
it seems like InfluxDB
starts.
2023/06/29 08:52:13 Using configuration at: /etc/kapacitor/kapacitor.conf
##::'##::::'## ##::: ##.... ##:::'## ##:::'##... ##:. ##::... ##..::'##.... ##: ##.... ##:
##:'##::::'##:. ##:: ##:::: ##::'##:. ##:: ##:::..::: ##::::: ##:::: ##:::: ##: ##:::: ##:
#####::::'##:::. ##: ########::'##:::. ##: ##:::::::: ##::::: ##:::: ##:::: ##: ########::
##. ##::: #########: ##.....::: #########: ##:::::::: ##::::: ##:::: ##:::: ##: ##.. ##:::
##:. ##:: ##.... ##: ##:::::::: ##.... ##: ##::: ##:: ##::::: ##:::: ##:::: ##: ##::. ##::
##::. ##: ##:::: ##: ##:::::::: ##:::: ##:. ######::'####:::: ##::::. #######:: ##:::. ##:
..::::..::..:::::..::..:::::::::..:::::..:::......:::....:::::..::::::.......:::..:::::..::
ts=2023-06-29T08:52:13.425+02:00 lvl=error msg="error while sending usage report on startup" service=reporting err="Post \"https://usage.influxdata.com/api/v1/usage/kapacitor\": dial tcp 0.0.0.0:443: connect: connection refused"
time="2023-06-29T08:52:21+02:00" level=info msg="Reporting usage stats" component=usage freq=24h reporting_addr="https://usage.influxdata.com" stats="os,arch,version,cluster_id,uptime"
time="2023-06-29T08:52:21+02:00" level=info msg="Serving chronograf at http://127.0.0.1:8889" component=server
[08:52:22] INFO: Starting NGINX...
From Glances
How do I deal with this CPU_IOWAIT
and MEMSWAP
issue?
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!
Problem/Motivation
Add-on version: 4.7.0 You are running the latest version of this add-on. System: Home Assistant OS 10.3 (aarch64 / odroid-n2) Home Assistant Core: 2023.6.3 Home Assistant Supervisor: 2023.06.2
Expected behavior
It should connect and start
Actual behavior
Connection refused and restarts
Steps to reproduce
Not sure how to reproduce. Just noticed it happening this week.
Proposed changes
None