after running ansible for TrinityX 16 on Rocky 9.8, trix-diag shows not all services are available.

[hmg22]

After running into issues with Rocky 10, I am trying Rocky 9. This system has one head node, with only two networks: public and private. No infiniband, no management network. No OOD.

The first ansible step seems to go well

xxxxxx : ok=869 changed=453 unreachable=0 failed=0 skipped=672 rescued=0 ignored=10

I checked if the luna2 daemon was running, and it wasn't. So I started it without issue, but why did if fail the first time?

Running trix-diag gives:

[root@xxxxxx site]# trix-diag
Trinity Core
chronyd: active (running) since Thu 2026-09-10 11:05:52 IDT; 13min ago
named: active (running) since Thu 2026-09-10 11:05:54 IDT; 13min ago
dhcpd: failed (Result: exit-code) since Thu 2026-09-10 11:17:57 IDT; 1min 2s ago
mariadb: active (running) since Thu 2026-09-10 11:06:31 IDT; 12min ago
nfs-server: active (exited) since Thu 2026-09-10 11:04:10 IDT; 14min ago
nginx: active (running) since Thu 2026-09-10 11:09:13 IDT; 9min ago

Luna
luna2-daemon: active (running) since Thu 2026-09-10 11:17:56 IDT; 1min 2s ago
aria2c: failed (Result: exit-code) since Thu 2026-09-10 11:09:31 IDT; 9min ago

LDAP
slapd: Unit slapd.service could not be found.
sssd: active (running) since Thu 2026-09-10 11:06:08 IDT; 12min ago

Slurm
slurmctld: active (running) since Thu 2026-09-10 11:15:26 IDT; 3min 32s ago

Monitoring core
grafana-server: active (running) since Thu 2026-09-10 11:15:51 IDT; 3min 7s ago
prometheus-server: active (running) since Thu 2026-09-10 11:15:28 IDT; 3min 31s ago

Trinity OOD
httpd: Unit httpd.service could not be found.

I tried to start the dhcpd service but it fails.

journalctl -xeu dhcpd.service gave (names and IP address redacted):

Sep 10 11:20:27 xxxxxx dhcpd[79832]: No subnet declaration for enp2s0f0np0 (x.x.x.x).
Sep 10 11:20:27 xxxxxx dhcpd[79832]: ** Ignoring requests on enp2s0f0np0. If this is not what
Sep 10 11:20:27 xxxxxx dhcpd[79832]: you want, please write a subnet declaration
Sep 10 11:20:27 xxxxxx dhcpd[79832]: in your dhcpd.conf file for the network segment
Sep 10 11:20:27 xxxxxx dhcpd[79832]: to which interface enp2s0f0np0 is attached. **
Sep 10 11:20:27 xxxxxx dhcpd[79832]:
Sep 10 11:20:27 xxxxxx dhcpd[79832]:

That interface is the public facing interface. Should there be a subnet declaration for that?

And what about slapd and aria2c?

Thanks.

[Gio200023]

Hi hmg22,

this looks primarily like an interface-selection/configuration issue, rather than a requirement to serve DHCP on the public network.

DHCPD is attempting to use the public interface as well as the provisioning/private interface. Unless you intend to PXE/provision nodes from the public LAN, do not add a public subnet declaration; you can verify that the generated DHCP configuration/service is restricted to the private/provisioning interface and that all.yaml defines the head-node interfaces/networks accordingly.

The luna2-daemon initial failure may be a race issue during the first playbook run, but its journal output from that time would confirm it. SLAPD and HTTPD can be expected to be absent when the corresponding LDAP/OOD roles are not deployed; trix-diag currently reports those optional units unconditionally. aria2c needs its own service log/configuration checked, but it is separate from the DHCP failure.

Kind regards,
Giovanni

[hmg22]

Hi, thanks for the reply.

In the all.yml file there is a line:

"# DNS forwarders. These should normally point to your organization's DNS servers."

trix_dns_forwarders:

So I entered our institute's DNS machines (on the public network). Should I not do that? Is that what is causing the error?

Thanks

[Gio200023]

Hi hmg22,

The interfaces are declared in the all.yaml in the entries:
firewalld_public_interfaces: [ens3]
firewalld_trusted_interfaces: [ens6]

Can you confirm these are setup correctly?

Giovanni

[hmg22]

Hi, thanks for your reply.

Yes the two interfaces are correctly defined: the public interface is set to the external facing ethernet port,
and the internal interface is set to the other port that is attached to the private switch.