Session-129 | NTP (Chrony) Server & Clients Configuration in Linux | Nehra Classes

Поделиться
HTML-код
  • Опубликовано: 3 окт 2024
  • Session-129 | NTP (Chrony) Server & Clients Configuration in Linux | Nehra Classes
    *********
    🎬 Video Chapters: 👇
    00:00 Channel Intro
    *********
    ✅ Click Here 👉 www.youtube.co...
    *********
    📚 Available Courses Playlists For Members:
    RHCSA (Hindi) 👉 • RedHat Certified Linux...
    RHCSA (English) 👉 • RedHat Certified Linux...
    RHCE (Hindi) 👉 • Playlist
    RHCE (English) 👉 • Playlist
    Ansible (English) 👉 • RHCE V8 (EX294) Ansibl...
    Shell Scripting (English)👉 • Playlist
    AWS (English) 👉 • Playlist
    *********
    🤝 Join Membership 👉 / @nehraclasses
    *********
    🙏🙏 Thanks for watching the video. If it helped you then, please do like & share it with others as well. Feel free to post your queries & suggestions in the comment box, we will be happy to answer your queries.
    👍👍 If you like our hard work then please do subscribe to our channel & turn on the bell notification to get the latest notifications of our video.
    *****
    My DSLR Camera 👉 amzn.to/36954Ml
    My Microphone 👉 amzn.to/3mZavTS
    My iPhone 👉 amzn.to/3lWa63j
    My Gaming Router 👉 amzn.to/3j3dQON
    My FireStick 👉 amzn.to/345150F
    My Head-Phone 👉 amzn.to/3ie4rDB
    ******
    My Dream Laptop 👉 amzn.to/37j11fp
    My Dream TV 👉 amzn.to/2KR32b4
    My Dream IPhone 👉 amzn.to/36j8oE1
    ******
    📲 Contact Us:
    Telegram 👉 t.me/NehraClasses
    Email 👉 nehraclasses@gmail.com
    ******
    ✅ Follow Us On Social Media Platforms:
    Twitter Handle 👇
    / nehraclasses
    Facebook Page 👇
    / nehraclasses
    Instagram Handle 👇
    / nehraclasses
    Website 👇
    nehraclasseson...
    =======
    ©COPYRIGHT. ALL RIGHTS RESERVED.
    #NehraClasses #NehraClassesLive #LinuxTraining

Комментарии • 31

  • @VibeRover
    @VibeRover 2 года назад +2

    Khatarnaak...... explanation......
    Pura samj Gaya muze❤️❤️❤️❤️🤟🤟🤟🤟

  • @harispalegar6806
    @harispalegar6806 Год назад +1

    Each Session have unique and mind blowing..!!
    Thank You so Much..

  • @akshayjain693
    @akshayjain693 Год назад +1

    Great teacher of Linux

  • @devendradewangan8616
    @devendradewangan8616 11 месяцев назад +1

    Informative session as usual

  • @syedarahman6299
    @syedarahman6299 Год назад +2

    Thanks a lot. Very nicely explained all these step.

  • @raneesh5240
    @raneesh5240 6 месяцев назад +1

    Nice section 👌

  • @uttamkumarkumar3171
    @uttamkumarkumar3171 2 года назад +2

    Sirji nice well explain session

  • @afrasiyabkhan6170
    @afrasiyabkhan6170 2 года назад +2

    thank you sir from Pakistan

  • @karthickram3804
    @karthickram3804 7 месяцев назад +1

    could you please tell me the English version of this Nehra ji.. such a good explanation with clear examples..please ..

    • @NehraClasses
      @NehraClasses  7 месяцев назад

      please check english server playlist

  • @krishanveerchaudhary4037
    @krishanveerchaudhary4037 2 года назад +1

    Sir RHCSA exam me isse trha h solution krna h kya NTP ke question ka.
    Sir This is enough knowlege of RHCSA exam for this topic

  • @MrPrabhu666
    @MrPrabhu666 Месяц назад +1

    Hi sir,
    Unable to sync ntp time in rhel 7.3
    Please send me what configuration need to change in chrony.conf file

    • @NehraClasses
      @NehraClasses  29 дней назад

      To resolve issues with NTP time synchronization in RHEL 7.3 using `chrony`, you'll need to ensure that the `chrony.conf` file is properly configured. Below is a basic configuration for `chrony.conf` that you can adjust as needed:
      ### Sample `chrony.conf` Configuration
      ```bash
      # Use public servers from the pool.ntp.org project.
      server 0.centos.pool.ntp.org iburst
      server 1.centos.pool.ntp.org iburst
      server 2.centos.pool.ntp.org iburst
      server 3.centos.pool.ntp.org iburst
      # Ignore stratum in a server's response.
      stratumweight 0
      # Record the rate at which the system clock gains/losses time.
      driftfile /var/lib/chrony/drift
      # Allow the system clock to be stepped in the first three updates
      # if its offset is larger than 1 second.
      makestep 1.0 3
      # Enable kernel synchronization of the real-time clock (RTC).
      rtcsync
      # Allow NTP client access from local network.
      allow 192.168.0.0/24
      # Serve time even if not synchronized to any NTP server.
      local stratum 10
      # Log measurements and statistics.
      logdir /var/log/chrony
      # Specify the command key used to authenticate administrative commands.
      commandkey 1
      ```
      ### Key Points to Check:
      1. **NTP Servers:**
      - Make sure the `server` lines point to valid and reachable NTP servers. The `iburst` option speeds up the initial synchronization.
      2. **Allow Network:**
      - If you need to allow clients from your local network to query your chrony server, use the `allow` directive with your network's CIDR notation.
      3. **Real-Time Clock Sync:**
      - The `rtcsync` option ensures the hardware clock is synced with the system clock.
      4. **Local Time Server:**
      - If this machine should act as a time server for others, `local stratum` sets its stratum level when it's unsynchronized.
      ### Steps to Apply Changes:
      1. **Edit the Configuration:**
      - Open the `chrony.conf` file:
      ```bash
      sudo vi /etc/chrony.conf
      ```
      - Make the necessary changes.
      2. **Restart Chrony Service:**
      - After making changes, restart the chrony service:
      ```bash
      sudo systemctl restart chronyd
      ```
      3. **Check Synchronization Status:**
      - Verify the synchronization status:
      ```bash
      chronyc tracking
      chronyc sources
      ```
      This configuration should help you set up and sync NTP time correctly in RHEL 7.3. If the issue persists, check for network connectivity to the NTP servers or any firewall rules that might be blocking NTP traffic.

  • @dineshmohan6012
    @dineshmohan6012 Месяц назад +1

    hello sir, i am getting system clock synchronised as no and thats why ntp is not working properly . what should i do
    root@client ~]# timedatectl
    Local time: Tue 2024-08-27 18:01:57 IST
    Universal time: Tue 2024-08-27 12:31:57 UTC
    RTC time: Tue 2024-08-27 12:31:56
    Time zone: Asia/Kolkata (IST, +0530)
    System clock synchronized: no
    NTP service: active
    RTC in local TZ: no

    • @NehraClasses
      @NehraClasses  Месяц назад +1

      The error message "System clock synchronized: no" indicates that your system's clock is not synchronized with an external time source. This can prevent NTP (Network Time Protocol) from working correctly, as it relies on accurate time synchronization.

    • @dineshmohan6012
      @dineshmohan6012 Месяц назад

      @@NehraClasses ok sir, what to do to solve it. I tried sane steps as mentioned in video but system clock sync shows no

    • @dineshmohan6012
      @dineshmohan6012 Месяц назад

      @@NehraClasses should i connect both client and server to internet ? cant we configure a ntp for a private network

  • @Linuxhunt
    @Linuxhunt Месяц назад +1

    hii sir session is amaizing ..
    but i am facing some isse that is when i use chronyc sources i get output but when i use chronyc clients i get no output .
    please help me if you can guys

    • @NehraClasses
      @NehraClasses  Месяц назад

      I'm glad you enjoyed the session! Regarding your issue with `chronyc`, it seems like `chronyc sources` is working fine, which means your NTP (Network Time Protocol) sources are configured correctly. However, getting no output from `chronyc clients` suggests that there might not be any clients currently connected to your chrony server.
      Here are a few things to check:
      1. **Verify if the chrony server is configured as a time source**: Ensure that your chrony server is set up to serve time to clients. You should have the `allow` directive in your `/etc/chrony/chrony.conf` file, which allows clients to connect to the server.
      2. **Check the network configuration**: Ensure that the clients are correctly configured to use your chrony server as their NTP server and that there's no firewall blocking the NTP requests.
      3. **Confirm that clients are requesting time**: If your clients aren't correctly configured to use your chrony server or are turned off, they won't show up in `chronyc clients`. You can check the client’s NTP configuration to ensure it's pointing to your chrony server.
      4. **Restart the chrony service**: Sometimes, simply restarting the chrony service on both the server and client machines can resolve the issue.
      To restart chrony:
      ```bash
      sudo systemctl restart chronyd
      ```
      5. **Enable logging**: You might want to enable detailed logging to see if there are any clues in the logs.
      If you've checked all the above and still face issues, let me know the specific configuration and setup details, and I can assist further!

    • @Linuxhunt
      @Linuxhunt Месяц назад

      @@NehraClasses thanks to reply me sir and thanks to solve my problem ❤❤❤❤😊😊😊😊

    • @aliadeel6093
      @aliadeel6093 5 дней назад

      same issue I am facing

    • @aliadeel6093
      @aliadeel6093 5 дней назад

      Solution, on server machine please recheck the subnet mask. I have put /16 instead of /24. now its working fine.

  • @niteshsingla5447
    @niteshsingla5447 2 года назад

    Sir at 27:30 in my server machine show system clock synchronised no ,how to fix this to Yes please help me🙏🏻

  • @VikasChahar1411
    @VikasChahar1411 2 года назад

    Hi sir my client machine shows the ntp server as not reachable which is indicated by ^? Symbol how can I fix it? Please help

  • @T7shorts
    @T7shorts 2 года назад

    Hii, sir please make a tutorial on setting up client to client vpn using openvpn or wireguard.

    • @NehraClasses
      @NehraClasses  2 года назад

      Video already uploaded please check

    • @T7shorts
      @T7shorts 2 года назад

      @@NehraClassessir please drop a link ot name here.