Seems like I'm not the only one. Kinda confused as to why it is happening, maybe the error is a misnomer
https://community.influxdata.com/t/influxdb2-telegraf-proxmox-field-type-conflict-while-using-inputs-socket-listener-for-proxmox-metrics/23585
When I run telegraf --test /etc/telegraf the output for system is:
> system,host=134e7e15f4ba load1=2.21,load15=1.92,load5=2.31,n_cpus=1i,n_users=0i 1667813275000000000
> system,host=134e7e15f4ba uptime=245239i 1667813275000000000
> system,host=134e7e15f4ba uptime_format="2 days, 20:07"...
Thank you for taking the time to check the code and confirm it isn't proxmox. Considering The only two sources I have writing to the influxdb are proxmox and telegraf I'm confused as to what could have created the metric as a float.
I will investigate further. Thanks again.
Hi,
I happened to look at my influx logs and noticed the following error occurring:
ts=2022-11-03T15:52:15.241668Z lvl=info msg="Failed to write point batch to database" log_id=0dwTt70G000 service=udp db_instance=udp error="partial write: field type conflict: input field \"uptime\" on...
with mine this happens when my session is stale and/or I'm logging on to another node in the cluster from a logon session on a different server.
normally just refreshing the page and logging in again fixes it.
Not saying that's the answer, just that I've seen it before.
Hi,
Given the changes that proxmox makes to grub running does anyone know the process to add more entries to the grub menu please ?
I tried grml-rescue to no avail.
Your help would be appreciated.
I think, but am not sure, that lxc provides a certain level of isolation, but not as much as a vm. If you run docker in lxc some containers may not work if they require access to the kernel that lxc will not permit ?
If someone could clarify or correct me I would appreciate it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.