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.
Related
I'm building a pipeline on Azure DevOps with a Linux image as a base (ubuntu-latest). Here I'm installing PostgreSQL version 12 with PostGIS.
Here's what I install:
sudo apt-get install -y postgresql-12 postgresql-client-12 postgresql-12-postgis-3 postgresql-12-postgis-3-scripts
First I tried to install it without mentioning any version numbers, but then I got the error mentioned below and I followed recommendations to specifically do it like this.
Hence the specifically mentioned version numbers
No special additions, just a plain installation of Postgres.
Installation is going fine without any errors.
Then when I create my database and connect to it, I do CREATE EXTENSION POSTGIS; and I get this error:
psql:./create_tables.sql:3: ERROR: could not open extension control file "/usr/share/postgresql/14/extension/postgis.control": No such file or directory
I'm pulling my hair for some time now about this and I totally don't get where it gets that reference to a version 14 folder from. There is absolutely no version 14 installed.
I also tried to pull the Debian packages from the Postgres.org instead of the Ubuntu libraries, I tried to install PostGIS 2.5 and PostGIS 2.5 scripts packages. But whatever I do, I get the same result. Once I start the pipeline, the image gets built and Postgresql and PostGIS installed and then I get the same error as a result.
Did anyone have this same experience? Where could this library folder reference for version 14 come from?
EDIT 2022/05/21: I've added some checks to the scripts and when checking the version of PostgreSQL(via SELECT version(); ) it gives version 14 (!), which at least explains the error. Apparently version 14 indeed IS installed and runs on the default port 5432. Version 12 that is explicitly installed also runs, it runs on port 5433 (checked via cat /etc/postgresql/12/main/postgresql.conf ). I now explicitly start version 12 and connect in my scripts to port 5433, so I can continue, but I still wonder where that version 14 installation comes from.
Postgres 14 is pre-installed on the Microsoft Hosted agent for ubuntu-20
Reference:
https://github.com/actions/virtual-environments/blob/main/images/linux/Ubuntu2004-Readme.md#postgresql
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.
I am trying to install mongodb 4 on Ubuntu 15.10 but its giving me this error when I start mongod:
Failed to start mongod.service: Unit mongod.service not found
I followed this official installation guide:
https://docs.mongodb.com/manual/tutorial/install-mongodb-on-ubuntu/
There is no official installation instructions for Ubuntu 15.10
I was successfully able to install on Ubuntu 16 but I am getting issues on Ubuntu 15.10.
Since ubuntu 15 isn't officially supported, you might have installed either the version for ubuntu 14 or 16.
Ubuntu possibly upgraded the init system to upstart/systemd (around v15). It's possible that the mongo release for ubuntu 14 varies as in it's packaged for a different init system.
You could write your own init script and install it into /etc/init.d. Alternatively using process control systems like supervisor.
Your other option (probably better for security) is to get a new server and migrate there. It could be potentially done without downtime.
If Ubuntu 16 isn't working for you, and you need to go back in time to an earlier version, I would choose the previous Long Term Support version, so the last 14.x rather than 15.x.
You are correct in using Mongo 3.6 with Meteor, there are likely to be compatibility issues with 4.0
I am trying to install MongoDB on Windows 7 Enterprise (32bit) VM running in VirtualBox on Windows7 Ultimate 64bit.
The MongoD.exe start up reports a missing Microsoft Hotfix, KB2731284. I downloaded and installed the hot fix on the VM. The hotfix was not required on the Host PC.
Mongod.exe still reported it was not installed. Ran the hotfix a second time and it reported that it was already installed.
I tried uninstalling an reinstalling mongoDB, no luck.
Stuck, any ideas?
MongoDB.com lists stackoverflow as the support portal.
per SO
I think you can run MongoDb without applying the Hotfix, but I would not recommend it. In long time you may run into problems. They have included some fixes in MongoDB to workaround the problem.
On Windows 7 and Windows Server 2008 R2 when applying the hotfix you get a better file allocation performance what is relevant for MongoDB
So when using mongo 2.6.0 there is workaround implemented.
I am using centos 5.8 in xencenter , i need to upgrade to centos6.5.
i tried with yum update it will updated to centos 5.10 only,please any one help me.
Thanks,
Prasad
I am guessing that you are trying to update a virtual machine. If this is the case then you can try the following.
Boot your CentOS 5.8 VM using the CentOS6 ISO
On the initial screen press tab
when the boot command appears, append upgradeany
vmlinuz initrd=initrd.img upgradeany
When you pass the language and devices selections and the system is done examining the storage, you will be prompted if you want to upgrade an existing installation and be shown a drop down list of versions that were found.