CoolerControl Daemon Connection Error
Hello!
I just installed CoolerControl, however when I try to initialize it I keep getting Daemon Connection Error.
I tried running: sudo systemctl enable --now coolercontrold but It doesn't return anything and it still get me the same error.
Has anybody encountered the same error?
Thanks!
41 Replies
try rebooting first
Hello! I have rebooted several times already š¦
how did you install it? ujust? @Diego N
if yes then what is
systemctl status coolercontroldI did
also what is
rpm-ostree statusMar 21 04:38:09 bazzite coolercontrold[1725]: Initialized Liquidctl Devices: {"Gigabyte RGB Fusion 2.0 5702 Controller":{"driver name":["RgbFusion2"],"driver version":["1.14.0"],"locations":["/dev/hidraw11"]}}
Mar 21 04:38:09 bazzite coolercontrold[1725]: NVML found and initialized.
Mar 21 04:38:09 bazzite coolercontrold[1725]: Initialized CPU Devices: {"AMD Ryzen 5 9600X 6-Core Processor":{"locations":["/sys/class/hwmon/hwmon4","/sys/devices/pci0000:00/0000:00:18.3","pci:v00001022d000014E3sv00000000sd00000000bc06sc00i00"],"driver name":["k10temp"],"driver version":["6.13.6-1>
Mar 21 04:38:09 bazzite coolercontrold[1725]: Initialized GPU Devices: {"amdgpu":{"driver name":["amdgpu"],"locations":["/sys/class/hwmon/hwmon1","/sys/devices/pci0000:00/0000:00:08.1/0000:11:00.0","pci:v00001002d000013C0sv00001458sd0000D000bc03sc00i00"],"driver version":["6.13.6-103.bazzite.fc41.>
Mar 21 04:38:09 bazzite coolercontrold[1725]: Initialized Hwmon Devices: {"gigabyte_wmi":{"locations":["/sys/class/hwmon/hwmon5","/sys/devices/platform/PNP0C14:00/wmi_bus/wmi_bus-PNP0C14:00/DEADBEEF-2001-0000-00A0-C90629100000","wmi:DEADBEEF-2001-0000-00A0-C90629100000"],"driver name":["gigabyte-w>
Mar 21 04:38:09 bazzite coolercontrold[1725]: Initialized Custom Sensors: []
Mar 21 04:38:09 bazzite coolercontrold[1725]: Applying all saved device settings
Mar 21 04:38:09 bazzite coolercontrold[1725]: API bound to address: 127.0.0.1:11987
Mar 21 04:38:09 bazzite coolercontrold[1725]: API bound to address: [::1]:11987
Mar 21 04:38:09 bazzite coolercontrold[1725]: Initialization Complete
what is the Active: status
State: idle
Deployments:
ā ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
Digest: sha256:ba6ca9ecdb68be749094f32e01ccb98da50a2b09af4f1f59c3b18f448635809a
Version: 41.20250317 (2025-03-17T05:44:17Z)
LayeredPackages: coolercontrol lact liquidctl
LocalPackages: XPPenLinux-4.0-1.el7.x86_64
ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
Digest: sha256:ba6ca9ecdb68be749094f32e01ccb98da50a2b09af4f1f59c3b18f448635809a
Version: 41.20250317 (2025-03-17T05:44:17Z)
LayeredPackages: lact
LocalPackages: XPPenLinux-4.0-1.el7.x86_64
ā coolercontrold.service - CoolerControl Daemon
Loaded: loaded (/usr/lib/systemd/system/coolercontrold.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/system/service.d
āā10-timeout-abort.conf
Active: active (running) since Fri 2025-03-21 04:38:07 EDT; 7min ago
Invocation: 4d9798ba131c46078770bad45eb4d44d
Main PID: 1725 (coolercontrold)
Tasks: 6 (limit: 37015)
Memory: 51.9M (peak: 54.1M)
CPU: 1.654s
CGroup: /system.slice/coolercontrold.service
āā1725 /usr/bin/coolercontrold
the daemon seems fine
what is the error from the gui?
I get the following
Nothing loads, I get a blank page, but no 404 errors like in the GUI
what about
curl -v http://localhost:11987/health* Host localhost:11987 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
* Trying [::1]:11987...
* Connected to localhost (::1) port 11987
GET /health HTTP/1.1 Host: localhost:11987 User-Agent: curl/8.9.1 Accept: /* Request completely sent off < HTTP/1.1 200 OK < content-type: application/json < vary: origin, access-control-request-method, access-control-request-headers < access-control-allow-credentials: true < content-length: 403 < date: Fri, 21 Mar 2025 09:02:07 GMT < * Connection #0 to host localhost left intact {"status":"Runnable","description":"Health check for CoolerControl Daemon","current_timestamp":"2025-03-21T05:02:07.425742574-04:00","details":{"uptime":"00:24:00","version":"2.0.0","pid":1725,"memory_mb":51.18,"warnings":0,"errors":0,"liquidctl_co
i think you are basically hitting this bug https://gitlab.com/coolercontrol/coolercontrol/-/issues/418, not sure whats wrong or how to fix it tho, ill try asking if the maintainer can repro
I see
Do you think it has something to do with ostree-image-signed?
Yesterday I had to install a package locally, a driver for my Pen Display
shouldnt be
the weird thing is the curl worked
wait what is
curl -v http://localhost:11987I'm not completely sure how ostree works but I remembered reading in the documentation that installing layered packages manually could create problems down the line, like failing to update or similar things
* Host localhost:11987 was resolved.
* IPv6: ::1
* IPv4: 127.0.0.1
* Trying [::1]:11987...
* Connected to localhost (::1) port 11987
GET / HTTP/1.1 Host: localhost:11987 User-Agent: curl/8.9.1 Accept: /* Request completely sent off < HTTP/1.1 404 Not Found < vary: origin, access-control-request-method, access-control-request-headers < access-control-allow-credentials: true < content-length: 0 < date: Fri, 21 Mar 2025 09:11:46 GMT < * Connection #0 to host localhost left intact
i mean the fact that some other people have seemingly the same problem state that it could be from the os
mine work fine tho for some reason
got it
I see the Issue was created 16 hours ago
might be a recent bug?
yeah its really new
status seems Closed tho
i mean also coolercontrol recently revamped their ui
if you read the conclusion basically they think its not coolercontrol issue but something blocking it
ahhh I see now
pffff well, it seems we'll have to wait for them to bring in the big guns XD
thanks so much for your help [:
At least now I know that is not something just in my system.
@Diego N apparently the appimage works, you could use it to configure for now
Yeah I'm getting exact same issue.
Where is the app image located?
AppImage | CoolerControl
CoolerControl Documentation
also youll still need the ujust if i understand correctly
Got it. I'm going to give LACT a try later but I'll try this after. My daemon is running fine too it's just the GUI that seems borked.
I'm having the issue as well. I see the bug has been reported to the bazzite github issue tracker: https://github.com/ublue-os/bazzite/issues/2417
GitHub
Coolercontrol no longer works Ā· Issue #2417 Ā· ublue-os/bazzite
Describe the bug Just did an update and it looks like other people are having the same issue on bazzite/bluefin. See coolercontrol issue here: https://gitlab.com/coolercontrol/coolercontrol/-/issue...
Glad it's not just me. There is a workaround for GPU. LACT is still working. And for fans BIOS fan curve can be set.
I had the problem, but a recent update in Coolercontrol fixed it for me
@biebel @Andy10115 @Diego N yeah looks like its a packaging issue, can you verify if latest update work? i saw terra updated but bazzite uses different copr
not working for yet me after ujust update (testing-41.20250321)
ah too bad, can you create a new issue in coolercontrol repo to integrate this fix
https://github.com/terrapkg/packages/commit/cd79097020ed31613e56fc66544943571c5b74c2
GitHub
fix(coolercontrol): bake the ui into the daemon properly (#4091) (#...
Resolve #4090
(cherry picked from commit 568f9f4e73b9944945b0fc799f4023c0af39b086)
Co-authored-by: madomado
i dont have gitlab acc š
Me neither apparently :/ I also seem pretty bad at recognising busses in captchas lol
oh i thought you are the reporter in github lol
I'll have to test again tomorrow night. Workaround of LACT fan control worked for me. I'll update and check version. Sorry limited time due to small children lol.
Fixed for me now after updating just now in testing