What I need to do to install varnish-4.1.3-beta1 in a CentOS 7?
Since I don't find the rpm in the repo.
You can compile varnish from source using the instructions found in the varnish documentation.
With the help of Lasse Karstensen from Varnish support, follows the rpm for installation:
https://jenkins.varnish-software.com/view/VC4/job/VC4-rpm-el7/
(more specific:
https://jenkins.varnish-software.com/view/VC4/job/VC4-rpm-el7/lastSuccessfulBuild/artifact/rpm-build/varnish-4.1/el7/ )
Installation Procedure:
Download all the files except the .src.rpm one.
Use: rpm -Uvh to install
Related
I want to install chromedriver in one of the AWS EC2 instance which is linux(Red Hat Enterprise Linux Server release 6.7 Santiago - 64 bit). While installing the chromedriver, we ran into issue due to missing packages. I could find the package here but this in turn requires many other packages. Using any other AMI is not an option.
Error is -
error while loading shared libraries libgconf-2.so.4 cannot open shared object file
I am using Ubuntu x64 and yum didn't work for me. But I found somebody mentioning simply use
$sudo apt install libgconf-2-4
worked for me to install the libgconf.
Please ask yum for the file, libgconf-2.so.4 : $ yum provides */libgconf-2.so.4
Install GConf2 : # yum install GConf2
Packages http://mirror.centos.org/centos/6.8/os/ ... and updates http://mirror.centos.org/centos/6.8/updates/
The chromedriver depends on the same packages / files as GConf2, and then some. Please see for yourself : $ ldd chromedriver , where 'chromedriver' is the unzipped executable.
EDIT :
Solution for the chromedriver issue : Install a chromedriver for RHEL 6, chromedriver-31.0.1650.63-1.el6.x86_64.rpm https://drive.google.com/file/d/0B7S255p3kFXNX1c0UWlGOWpZOHM/view?usp=sharing
Please download the package, and 1) cd Downloads/ 2) yum install chromedriver-31.0.1650.63-1.el6.x86_64.rpm ... and you have /usr/local/bin/chromedriver
P.S. : The EL6 chromedriver was built from the source package chromium-31.0.1650.63-1.el6.src.rpm
You might want to read this CentOS thread about your GLIBCXX_3.4.15. Especially apropos is this answer on the thread, especially the FAQ it references.
CentOS (which aims to be as compatible with RHEL as possible) is a curated LTS distribution (as is RHEL). You might find a version of chromedriver compiled for RHEL 6 in one of the many repositories. If not, you'll probably have to build it yourself.
When I tried install deluge on my CentOS 7.1 I was facing dependecy problems due to some el6 which are not meant for CentOS 7.1. So, I found this page:
https://gist.github.com/dasgoll/111f6f3364e2ab97bc08
His instructions:
Centos 7.1
yum -y install wget wget hxxp://li.nux.ro/download/nux/dextop/el7/x86_64/nux-dextop-release-0-5.el7.nux.noarch.rpm
rpm -ivh nux-dextop-release-0-5.el7.nux.noarch.rpm
yum -y install deluge-web
systemctl start deluge-web
systemctl stop firewalld
browse http://192.168.3.101:8112
check it
yum install deluge-console
And my question is: Why he installed "nux-dextop-release-0-5.el7.nux.noarch.rpm" from li.nux.ro (if I'm not wrong it's a repository, correct me if I'm)? Because I had this dependency problem earlier when I tried installing deluge. But when I used his instructions it resolved all the dependencies automatically for me. So does this rpm file he installed on the first place was for resolving dependencies? If not then how can one work around with dependencies while installing a piece of software/application. Than You in advance.
P.S. I asked the same question in comments there too. But I'm uncertain of receiving reply there (no offence for the guy/girl - dasgoll).
Third party package repos will often use a *-release package to contain both a yum repo definition and a rpm signing public key so that end users can install packages directly from the repo using yum instead of having to find and then download them one by one.
I am trying to install jpegoptim on a CentOS 6 server. I have downloaded and unpacked the package but when I try to run ./configure from the jpegoptim-1.3.0 directory I get an error that says:
"cannot find libjpeg or you have too old version (v6 or later required)."
I have checked and I have libjpeg-turbo install, which should supercede libjpeg. I have not been able to find anything on the net about this issue. What am I doing wrong?
Thanks,
Rob
The configure script is looking for jpeglib.h which is in the libjpeg-turbo-devel package.
You may want to use yum to help you with what you are looking for. The following may get you what you need:
yum search libjpeg
yum install libjpeg*
Note I have the epel repository installed on my system too. So if the above don't give you what you want, you may need to install the epel repository first.
So basically I'm trying to install APC, but I can't get pecl to work on Centos 5.8 i686
I have the latest stable releases of php-fpm, mysql, and nginx. Everything is working at 100%, everything is smooth. I'm running a live website with no problems. I just can't pecl to work.
yum install php-pear:
Most of the packages I'm trying to instal have dependency issues with php-common (whatever that is).
php-common = 5.1.6-32.el5 is needed
Much help is appreciated!
/usr/bin/pecl is available from php-pear package.
The dependency failures you got are stange. Probably because you have mixed installation of php-* 5.1 RPMs and php53-* 5.3 RPMs and get conflicts on devel files. You should do some clean up to keep only one set of RPMs for your target version, either 5.1 or 5.3.
You also have to install gcc, httpd-devel, php(53)-devel and finally php-pear to get phpize working.
Then you should be able to run pecl install apc
First of all assure you have your distro updated, you can do it with
yum update
Then check if you are not using any third-party repo, that contains this packages.
If you can, remove all the php packages with
yum remove php*
and try to install them again.
If you can't solve it, try the Fedora EPEL repositories which provides some updated packages.
All the commands needs be run by root.
My client had some developer write a small c++ command-line app to run on their Linux servers. On one of the servers (running Fedora 11), when I execute the app I get the following error:
error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
Obviously the first thing I did was
yum install libstdc++
But I get
Package libstdc++-4.4.1-2.fc11.x86_64 already installed and latest version
So the library already exists and is up-to-date. Usually to me these errors indicate a missing library. So where should I look next?
rpm hence the repo knows about shared library names and what provides them. So
yum install 'libstdc++.so.5'
wiil install whatever is necessary if the repo has it.
In your case it would fetch compat-libstdc++-33-3.2.3-66.i586.rpm and its 32-bit deps if you don't have them already because the binary you are trying to run is apparently 32-bit
libstdc++-4.4.1-2.fc11.x86_64 installs libstdc++.so.6. You need the compat-libstdc++-33-3.2.3-66.x86_64 package to get libstdc++.so.5. (Do not symlink! libstdc++.so.5 and libstdc++.so.6 are incompatible.)
yum install compat-libstdc++-33 solved this for me.
libstdc++.so.5 is a very old version of the standard c++ library.
Do a yum search libstdc++ , you'll have to install one of the compat-libstdc++ packages.
As stated by caf and aaron, running yum install compat-libstdc++-33 libstdc++.so.5 -y worked for me when I got a similar error.
The only catch I ran into was, I didn't have the correct repo checked out so I had to run yum-config-manager --enable rhel-7-server-optional-rpms to access the files. If you are using something other than RedHat 7 you will need to search for the correct repo.
You could always check if you have the correct repo by running yum provides libstdc++.so.5 first.
worked for me too on RedHat 7 : error was :
error while loading shared libraries: libstdc++.so.5: wrong ELF class: ELFCLASS32
The solution was :
yum install compat-libstdc++-33 libstdc++.so.5 -y
Have you checked that the package does install libstdc++.so.5 and not some other version? That's your most likely problem.