How can i convert metricbeat to a shippable RPM which could be installed by SCP on servers without internet?
How i installed metric beat
sudo rpm --import https://packages.elastic.co/GPG-KEY-elasticsearch
in /etc/yum.repos.d/elastic.repo add
[elastic-7.x]
name=Elastic repository for 7.x packages
baseurl=https://artifacts.elastic.co/packages/7.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=1
autorefresh=1
type=rpm-md
Sudo yum install metricbeat
How can I make this into a copyable rpm?
You can download the RPM using yumdownloader and use scp, or some other method, to copy it to the servers without internet access.
Related
I am trying to install skopeo on AWS Linux but getting error - No package found.
[root#master ~]# yum -y install skopeo
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
amzn2-core | 3.7 kB 00:00:00
228 packages excluded due to repository priority protections
No package skopeo available.
Error: Nothing to do
[root#master ~]#
How can I install Skopeo on AWS Linux?
Is there any other tool available on AWS linux which helps to inspect images?
Edited: This package is available in the CentOS-7 Extras repo. Enabling this repo on Amazon Linux 2 may have unintended consequences. You may want to consider running an EC2 instance of CentOS or RHEL to manage this workload. If you want to live on the edge IMO, do the below at your own risk.
You can either download (wget or curl) and install the package manually with rpm, and resolve the dependencies, or you can configure the CentOS-7 repository and try to install directly with Yum.
In order to install packages from the CentOS-7 Extras repo, you need to download the GPG key :
cd /etc/pki/rpm-gpg/
curl -s https://www.centos.org/keys/RPM-GPG-KEY-CentOS-7
You will then need to create a repo file in /etc/yum.repos.d :
[extras]
name=CentOS-7 - Extras
mirrorlist=http://mirrorlist.centos.org/?release=7&arch=$basearch&repo=extras
#baseurl=http://mirror.centos.org/centos/7/extras/$basearch/
enabled=0
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-CentOS-7
priority=1
This only gets you part way there :
# yum --disablerepo='*' --enablerepo='extras' search skopeo
Loaded plugins: extras_suggestions, langpacks, priorities, update-motd
============================================================================================ N/S matched: skopeo =============================================================================================
skopeo.x86_64 : Inspect container images and repositories on registries
skopeo-containers.x86_64 : Configuration files for working with image signature
containers-common has a dependency on subscription-manager which is part of the CentOS-7 core packages, and there are related dependencies. You can download these core packages here :
http://mirror.centos.org/centos/7/os/x86_64/Packages/
You will need the following packages :
cd /tmp
wget http://mirror.centos.org/centos/7/os/x86_64/Packages/subscription-manager-1.24.42-1.el7.centos.x86_64.rpm
wget http://mirror.centos.org/centos/7/os/x86_64/Packages/subscription-manager-plugin-ostree-1.24.42-1.el7.centos.x86_64.rpm
wget http://mirror.centos.org/centos/7/os/x86_64/Packages/subscription-manager-rhsm-1.24.42-1.el7.centos.x86_64.rpm
wget http://mirror.centos.org/centos/7/os/x86_64/Packages/subscription-manager-rhsm-certificates-1.24.42-1.el7.centos.x86_64.rpm
wget python-syspurpose-1.24.42-1.el7.centos.x86_64.rpm
wget http://mirror.centos.org/centos/7/os/x86_64/Packages/python-syspurpose-1.24.42-1.el7.centos.x86_64.rpm
wget http://mirror.centos.org/centos/7/os/x86_64/Packages/python-dmidecode-3.12.2-4.el7.x86_64.rpm
You will also need to install dependencies available from Amazon Linux 2 :
yum install dbus-python pygobject3-base python-decorator python-dmidecode python-ethtool python-inotify python-syspurpose python-gobject-base gobject-introspection
Now you can install the manually downloaded RPMs :
rpm -i *rpm
I completed all of these steps on a test server, and everything installed. I'm not familiar with the Skopeo tools, so I can't speak as to whether or not it will work.
Once word of caution, when you add third party repos to an OS, you risk unintentional upgrades of other packages during a normal OS upgrade, and this can break things.
You can avoid this by setting "enable = 0" in the Yum repo files, and enabling the repo at the command line ONLY when you want to update those packages (i.e. "yum --enablerepo=remi update skopeo")
OK, hope this helps.
I have logstash installed on one of my CentOS 7 hosts. When I run the sudo yum list installed command, it is not on the list. When I try to install logstash, yum offers me a fresh install. What could be the reason for this behavior?
Probably logstash was installed manually then, and not by yum/rpm. You can check this by asking rpm (which is used by yum under the hood):
rpm -qf /path/to/logstash-binary
translation: to which package does /path/to/logstash-binary belong. Then you'll know if it belongs to an rpm package. If not, that means the binary was installed in some other way (unzipping, ...). rpm (and hence yum) has no knowledge of any files not installed by an rpm package.
I am using CentOS 7.2.
I would like to install the latest version of rsync - rsync-3.1.2,
rsync-3.0.9 is on system, installed when installing mariadb with yum,
# rpm -qa |grep rsync
rsync-3.0.9-17.el7.x86_64
removing rsync-3.0.9 first,
# yum remove rsync
rsync and mariadb were removed together,
then,
installing rsync-3.1.2 from source code,
# wget https://download.samba.org/pub/rsync/src/rsync-3.1.2.tar.gz
# tar -zxvf rsync-3.1.2.tar.gz
# cd rsync-3.1.2
# ./configure
# make
# make install
then,
installing mariadb with yum again,
but rsync-3.0.9 will still be installed.
How can I solve the problem?
You can install rsync 3.1.2 from the Fedora 24 .rpm package:
wget http://dl.fedoraproject.org/pub/fedora/linux/releases/24/Everything/x86_64/os/Packages/r/rsync-3.1.2-2.fc24.x86_64.rpm
rpm -Uvh rsync-3.1.2-2.fc24.x86_64.rpm
(but that question doesn't really belong to stackoverflow)
You can install rsync 3.1.2 from the gf-plus repo. Just follow the steps below:
Install the gf-release package.
sudo rpm -Uvh http://mirror.ghettoforge.org/distributions/gf/el/7/gf/x86_64/gf-release-7-10.gf.el7.noarch.rpm
Upgrade rsync package from the gf-plus repo.
sudo yum install -y --enablerepo=gf-plus rsync
Check rsync version.
hash -r; rsync --version | awk 'NR==1 {print $3}'
If it prints 3.1.2, rsync is upgraded.
By default, only the gf repo is enabled, which claims that it "won't overwrite core distro packages". You can disable it:
sudo yum-config-manager --disable gf
(For command not found error, run sudo yum install -y yum-utils and try again.)
Or simply remove all the gf* repos by removing the gf-release package:
sudo yum remove -y gf-release
You either need to install all of your software using packages, or install all of your software from source. Trying to mix and match is going to lead to exactly the sort of problem you are experiencing here: the mariadb package has a dependency on rsync, but the package manager doesn't know anything about the files you have installed from source.
The correct way to solve this problem is to build your own rsync package that can then be installed with yum. You can start with the source package for your distribution and then modify it for 3.1.2. You may be able to utilize a more recent package (e.g., from Fedora) and rebuild it for your system.
You can find the source RPM for rsync-3.0.9 here, and there is some documentation that will hopefully help you get started here.
CentOS 7 has been out nearly a year now. Has anyone installed RedHawk on CentOS 7? I do not see binaries available on the RedHawk download page. Has anyone successfully built it from sources? Are there issues?
I also do not find RPMs for omniORB-servers or omniORB-devel. Has anyone succeeded in building these on CentOS7?
Terry, Ive built redhawk yum repositories for CentOS7 which you can find below however a few things to note:
As Ryan pointed out, currently redhawk only officially supports CentOS6 and Ubuntu, these rpms are not offically built and distributed by redhawksdr.org. However if you do have any issues with them or find any problems please feel free to feed this back to me.
These RPMs were originally built prior to Fedora packaing omniORB 4.2. To account for this, I built and packaged omniORB 4.1 for CentOS7 which is the same version redhawk uses on CentOS6. My omniORB41 package and EPEL's omniORB (v4.2) package conflict so you cannot have the epel package installed. I have not tested redhawk with omniORB 4.2 which is why I packaged the older 4.1 version.
You can find the 1.10.1 yum repository here:
http://yum.axiosengineering.com/redhawk/1.10.1/el7/x86_64/
I will hopefully soon update with 1.10.2
You will also need the dependency repository here:
http://yum.axiosengineering.com/redhawk-deps/1.10/el7/x86_64/
To install via yum, create the file /etc/yum.repos.d/redhawk_axios.repo
With the following text:
[redhawk]
name=UNOFFICIAL REDHAWK 1.10.1
baseurl=http://yum.axiosengineering.com/redhawk/1.10.1/el7/x86_64/
enabled=1
gpgcheck=0
[redhawk-deps]
name=UNOFFICIAL REDHAWK DEPS
baseurl=http://yum.axiosengineering.com/redhawk-deps/1.10/el7/x86_64/
enabled=1
gpgcheck=0
Then from a terminal:
sudo yum clean all
sudo yum install redhawk* frontendInterfaces* bulkioInterfaces* GPP-*
REDHAWK is only officially supported on CentOS 6 and Ubuntu 14.04. omniORB should now be in Fedora EPEL 7:
https://apps.fedoraproject.org/packages/omniORB
I recently installed Redhawk 2.3.0 on Centos 7.9 by following these instructions https://redhawksdr.org/2.3.0/manual/installation/
The exact commands I used:
mkdir ~/Documents/Redhawk
cd ~/Documents/Redhawk
sudo yum install https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
wget https://github.com/RedhawkSDR/redhawk/releases/download/2.3.0/redhawk-yum-2.3.0-el7-x86_64.tar.gz
tar xzvf redhawk-yum-2.3.0-el7-x86_64.tar.gz
cd redhawk-2.3.0-el7-x86_64
sudo yum install -y redhawk-release*.rpm
sudo nano /etc/yum.repos.d/redhawk.repo
Content of /etc/yum.repos.d/redhawk.repo:
[redhawk]
name=REDHAWK Repository
baseurl=file:///home/causer/Documents/Redhawk/redhawk-2.3.0-el7-x86_64
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhawk
Once the file is saved (ctrl+x, y), in the same directory as before:
sudo yum groupinstall "REDHAWK Runtime"
. /etc/profile.d/redhawk.sh
. /etc/profile.d/redhawk-sdrroot.sh
sudo /usr/sbin/usermod -a -G redhawk causer
sudo nano /etc/omniORB.cfg
sudo $OSSIEHOME/bin/cleanomni
sudo systemctl enable omniNames.service
sudo systemctl enable omniEvents.service
Copy redhawk.desktop to the desktop and run it (rpm -qpl on the redhawk-ide-xyz.rpm its near the bottom of the list)
sudo yum install java-1.8.0-openjdk-javadoc
Any installation or update using yum command I ended up error: Error: xz compression not available. On website I read that Python library is missing. When you try to install a library (sudo yum update pyliblzma) again failed with error. Do not know how? Thanks.
This problem comes if you installed a wrong epel release on your machine. If so, then you need to remove the epel release by
yum remove epel-release
Sometimes that is not enough, you need to remove the cache as well by:
rm -rf /var/cache/yum/x86_64/6/epel
Then you can install the epel-release again
yum -y install epel-release
You need install the EPEL repository by downloading the appropriate RPM package for your system and installing it. For example, for CentOS and Red Hat Enterprise Linux 6.x:
wget http://dl.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
sudo rpm -Uvh epel-release-6*.rpm
If you get a File Not Found error message when trying to download the package, the version number might have changed. You can access the latest version of the RPM installer from the Fedora EPEL wiki page. The wiki page also includes additional instructions for Red Hat Network subscribers who are installing the EPEL repository.
Finally, install the Python library:
yum install pyliblzma
This works perfecly in my CentOS 6.x.
I've found a solution on this page of stackexchange, working in CentOS 6.X:
https://unix.stackexchange.com/a/314756
sudo rpm -e epel-release-7-5.noarch
wget http://download.fedoraproject.org/pub/epel/6/x86_64/epel-release-6-8.noarch.rpm
sudo rpm -ivh epel-release-6-8.noarch.rpm
sudo yum clean all
sudo rpmdb -v --rebuilddb
sudo yum -y install libselinux-python
I was also suffering from this issue..
If you are installing packages but it is already available on your system.
Remove existing packages and then try to install new.
It will work properly...
I was able to solve this problem by installing pyliblzma using rpm instead of yum as yum is not working.
Find pyliblzma rpm package according to your architecture and install it using the command.
rpm -Uvh pyliblzma-version-release.architecture.rpm
I used the following command to install pyliblzma for my 64 bit Redhat 6.8 machine. Please check URL in the command and make changes accordingly.
rpm -Uvh http://dl.fedoraproject.org/pub/epel/6/x86_64/pyliblzma-0.5.3-3.el6.x86_64.rpm
In my case the issue was caused by missing modules in python's site-packages directory. Here's what I did:
$ rpm -Va
to get a list of all files belonging to all rpms that do not verify. I got a bunch of messages about missing modules:
missing /usr/lib64/python2.7/site-packages/...
Luckily, I had an identical CentOS version elsewhere with all these packages present, so I just copied them over and ran
$ rpmdb -v --rebuilddb
to rebuild rpm database.