rrdtool fails on identificat timestamps as root cause for /var/lib/rrdtool/....

[Joris L.]

Jun 25 12:59:26 myhost collectd[42379]: rrdtool plugin: rrd_update_r (/var/lib/collectd/rrd/pvx/cgroups-<vmid>/.......rrd) failed: /var/lib/collectd/rrd/pvx/cgroups-<vmid>/........rrd: illegal attempt to update using time 1593082766 when last update time is 1593082766 (minimum one second step)

All hosts are synced using NTP. Because the notifciation is explicit about time i do not look at collectd.conf configuration which appears to work well.

Tried:

find /var/lib/rrdcache/ -type f -mtime +5 -delete​

​

which removed some files, to no avail.

Please recommend what to investigate and where to look for a fix.

<vmid> is here for a privileged LXC, the log excerpt on the first line is from /var/log/syslog on the VM server.

 

[dcsapak]

collectd

but this is not a tool which is installed by default...

 

[Joris L.]

but this is not a tool which is installed by default...

Okay, and ?

Please, make proxmox into a mini distribution then.

 

[dcsapak]

Okay, and ?

sorry for the late answer...

my point was, if you install additional software from the debian repositories, we have no influence on them and how they are configured...
we do not touch the files referenced in the original post, so it is not really an issue of our stack...

 

[Joris L.]

sorry for the late answer...

my point was, if you install additional software from the debian repositories, we have no influence on them and how they are configured...
we do not touch the files referenced in the original post, so it is not really an issue of our stack...

Why not reduce proxmox to a specialist distro then ?

After installing the package i see nothing but trouble which i cannot blame on Debian.

There is an rrdcache process running unbound but i find the process nowhere for example.

 

[tom]

I follow your posts, you seems to have many issues where no other is seeing. So there must be something really different and/or broken on your installation and environment.

If you have issues, please provide the details in full, most times you missed to post details, e.g. in this post https://forum.proxmox.com/threads/debian-lxc-standard-10-x-slow-to-boot-unstable.72434/

This forum is only for Proxmox VE support., if you have questions outside our packages, we cannot guarantee detailed answers.

 

[Joris L.]

I follow your posts, you seems to have many issues where no other is seeing. So there must be something really different and/or broken on your installation and environment.

If you have issues, please provide the details in full, most times you missed to post details, e.g. in this post https://forum.proxmox.com/threads/debian-lxc-standard-10-x-slow-to-boot-unstable.72434/

This forum is only for Proxmox VE support., if you have questions outside our packages, we cannot guarantee detailed answers.

Reading my posts you should have found ... most issues i posted about at length in frustration were caused by the consequences of an upgrade to 32GB of ram. This forced me to lower default ram speed from 3200Mhz profile to custom 2667Mhz profile Since, no more weird issues. I am to upgrade the CPU to avoid any memory related issues which appear to be specific to this 1st gen CPU. For this setup i also experiment with kernel boot parameters in relation to PCI-E passthrough, performance, security.

I run a one man maintained lab environment where i maintain a growing number of machines and service in addition to working on customer assignments. I do not have the luxury others may have being part of a team etc.

I am naturally hesitant to posting any configuration to a public forum, i almost never did in the past 20 years. I also do not see the point of doing so most often, especially when i most often resolve the issue myself eventually. Also explaining the decline in the number of my posts. Proxmox was and is new to me. It is probably overkill for what i need here but it was the fastest installed solution at hand at the time.

As a paying customer i hoped to have more than a public forum to disclose configuration details on to the world.

 

[t.lamprecht]

As a paying customer i hoped to have more than a public forum to disclose configuration details on to the world.

The (not world visible) enterprise support portal is over here https://my.proxmox.com/

After installing the package i see nothing but trouble which i cannot blame on Debian.

Debian is not to blame, if you manually install packages out of Proxmox VE's scope it's always you being responsible for that actions. If an update of ours would pull it in and break things, we'd be to blame - but I do not think that happened here.
That said, we may well add a conflict to the "collectd" package if it breaks Proxmox VE systems.

Why not reduce proxmox to a specialist distro then ?

Because that would reduce the freedom of a lot of people, and we do not want that, just to avoid issues with a small count of the 50k Debian packages available. Note that you cannot install all available Debian packages at the same time - this would break things to

 

[Joris L.]

The (not world visible) enterprise support portal is over here https://my.proxmox.com/



Debian is not to blame, if you manually install packages out of Proxmox VE's scope it's always you being responsible for that actions. If an update of ours would pull it in and break things, we'd be to blame - but I do not think that happened here.
That said, we may well add a conflict to the "collectd" package if it breaks Proxmox VE systems.



Because that would reduce the freedom of a lot of people, and we do not want that just to avoid issues with a small count of the 50k packages available. Note that you cannot install all available Debian packages at the same time - this would break things to

thanks for the constructive response

My personal view is a specialist distro with the Debian repositories to be supplemented at will as optional would be the most convenient for everone. Just my view.