CentOS 8 is almost 7GB large and doesn't fit on a 4.7GB DVD. So I downloaded the boot.iso file and tried to install it.
During installation I need to select "Installation Source". I can enter select "closest mirror" or enter an http(s) or ftp URL.
"closest mirror" directly returns with the error message: "Error setting up base repository".
I tried to enter the URL of a mirror für the full Centos 8 image, which is listed on the centos website. It says downloading package metadata. After waiting for 40 minutes I quit the installation. Of course I was connected to WiFi.
How can I proceed with the installation of Centos 8?
I successfully installed centos 8 using this source "http://mirror.myren.net.my/centos/8/BaseOS/x86_64/os/"
Try adjusting your mirror accordingly.
Refer below image for install screenshot.
Related
When I tried to install Postgres SQL(11/12/13) in my windows 10 home edition when it almost comes near to complete installation showing this error:
Problem Running Post-Install Step. Installation May Not Complete Correctly failed to start the database server.
enter image description here
I googled about this issue but no luck, some of post show the create net postgres user but in windows 10 home edition local user/group options not available.
please help on this issue?
I have gotten Eclipse 2020-06 installed under Windows 10 and have also gotten it to recognize and "update" my Project from Eclipse Oxygen.
I need to install Red Hat Tools and neither it nor installation of other Red Hat add ons is working. Everything fails with "unable to read repository".
For example, I have tried to install using both the Eclipse Marketplace and Help Install New Software for:
JBoss Tools, Code Ready Studio and I get:
Unable to read repository at https://devstudio.redhat.com/12/stable/composite/12.16.0/compositeContent.xml
Unable to read repository at https://download.jboss.org/jbosstools/oxygen/updates/content.xml
Unable to read repository at https://download.jboss.org/jbosstools/photon/updates/content.xml
Unable to read repository at https://download.jboss.org/jbosstools/2020-06/updates/content.xml
Connection to http://download.jboss.org/jbosstools/photon/staging/updates/central/4.16.0.Final/p2.index failed on Received fatal alert: internal_error. Retry attempt 0 started
All of the attemps show the following in the Errors log :
javax.net.ssl.SSLException: Received fatal alert: internal_error
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:129)
at java.base/sun.security.ssl.Alert.createSSLException(Alert.java:117)
When I am using Install New Software I get the above error as soon as I selet the (Red Hat related) Work With item.
I can reach the internet with the Eclipse "embedded" browser. In Install New Software I can select non-Red Hat packages and see all of the available modules. I have deleted the cache at p2\org.eclipse.equinox.p2.repository\cache and I have Removed and added back the Source for Red Hat Tools (as above).
My searches have resulted in numerous older posts with suggestions that a proxy is causing the problem but I don't see how that can be the case. This is failing on a home network with no proxy and the Windows 10 system Eclipse is running on does not have a proxy set up.
Can someone suggest why this is failing?
Thank you in advance.
Many thanks to howlger! I had a bad install of the JDK. I started fresh, installed AdoptOpenJDK's .msi, installed Eclipse and am finally able to install CodeReady Studio (includes Jboss Tools). Thanks again very much!
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 wanna to install openmotif22 on centos 7 but I get the message from installer “Sorry, this did not work. The file is not supported.”
Can you share with us the command you are using to perform the install as well as the exact package you are attempting to install.
Are you using the steps documented here:
https://centos.pkgs.org/7/puias-computational-x86_64/openmotif22-2.2.3-19.sdl7.x86_64.rpm.html
I try to install github desktop via chocolatey (vagrant provisioning) on my windows virtual machine. The installation process runs until the actual github installation. The error message looks like this:
Download of GitHubSetup.exe (663.49 KB) completed
WARNING: Ignoring checksums due to feature checksumFiles turned off or option --ignore-checksums set.
Installing github...
github has been installed.
Microsoft's ClickOnce framework is downloading and extracting the ~110
MB install files.
This may take several minutes or longer. Please wait...
The installation hangs at this point. I read about this issue at the official chocolatey webpage . How can I workaround this problem?