-
-
Notifications
You must be signed in to change notification settings - Fork 99
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
[Bug] Using "DASHDOT_ENABLE_CPU_TEMPS=true" gives a large error message (crashes the container) #706
Comments
Hi there, thanks for creating an issue. Can you please run the following on your system and paste the output?
The CPU temperature flag shouldn't be able to crash the container, normally. |
Here you go :)
Output: |
Can you please test it again with the latest release and see if there is any new log output? |
Different error now:
Full log output: Also did the |
Thanks a lot! I now know what's causing this issue and will try my best to fix it! |
Can you please try the latest dev build |
Slightly new error now :)
Full log: Also did the |
Ahh sorry, I made a typo. Can you please pull the dev image again and re-test? |
It works now 👍 |
Perfect, thanks for the continuous help with investigating! |
## [5.2.2](v5.2.1...v5.2.2) (2023-08-23) ### Bug Fixes * **api:** calculation for cpus with E/P cores not working ([3386923](3386923)), closes [#706](#706) * checksum for typescript ([6a14829](6a14829)) * **speedtest:** not working on windows install ([#731](#731)) ([423837b](423837b)), closes [#729](#729) ### Reverts * upgrade prism-react-renderer to v2 ([6d60009](6d60009))
🎉 This issue has been resolved in version 5.2.2 Please check the changelog for more details. |
Description of the bug
As the title says, enabling the environment
DASHDOT_ENABLE_CPU_TEMPS
makes my docker container go haywire.How to reproduce
I use this docker compose example:
So I guess using that example, with the
DASHDOT_ENABLE_CPU_TEMPS
set totrue
makes it give the error mentioned down below.It happens as soon as I try to load the webpage
http://ip.of.server:3001
or the reverse proxied urlhttps://dash.domain.com
- otherwise it just hangs if I use thedocker logs -tf dash
and monitor what's happening. It gets stuck after completing the speedtest - and then if I try and load the webpage, it gives the error message.Relevant log output
Info output of dashdot cli
What browsers are you seeing the problem on?
Chrome
Where is your instance running?
Linux Server
Additional context
I've added the correct things in my
/etc/modules
as well:The text was updated successfully, but these errors were encountered: