Replies: 2 comments 1 reply
-
And.... I think I've found the culprit. I had specified the connection to the mqtt server as 127.0.0.1 but for "reasons", I must have configured mqtt to only listen on it's external interface. Having made the change, viewu isn't even registering in terms of cpu usage. |
Beta Was this translation helpful? Give feedback.
1 reply
-
I think we can close it as answered 😁DeanOn 23 May 2024, at 20:33, mjehrhart ***@***.***> wrote:
Nice. I’m glad you found the issue. Is there anything I need to do or can this be marked as answered? That’s a huge log file!
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Matt,
Took me a while to get around to this but as per our conversation on reddit, I was seeing viewu burning a lot of cpu cycles. Output from docker status viewu;
The number is hovering around the 118 mark. Output from viewu logs is revealing and might explain the behaviour;
This error is repeated a LOT. I'm still waiting for an export of the log to count the entries but the log file is at 2GB so far and growing about 100MB every couple of seconds. There are 73 million entries so far so I'm going to abort the export and start looking at config but for now, I think we can safely assume that this is at least a contributing factor to the high cpu usage :)
Beta Was this translation helpful? Give feedback.
All reactions