Session-68 | Configure Local YUM/DNF Repository in RHEL 8 | Managing Repositories | Nehra Classes

Поделиться
HTML-код
  • Опубликовано: 11 сен 2024
  • Session-68 | Configure Local YUM/DNF Repository in RHEL 8 | Managing Repositories | 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

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

  • @shabanraaz9064
    @shabanraaz9064 18 дней назад +1

    thank you so much for such a detailed session. ❤

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

    Thank you for this wonderful session had a very good idea about managing repos in Linux. Enjoyed the learning 👍

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

    Hello sir, your content is top notch in Linux administration domain.

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

    Sir you have clarified all my queries in a single video so clearly. This video is really awesome.

  • @afzaalawan
    @afzaalawan 9 месяцев назад +1

    a great video on repo concept, many thanks

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

    Thank you for this lecture.

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

    thank you nehra sir

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

    Nice one
    clear command equivalent to 'crtl + l'

  • @navneetb1231
    @navneetb1231 2 месяца назад +1

    Some organisation uses their own server for intsalling packages in baseurl option. What is that. How to configure that server to fetch packages

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

      Please follow this tutorial
      ruclips.net/user/liveJOz1AIqXMDM?si=Qe1f6gnRm8zg5-Lf

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

    good info

  • @diptosaha07
    @diptosaha07 Год назад

    Sir, why i am facing this type of problem after installing EPEL. I can not install chromium for this problem.
    Problem: conflicting requests
    - nothing provides libQt5Core.so.5()(64bit) needed by chromium-112.0.5615.165-1.el8.x86_64
    - nothing provides libQt5Core.so.5(Qt_5)(64bit) needed by chromium-112.0.5615.165-1.el8.x86_64
    - nothing provides libQt5Gui.so.5()(64bit) needed by chromium-112.0.5615.165-1.el8.x86_64
    - nothing provides libQt5Gui.so.5(Qt_5)(64bit) needed by chromium-112.0.5615.165-1.el8.x86_64
    - nothing provides libQt5Widgets.so.5()(64bit) needed by chromium-112.0.5615.165-1.el8.x86_64
    - nothing provides libQt5Widgets.so.5(Qt_5)(64bit) needed by chromium-112.0.5615.165-1.el8.x86_64
    - nothing provides libatomic.so.1()(64bit) needed by chromium-112.0.5615.165-1.el8.x86_64
    - nothing provides libatomic.so.1(LIBATOMIC_1.0)(64bit) needed by chromium-112.0.5615.165-1.el8.x86_64
    - nothing provides libpipewire-0.3.so.0()(64bit) needed by chromium-112.0.5615.165-1.el8.x86_64
    (try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

  • @viraltube6974
    @viraltube6974 11 месяцев назад

    Hi sir,
    I need your help on setup nginx , I want to hide servers name from nginx but it is required header module so that I can hide the name but problem is my server is airgap there is no internet than how can I install thal module

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

    Do you have an English version of this video?

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

      Yes, please follow english rhcsa playlist

  • @AkshayPatil-j1z
    @AkshayPatil-j1z 27 дней назад +1

    why this error during downloading metadata for repository baseos on client side in rhel9.4

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

      Errors when downloading metadata for a repository in RHEL 9.4, especially for the baseos repository, can arise due to several reasons. Below are some common causes and solutions to resolve the issue:
      1. Network Issues
      Cause: The client might have network connectivity issues that prevent it from reaching the repository server.
      Solution: Verify network connectivity by pinging the repository server or running curl on the repository URL to ensure it's reachable.
      ping repository_url
      curl -I repository_url
      2. Incorrect Repository Configuration
      Cause: The repository configuration file might be incorrectly set up, pointing to an invalid URL or missing required parameters.
      Solution: Check the repository configuration in /etc/yum.repos.d/. Ensure that the base URL (baseurl) and gpg key settings are correct.
      sudo nano /etc/yum.repos.d/baseos.repo
      Example of a correctly configured baseos repo:
      [baseos]
      name=Red Hat Enterprise Linux 9.4 BaseOS
      baseurl=mirror.centos.org/centos/9-stream/BaseOS/x86_64/os/
      enabled=1
      gpgcheck=1
      gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
      3. Repository Not Enabled
      Cause: The baseos repository might not be enabled on the client.
      Solution: Ensure the repository is enabled by checking its status and enabling it if necessary.
      sudo dnf repolist all
      sudo dnf config-manager --set-enabled baseos
      4. Outdated or Corrupt Cache
      Cause: The DNF/YUM cache might be outdated or corrupt, causing issues with metadata retrieval.
      Solution: Clean the cache and try updating the metadata again.
      sudo dnf clean all
      sudo dnf makecache
      5. Subscription or Entitlement Issues (RHEL-specific)
      Cause: If you're using RHEL and your system isn’t properly registered with Red Hat Subscription Management (RHSM), or if your subscription is invalid or expired, you might face issues with accessing repositories.
      Solution: Ensure that your system is registered and has a valid subscription.
      sudo subscription-manager status
      sudo subscription-manager refresh
      sudo subscription-manager attach --auto
      6. Proxy Configuration Issues
      Cause: If your environment uses a proxy, but it's not properly configured for DNF/YUM, you might face issues with downloading metadata.
      Solution: Configure the proxy in the DNF/YUM configuration.
      Add the following lines to /etc/yum.conf or the specific repo file in /etc/yum.repos.d/:
      proxy=proxy-server:port
      proxy_username=your-username
      proxy_password=your-password
      7. Repository Server Issues
      Cause: The repository server itself may be down or experiencing issues.
      Solution: Wait and try again later or check Red Hat’s status page for any known outages. You can also switch to another mirror if available.
      8. GPG Key Issues
      Cause: If the GPG key used to verify the repository is missing or corrupt, it can cause issues during metadata download.
      Solution: Import the GPG key again.
      sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
      If you've tried these steps and are still facing issues, please provide the exact error message, and I can help troubleshoot further.

  • @user-zz6ez3fi1q
    @user-zz6ez3fi1q 6 месяцев назад +1

    I want to access the whole playlist of this session. Is it available?

  • @harendrasingh1457
    @harendrasingh1457 8 дней назад +1

    hi sir i am not able to install local repository in rhel 7 please help me sir

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

      kindly follow rhel 7 repository configuration tutorial

  • @user-cv6su6fv5q
    @user-cv6su6fv5q Год назад +1

    Sir I have used Cent-Os 7 so when create local.repo so it is mention AppStream and BaseOS both or only BaseOs. please guide

    • @NehraClasses
      @NehraClasses  Год назад

      In CentOS 7 no need to create local repositories. And there is no need to create separate sections for the app stream and baseos

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

    hi sir, closed env me jaha internet allowed hi nahi hai directly server pe due to security concerns, waha kaise subscribe kare OS ko for using yum and other tools? how to use subscription-manager and login through id/password because internet is not there?

  • @Awwe12675
    @Awwe12675 Год назад

    I’m really confused why they giving two node
    And should I use ssh or kvm in exam ?

  • @Awwe12675
    @Awwe12675 Год назад

    I get failed exam exam
    They give me link for repo I configuration it
    But not working
    So I can get again exam without payments again it’s impossible?

  • @Blomvi
    @Blomvi 9 месяцев назад +1

    hello, is there a way we can have the english version please?

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

      please follow our rhcsa english playlist.

  • @AnudeepSingh164
    @AnudeepSingh164 2 месяца назад +1

    sir merko samjh ni a rha iso image kha sa milage ek short video bana kr help krdo

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

      same iso image with which you did the installation

    • @AnudeepSingh164
      @AnudeepSingh164 2 месяца назад

      @@NehraClasses ok sir thanks keep suporting and our college students also likes your videos we need to know war deployment too plase create a video on it

  • @omkarshukla742
    @omkarshukla742 3 месяца назад +1

    what will be impact if inode will full

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

      system will not allow you to create the new files.

    • @omkarshukla742
      @omkarshukla742 3 месяца назад

      @@NehraClasses thanks sir

  • @kohinoorteamyogeshchhabra8255
    @kohinoorteamyogeshchhabra8255 Год назад

    Sir epel wala package install ni ho rha

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

    sir how to find gpg path by using cmd line direct

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

    how to do the same centos server

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

      on centos there is no need to configure the local repository.

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

    can we use yum Repositories and epel 7 packages in centos 8 ?

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

    Please provide english subtitles or english version

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

      Please check english training playlist

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

  • @AkshayPatil-j1z
    @AkshayPatil-j1z 27 дней назад +1

    why this error during downloading metadata for repository baseos on client side in rhel9.4

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

      The error you're encountering while downloading metadata for the `baseos` repository in RHEL 9.4 typically indicates an issue with the repository configuration or network connectivity. Here are some common causes and solutions:
      ### Possible Causes and Solutions
      1. **Network Connectivity Issues:**
      - **Cause**: The client system might be experiencing network issues, preventing it from reaching the repository servers.
      - **Solution**: Check your network connection by pinging a reliable external server, like Google's DNS (`ping 8.8.8.8`). Ensure that the client has proper internet access.
      2. **Repository Configuration Issues:**
      - **Cause**: The `baseos` repository configuration might be incorrect or incomplete.
      - **Solution**: Check the repository configuration file located at `/etc/yum.repos.d/` (e.g., `/etc/yum.repos.d/redhat.repo` or custom repo files). Ensure that the `baseurl`, `mirrorlist`, or `metalink` entries are correct and pointing to valid URLs.
      3. **Subscription or Entitlement Issues:**
      - **Cause**: If your RHEL system is not properly registered or the subscription has expired, it won't be able to access the repositories.
      - **Solution**: Verify your subscription status with the following commands:
      ```bash
      subscription-manager status
      subscription-manager list --available
      ```
      If the subscription is inactive or expired, renew it or attach a valid one using `subscription-manager`.
      4. **Repository Server Issues:**
      - **Cause**: The repository server you're trying to access might be down or temporarily unavailable.
      - **Solution**: Try accessing the repository later or manually browse to the repository URL using a web browser to check if it's accessible.
      5. **Proxy Configuration:**
      - **Cause**: If you're behind a proxy and it's not configured correctly, it could block access to the repository.
      - **Solution**: Configure the proxy in the `/etc/yum.conf` file by adding:
      ```bash
      proxy=your-proxy-server:port
      proxy_username=your-username
      proxy_password=your-password
      ```
      Or export the proxy settings:
      ```bash
      export http_proxy=your-proxy-server:port
      export https_proxy=your-proxy-server:port
      ```
      6. **Outdated or Corrupt Repository Cache:**
      - **Cause**: The local repository cache might be outdated or corrupted.
      - **Solution**: Clear the cache and try updating again:
      ```bash
      sudo yum clean all
      sudo yum makecache
      sudo yum update
      ```
      7. **Repository URL or GPG Key Issues:**
      - **Cause**: If the repository URL has changed or the GPG key is incorrect, metadata download will fail.
      - **Solution**: Ensure that the correct GPG key is imported, and the repository URL is valid. You can update the GPG key with:
      ```bash
      sudo rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
      ```
      ### Additional Troubleshooting Steps:
      - **Check Logs**: Look at `/var/log/yum.log` or `/var/log/dnf.log` for more detailed error messages.
      - **Try Alternative Mirrors**: If the default mirror is down, you can manually change the `baseurl` in the repo file to point to an alternative mirror.
      If none of these solutions resolve the issue, please share the exact error message you're receiving, and I can provide more specific assistance.