Running a Laravel installation on a RedHat Enterprise Linux 7 server using PHP 7.1. I can see php-pgsql.x86_64 listed in the available yum packages, but it doesn't appear to be compatible with PHP 7.1 (and indeed is listed as version 5.4.16-43.el7_4.1).
On a lark, I tried installing it anyway and physically moved the pgsql.ini and pdo_pgsql.ini files from /etc/php.d into the relevant PHP 7.1 folder /etc/opt/rh/rh-php71/php.d/ (and did the same with the .so files they reference), but that returns an error indicating that the package couldn't be read (undefined symbol: file_globals_id in Unknown on line 0).
Has anyone managed to get PHP 7.1 talking to PostgreSQL on RHEL 7?
The sysadmin who originally created the server for me set me straight. The problem was I was looking in the wrong repository for the packages I needed for my particular PHP installation. Running the following two commands did the trick:
sudo yum install --disablerepo=* --enablerepo=rhui-REGION-rhel-server-rhscl rh-php71-php-odbc
sudo yum install --disablerepo=* --enablerepo=rhui-REGION-rhel-server-rhscl rh-php71-php-pgsql
We then added those two packages to the Ansible playbook so future generations would not suffer needlessly.
Related
From few days I am trying to install Agensgraph in Windows 10 with Agensbrowser. I got Agensgraph setup from Bitnine.net and also AgensBrowser in zip file having some files. I installed agensgraph easily on my windows but I don't know how to Install the agensbrowser eventhough i follow the Documentation for installation such as install java 1.8 rename file... but still don't understand, so Problems/questions I have:
I installed agensgraph from setup directly, Is there any other setting i have to do for it?
While Installing AgensBrowser I got these things from documentation which I don't understand that how to do that:
– Install DB for AgensBrowser management (Are they talking about PostgreSQL. already installed.)
– Create an AgensBrowser Admin account
How to setup its environment and how can i start with it??
please help me in that, i am struggling with it from many days.
System have Windows 10, PostgreSQL installed, Agensgraph setup Installed, java 1.8.
I am installing OpenProject 8.3.1 on my apache 2.4 CentOS7 WHM/CPanel VPS using packaged installation and I've run into the following problem:
When I run openproject configure right after installation process it goes well up until the line "No package mod_ssl available". Followed by "Error: Nothing to do". Openproject can't be accessed.
I'm using PostgreSQL and auto installation/configuration option. I've tried skipping all but the most essential options in configuration, to no help.
The mod_ssl unavailable bit is the most surprising, since after I run rpm -qa|grep mod_ssl I get "ea-apache24-mod_ssl-2.4.38-3.3.1.cpanel.x86_64" - meaning I in fact do have mod_ssl available.
It looks like you are using a non-standard CentOS edition with CPanel. I don't think OpenProject can be installed on such a distribution, because it seems to come with limitations as to what packages are available. The mod_ssl package you mention is the one originally distributed by the CentOS distribution.
Scenario: new installation of plesk 12.5 on centOS 7 into an OpenVZ container (proxmox):
Installing Plesk 12.5 I get the following error:
Exception: Failed to solve dependencies: 1:perl-JSON-XS-2.27-2.el6.x86_64 requires perl(:MODULE_COMPAT_5.10.1)
any tips?
You mention CentOS 7, but the package you are attempting to install (perl-JSON-XS-2.27-2.el6.x86_64) is for RedHat/CentOS 6, denoted by the el6 tag in the package name.
In any case, the issue appears to be due to not having the correct repositories available in yum to solve all necessary dependencies. Plesk maintains their own yum repositories to provide all of the necessary packages. Usually the install script will handle this for you (the install script is just a quick way to obtain the Plesk autoinstaller which should have the proper source repository configured).
I would suggest you examine the currently configured yum repositories in your container and make sure there are no conflicting repositories. Depending on the components you are installing with Plesk, it will want to manage nginx, apache, mysql, php, and some perl components so make sure you do not have yum repositories attempting to install related packages. Also, if you are indeed using CentOS 7, make sure you have no repositories attempting to install CentOS 6 packages. This bash one-liner should print out all the configured yum repository URLs so you can quickly scan if any are using the wrong version:
grep -re '^\(mirrorlist\|baseurl\)' /etc/yum.repos.d/
If you need further troubleshooting help, please include how you are attempting to install Plesk.
I have a CentOS 7.2 laptop. I have VirtualBox 5.0.x installed on it. Out of the box, it appears that I have Vagrant 1.7.2. Apparently this doesn't support VirtualBox 5.0.x, but it appears that version 1.8.1 does. What is the proper way to get access to 1.8.1? There is an installation rpm for 1.8.1 that I've downloaded, I can run this with "rpm", but do I have to do anything else before I do that?
Use Software Collections to get Vagrant 1.8.1 on CentOS: Vagrant 1.8 by Software Collections (the linked page contains instructions on how to do that). That will give you a build tested by the CentOS project.
As a sidenote: If you downloaded a standalone RPM package (presumably directly from the Vagrant project) and wish to install it, do it using the yum package manager, not rpm -- yum takes care of dependencies.
What's the syntax to get JBoss AS (latest, say 7.1.1) on CentOS (latest, 6.5)? I tried
su
yum install jbossas
but get the error
No package jbossas available.
Error: Nothing to do
Either I need to add some repos to yum or the package name is wrong. I understand I can just unzip the .zip into /bin/ per this post, but that would lead to messy/orphaned files in upgrades, so I'm looking for open, community repos that might have the jboss-as binaries.
So far my knowledge, you can not do this using yum at CentOS. Also, you can not upgrade from one version of JBoss into another one automatically(like any software or compiler do it automatically). Things are totally different here. For example JBoss 5.1 is having a totally different directory architecture compare to JBoss 7.1.