<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<font size="2" face="Courier 10 Pitch">Hi guys.<br>
<br>
I have a simple resource<br>
<br>
-> $ pcs resource config KEA-DHCP4<br>
Resource: KEA-DHCP4 (class=systemd type=kea-dhcp4.service)<br>
Meta Attributes: KEA-DHCP4-meta_attributes<br>
failure-timeout=25s<br>
Operations:<br>
monitor: KEA-DHCP4-monitor-interval-60s<br>
interval=60s timeout=100s<br>
start: KEA-DHCP4-start-interval-0s<br>
interval=0s timeout=100s<br>
stop: KEA-DHCP4-stop-interval-0s<br>
interval=0s timeout=100s<br>
<br>
which when cluster attempts to star it fails.<br>
I have not tried all the types of resources yet but it seems there
might be a pattern.<br>
When the resource is configured to connect to mysql then there is:<br>
<br>
INIT_FAIL failed to initialize Kea server: configuration error
using file '/etc/kea/kea-dhcp4.conf': Unable to open database:
Can't connect to server on '127.0.0.1' (115)<br>
<br>
I've only migrated to Centos 10, this still works on Centos 9 with
pacemaker-libs-2.1.10-2.el9<br>
c10 runs with pacemaker-libs-3.0.1-5.el10<br>
</font><font size="2" face="Courier 10 Pitch">kea-dhcp4.service
starts with _systemctl_ - no issue.</font><br>
<font size="2" face="Courier 10 Pitch"><br>
Do you know what might be the issue?<br>
<br>
thanks, L.</font>
</body>
</html>