[ClusterLabs] Systemd resource started on node after reboot before cluster is stable ?

Andrei Borzenkov arvidjaar at gmail.com
Wed Feb 15 06:16:39 EST 2023


On Wed, Feb 15, 2023 at 12:49 PM Adam Cecile <acecile at le-vert.net> wrote:
>
> Hello,
>
> 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.
>
> 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.
>
>
> Here is the systemctl status tomcat9 on this host:
>
> tomcat9.service - Apache Tomcat 9 Web Application Server
>      Loaded: loaded (/lib/systemd/system/tomcat9.service; disabled; vendor preset: enabled)
>     Drop-In: /etc/systemd/system/tomcat9.service.d
>              └─override.conf
>      Active: inactive (dead)
>        Docs: https://tomcat.apache.org/tomcat-9.0-doc/index.html
>
> Feb 15 09:43:27 server tomcat9[1398]: Starting service [Catalina]
> Feb 15 09:43:27 server tomcat9[1398]: Starting Servlet engine: [Apache Tomcat/9.0.43 (Debian)]
> Feb 15 09:43:27 server tomcat9[1398]: [...]
> Feb 15 09:43:29 server systemd[1]: Stopping Apache Tomcat 9 Web Application Server...
> Feb 15 09:43:29 server systemd[1]: tomcat9.service: Succeeded.
> Feb 15 09:43:29 server systemd[1]: Stopped Apache Tomcat 9 Web Application Server.
> Feb 15 09:43:29 server systemd[1]: tomcat9.service: Consumed 8.017s CPU time.
>
> You can see it is disabled and should NOT be started

"Disabled" in systemd just means that links in [Install] section are
not present. This unit may be started by explicit request, or by
explicit dependency like Wants or Requires in another unit. Check
"systemctl show -p WantedBy -p RequiredBy tomcat9.service".

> with the same, start/stop is under Corosync control
>
>
> The systemd resource is defined like this:
>
> primitive tomcat9 systemd:tomcat9.service \
>         op start interval=0 timeout=120 \
>         op stop interval=0 timeout=120 \
>         op monitor interval=60 timeout=100
>
>
> Any idea why this happened ?
>
> Best regards, Adam.
>
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
>
> ClusterLabs home: https://www.clusterlabs.org/


More information about the Users mailing list