ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Cockpit: sync system time

    Scheduled Pinned Locked Moved IT Discussion
    cockpitsystem timesyncfedora29fedora server
    13 Posts 6 Posters 1.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • black3dynamiteB
      black3dynamite
      last edited by black3dynamite

      The set time should be set to Automatically using NTP

      There’s a greyed out option to automatically use a specific NTP server.

      FATeknollogeeF 1 Reply Last reply Reply Quote 0
      • FATeknollogeeF
        FATeknollogee @black3dynamite
        last edited by

        @black3dynamite said in Cockpit: sync system time:

        The set time should be set to Automatically using NTP

        There’s a greyed out option to automatically use a specific NTP server.

        I'm on the Automatic setting but the Red checkmark still says "Time not synced".

        black3dynamiteB 1 Reply Last reply Reply Quote 0
        • black3dynamiteB
          black3dynamite @FATeknollogee
          last edited by

          @FATeknollogee said in Cockpit: sync system time:

          @black3dynamite said in Cockpit: sync system time:

          The set time should be set to Automatically using NTP

          There’s a greyed out option to automatically use a specific NTP server.

          I'm on the Automatic setting but the Red checkmark still says "Time not synced".

          Is chronyd.service running?
          https://1.2.3.4:9090/system/services#/chronyd.service

          FATeknollogeeF 1 Reply Last reply Reply Quote 0
          • FATeknollogeeF
            FATeknollogee @black3dynamite
            last edited by

            @black3dynamite chronyd is active

            1 Reply Last reply Reply Quote 0
            • Emad RE
              Emad R @FATeknollogee
              last edited by

              @FATeknollogee

              timedatectl list-timezones
              timedatectl set-timezone Asia/Tokyo

              FATeknollogeeF 1 Reply Last reply Reply Quote 0
              • FATeknollogeeF
                FATeknollogee @Emad R
                last edited by

                @Emad-R Those settings are already set by default.

                1 Reply Last reply Reply Quote 0
                • wrx7mW
                  wrx7m
                  last edited by

                  Are you syncing NTP from an external server? Possibly firewall not letting 123 out? Also, could be a similar issue for internal.

                  1 Reply Last reply Reply Quote 0
                  • FATeknollogeeF
                    FATeknollogee
                    last edited by

                    Am I the only one with the red exclamation?

                    scottalanmillerS 1 Reply Last reply Reply Quote 0
                    • scottalanmillerS
                      scottalanmiller @FATeknollogee
                      last edited by

                      @FATeknollogee said in Cockpit: sync system time:

                      Am I the only one with the red exclamation?

                      I've not seen it.

                      1 Reply Last reply Reply Quote 0
                      • FATeknollogeeF
                        FATeknollogee
                        last edited by

                        Went back, took another look, red mark is gone!!
                        Go figure!

                        scottalanmillerS 1 Reply Last reply Reply Quote 0
                        • scottalanmillerS
                          scottalanmiller @FATeknollogee
                          last edited by

                          @FATeknollogee said in Cockpit: sync system time:

                          Went back, took another look, red mark is gone!!
                          Go figure!

                          It just needed...... time.

                          1 Reply Last reply Reply Quote 3
                          • 1
                            1337
                            last edited by 1337

                            NTP can take a considerable amount of time (hours) to whip the system clock into submission if it had drifted far off UTC.

                            You can start the ntpd with an option to force it to change time directly. It used to be that you'd run ntpdate first and then start ntpd but ntpdate has been depreciated.

                            ntpq -p will show a little more details about the status of ntp sync. First thing to run when troubleshooting ntp.

                            1 Reply Last reply Reply Quote 1
                            • 1 / 1
                            • First post
                              Last post