<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello,</p>
<p>Just had some issue with unexpected server behavior after reboot.
This node was powered off, so cluster was running fine with this
tomcat9 resource running on a different machine.</p>
<p>After powering on this node again, it briefly started tomcat
before joining the cluster and decided to stop it again. I'm not
sure why.</p>
<p><br>
</p>
<p>Here is the systemctl status tomcat9 on this host:</p>
<p>tomcat9.service - Apache Tomcat 9 Web Application Server<br>
Loaded: loaded (/lib/systemd/system/tomcat9.service;
disabled; vendor preset: enabled)<br>
Drop-In: /etc/systemd/system/tomcat9.service.d<br>
└─override.conf<br>
Active: inactive (dead)<br>
Docs: <a class="moz-txt-link-freetext" href="https://tomcat.apache.org/tomcat-9.0-doc/index.html">https://tomcat.apache.org/tomcat-9.0-doc/index.html</a><br>
<br>
</p>
<p>Feb 15 09:43:27 server tomcat9[1398]: Starting service [Catalina]<br>
Feb 15 09:43:27 server tomcat9[1398]: Starting Servlet engine:
[Apache Tomcat/9.0.43 (Debian)]<br>
Feb 15 09:43:27 server tomcat9[1398]: [...]<br>
Feb 15 09:43:29 server systemd[1]: Stopping Apache Tomcat 9 Web
Application Server...<br>
Feb 15 09:43:29 server systemd[1]: tomcat9.service: Succeeded.<br>
Feb 15 09:43:29 server systemd[1]: Stopped Apache Tomcat 9 Web
Application Server.<br>
Feb 15 09:43:29 server systemd[1]: tomcat9.service: Consumed
8.017s CPU time.</p>
<p>You can see it is disabled and should NOT be started with the
same, start/stop is under Corosync control</p>
<p><br>
</p>
<p>The systemd resource is defined like this:</p>
<p>primitive tomcat9 systemd:tomcat9.service \<br>
op start interval=0 timeout=120 \<br>
op stop interval=0 timeout=120 \<br>
op monitor interval=60 timeout=100<br>
</p>
<p><br>
</p>
<p>Any idea why this happened ?</p>
<p>Best regards, Adam.<br>
</p>
<div id="grammalecte_menu_main_button_shadow_host" style="width:
0px; height: 0px;"></div>
</body>
</html>