-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Error getting VM curent VM status - Proxmox error #9611
Comments
I've managed to fix this by changing the type of the VM ID from string to int: https://github.com/atetevoortwis/telegraf/tree/bugfix/9611 |
That seems like a simple enough fix
@atetevoortwis Where are the proxmox scrips located? I can't seem to find the files to edit in my installation. |
@abrondijk , see the only commit in my branch: atetevoortwis@9dd992f |
@atetevoortwis I've tested your changes and it solves the problem for me as well. I'd suggest perhaps opening a pull request so this can get fixed? |
i can btw. confirm this error with the following versions: |
the issue btw. still remains, because the contribution license is not accepted in the PR... |
I have 2 nodes and both not working. |
You can just build telegraf yourself from the branch mentioned by atetevoortwis, that works fine for me on the latest proxmox 7. |
Relevant telegraf.conf:
System info:
PVE 7.0-11 based on debian 11
Telegraf version 1.19.2, installed according to this guide.
Steps to reproduce:
Expected behavior:
I expect telegraf to behave normally and to not spam errors in syslog.
Actual behavior:
The following error on every poll:
Besides the fact that current is spelled with only 1 R, I expect the data from proxmox to be gathered and sent to my output plugins.
Additional info:
I can confirm that the api token I use is correct, because if I change it, I get a completely different error.
The text was updated successfully, but these errors were encountered: