1
24.1 Production Series / Re: unable to update from 23.7 to 24.1
« on: May 03, 2024, 04:03:41 pm »
I actually got a glimpse of that error on a VM I discovered that was off for a few months.
When I turned it on it would keep proposing to update to 24.1.r1 from 24.1.r_3.
Restarted services or rebooting didn't help, so I tried -Vbkr and saw it failing to verify the cert.
Inspected the cert with openssl and found it not valid yet, which ultimately revealed the ntp issue - machine time was in January.
So the previous comment about the FW being 30 seconds behind is a clear indication time is not syncing and causing the update issues for the OP - if there's no proxy upstream.
The time can be set in CLI to get the machine to update, and the NTP issue can be solved after.
The date command for the CLI is this one, two digits for year month day hour minutes .seconds
When I turned it on it would keep proposing to update to 24.1.r1 from 24.1.r_3.
Restarted services or rebooting didn't help, so I tried -Vbkr and saw it failing to verify the cert.
Inspected the cert with openssl and found it not valid yet, which ultimately revealed the ntp issue - machine time was in January.
So the previous comment about the FW being 30 seconds behind is a clear indication time is not syncing and causing the update issues for the OP - if there's no proxy upstream.
The time can be set in CLI to get the machine to update, and the NTP issue can be solved after.
The date command for the CLI is this one, two digits for year month day hour minutes .seconds
Code: [Select]
date yymmddhhmm.ss