[SOLVED] RRDC time spam

[ShinigamiLY]

Hey proxmox folks,

Im new at proxmox and wanted to give it a try. Atm im still a bit frustrated cause of some stufs like the RRDC time spam.
I know, it exists some threads about the timesync ntp and so on like this thread https://forum.proxmox.com/threads/solved-rrdc-update-error.16256/

After a lot of trys and new installations, I werent still able to bring this message away...

Atm I have a fresh installation of it @ Proxmox 6.0

Message:

Jul 16 18:41:43 pve pmxcfs[1062]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-node/pve: -1
Jul 16 18:41:43 pve pmxcfs[1062]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve/local: -1
Jul 16 18:41:43 pve pmxcfs[1062]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/pve/local: /var/lib/rrdcached/db/pve2-storage/pve/local: illegal attempt to update using time 1563295303 when last update time is 1563301843 (minimum one second step)
Jul 16 18:41:43 pve pmxcfs[1062]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve/local-zfs: -1
Jul 16 18:41:43 pve pmxcfs[1062]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/pve/local-zfs: /var/lib/rrdcached/db/pve2-storage/pve/local-zfs: illegal attempt to update using time 1563295303 when last update time is 1563301843 (minimum one second step)

I already tried to use another ntp, to sync it with the bios time and so on...
I even added other ntp servers to the /etc/systemd/timesyncd.conf

or
hwclock --systohc --localtime
or
hwclock --systohc --utc

and so on. Im prety frustrated and yes, the bios time changed after syncing but still, it exists an half seccond difference.

Local time: Tue 2019-07-16 18:45:53 CEST
Universal time: Tue 2019-07-16 16:45:53 UTC
RTC time: Tue 2019-07-16 16:45:52
Time zone: Europe/Berlin (CEST, +0200)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

Any idea?

 

[Alwin]

This could happen because of BIOS settings. Is the BIOS up-to-date? Use a local time server to sync from.

 

[ShinigamiLY]

I did. As u can see in my previous post, the ntp is active and the syncing works.
I even did a sync with the bios with the command hwclock --systohc --localtime

Anyway.
Looks like deleting the files at
/var/lib/rrdcached/db/pve2-storage/pve/local
Resolved it.

 

[karlos]

i found this error after installing on a 2018 NUC. Updating bios, reinstalling fixed it.

 

[PachangaDad]

This worked for me too, Thanks

 

[ieronymous]

Hi
A little bit of an old post but still relevant to this day and version of proxmox 6.2.15
I am having the same problems as you are countering

Nov 24 11:19:55 pve1 pvedaemon[1513]: worker exit
Nov 24 11:19:55 pve1 pvedaemon[1512]: worker 1513 finished
Nov 24 11:19:55 pve1 pvedaemon[1512]: starting 1 worker(s)
Nov 24 11:19:55 pve1 pvedaemon[1512]: worker 17922 started
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-node/pve1: -1
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-node/pve1: /var/lib/rrdcached/db/pve2-node/pve1: illegal attempt to update using time 1606209604 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/100: -1
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/100: /var/lib/rrdcached/db/pve2-vm/100: illegal attempt to update using time 1606209604 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/101: -1
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/101: /var/lib/rrdcached/db/pve2-vm/101: illegal attempt to update using time 1606209604 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/200: -1
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/200: /var/lib/rrdcached/db/pve2-vm/200: illegal attempt to update using time 1606209604 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve1/local-zfs: -1
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/pve1/local-zfs: /var/lib/rrdcached/db/pve2-storage/pve1/local-zfs: illegal attempt to update using time 1606209604 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve1/local: -1
Nov 24 11:20:04 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/pve1/local: /var/lib/rrdcached/db/pve2-storage/pve1/local: illegal attempt to update using time 1606209604 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-node/pve1: -1
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-node/pve1: /var/lib/rrdcached/db/pve2-node/pve1: illegal attempt to update using time 1606209614 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/100: -1
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/100: /var/lib/rrdcached/db/pve2-vm/100: illegal attempt to update using time 1606209614 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/200: -1
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/200: /var/lib/rrdcached/db/pve2-vm/200: illegal attempt to update using time 1606209614 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/101: -1
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-vm/101: /var/lib/rrdcached/db/pve2-vm/101: illegal attempt to update using time 1606209614 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve1/local: -1
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/pve1/local: /var/lib/rrdcached/db/pve2-storage/pve1/local: illegal attempt to update using time 1606209614 when last update time is 1606210146 (minimum one second step)
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-storage/pve1/local-zfs: -1
Nov 24 11:20:14 pve1 pmxcfs[1356]: [status] notice: RRD update error /var/lib/rrdcached/db/pve2-storage/pve1/local-zfs: /var/lib/rrdcached/db/pve2-storage/pve1/local-zfs: illegal attempt to update using time 1606209614 when last update time is 1606210146 (minimum one second step)

Bios up to date
I tried changing bios battery (it was old anyway)
Removing /var/lib/rrdcached/db/pve2-storage/pve/local only solve it until next reboot (what are those filees that are safely to be removed?)
And now I changed the time in gui from the correct one (by the way its almost impossible to sync in second the time in proxmox and bios)
to UTC and messages stopped but I have wrong time. How weird is that? Now that the time difference is 2 hours no RRD update error messages
but when the time difference is between min/secs errors happens Just dont get it.
By the way editing file /etc/systemd/timesyncd.conf involes to remove the # at NTP= and put there a time server of my choice? After altering that would it be visible to gui also? Does this cahnge here takes lead over the gui appearence (because Timezone cant be a null value - no choice to default or nothing )

By the way does anyone knows what that
pve1 pvedaemon[1513]: worker exit
pve1 pvedaemon[1512]: worker 1513 finished
pve1 pvedaemon[1512]: starting 1 worker(s)
pve1 pvedaemon[1512]: worker 17922 started
is?

Thank you