-
-
Notifications
You must be signed in to change notification settings - Fork 16
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
[Jira Tracker] TrueNAS API reports error 500 when sensor on TrueNAS side is not working #12
Comments
error 500 is not documented at all, so confirming on truenas forums |
Confirmed this looks like a bug by ixsystems. Jira ticked opened NAS-115761 |
I'm also having this issue, here's my logbook: NAS Uptime changed to June 20, 2022 at 3:11 PM NAS Uptime became unavailable NAS Uptime changed to June 20, 2022 at 3:11 PM NAS Uptime became unavailable I'm running TrueNAS Core v13 (same issue with v12) in a QEMU VM. Any clue? |
Open a separate issue for it, you will also need to provide debugs capturing the issue. |
I think the problem is exactly the same:
|
Technically, yes. It is related to TrueNAS bug. But it has nothing to do with tracking it. |
Edit: Seems like what I thought fixed it, doesn't work. I did have this issue, but then it started working again after a reboot. Strange. |
System -> Reporting -> Report CPU usage in percent -> false |
I explored a bit more and I was finally able to fix it!
Also ran Credits: https://www.truenas.com/community/threads/rrdcached-could-not-read-rrd-file.74785/post-534842 |
Tried the Report CPU usage in percent -> false option, but didn't do anything. I also tried the fix you mentioned but didn't work for me either. I get to the final point where I have to start collectd and it says:
|
What about |
I ran it on the third line, the fourth line is the output. |
And did you reboot it? And maybe reconfigure the integration... |
Yep, both TrueNAS and HA and tried reconfiguring the integration. The funny thing is that 1.02 runs fine. |
The integration never worked for me before. Only today after those commands. Sorry I can't help you :/ |
Don't worry, you get an A for effort heh. |
I will be locking conversation here as it is being used to unrelated discussions. This issue is only a placeholder for TrueNAS API bug. |
Should not reoccur anymore due to workaround |
ok, I will only use another branch based on author's advice.
strange I have 2 TrueNAS Scale servers on different Proxmox servers. 1 is reporting correctly in HA and one I'm still getting a 500.
Originally posted by @pcampan in #9 (comment)
The text was updated successfully, but these errors were encountered: