Metric Server > InfluxDB does not work if the bucket has special character.

EVOTk

Member
Dec 16, 2020
3
1
8
34
Hello,
My bucket is called "evo-bucket", I can configure the influxdb server in proxmox but it gives me errors:

1699483981156.png

If I use a name with no special characters (e.g. proxmox), then the operation is normal, and the information is present in the bucket.

Proxmox VE 8.0.4

Edit : I'm try config bucket with name "evo\-bucket" in proxmox, have erreur 404 not found
 
Last edited:
  • Like
Reactions: MisterY
Hi,

could you share your /etc/pve/status.cfg and the output of journalctl -u pvestatd (trim the latter so a reasonable size, I just want to see if anything else regarding metrics is logged).

I've tried to set up a bucket with a '-' in the name, for me this seems to work without issues.

EDIT: Also, what is the exact version of InfluxDB that you use?

Thanks!
 
Last edited:
Thx for reply !

InfluxDB v2.7.1

1699524959110.png

journalctl -u pvestatd
Code:
nov. 04 23:12:47 prox pvestatd[1205]: VM 111 qmp command failed - VM 111 not running
nov. 04 23:32:28 prox systemd[1]: Reloading pvestatd.service - PVE Status Daemon...
nov. 04 23:32:28 prox pvestatd[90484]: send HUP to 1205
nov. 04 23:32:28 prox pvestatd[1205]: received signal HUP
nov. 04 23:32:28 prox pvestatd[1205]: server shutdown (restart)
nov. 04 23:32:28 prox systemd[1]: Reloaded pvestatd.service - PVE Status Daemon.
nov. 04 23:32:28 prox pvestatd[1205]: restarting server
nov. 04 23:33:32 prox systemd[1]: Stopping pvestatd.service - PVE Status Daemon...
nov. 04 23:33:32 prox pvestatd[1205]: received signal TERM
nov. 04 23:33:32 prox pvestatd[1205]: server closing
nov. 04 23:33:32 prox pvestatd[1205]: server stopped
nov. 04 23:33:33 prox systemd[1]: pvestatd.service: Deactivated successfully.
nov. 04 23:33:33 prox systemd[1]: Stopped pvestatd.service - PVE Status Daemon.
nov. 04 23:33:33 prox systemd[1]: pvestatd.service: Consumed 1h 50min 28.951s CPU time.
-- Boot 15d247651ae345c4bc09585bb1e71d65 --
nov. 04 23:34:01 prox systemd[1]: Starting pvestatd.service - PVE Status Daemon...
nov. 04 23:34:02 prox pvestatd[1183]: starting server
nov. 04 23:34:02 prox systemd[1]: Started pvestatd.service - PVE Status Daemon.
nov. 05 12:36:42 prox pvestatd[1183]: auth key pair too old, rotating..
nov. 06 12:36:45 prox pvestatd[1183]: auth key pair too old, rotating..
nov. 07 12:36:47 prox pvestatd[1183]: auth key pair too old, rotating..
nov. 08 12:36:47 prox pvestatd[1183]: auth key pair too old, rotating..
nov. 08 23:38:58 prox pvestatd[1183]: metrics send error 'Supervision': 422 Unprocessable Entity
nov. 08 23:38:59 prox pvestatd[1183]: metrics send error 'Supervision': 422 Unprocessable Entity
[...]
nov. 08 23:56:49 prox pvestatd[1183]: metrics send error 'Supervision': 422 Unprocessable Entity
nov. 09 07:59:58 prox pvestatd[1183]: metrics send error 'Supervision': 404 Not Found
[...]
nov. 09 08:00:28 prox pvestatd[1183]: metrics send error 'Supervision': 404 Not Found
nov. 09 11:14:58 prox pvestatd[1183]: metrics send error 'Supervision': 422 Unprocessable Entity
[...]
nov. 09 11:16:48 prox pvestatd[1183]: metrics send error 'Supervision': 422 Unprocessable Entity

At nov. 08 23:38:58 prox pvestatd[1183]: metrics send error 'Supervision': 422 Unprocessable Entity
> Set "evo-bucket"

After, i'm set generic name "proxmox", and create proxmox bucket in InfluxDB, the info was correctly uploaded to influxDB, and no error in the logs

At nov. 09 07:59:58 prox pvestatd[1183]: metrics send error 'Supervision': 404 Not Found
> i'm try "evo\-bucket"

At nov. 09 11:14:58 prox pvestatd[1183]: metrics send error 'Supervision': 422 Unprocessable Entity
> I'm set "evo-bucket"


I've tried to set up a bucket with a '-' in the name, for me this seems to work without issues.
Indeed, I just created an evo2-bucket, and it works too. I don't understand why it doesn't work with my current bucket.
 
Indeed, I just created an evo2-bucket, and it works too. I don't understand why it doesn't work with my current bucket.
Weird. I don't really know much about InfluxDB - maybe somebody else has an idea why that happens.
 
  • Like
Reactions: EVOTk

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!