Recent content by BobhWasatch

On the master that is serving time to clients you need the "allow" line at least. In addition, IF the master does NOT have NTP available and you want to use the local clock instead, then you also need "local", but the stratum needs to be less than 10. See here for an example...

Most NTP servers will say their time is invalid or a high stratum unless they are synchronized to an external source like another NTP server or a GPS clock. One common symptom of this is that the clients of that server will refuse to synchronize. You can check the status of the clock with...

No worries, I don't need anybody to defend me. Plus, I didn't read the thread very carefully or I would have seen that the OP was using NTP but noted that his issue was the gap between VM startup and when NTP noticed the wrong time. The hook script workaround, like the guest agent method...

Sorry if I accidentally stepped on your bad mood. Was just trying to solve the immediate problem.

You have to configure NTP to correct the time when the delta is large, else it won't correct this problem. How you do that varies by NTP server. For chrony you need something like "makestep 0.1 -1" in the config file. Apparently you don't all know about that.

You could use NTP inside the VM.

I believe that is supposed to update the available packages. PVE also does that on a periodic basis. What happens if you do "apt update" from the command line? What error do you get?

Just to be clear...the way terminals work is they use fixed-size character cells. So many lines by so many columns. This information is communicated to the remote end so it knows how much room there is on the display. The remote end has limited control over the font and size of the terminal. It...

It is not a bug. They changed the default output format between v8 and V9 to make it easier to understand the starttime and endtime fields. But that made it not fit on your particular terminal with your particular setup. Nobody cares but you. Life is hard.

Please look at the Starttime and Endtime columns. See that one shows Unix time format while the other shows fully broken-out time. The latter takes up more screen width because there are more characters. It isn't a font problem, it is a display format change. Maybe you can use a format option...

The fonts look the same to me, but the way times are displayed is different and takes up more characters. Anyway, the font size for ssh would be controlled by your terminal, not by anything on the remote side.

You are missing the command option: pvesm set <storage-name> --disable 0 Edited to put storage-name befre the option.

A really common way this happens is backup up to a remote server using NFS or CIFS. The mount fails for whatever reason and the backups get written to the directory where the remote is supposed to be mounted. That's why everyone is suggesting you unmount those shares before checking space. When...

https://ubuntu.com/download/server?pubDate=20260418#system-requirements-tab-lts 1.5 GB system memory 5 GB of free hard drive space Either a USB port or a DVD drive for the installer media I guess not only does nobody read the instructions, they don't even read the wrapper.

While it may not have messed with the network, it may have messed with the web page. Some of those scripts purport to remove the "nag screen" and as a result they can cause problems when PVE is newer than when the script was last updated.