Influxdb restaring
przemo opened this issue · 2 comments
przemo commented
Problem/Motivation
The influxDB engine is in stop/start loop - increase in CPU usage.
I changed the logs to TRACE
however I am unable to infer what would be the issue.
It was working flawlessly for last couple years.
HA runs on Proxmox VM (OVA). The allocated storage is used at 70%.
I want to avoid removing the addon because I don't want to lose the data.
Expected behavior
The opposite of the above.
Actual behavior
end
[08:13:59] INFO: Starting the InfluxDB...
[08:14:04] INFO: InfluxDB stopped, restarting...
[08:14:05] TRACE: bashio::config: envvars|keys
[08:14:05] TRACE: bashio::addon.config
[08:14:05] TRACE: bashio::cache.exists: addons.self.options.config
[08:14:05] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[08:14:05] TRACE: bashio::cache.get: addons.self.options.config
[08:14:05] TRACE: bashio::cache.exists: addons.self.options.config
[08:14:05] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[08:14:05] TRACE: bashio::jq: {"auth":false,"reporting":true,"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","envvars":[],"log_level":"trace"} if (.envvars|keys == null) then
null
elif (.envvars|keys | type == "string") then
.envvars|keys // empty
elif (.envvars|keys | type == "boolean") then
.envvars|keys // false
elif (.envvars|keys | type == "array") then
if (.envvars|keys == []) then
empty
else
.envvars|keys[]
end
elif (.envvars|keys | type == "object") then
if (.envvars|keys == {}) then
empty
else
.envvars|keys
end
else
.envvars|keys
end
[08:14:05] INFO: Starting the InfluxDB...
[08:14:11] INFO: InfluxDB stopped, restarting...
[08:14:12] TRACE: bashio::config: envvars|keys
[08:14:12] TRACE: bashio::addon.config
[08:14:12] TRACE: bashio::cache.exists: addons.self.options.config
[08:14:12] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[08:14:12] TRACE: bashio::cache.get: addons.self.options.config
[08:14:12] TRACE: bashio::cache.exists: addons.self.options.config
[08:14:12] TRACE: bashio::fs.file_exists: /tmp/.bashio/addons.self.options.config.cache
[08:14:12] TRACE: bashio::jq: {"auth":false,"reporting":true,"ssl":false,"certfile":"fullchain.pem","keyfile":"privkey.pem","envvars":[],"log_level":"trace"} if (.envvars|keys == null) then
null
elif (.envvars|keys | type == "string") then
.envvars|keys // empty
elif (.envvars|keys | type == "boolean") then
.envvars|keys // false
elif (.envvars|keys | type == "array") then
if (.envvars|keys == []) then
empty
else
.envvars|keys[]
end
elif (.envvars|keys | type == "object") then
if (.envvars|keys == {}) then
empty
else
.envvars|keys
end
else
.envvars|keys
end
[08:14:12] INFO: Starting the InfluxDB...
Steps to reproduce
No idea.
Proposed changes
rjodwyer commented
same issue here.
hassio image on bare metal.
tried "ha core rebuild" with no luck.
HeedfulCrayon commented
I just barely encountered the same issue. Causing some major problems with HA because I have some sensor queries that are no longer working either