Aliases not being updated, because "Last Updated" is in the future

[Maarten]

Hi, I've got a problem with aliases not being updated. The reason seems to be that the timestamp of it lies within the future.

Code: [Select]

/var/db/aliastables

-rw-r-----  1 root  wheel    32 Jan 14 13:54:39 2022 WebServers.md5.txt
-rw-r-----  1 root  wheel   250 Jan 14 13:54:39 2022 WebServers.self.txt
-rw-r-----  1 root  wheel   250 Jan 14 13:54:39 2022 WebServers.txt

What's the best approach to solve this? I can do a "touch"  to the file to give it the current timestamp, but I don't know if that's the way to go or even which of the 3 files to touch.

Best regards,

Maarten

[Fright]

Hi
imho deleting *.md5.* and waiting for the next update cycle should be enough

[Maarten]

Hi Fright,

Thanks for your response, this did the job perfectly!

Best regards

[franco]

Hi Maarten,

Is this a VM? It's likely a VM because the time sync is running fast?


Cheers,
Franco

[Maarten]

Hi Franco,

Yes it's a VM, I always disable timesync, but maybe it was activated at some time during a VM move or so.

[franco]

I've seen Hyper-V running fast quite a bit (a second for each minute or so) in the last couple of years with customers so much so that NTP stops correcting it at some point because of too much time drift.

Might be good to keep this under observation since it could expire SSL authentication which is really annoying trying to figure out what's going on.


Cheers,
Franco

[Maarten]

Thanks for the info!