I get this error while installing Postgres on my M1 MacBook Pro Problem running post-install step. Installation may not complete correctly The database cluster initialisation failed.
Related
I am currently self-studying postgreSQL from the ground up. I have spent the last 3 days trying to install PostgreSQL 14 and pgAdmin 4 into Mac OS Big Sur (version 11.6.2), but I kept getting the following errors:
1. When running pgAdmin 4, I encountered this message at the very beginning:
2. When installing postgreSQL 14 from EDB, at the very end of the installation process, I kept bumping into the error message: Problem running post-install step. Installation may not complete correctly Failed to start the database server. I tried following the solutions suggested in this thread, but I still get the same error in 1.
Question. Can someone please help me with the entire installment process to overcome these errors? Also, I am curious to know if pgAdmin 4's role to PostgreSQL 14 is the same as Rstudio's role to R or Anaconda to Python?
Question: Is it possible to run tensorflow-data-validation on MacOS with M1 chip?
Steps taken: I have created a conda environment (tfdv38) in which I have installed the Mac-optimized TensorFlow.
I have tried to install the package within the environment, this didn't work:
(tfdv38) ... % pip install tensorflow-data-validation
ERROR: Could not find a version that satisfies the requirement tensorflow-data-validation
ERROR: No matching distribution found for tensorflow-data-validation
Any suggestions?
At the moment unfortunately we don't support TFT, TFX and TFDV for M1 Mac, We are currently working on this issue, and will have an update in the fairly near future. In the meantime, some users have reported success with Rosetta. Other options include using a VM. We understand that neither of those is ideal.
You can also check on our Tensorflow Forum, same discussion is going on here.
TFDV is tested on the following 64-bit operating systems. Supported platforms :
macOS 10.14.6 (Mojave) or later
Ubuntu 16.04 or later
Windows 7 or later
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 Ubuntu 16.04 running and Nvidia drivers and CUDA and cud installed a long time ago. Yesterday the server was rebooted, and after I login through ssh, I wanted to check the GPU using nvidia-smi but failed.
The error message was "NVIDIA-SMI has failed because it couldn't communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running."
The server has:
Ubuntu 16.04
Nvidia k80c x4
CUDA 9.0
Has anyone faced this problem and can offer a possible solution? I don't really want to reinstall the driver as it could cause other problems.
This problem is eventually solved by re-installing the Nvidia GPU driver. The root cause of this error is because the server has shut down due to unstable power supply while running using the GPU.
I'm running into a segmentation fault when trying to get started using flatpak and flathub on Ubuntu on Windows 10. My Windows 10 setup is actually a VM running on a Windows 8.1 laptop, but I don't think that's the issue.
I was able to get flatpak installed, but when trying to access flathub it just immediately seg faults. On the flatpak.org website, they say that you can add the Flathub repository with this command:
$ flatpak remote-add --if-not-exists flathub https://dl.flathub.org/repo/flathub.flatpakrep
But that as admin results in the following error:
Segmentation fault (core dumped)
Can anybody with experience using flathub on Ubuntu 16.04.3 on Windows 10 explain how they got that to work? Thanks.