[ClusterLabs] Fedora 31 - systemd based resources don't start

Maverick mvrk at sapo.pt
Mon Feb 17 12:35:24 EST 2020


Hi,

When i start my cluster, most of my systemd resources won't start:

Failed Resource Actions:
  * apache_stop_0 on boss1 'OCF_TIMEOUT' (198): call=82, status='Timed  
Out', exitreason='', last-rc-change='1970-01-01 01:00:54 +01:00',  
queued=29ms, exec=197799ms
  * openvpn_stop_0 on boss1 'OCF_TIMEOUT' (198): call=61,  
status='Timed Out', exitreason='', last-rc-change='1970-01-01 01:00:54  
+01:00', queued=1805ms, exec=198841ms

So everytime i reboot my node, i need to start the resources manually  
using systemd, for example:

systemd start apache

and then pcs resource cleanup

Resources configuration:

Clone: apache-clone
  Meta Attrs: maintenance=false
  Resource: apache (class=systemd type=httpd)
   Meta Attrs: maintenance=false
   Operations: monitor interval=60 timeout=100 (apache-monitor-interval-60)
               start interval=0s timeout=100 (apache-start-interval-0s)
               stop interval=0s timeout=100 (apache-stop-interval-0s)

Resource: openvpn (class=systemd type=openvpn-server at 01-server)
   Meta Attrs: maintenance=false
   Operations: monitor interval=60 timeout=100 (openvpn-monitor-interval-60)
               start interval=0s timeout=100 (openvpn-start-interval-0s)
               stop interval=0s timeout=100 (openvpn-stop-interval-0s)

Btw, if i try a debug-start / debug-stop the mentioned resources start  
and stop ok.

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20200217/cb844ac6/attachment-0001.html>


More information about the Users mailing list