[Bug] GetCPUThermalZone message in log every 5 minutes

Open Beginner friendly
#2,575 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
go

Research direction

Start at service/system.go around line 485 and inspect GetCPUThermalZone plus the caller that runs every five minutes. Trace when the thermal-zone message is emitted, then verify that normal operation no longer produces the repeated info log and that the chosen startup warning behavior is consistent with the issue’s expectation.

Written by the indexing model from the issue text.

Description

bug

Describe the bug
Every 5 minutes the console gets an info message about thermal zone found.
CPU thermal zone found: x86_pkg_temp, path: /sys/devices/virtual/thermal/thermal_zone2. {"func": "service.GetCPUThermalZone", "file": "/home/runner/work/CasaOS/CasaOS/service/system.go", "line": 485}

To Reproduce

Installed it yesterday and it seems to be going on since install.

Expected behavior

Maybe warn once per boot

Screenshots
Image

Desktop (please complete the following information):
Linux andromeda 6.1.0-52-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.180-1 (2026-08-03) x86_64 GNU/Linux

# dmidecode 3.4
Getting SMBIOS data from sysfs.
SMBIOS 3.0.0 present.

Handle 0x0002, DMI type 2, 15 bytes
Base Board Information
	Manufacturer: Dell Inc.
	Product Name: 0FDY5C
	Version: A00
	Serial Number: **************************
	Asset Tag: Not Specified
	Features:
		Board is a hosting board
		Board is replaceable
	Location In Chassis: Not Specified
	Chassis Handle: 0x0003
	Type: Motherboard
	Contained Object Handles: 0

System Time

Run timedatectl and share the output

               Local time: Fri 2026-08-28 11:02:52 CEST
           Universal time: Fri 2026-08-28 09:02:52 UTC
                 RTC time: Fri 2026-08-28 09:02:52
                Time zone: Europe/Amsterdam (CEST, +0200)
System clock synchronized: yes
              NTP service: active
          RTC in local TZ: no

Logs

casaos.service.txt
casaos-app-management.log
casaos-gateway.log
casaos-local-storage.log
casaos-user-service.log

Additional context
It's just a basic desktop running as my server. CasaOS install was fresh, running the command from the official webpage, but the server was running for a year, with a few docker containers

Dominant language
Go
Stars
37.2k
Forks
2.2k
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from IceWhaleTech/CasaOS

All issues in IceWhaleTech/CasaOS

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.