[SOLVED] Proxmox 9 update /etc/chrony/chrony.conf

prmadmax

New Member
May 12, 2024
16
7
3
UK
www.phantomrebels.com
Hi,

During the Update I did a side by side compare of the chrony and used gyazo to take a screenshot of the /etc/chrony/chrony.conf changes which was just a couple of lines.

However the screenshot seemed to close the window and i saw a warning of an invalid option or something so not sure the file got updated.

How can i fix this with a fresh .conf file and reapply my changes? As right now I dont think it changed chrony conf at all.
 
Got this sorted.

Steps i did:
Code:
cp /etc/chrony/chrony.conf /etc/chrony/chrony.conf.bak
then
Code:
cp /usr/share/chrony/chrony.conf /etc/chrony/chrony.conf

Then I did nano /etc/chrony/chrony.conf to add back my local time-servers in the datacenter and issued
systemctl restart chrony
systemctl status chrony

Using these commands to check it was working:
chronyc tracking
chronyc sources -v

If anything looks wrong, let me know.
 
Last edited:
Hi,
could you (briefly) share how you solved it and mark the thread as solved? I.e. using the Edit Thread button and selecting the [SOLVED] prefix. This will help other users with similar issues find the solution more quickly.

Note that you can also check /var/log/apt/term.log (or rotated friends like /var/log/apt/term.log.1.gz) for the full upgrade log if you want to find the error again.
 
Hi,
could you (briefly) share how you solved it and mark the thread as solved? I.e. using the Edit Thread button and selecting the [SOLVED] prefix. This will help other users with similar issues find the solution more quickly.

Note that you can also check /var/log/apt/term.log (or rotated friends like /var/log/apt/term.log.1.gz) for the full upgrade log if you want to find the error again.
Done :)
 
  • Like
Reactions: fiona
@fiona looks like the line i saw briefly in the shell during the update was relating to something else:
Code:
running python rtupdate hooks for python3.13...
/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/resource.py:807: SyntaxWarning: invalid escape sequence '\d'
  for x in re.findall('(?:[\da-f]){2}',
 
@fiona looks like the line i saw briefly in the shell during the update was relating to something else:
Code:
running python rtupdate hooks for python3.13...
/usr/lib/x86_64-linux-gnu/glusterfs/python/syncdaemon/resource.py:807: SyntaxWarning: invalid escape sequence '\d'
  for x in re.findall('(?:[\da-f]){2}',
I think this can be safely ignored if you don't use glusterfs or more precisely, this sync daemon script. Would need to be investigated whether it's cosmetic or an actual issue and reported to Debian upstream if nobody did this yet. But since GlusterFS is not supported in Proxmox VE anymore, and I already got my hands full, it won't be me 0=)
 
  • Like
Reactions: prmadmax