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.
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 have a google VM instance which was running flawlessly. It has Centos-7 and Plesk installed in it.
I just stopped it, upgraded machine type (to better CPU and RAM) and started it again. My server stopped responding at all. No websites are running, I can't connect to SSH & Google Cloud SDK Shell is unable to reach server. It says NETWORK ERROR, CONNECTION TIMED OUT. My all other instances works well.
I tried rebooting & resetting multiple times. Reading out stuff from internet since last 6 hours but for no luck. I also tried to clone disk of the instance and creating new instance with the cloned disk but for no luck. Same network connection issue. May be something in OS got corrupted? Please suggest. I have a number of websites hosted on the server which are down due to this. Thanks a lot in advance.
I took screenshot of my VM using Google Cloud Shell. It is as follows:
I connected with serial console which is as follows:
While creating a ticket with google, I found that they've posted some information under "Known Issues". I am pasting the whole stuff as there is no direct link to reach there. The symptoms they told were exactly what was happening to me:
Below is Known Issue Posted by Google:
Description:
We are experiencing an issue with Google Compute Engine instances running RHEL and CentOS 7 and 8. More details on this issue are available in the following article and bugs: https://access.redhat.com/solutions/5272311 https://bugzilla.redhat.com/show_bug.cgi?id=1861977 (RHEL 8) https://bugzilla.redhat.com/show_bug.cgi?id=1862045 (RHEL 7) Symptoms: Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart with errors messages referring to a combination of: "X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID", "FXSAVE_STATE" or "Find image based on IP". This issue affects instances with specific versions of the shim package installed. To find the currently installed shim version, use the following command: rpm -q shim-x64 Affected shim versions: CentOS 7: shim-x64-15-7.el7_9.x86_64 CentOS 8: shim-x64-15-13.el8.x86_64 RHEL 7: shim-x64-15-7.el7_8.x86_64 RHEL 8: shim-x64-15-14.el8_2.x86_64 Workaround: Do not update or reboot instances running RHEL or CentOS 7 and 8. If you are on an affected shim version, run yum downgrade shim\* grub2\* mokutil to downgrade to the correct version. This command may not work on CentOS 8. If you have already rebooted, you will need to attach the disk to another instance, chroot into the disk, then run the yum downgrade command. We will provide an update by Thursday, 2020-07-30 14:00 US/Pacific with current details.
Start time:
July 30, 2020 at 9:08:34 PM GMT+5
How to diagnose:
Instances running RHEL and CentOS 7 and 8 that run yum update may fail to boot after restart with errors messages referring to a combination of: "X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID", "FXSAVE_STATE" or "Find image based on IP". This issue affects instances with specific versions of the shim package installed. To find the currently installed shim version, use the following command: rpm -q shim-x64 Affected shim versions: CentOS 7: shim-x64-15-7.el7_9.x86_64 CentOS 8: shim-x64-15-13.el8.x86_64 RHEL 7: shim-x64-15-7.el7_8.x86_64 RHEL 8: shim-x64-15-14.el8_2.x86_64
Workaround:
Do not update or reboot instances running RHEL or CentOS 7 and 8. If you are on an affected shim version, run yum downgrade shim\* grub2\* mokutil to downgrade to the correct version. This command may not work on CentOS 8. If you have already rebooted, you will need to attach the disk to another instance, chroot into the disk, then run the yum downgrade command.
I have a dreamhost dedicated server and I'm getting a driver error when trying to use Postgresql. I followed the instructions here to update/install pgsql. I got the error in the screenshot below.
The text of the error is:
Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation:
The following packages have unmet dependencies:
postgresql : Depends: postgresql-9.1 but it is not going to be installed
postgresql-contrib : Depends: postgresql-contrib-9.1 but it is not going to be installed
E: Unable to correct problems, you have held broken packages.
If I run psql --version It says 9.1.23 is installed.
I'm not sure if everything is fine because of that or what. Also, the DB is on AWS and is version 10.5. Is that even going to be compatible?
The Ubuntu version on dreamhost is 12.04, which is no deprecated, so I doubt I'm going to be able to update the pgsql driver there. I don't have any experience with this stuff, and I've read some stuff, but don't want to just go running things as this is a production server that will be in use first thing Monday AM and I don't want to screw anything up.
Locally I'm using the pdo driver with pgsql.
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.
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.