Skip to content
Search AlmaLinux

    Browse this documentation

    AlmaLinux 10: turning one host into a LAN time source

    An AlmaLinux 10.2 Server VM running chrony-4.8-2.el10.

    The host has no upstream NTP (the lab has no internet), so two directives make it serve its own clock to the LAN while a second VM syncs from it. Screenshot: public/evidence/chrony/alma-server.png.

    $ grep -E '^(allow|local stratum)' /etc/chrony.conf
    allow 192.168.2.0/24
    local stratum 10
    • allow 192.168.2.0/24: permit clients from that network;
    • local stratum 10: when no upstream is available, act as a stratum 10 reference.

    Restart with systemctl restart chronyd.

    $ chronyc tracking | grep -E '^(Reference ID|Stratum)'
    Reference ID : 7F7F0101 ()
    Stratum : 10

    Reference ID 7F7F0101 (127.127.1.1) is chrony’s marker for the local clock — meaning there is no upstream and the host is running on its own hardware clock. That is fine for a lab and unacceptable for production timekeeping.

    $ chronyc clients
    Hostname NTP Drop Int IntL Last Cmd Drop Int Last
    ===============================================================================
    192.168.2.243 7 0 3 - 28 0 0 - -
    $ chronyc serverstats | head -3
    NTP packets received : 7
    NTP packets dropped : 0

    clients shows who is polling and how many packets each sent; serverstats gives the aggregate. Both are server-side checks, which beat guessing from the client.

    $ firewall-cmd --list-services
    cockpit dhcpv6-client ntp ssh
    $ ss -lun | grep ':123 ' | head -1
    UNCONN 0 0 0.0.0.0:123 0.0.0.0:*

    The Server environment does not include ntp by default: firewall-cmd --permanent --add-service=ntp && firewall-cmd --reload.

    ScenarioSuitable
    Isolated lab needing one clockYes (accuracy follows the host RTC)
    Production internal time sourceNo: local is a degraded mode and does not correct frequency drift
    Short fallback while upstream is downTemporary, but watch the stratum

    A real time source should track at least two upstreams (pool or two server ... iburst entries); local belongs to fully isolated networks.

    AlmaLinux 10.2: serving time with local stratum and verifying a client

    • allow without local stratum: with no upstream the server reports stratum 0 and clients refuse it;
    • Forgetting to open ntp: clients stay at ^? while NTP packets received stays 0;
    • Reading local as “high precision”: it only makes the host usable, accuracy is the hardware clock’s;
    • Leaving local after upstream returns: chrony prefers real upstreams, but the stale directive misleads troubleshooting.
    Terminal window
    sudo grep -E '^(allow|local stratum)' /etc/chrony.conf
    sudo chronyc serverstats | head -3
    sudo chronyc clients | head -4
    sudo firewall-cmd --list-services | tr ' ' '\n' | grep -x ntp

    Checks:

    1. The allow network covers the client;
    2. NTP packets received grows while the client runs;
    3. The client’s IP appears in clients;
    4. ntp is in the firewall service list.

    常见问题

    Does local stratum 10 poison upstream?

    No. It is a local reference used only when no better source exists; clients see stratum 10 and above.

    Can I restrict which clients may query?

    Yes — allow takes networks or addresses, and restrict directives can narrow permissions further.

    Why is the client stratum 11?

    Each hop adds one: a stratum 10 server yields a stratum 11 client.