In the meantime, a crash occurred and the installation could not
proceed.
After a yum command unexpectedly stopped during a transaction, run yum-complete-transaction for EL7, or dnf history redo last for EL8.
If these cannot fix your package database, edit your question to add more detail on what failed, including the errors yum is printing.
Updates on a system without internet implies you provide an alterative repo. A local update mirror of your own. Couple ways to do that:
- Via IP: download packages to some internal http server of yours. Custom repo uses http URLs. Requires functional network on the host.
- Via "sneaker net": download packages to removable disk that can be attached to each host. Custom repo uses file:// URLs.
yum install --downloadonly downloads packages to the local cache as it usually does, but does not run the transaction.
yum install when given file names of RPMs, will install those rather than downloading from repos. Useful for one-off ad hoc installs.
You need the correct packages downloaded to resolve the update transaction you are doing. There are dependencies for specific versions of things.
RPMs are archives, like tar, but actually based on cpio. When installed, files will be extracted to the same location regardless of RPM file name. However, don't change the file name, it has useful information, and may be in the yum repo's metadata.
