I'm running apache-tomcat-8.5.51 on RHEL 7.7 and are using a SysV init script to start/stop it. However, it seems that RHEL 7 doesn't use SysVinit to restart services after a reboot. Does anyone have the systemd/systemctl configuration for starting/stopping tomcat ? (And of course, RHEL7 stopped providing tomcat at tomcat7, not 8.)
Related
How to make installed geoserver 2.18 as windows service? Two yeas ago I have install it on windows server 2008 R2 and sometimes it stops (when my session closed, for example), which is not acceptable, it needs geoserver works all the time.
Install tomcat as a windows service and deploy the geoserver war to tomcat. Note you will generally get better performance on a Linux box.
I am currently using Kolla-ansible for deploying my OpenStack environment and I am running the Openstack Victoria version on CentOS Linux 8. Due to EOL of CentOS Linux 8 is no longer supported. I wanted to migrate now on CentOS stream8.
On the official website they have mentioned the following Note:
CentOS Linux 8 (as opposed to CentOS Stream 8) is no longer supported as a host OS. The Victoria release will in the future support both CentOS Linux 8 and CentOS Stream 8, and provide a route for migration.
My question is:
Has anyone done this migration (any worrisome issues)?
Any idea, are they going to provide a migration route soon because the above-mentioned note is there for around 3-4 months and they stopped supporting CentOS Linux 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.
can I setup WildFly 18 for automatic restart after a JVM crash?
We use the JNI interface for native applications and we has a periodicly crash JVM. Use full-ha and ha modes does't work. Аfter JVM-crash, we should manually start server.
WildFly AS is not able to restart itself after JVM crash. You can't configure this on the application server level.
Operating System should be able to monitor services and restart them after crashes.
If you are using linux based system, you can utilize systemctl manager. See following:
How to configure Systemd for starting WildFly
General information about Systemd and Systemctl
I am using JBOSS EAP 6.3.GA on CentOs with open JDK 6 64 bit.
Previously, I started the JBOSS in standalone mode and it was working well.
Now, I was trying to start JBOSS in domain mode with 1 server only. It was working fine but after 20-30 mintues it shutdown itself with no error printing in log file.
I am unable to find what causes the error.
Need help.