[SOLVED] Proxmox rrdc update error, no mention of timezone in logs.

chrcoluk

Renowned Member
Oct 7, 2018
175
29
68
45
This is on my local proxmox installation 6.4.

I did some hardware work on the machine, swapped out some fans.

After I powered it back up I noticed was getting timeouts on the UI, and I figured out the web interface was restarting, I then found errors in the syslog as presented here.

https://forum.proxmox.com/threads/rrdc-and-rrd-update-errors.76219/

I then checked the time, and its 3am instead of 3pm.

'hwclock' reports the hardware time is correct, /etc/timezone has the correct timezone.

if I run
Code:
dpkg-reconfigure tzdata
it reports local time is 3pm, but then running date shows 3am.

Any idea what is going on? something somewhere seems to be overriding the time.

Bios shows the correct time.

--

Ignore its in 12 hour format and didnt notice the PM. I may post back if the UI issue doesnt resolve with different topic title.
 
Last edited:
Ok the original issue, as its still ongoing.

This is repeating in the syslog in a loop, no reason seems to be provided for the problem.

Code:
Aug 31 15:21:59 AMD pmxcfs[2326]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-node/AMD: -1
Aug 31 15:21:59 AMD pmxcfs[2326]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/101: -1
Aug 31 15:21:59 AMD pmxcfs[2326]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/104: -1
Aug 31 15:21:59 AMD pmxcfs[2326]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/105: -1
Aug 31 15:21:59 AMD pmxcfs[2326]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/103: -1
Aug 31 15:21:59 AMD pmxcfs[2326]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/100: -1
Aug 31 15:21:59 AMD pmxcfs[2326]: [status] notice: RRDC update error /var/lib/rrdcached/db/pve2-vm/102: -1
 
Hi,
Any idea what is going on? something somewhere seems to be overriding the time.
Did you setup an NTP daemon? What's the output of the follwoing CLI command timedatectl status?

We switched from the implicit old default of systemd-timesyncd to chrony as default for new installations with Proxmox VE 7.0, you may want to already switch to chrony now explicitly to get a time sync daemon that's a bit of a better fit for a server setup.
 
I did not set one up specifically, here is the output.

# timedatectl status
Local time: Tue 2021-08-31 19:35:38 BST
Universal time: Tue 2021-08-31 18:35:38 UTC
RTC time: Tue 2021-08-31 18:35:38
Time zone: Europe/London (BST, +0100)
System clock synchronized: yes
NTP service: active
RTC in local TZ: no

This is after I configured it to use my local ntp server, after reading up on the proxmox documentation, thanks for the advise on switching to chrony.

Also I stopped the rrdcached service for about 2 hours to keep the logs quiet, and now I restarted it and all seems well.
 

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!