coollabsio
[Bug]: sql: Scan error on column index 5, name "usedPercent": converting NULL to float64 is unsupported
Error Message and Logs
sql: Scan error on column index 5, name "usedPercent": converting NULL to float64 is unsupported
Steps to Reproduce
- Go to metrics page on any service with data less than the selected date.
- Select an amount of time that is greater than the data available.
Example Repository URL
No response
Coolify Version
v4.0.0-beta.369
Are you using Coolify Cloud?
No (self-hosted)
Operating System and Version (self-hosted)
Debian GNU/Linux 12 (bookworm)
Additional Information
No response
I am unable to reproduce this error. Maybe you can make a short video so I can better see what is going on.
Sorry for the late reply
https://github.com/user-attachments/assets/8b009537-1440-4293-8fae-27973779c7eb
Same there. I started getting this when I redeployed a container and it failed, rolling back to the previous one. The metrics were set to last 5 minutes, but there was no data yet, and this started popping every few seconds. I am not 100% confident in the origin of the error though, but I can say I do have the metrics activated too and that they don't load so it seems like the error is coming from there.
Edit: five minutes have passed (notice the time in the tray) and it did stop popping up and it started showing data. Seems like that was indeed the cause.
Hey, I've just got the error also on a nixpacks project. Just changed the nginx config a little bit and redeployed. Then the errors started comming in.
Restarting the project again seems to have solved the issue.
also on: v4.0.0-beta.379
sql: Scan error on column index 5, name "usedPercent": converting NULL to float64 is unsupported
same here. started appearing after a preview deployment, with the url template wrongly configured (container started successfully but url was not a valid url)
Version: v4.0.0-beta.379
Still having the same issue on v4.0.0-beta.380. It happened after a container restart, but I don’t think the restart caused it. I was adjusting Traefik settings a few times in the app config and restarted a couple of times before the error started showing up.
Any chance those effected might have a build occurring or hanging in the background?
When I had this problem, it was resolved by:
- (re)building without cache from docker image
- *not clicking deploy now (instead of waiting in queue)
can confirm this is still happening, even though its marked as done. do we need to do anything in Coolify to update the sentinel on servers?
The PR was submitted to the Senitnel repository and is still open. it has not been merged yet by the Senitnel developers.
Released the new version. You should get autoupdated based on your update configuration for your instance.
Cloud users will be updated soon as well.