• VMware

    Learn about VMware virtualization for its products like vsphere ESX and ESXi, vCenter Server, VMware View, VMware P2V and many more

  • Linux

    Step by step configuration tutorials for many of the Linux services like DNS, DHCP, FTP, Samba4 etc including many tips and tricks in Red Hat Linux.

  • Database

    Learn installation and configuration of databases like Oracle, My SQL, Postgresql, etc including many other related tutorials in Linux.

  • Did you find what you needed?
    Show your support and gratitude by making a contribution!!
    Life always offers you a second chance ... Its called tomorrow !!!

    Monday, July 03, 2017

    How to fix "Software selection (Source changed - please verify)"

    This is one of the most common error you will face if you are working on unattended Red Hat Linux installation where you have a customised list of Packages.



    Error:


    Solution:
    This error basically means that the list of rpms you planned on installation has one or many dependency issues hence the installation is halted unless you fix the dependency in your parent repository.

    How do we find out which dependency is giving this nightmare?
    • Connect to the GUI console of the node which is failing, for me it is VMware so I am connected to the "console"
    • Clock inside the console
    • Press "Alt+F2" to switch the console and get the shell prompt
    NOTE: Here F2 or any higher button can be used to switch between different terminals. Your installation was running on first terminal so to switch back to the installation console anytime you can press "Alt + F1"

    • Navigate to /tmp directory as it contains your anaconda logs which will help you troubleshoot the problem 
    NOTE: Once the installation succeeds these installation logs will be copied from "/tmp" to "/var/log/anaconda"

    • Open the "packaging.log" which will contain your rpm dependency check related logs
    # less packaging.log
    scroll to the last line (Press shift + G)




    As you can see there was dependency check fail for nscd rpm, now you can go back and fix this on your parent repository and restart the installation.

    I will just give some briefs on how to fix this
    • Go to your server which has the repository which is used for this installation
    # cd /export/home/iserver/linux/install/Linux/rhel7_64/ExtraPackages/
    • Copy the needed dependency glibc with the specified version inside the repo
    • Re-create the repodate using 
    # createrepo /export/home/iserver/linux/install/Linux/rhel7_64/ExtraPackages/
    Spawning worker 0 with 30 pkgs
    Workers Finished
    Saving Primary metadata
    Saving file lists metadata
    Saving other metadata
    Generating sqlite DBs
    Sqlite DBs complete

    Next restart the installation of the respective target node, things should be fine unless you have more dependency failures.

    I hope the article was helpful.


    Related Articles:
    How to save %pre installation log file after installation in Red Hat 7
    How to perform interactive kickstart installation on Red Hat

    Follow the below links for more tutorials

    Step by Step Red Hat Linux 7.0 installation (64 bit) with screenshots
    How to keep a process running after putty or terminal is closed
    How to change the MAC Address of Ethernet device in Linux?
    Step by Step CentOS 7 (64 bit) Installation Guide with Screenshots
    What is nice and how to change the priority of any process in Linux?
    How to save %pre installation log file after installation in Red Hat 7
    How to perform interactive kickstart installation on Red Hat
    How to forcefully stop and kill a process in Linux
    How to create customized bootable ISO image in RHEL/CentOS 7
    How to load modules from kernel during boot in Linux
    How to monitor network bandwidth in Linux using netperf
    How to preserve symbolic link while copying a file in Linux
    15 practical examples of rpm command usage in Linux
    Why is sudo command asking for root password in Linux
    What is umask and how to change the default value permanently?
    Understanding Partition Scheme MBR vs GPT


    0 comments:

    Post a Comment